From: syzbot <syzbot+a3c8e9ac9f9d77240afd@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, boqun.feng@gmail.com,
bottaawesome633@gmail.com, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, longman@redhat.com,
mingo@redhat.com, peterz@infradead.org, rbrasga@uci.edu,
skhan@linuxfoundation.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, will@kernel.org
Subject: Re: [syzbot] [ext4?] WARNING: locking bug in ext4_ioctl
Date: Mon, 06 Jan 2025 23:48:03 -0800 [thread overview]
Message-ID: <677cdc33.050a0220.a40f5.0019.GAE@google.com> (raw)
In-Reply-To: <000000000000d1149605fd5b0c0d@google.com>
syzbot suspects this issue was fixed by commit:
commit d7fe143cb115076fed0126ad8cf5ba6c3e575e43
Author: Ahmed Ehab <bottaawesome633@gmail.com>
Date: Sat Aug 24 22:10:30 2024 +0000
locking/lockdep: Avoid creating new name string literals in lockdep_set_subclass()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16c9ffd8580000
start commit: e42b1a9a2557 Merge tag 'spi-fix-v6.12-rc5' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4aec7739e14231a7
dashboard link: https://syzkaller.appspot.com/bug?extid=a3c8e9ac9f9d77240afd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=123fef57980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1598eebb980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: locking/lockdep: Avoid creating new name string literals in lockdep_set_subclass()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-01-07 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 5:19 [syzbot] [ext4?] WARNING: locking bug in ext4_ioctl syzbot
2023-06-05 6:29 ` syzbot
2023-06-05 12:15 ` syzbot
2025-01-07 7:48 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-27 16:51 [PATCH] ext4: " Remington Brasga
2024-09-27 18:59 ` [syzbot] [ext4?] " syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=677cdc33.050a0220.a40f5.0019.GAE@google.com \
--to=syzbot+a3c8e9ac9f9d77240afd@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=boqun.feng@gmail.com \
--cc=bottaawesome633@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rbrasga@uci.edu \
--cc=skhan@linuxfoundation.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.