Linux filesystem development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jan Kara <jack@suse.cz>, Al Viro <viro@zeniv.linux.org.uk>,
	David Howells <dhowells@redhat.com>,
	Aleksa Sarai <cyphar@cyphar.com>, Karel Zak <kzak@redhat.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC 2/3] fs: add vfs_cmd_create()
Date: Wed, 2 Aug 2023 10:02:33 +0200	[thread overview]
Message-ID: <20230802-nutzwert-evaluieren-4cb4b1184494@brauner> (raw)
In-Reply-To: <20230801154333.GC12035@lst.de>

On Tue, Aug 01, 2023 at 05:43:33PM +0200, Christoph Hellwig wrote:
> On Tue, Aug 01, 2023 at 03:09:01PM +0200, Christian Brauner wrote:
> > Split the steps to create a superblock into a tiny helper. This will
> > make the next patch easier to follow.
> > 
> > Signed-off-by: Christian Brauner <brauner@kernel.org>
> > ---
> >  fs/fsopen.c | 45 +++++++++++++++++++++++++++++++--------------
> >  1 file changed, 31 insertions(+), 14 deletions(-)
> > 
> > diff --git a/fs/fsopen.c b/fs/fsopen.c
> > index fc9d2d9fd234..af2ff05dcee5 100644
> > --- a/fs/fsopen.c
> > +++ b/fs/fsopen.c
> > @@ -209,6 +209,36 @@ SYSCALL_DEFINE3(fspick, int, dfd, const char __user *, path, unsigned int, flags
> >  	return ret;
> >  }
> >  
> > +static int vfs_cmd_create(struct fs_context *fc)
> > +{
> > +	struct super_block *sb;
> > +	int ret;
> > +
> > +	if (fc->phase != FS_CONTEXT_CREATE_PARAMS)
> > +		return -EBUSY;
> > +
> > +	if (!mount_capable(fc))
> > +		return -EPERM;
> > +
> > +	fc->phase = FS_CONTEXT_CREATING;
> > +
> > +	ret = vfs_get_tree(fc);
> > +	if (ret)
> > +		return ret;
> 
> The error handling here now fails to set FS_CONTEXT_FAILED.
> 
> Also at a very minimum I'd also want a helper for the reconfigure
> case to mirror this one.  But I think the whole sys_fsconfig and

That's acceptable.

  parent reply	other threads:[~2023-08-02  8:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 13:08 [PATCH RFC 0/3] fs: allow userspace to detect superblock reuse Christian Brauner
2023-08-01 13:09 ` [PATCH RFC 1/3] super: remove get_tree_single_reconf() Christian Brauner
2023-08-01 15:31   ` Christoph Hellwig
2023-08-02  7:20     ` Christian Brauner
2023-08-02 16:49   ` Jan Kara
2023-08-01 13:09 ` [PATCH RFC 2/3] fs: add vfs_cmd_create() Christian Brauner
2023-08-01 15:43   ` Christoph Hellwig
2023-08-01 15:48     ` Christoph Hellwig
2023-08-02  8:02     ` Christian Brauner [this message]
2023-08-02 17:01   ` Jan Kara
2023-08-02 17:13     ` Jan Kara
2023-08-01 13:09 ` [PATCH RFC 3/3] fs: add FSCONFIG_CMD_CREATE_EXCL Christian Brauner
2023-08-01 15:46   ` Christoph Hellwig
2023-08-02  7:38     ` Christian Brauner
2023-08-01 14:25 ` [PATCH RFC 0/3] fs: allow userspace to detect superblock reuse Josef Bacik
2023-08-02  7:49   ` Christian Brauner

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=20230802-nutzwert-evaluieren-4cb4b1184494@brauner \
    --to=brauner@kernel.org \
    --cc=cyphar@cyphar.com \
    --cc=dhowells@redhat.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=kzak@redhat.com \
    --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