From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] work.mount - infrastructure
Date: Tue, 17 Sep 2019 02:41:01 +0100 [thread overview]
Message-ID: <20190917014101.GF1131@ZenIV.linux.org.uk> (raw)
Infrastructure bits of mount API conversions; the rest is
more of per-filesystem patches and it'll go in a separate pull
request. Requests, actually, since some are (thankfully) in
the individual filesystem trees now (a huge NFS pile, for example).
The following changes since commit d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1:
Linux 5.3-rc5 (2019-08-18 14:31:08 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.mount-base
for you to fetch changes up to 0f071004109d9c8de7023b9a64fa2ba3fa87cbed:
mtd: Provide fs_context-aware mount_mtd() replacement (2019-09-05 14:34:23 -0400)
----------------------------------------------------------------
Al Viro (1):
new helper: get_tree_keyed()
David Howells (2):
vfs: Create fs_context-aware mount_bdev() replacement
mtd: Provide fs_context-aware mount_mtd() replacement
Eric Biggers (1):
vfs: set fs_context::user_ns for reconfigure
drivers/mtd/mtdcore.h | 1 +
drivers/mtd/mtdsuper.c | 179 ++++++++++++++++++++++++++++++++++++++++++++-
fs/fs_context.c | 4 +-
fs/nfsd/nfsctl.c | 3 +-
fs/proc/root.c | 3 +-
fs/super.c | 104 ++++++++++++++++++++++++++
include/linux/fs_context.h | 12 ++-
include/linux/mtd/super.h | 3 +
ipc/mqueue.c | 3 +-
net/sunrpc/rpc_pipe.c | 3 +-
10 files changed, 301 insertions(+), 14 deletions(-)
next reply other threads:[~2019-09-17 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 1:41 Al Viro [this message]
2019-09-18 20:30 ` [git pull] work.mount - infrastructure pr-tracker-bot
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=20190917014101.GF1131@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).