From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+62be362ff074b84ca393@syzkaller.appspotmail.com>
Cc: kent.overstreet@linux.dev, kvm@vger.kernel.org,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, pbonzini@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] WARNING in srcu_check_nmi_safety
Date: Fri, 16 Aug 2024 11:23:43 -0700 [thread overview]
Message-ID: <Zr-ZL9X87N6XhE60@google.com> (raw)
In-Reply-To: <000000000000d258a006179e07df@google.com>
On Sat, May 04, 2024, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 3d25a941ea50 Merge tag 'block-6.9-20240503' of git://git.k..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1143ae60980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=45d8db3acdc1ccc6
> dashboard link: https://syzkaller.appspot.com/bug?extid=62be362ff074b84ca393
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: i386
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-3d25a941.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/49d9f26b0beb/vmlinux-3d25a941.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/d2c424c14fff/bzImage-3d25a941.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+62be362ff074b84ca393@syzkaller.appspotmail.com
See https://lore.kernel.org/all/Zr-Ydj8FBpiqmY_c@google.com for an explanation.
#syz invalid
prev parent reply other threads:[~2024-08-16 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 10:09 [syzbot] [bcachefs?] WARNING in srcu_check_nmi_safety syzbot
2024-08-16 18:23 ` Sean Christopherson [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=Zr-ZL9X87N6XhE60@google.com \
--to=seanjc@google.com \
--cc=kent.overstreet@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=syzbot+62be362ff074b84ca393@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).