From: Miklos Szeredi <miklos@szeredi.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: [GIT PULL] fuse update for 4.17
Date: Mon, 16 Apr 2018 11:49:20 +0200 [thread overview]
Message-ID: <20180416094920.GE19579@veci.piliscsaba.redhat.com> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
Late pull request, sorry. I just totally forgot about it, probably because fuse
updates are so rare these days (hoping to get back to regular fuse updates once
overlayfs is "finished").
This contains a few fixes and minor improvements, but the most interesting part
is user namespace support, mostly done by Eric Biederman. This doesn't yet
enable unprivileged mounting of fuse filesystems, but that's now a really simple
step, since all support for that should be in place.
Thanks,
Miklos
---
Eric W. Biederman (3):
fuse: Remove the buggy retranslation of pids in fuse_dev_do_read
fuse: Fail all requests with invalid uids or gids
fuse: Support fuse filesystems outside of init_user_ns
Miklos Szeredi (4):
fuse: atomic_o_trunc should truncate pagecache
fuse: honor AT_STATX_DONT_SYNC
fuse: honor AT_STATX_FORCE_SYNC
fuse: add writeback documentation
Seth Forshee (1):
fuse: Restrict allow_other to the superblock's namespace or a descendant
Szymon Lukasz (1):
fuse: return -ECONNABORTED on /dev/fuse read after abort
---
Documentation/filesystems/fuse-io.txt | 38 +++++++++++++++++++++++++++++
fs/fuse/acl.c | 4 ++--
fs/fuse/control.c | 2 +-
fs/fuse/cuse.c | 11 ++++++---
fs/fuse/dev.c | 40 +++++++++++++++----------------
fs/fuse/dir.c | 45 +++++++++++++++++++++++++----------
fs/fuse/fuse_i.h | 14 +++++++++--
fs/fuse/inode.c | 40 +++++++++++++++++++------------
include/uapi/linux/fuse.h | 7 +++++-
kernel/user_namespace.c | 1 +
10 files changed, 145 insertions(+), 57 deletions(-)
create mode 100644 Documentation/filesystems/fuse-io.txt
reply other threads:[~2018-04-16 9:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180416094920.GE19579@veci.piliscsaba.redhat.com \
--to=miklos@szeredi.hu \
--cc=ebiederm@xmission.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.