From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot <syzbot+f5608de5d89cc0d998c7@syzkaller.appspotmail.com>,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in bd_register_pending_holders
Date: Sat, 11 Sep 2021 01:57:53 +0900 [thread overview]
Message-ID: <d4d71dc8-0373-b7a9-2a95-ba2d3c87f968@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <000000000000e272fb05cba51fe4@google.com>
Since commit dfbb3409b27fa42b in axboe/linux-block.git#block-5.15 breaks
"sb_writers#$N => &p->lock => major_names_lock" dependency chain,
I think that this dependency chain should be no longer possible.
#syz fix: block: genhd: don't call blkdev_show() with major_names_lock held
On 2021/09/10 23:42, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 27151f177827 Merge tag 'perf-tools-for-v5.15-2021-09-04' o..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=104612b3300000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ac2f9cc43f6b17e4
> dashboard link: https://syzkaller.appspot.com/bug?extid=f5608de5d89cc0d998c7
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+f5608de5d89cc0d998c7@syzkaller.appspotmail.com
next prev parent reply other threads:[~2021-09-10 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 14:42 [syzbot] possible deadlock in bd_register_pending_holders syzbot
2021-09-10 16:57 ` Tetsuo Handa [this message]
2021-09-20 17:10 ` Eric Dumazet
2021-09-21 7:13 ` Christoph Hellwig
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=d4d71dc8-0373-b7a9-2a95-ba2d3c87f968@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+f5608de5d89cc0d998c7@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).