From: Hillf Danton <hdanton@sina.com>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: Ujwal Kundur <ujwal.kundur@gmail.com>,
axboe@kernel.dk, ming.lei@redhat.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+2e9e529ac0b319316453@syzkaller.appspotmail.com,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] block: prevent deadlock in del_gendisk()
Date: Tue, 5 Aug 2025 19:59:59 +0800 [thread overview]
Message-ID: <20250805120001.3990-1-hdanton@sina.com> (raw)
In-Reply-To: <e312219e-aa6c-a9a6-fa01-cf38435010be@huaweicloud.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 736 bytes --]
On Mon, 4 Aug 2025 15:51:48 +0800 Yu Kuai wrote:
> ÔÚ 2025/08/03 21:41, Ujwal Kundur дµÀ:
> > A potential unsafe locking scenario presents itself when
> > mutex_lock(&disk->open_mutex) is called with reader's lock held on
> > update_nr_hwq_lock:
> > CPU0 CPU1
> > ---- ----
> > rlock(&set->update_nr_hwq_lock)
> > lock(&nbd->config_lock);
> > lock(&set->update_nr_hwq_lock);
> > lock(&disk->open_mutex)
> >
> This problem is already fixed inside nbd by:
> 8b428f42f3ed ("nbd: fix lockdep deadlock warning")
>
Deadlock still exists [1].
[1] https://lore.kernel.org/lkml/6891742c.050a0220.7f033.001a.GAE@google.com/
next prev parent reply other threads:[~2025-08-05 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-03 13:41 Ujwal Kundur
2025-08-04 7:51 ` Yu Kuai
2025-08-05 11:59 ` Hillf Danton [this message]
2025-08-06 0:58 ` Yu Kuai
2025-08-06 15:17 ` Ujwal Kundur
2025-08-08 8:41 ` kernel test robot
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=20250805120001.3990-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=syzbot+2e9e529ac0b319316453@syzkaller.appspotmail.com \
--cc=ujwal.kundur@gmail.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®