From: Christoph Hellwig <hch@infradead.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: viro@zeniv.linux.org.uk, hch@infradead.org,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yukuai3@huawei.com,
yi.zhang@huawei.com
Subject: Re: [PATCH] fs: fix possible inconsistent mount device
Date: Fri, 12 Aug 2022 23:48:18 -0700 [thread overview]
Message-ID: <YvdJMj5hNem2PMVh@infradead.org> (raw)
In-Reply-To: <20220813060848.1457301-1-yukuai1@huaweicloud.com>
On Sat, Aug 13, 2022 at 02:08:48PM +0800, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@huawei.com>
>
> If device support rename, for example dm, following concurrent scenario
> is possible:
The fix is easy: don't rename mounted block device, and even
bettersimply don't rename them at all, which is just causing huge
amounts of pain.
next prev parent reply other threads:[~2022-08-13 6:48 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 [this message]
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
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=YvdJMj5hNem2PMVh@infradead.org \
--to=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=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;
as well as URLs for NNTP newsgroup(s).