From: syzbot <syzbot+02a127be2df04bdc5df0@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, fdmanana@suse.com,
josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, quwenruo.btrfs@gmx.com,
syzkaller-bugs@googlegroups.com, wqu@suse.com
Subject: Re: [syzbot] [btrfs?] BUG: sleeping function called from invalid context in getname_kernel
Date: Thu, 10 Oct 2024 06:02:05 -0700 [thread overview]
Message-ID: <6707d04d.050a0220.64b99.0018.GAE@google.com> (raw)
In-Reply-To: <670689a8.050a0220.67064.0045.GAE@google.com>
syzbot has bisected this issue to:
commit 94a5b169bf5c7c47d3b1af759cf70bf1ab236ddb
Author: Qu Wenruo <wqu@suse.com>
Date: Tue Sep 24 03:22:17 2024 +0000
btrfs: avoid unnecessary device path update for the same device
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17c96fd0580000
start commit: 33ce24234fca Add linux-next specific files for 20241008
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=14296fd0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10296fd0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4750ca93740b938d
dashboard link: https://syzkaller.appspot.com/bug?extid=02a127be2df04bdc5df0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=112f97d0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=101d4f9f980000
Reported-by: syzbot+02a127be2df04bdc5df0@syzkaller.appspotmail.com
Fixes: 94a5b169bf5c ("btrfs: avoid unnecessary device path update for the same device")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-10-10 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 13:48 [syzbot] [btrfs?] BUG: sleeping function called from invalid context in getname_kernel syzbot
2024-10-09 23:21 ` Qu Wenruo
2024-10-10 0:54 ` syzbot
2024-10-10 13:02 ` 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=6707d04d.050a0220.64b99.0018.GAE@google.com \
--to=syzbot+02a127be2df04bdc5df0@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wqu@suse.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