From: syzbot <syzbot+a70e2ad0879f160b9217@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@kernel.org, mingo@redhat.com, peterz@infradead.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com,
will@kernel.org
Subject: Re: WARNING in close_fs_devices (3)
Date: Sun, 29 Nov 2020 08:52:08 -0800 [thread overview]
Message-ID: <000000000000d324e605b541b602@google.com> (raw)
In-Reply-To: <0000000000007e15b505b530766d@google.com>
syzbot has bisected this issue to:
commit 4d004099a668c41522242aa146a38cc4eb59cb1e
Author: Peter Zijlstra <peterz@infradead.org>
Date: Fri Oct 2 09:04:21 2020 +0000
lockdep: Fix lockdep recursion
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=178c99fd500000
start commit: 6174f052 Add linux-next specific files for 20201127
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=144c99fd500000
console output: https://syzkaller.appspot.com/x/log.txt?x=104c99fd500000
kernel config: https://syzkaller.appspot.com/x/.config?x=79c69cf2521bef9c
dashboard link: https://syzkaller.appspot.com/bug?extid=a70e2ad0879f160b9217
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11727795500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1793dcc9500000
Reported-by: syzbot+a70e2ad0879f160b9217@syzkaller.appspotmail.com
Fixes: 4d004099a668 ("lockdep: Fix lockdep recursion")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-11-29 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 20:17 WARNING in close_fs_devices (3) syzbot
2020-11-29 13:59 ` syzbot
2020-11-29 16:52 ` 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=000000000000d324e605b541b602@google.com \
--to=syzbot+a70e2ad0879f160b9217@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox