linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: miklos@szeredi.hu, viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	dhowells@redhat.com, anprice@redhat.com
Subject: [RFC PATCH 0/4] fuse: Convert to fs_context
Date: Tue, 19 Mar 2019 16:23:23 +0000	[thread overview]
Message-ID: <155301260319.7556.1326405089184672936.stgit@warthog.procyon.org.uk> (raw)


Hi Miklós,

Here's a set of patches that convert fuse to use mount API:

 (1) Provide a replacement for mount_bdev() that takes an fs_context to
     specify the parameters.

     I also put a block device pointer and block device file mode into the
     fs_context struct for use in the sget_fc() test and set functions.

 (2) Improve handling of fd-type parameters.

 (3) Convert fuse to implement the mount API interface.

 (4) Move as much of the subtype parameter handling into the fuse driver as
     possible.

These are on top of:

	http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=mount-api-viro

Thanks,
David
---
David Howells (4):
      vfs: Create fs_context-aware mount_bdev() replacement
      vfs: Make fs_parse() handle fs_param_is_fd-type params better
      fuse: Convert to mount API
      fuse: Move the subtype parameter into fuse


 fs/fs_context.c            |   14 --
 fs/fs_parser.c             |   15 ++
 fs/fuse/inode.c            |  289 +++++++++++++++++++++++++-------------------
 fs/super.c                 |  111 ++++++++++++++++-
 include/linux/fs_context.h |    7 +
 5 files changed, 291 insertions(+), 145 deletions(-)


             reply	other threads:[~2019-03-19 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 16:23 David Howells [this message]
2019-03-19 16:23 ` [RFC PATCH 1/4] vfs: Create fs_context-aware mount_bdev() replacement David Howells
2019-03-26 21:02   ` Andrew Price
2019-03-27 11:23   ` David Howells
2019-03-27 13:51     ` Andrew Price
2019-03-19 16:23 ` [RFC PATCH 2/4] vfs: Make fs_parse() handle fs_param_is_fd-type params better David Howells
2019-03-19 16:23 ` [RFC PATCH 3/4] fuse: Convert to mount API David Howells
2019-03-19 16:23 ` [RFC PATCH 4/4] fuse: Move the subtype parameter into fuse David Howells

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=155301260319.7556.1326405089184672936.stgit@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=anprice@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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).