From: Miklos Szeredi <miklos@szeredi.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] fuse update for 6.0
Date: Mon, 8 Aug 2022 14:35:28 +0200 [thread overview]
Message-ID: <YvEDEKQSOaDaFiWb@miu.piliscsaba.redhat.com> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git tags/fuse-update-6.0
- Fix an issue with reusing the bdi in case of block based filesystems
- Allow root (in init namespace) to access fuse filesystems in user
namespaces if expicitly enabled with a module param
- Misc fixes
Thanks,
Miklos
---
Daniil Lunev (2):
vfs: function to prevent re-use of block-device-based superblocks
fuse: retire block-device-based superblock on force unmount
Dave Marchevsky (1):
fuse: Add module param for CAP_SYS_ADMIN access bypassing allow_other
Deming Wang (2):
virtiofs: delete unused parameter for virtio_fs_cleanup_vqs
virtio_fs: Modify format for virtio_fs_direct_access
Jeffle Xu (1):
fuse: avoid unnecessary spinlock bump
Miklos Szeredi (4):
fuse: write inode in fuse_release()
fuse: fix deadlock between atomic O_TRUNC and page invalidation
fuse: limit nsec
fuse: ioctl: translate ENOSYS
Xie Yongji (1):
fuse: Remove the control interface for virtio-fs
---
Documentation/filesystems/fuse.rst | 29 +++++++++++++++++++++++-----
fs/fuse/control.c | 4 ++--
fs/fuse/dax.c | 2 +-
fs/fuse/dir.c | 16 +++++++++++++++-
fs/fuse/file.c | 39 +++++++++++++++++++++++++-------------
fs/fuse/inode.c | 16 ++++++++++++++--
fs/fuse/ioctl.c | 15 +++++++++++++--
fs/fuse/virtio_fs.c | 9 ++++-----
fs/super.c | 33 ++++++++++++++++++++++++++++++--
include/linux/fs.h | 2 ++
10 files changed, 132 insertions(+), 33 deletions(-)
next reply other threads:[~2022-08-08 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 12:35 Miklos Szeredi [this message]
2022-08-08 18:42 ` [GIT PULL] fuse update for 6.0 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=YvEDEKQSOaDaFiWb@miu.piliscsaba.redhat.com \
--to=miklos@szeredi.hu \
--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).