linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	syzbot <syzbot+f5608de5d89cc0d998c7@syzkaller.appspotmail.com>,
	axboe@kernel.dk, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	Song Liu <song@kernel.org>
Subject: Re: [syzbot] possible deadlock in bd_register_pending_holders
Date: Tue, 21 Sep 2021 08:13:15 +0100	[thread overview]
Message-ID: <YUmGC7CKhMj4qQg1@infradead.org> (raw)
In-Reply-To: <8431ea39-7ace-a601-419a-dca74e1db287@gmail.com>

On Mon, Sep 20, 2021 at 10:10:55AM -0700, Eric Dumazet wrote:
> Note that current kernels (which include dfbb3409b27fa42b)
> still hit this :
> 
> [    3.197383] ======================================================
> [    3.204253] WARNING: possible circular locking dependency detected
> [    3.211116] 5.15.0-dbx-DEV #16 Not tainted
> [    3.215907] ------------------------------------------------------
> [    3.222770] kinit/1 is trying to acquire lock:
> [    3.227900] ffffa09bc8971230 (&mddev->open_mutex){+.+.}-{3:3}, at: md_open+0xf3/0x150
> [    3.237803] 
>                but task is already holding lock:
> [    3.245020] ffffa09bcf003f18 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0xa2/0x580

This should be fixed by:

https://marc.info/?l=linux-raid&m=163049641806992&w=2

Song, what is the plan to get that into Linus' tree?

      reply	other threads:[~2021-09-21  7:13 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
2021-09-20 17:10   ` Eric Dumazet
2021-09-21  7:13     ` Christoph Hellwig [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=YUmGC7CKhMj4qQg1@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=song@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).