From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: viro@zeniv.linux.org.uk, jack@suse.cz, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: open the block device after allocation the super_block
Date: Wed, 26 Jul 2023 14:57:15 +0200 [thread overview]
Message-ID: <20230726-gurken-weltall-ddaa4e42fbdb@brauner> (raw)
In-Reply-To: <20230726125106.GA14306@lst.de>
On Wed, Jul 26, 2023 at 02:51:06PM +0200, Christoph Hellwig wrote:
> On Tue, Jul 25, 2023 at 06:32:05PM +0200, Christian Brauner wrote:
> > I've removed the references to bind mounts from the commit message.
> > I mentioned in [1] and [2] that this problem is really related to
> > superblocks at it's core. It's just that technically a bind-mount would
> > be created in the following scenario where two processes race to create
> > a superblock:
>
> I wanted to keep some of Jan's original logic. In the end a bind mount
> is just one of many reuses of a super block so I think your updated
> log is fine.
>
> Btw, it might make sense to place this on a separate branch, and Jan's
> block work will have to pull it in, and it might be good to not
> require the entire vfs misc tree to be pult in.
Ok, now on the vfs.super branch.
next prev parent reply other threads:[~2023-07-26 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 17:51 [PATCH] fs: open the block device after allocation the super_block Christoph Hellwig
2023-07-25 12:35 ` Christian Brauner
2023-07-25 16:32 ` Christian Brauner
2023-07-26 12:51 ` Christoph Hellwig
2023-07-26 12:57 ` Christian Brauner [this message]
2023-07-25 15:53 ` Christian Brauner
2023-08-15 14:43 ` Christian Brauner
2023-08-16 7:29 ` Christian Brauner
2023-08-16 21:39 ` Jan Kara
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=20230726-gurken-weltall-ddaa4e42fbdb@brauner \
--to=brauner@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).