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.2
Date: Mon, 12 Dec 2022 12:10:44 +0100 [thread overview]
Message-ID: <Y5cMNDpL5digt1rJ@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.2
- Allow some write requests to proceed in parallel
- Fix a performance problem with allow_sys_admin_access
- Add a special kind of invalidation that doesn't immediately purge
submounts
- On revalidation treat the target of rename(RENAME_NOREPLACE) the same as
open(O_EXCL)
- Use type safe helpers for some mnt_userns transformations
- Misc cleanups
Thanks,
Miklos
---
Christian Brauner (1):
fuse: port to vfs{g,u}id_t and associated helpers
Dave Marchevsky (1):
fuse: Rearrange fuse_allow_current_process checks
Dharmendra Singh (1):
fuse: allow non-extending parallel direct writes on the same file
Fabio M. De Francesco (1):
fs/fuse: Replace kmap() with kmap_local_page()
Jann Horn (1):
fuse: Remove user_ns check for FUSE_DEV_IOC_CLONE
Jiachen Zhang (1):
fuse: always revalidate rename target dentry
Miklos Szeredi (1):
fuse: add "expire only" mode to FUSE_NOTIFY_INVAL_ENTRY
ye xingchen (1):
fuse: remove the unneeded result variable
---
fs/fuse/acl.c | 2 +-
fs/fuse/cuse.c | 5 +----
fs/fuse/dev.c | 7 +++----
fs/fuse/dir.c | 43 +++++++++++++++++++++++++------------------
fs/fuse/file.c | 43 ++++++++++++++++++++++++++++++++++++++++---
fs/fuse/fuse_i.h | 4 ++--
fs/fuse/readdir.c | 4 ++--
include/uapi/linux/fuse.h | 16 ++++++++++++++--
8 files changed, 88 insertions(+), 36 deletions(-)
next reply other threads:[~2022-12-12 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 11:10 Miklos Szeredi [this message]
2022-12-13 5:00 ` 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=Y5cMNDpL5digt1rJ@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
all inboxes | Powered by JetHome®