From: syzbot <syzbot+934ebb67352c8a490bf3@syzkaller.appspotmail.com>
To: axboe@kernel.dk, cgroups@vger.kernel.org, hdanton@sina.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
ming.lei@redhat.com, syzkaller-bugs@googlegroups.com,
tj@kernel.org
Subject: Re: [syzbot] possible deadlock in throtl_pending_timer_fn
Date: Fri, 29 Jul 2022 20:25:08 -0700 [thread overview]
Message-ID: <0000000000004e96a405e4fd5051@google.com> (raw)
In-Reply-To: <000000000000921fd405db62096a@google.com>
syzbot has bisected this issue to:
commit 0a9a25ca78437b39e691bcc3dc8240455b803d8d
Author: Ming Lei <ming.lei@redhat.com>
Date: Fri Mar 18 13:01:43 2022 +0000
block: let blkcg_gq grab request queue's refcnt
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16c3cfc2080000
start commit: cb71b93c2dc3 Add linux-next specific files for 20220628
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=15c3cfc2080000
console output: https://syzkaller.appspot.com/x/log.txt?x=11c3cfc2080000
kernel config: https://syzkaller.appspot.com/x/.config?x=badbc1adb2d582eb
dashboard link: https://syzkaller.appspot.com/bug?extid=934ebb67352c8a490bf3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17713dee080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15d24952080000
Reported-by: syzbot+934ebb67352c8a490bf3@syzkaller.appspotmail.com
Fixes: 0a9a25ca7843 ("block: let blkcg_gq grab request queue's refcnt")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-07-30 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 21:23 [syzbot] possible deadlock in throtl_pending_timer_fn syzbot
2022-03-30 2:52 ` Ming Lei
2022-03-30 2:52 ` syzbot
2022-03-30 3:01 ` Ming Lei
2022-07-29 23:32 ` syzbot
2022-07-30 3:25 ` syzbot [this message]
2022-07-30 11:17 ` Ming Lei
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=0000000000004e96a405e4fd5051@google.com \
--to=syzbot+934ebb67352c8a490bf3@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=hdanton@sina.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).