From: Yu Kuai <yukuai1@huaweicloud.com>
To: Christoph Hellwig <hch@infradead.org>, Yu Kuai <yukuai1@huaweicloud.com>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] fs: fix possible inconsistent mount device
Date: Fri, 2 Sep 2022 14:09:58 +0800 [thread overview]
Message-ID: <79effa0e-7ffe-4275-cf36-01fd3d0615b9@huaweicloud.com> (raw)
In-Reply-To: <YvdPlDPX82NsC6/d@infradead.org>
Hi, Christoph!
在 2022/08/13 15:15, Christoph Hellwig 写道:
> On Sat, Aug 13, 2022 at 03:09:58PM +0800, Yu Kuai wrote:
>> Thanks for your reply. Do you think it's better to remove the rename
>> support from dm? Or it's better to add such limit?
>
> It will probably be hard to entirely remove it. But documentation
> and a rate limited warning discouraging it seems like a good idea.
> .
>
I just found that not just rename, mount concurrent with device
remove/create can trigger this problem as well:
t1: t2
// create dm-0 with name test1
// mount /dev/mapper/test1
mount_bdev
blkdev_get_by_path
lookup_bdev
// remove dm-0
// create dm-0 with different name test2
blkdev_get_by_dev
// succeed
Do you think it's ok to add such checking to prevent this problem?
Thanks,
Kuai
prev parent reply other threads:[~2022-09-02 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 6:08 [PATCH] fs: fix possible inconsistent mount device Yu Kuai
2022-08-13 6:48 ` Christoph Hellwig
2022-08-13 7:09 ` Yu Kuai
2022-08-13 7:15 ` Christoph Hellwig
2022-08-13 7:25 ` Yu Kuai
2022-09-02 6:09 ` Yu Kuai [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=79effa0e-7ffe-4275-cf36-01fd3d0615b9@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--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).