From: syzbot <syzbot+8d7226784b8fcb4c9d04@syzkaller.appspotmail.com>
To: anton.ivanov@cambridgegreys.com, axboe@kernel.dk, bp@alien8.de,
dave.hansen@linux.intel.com, hch@lst.de, hpa@zytor.com,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, martin.petersen@oracle.com,
mingo@redhat.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: [syzbot] [bcachefs?] WARNING: locking bug in rcu_pending_exit
Date: Sun, 01 Dec 2024 12:03:05 -0800 [thread overview]
Message-ID: <674cc0f9.050a0220.48a03.0012.GAE@google.com> (raw)
In-Reply-To: <6716e2ac.050a0220.1e4b4d.0064.GAE@google.com>
syzbot has bisected this issue to:
commit 5db755fbb1a0de4a4cfd5d5edfaa19853b9c56e6
Author: Christoph Hellwig <hch@lst.de>
Date: Fri May 31 07:47:56 2024 +0000
ubd: refactor the interrupt handler
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1739bf78580000
start commit: 2ba9f676d0a2 Merge tag 'drm-next-2024-11-29' of https://gi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14b9bf78580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10b9bf78580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a857d0dac7fee57c
dashboard link: https://syzkaller.appspot.com/bug?extid=8d7226784b8fcb4c9d04
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1037f9e8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=155d1d30580000
Reported-by: syzbot+8d7226784b8fcb4c9d04@syzkaller.appspotmail.com
Fixes: 5db755fbb1a0 ("ubd: refactor the interrupt handler")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-12-01 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 23:24 [syzbot] [bcachefs?] WARNING: locking bug in rcu_pending_exit syzbot
2024-11-30 21:47 ` syzbot
2024-12-01 20:03 ` syzbot [this message]
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=674cc0f9.050a0220.48a03.0012.GAE@google.com \
--to=syzbot+8d7226784b8fcb4c9d04@syzkaller.appspotmail.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox