From: syzbot <syzbot+c2b68bdf76e442836443@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, brauner@kernel.org, bvanassche@acm.org,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ext4?] general protection fault in ep_poll_callback
Date: Fri, 21 Jul 2023 02:30:37 -0700 [thread overview]
Message-ID: <000000000000d96eec0600fbea8f@google.com> (raw)
In-Reply-To: <000000000000c11ed40600e994b1@google.com>
syzbot has bisected this issue to:
commit a0b0fd53e1e67639b303b15939b9c653dbe7a8c4
Author: Bart Van Assche <bvanassche@acm.org>
Date: Thu Feb 14 23:00:46 2019 +0000
locking/lockdep: Free lock classes that are no longer in use
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16c0c84ea80000
start commit: bfa3037d8280 Merge tag 'fuse-update-6.5' of git://git.kern..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=15c0c84ea80000
console output: https://syzkaller.appspot.com/x/log.txt?x=11c0c84ea80000
kernel config: https://syzkaller.appspot.com/x/.config?x=27e33fd2346a54b
dashboard link: https://syzkaller.appspot.com/bug?extid=c2b68bdf76e442836443
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=111c904ea80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=116b0faaa80000
Reported-by: syzbot+c2b68bdf76e442836443@syzkaller.appspotmail.com
Fixes: a0b0fd53e1e6 ("locking/lockdep: Free lock classes that are no longer in use")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-21 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 11:38 [syzbot] [ext4?] general protection fault in ep_poll_callback syzbot
2023-07-21 9:30 ` syzbot [this message]
2023-07-21 9:47 ` Aleksandr Nogikh
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=000000000000d96eec0600fbea8f@google.com \
--to=syzbot+c2b68bdf76e442836443@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=bvanassche@acm.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox