From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "yukuai3@huawei.com" <yukuai3@huawei.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"yi.zhang@huawei.com" <yi.zhang@huawei.com>
Subject: Re: [PATCH RESEND] blk-mq: fix possible creation failure for 'debugfs_dir'
Date: Wed, 20 Apr 2022 03:40:02 +0000 [thread overview]
Message-ID: <97c78b6cbb95c2e63e2ef70a8901360f4ed23dc3.camel@intel.com> (raw)
In-Reply-To: <20220415035607.1836495-1-yukuai3@huawei.com>
On Fri, 2022-04-15 at 11:56 +0800, Yu Kuai wrote:
> 'q->debugfs_dir' is created in blk_register_queue(), however, it's not
> removed in blk_unregister_queue() and is delayed to blk_release_queue().
> Thus it's possible that del_gendisk() is done and blk_release_queue()
> is not called yet, and in the mean time blk_register_queue() is called
> for the new device with the same name. In this case, kernel will
> compalin about creation failure for 'debugfs_dir' like following:
>
> debugfs: Directory 'nullb1' with parent 'block' already present!
>
> Fix the problem by moving forward the removal of 'debgfs_dir' to
> blk_unregister_queue().
>
> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
Looks like I'm late to the party, but for what its worth:
Tested-by: Dan Williams <dan.j.williams@intel.com>
Thanks!
prev parent reply other threads:[~2022-04-20 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 3:56 [PATCH RESEND] blk-mq: fix possible creation failure for 'debugfs_dir' Yu Kuai
2022-04-20 2:10 ` Jens Axboe
2022-04-20 3:40 ` Williams, Dan J [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=97c78b6cbb95c2e63e2ef70a8901360f4ed23dc3.camel@intel.com \
--to=dan.j.williams@intel.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yi.zhang@huawei.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;
as well as URLs for NNTP newsgroup(s).