From: syzbot <[email protected]>
To: [email protected], [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [syzbot] WARNING: still has locks held in io_sq_thread
Date: Mon, 29 Mar 2021 11:00:05 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
syzbot has bisected this issue to:
commit c8cc7e853192d520ab6a5957f5081034103587ae
Author: Peter Zijlstra <[email protected]>
Date: Tue Feb 9 08:30:03 2021 +0000
lockdep: Noinstr annotate warn_bogus_irq_restore()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=152deb3ad00000
start commit: 81b1d39f Merge tag '5.12-rc4-smb3' of git://git.samba.org/..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=172deb3ad00000
console output: https://syzkaller.appspot.com/x/log.txt?x=132deb3ad00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d4e9addca54f3b44
dashboard link: https://syzkaller.appspot.com/bug?extid=796d767eb376810256f5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17d06ddcd00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=150764bed00000
Reported-by: [email protected]
Fixes: c8cc7e853192 ("lockdep: Noinstr annotate warn_bogus_irq_restore()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-03-29 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 7:34 [syzbot] WARNING: still has locks held in io_sq_thread syzbot
2021-03-29 12:54 ` Jens Axboe
2021-03-29 13:29 ` syzbot
2021-03-29 13:30 ` Jens Axboe
2021-03-29 18:00 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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