Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Jens Axboe <axboe@kernel.dk>
To:     yukuai3@huawei.com
Cc:     linux-block@vger.kernel.org, yi.zhang@huawei.com,
        linux-kernel@vger.kernel.org
In-Reply-To: <20220415035607.1836495-1-yukuai3@huawei.com>
References: <20220415035607.1836495-1-yukuai3@huawei.com>
Subject: Re: [PATCH RESEND] blk-mq: fix possible creation failure for 'debugfs_dir'
Message-Id: <165042064016.532249.4832316049346088891.b4-ty@kernel.dk>
Date:   Tue, 19 Apr 2022 20:10:40 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 15 Apr 2022 11:56:07 +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:
> 
> [...]

Applied, thanks!

[1/1] blk-mq: fix possible creation failure for 'debugfs_dir'
      commit: a87c29e1a85e64b28445bb1e80505230bf2e3b4b

Best regards,
-- 
Jens Axboe