mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] fuse update for 6.15
Date: Tue, 1 Apr 2025 13:02:35 +0200	[thread overview]
Message-ID: <CAJfpegsQDTYsEWHMK9skpNzUO=GA_DR7zGHftyO2sZH5wjaZLA@mail.gmail.com> (raw)

Hi Linus,

Please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git
tags/fuse-update-6.15

- Allow connection to server to time out (Joanne Koong)

- If server doesn't support creating a hard link, return EPERM rather
than ENOSYS (Matt Johnston)

- Allow file names longer than 1024 chars (Bernd Schubert)

- Fix a possible race if request on io_uring queue is interrupted
(Bernd Schubert)

- Misc fixes and cleanups

Commit 1dfe2a220e9c ("fuse: fix uring race condition for null
dereference of fc") in this queue has already been merged into
v6.14-final through Christian's tree (commit d9ecc77193ca).   For some
reason this causes a merge conflict, the resolution of which is to
just take the version from this pull (i.e. remove the atomic_set()).

Thanks,
Miklos
---

Bernd Schubert (3):
      fuse: {io-uring} Fix a possible req cancellation race
      fuse: Allocate only namelen buf memory in fuse_notify_
      fuse: Increase FUSE_NAME_MAX to PATH_MAX

Joanne Koong (4):
      fuse: add kernel-enforced timeout option for requests
      fuse: add default_request_timeout and max_request_timeout sysctls
      fuse: fix uring race condition for null dereference of fc
      fuse: remove unneeded atomic set in uring creation

Luis Henriques (1):
      fuse: removed unused function fuse_uring_create() from header

Matt Johnston (1):
      fuse: Return EPERM rather than ENOSYS from link()

Miklos Szeredi (1):
      fuse: optmize missing FUSE_LINK support

---
 Documentation/admin-guide/sysctl/fs.rst |  25 +++++
 fs/fuse/dev.c                           | 162 +++++++++++++++++++++++++++-----
 fs/fuse/dev_uring.c                     |  47 +++++++--
 fs/fuse/dev_uring_i.h                   |  18 ++--
 fs/fuse/dir.c                           |  11 ++-
 fs/fuse/fuse_dev_i.h                    |   4 +
 fs/fuse/fuse_i.h                        |  47 ++++++++-
 fs/fuse/inode.c                         |  51 +++++++++-
 fs/fuse/sysctl.c                        |  24 +++++
 include/uapi/linux/fuse.h               |  12 ++-
 10 files changed, 358 insertions(+), 43 deletions(-)

             reply	other threads:[~2025-04-01 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 11:02 Miklos Szeredi [this message]
2025-04-03  0:06 ` Linus Torvalds
2025-04-03  0:11 ` 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='CAJfpegsQDTYsEWHMK9skpNzUO=GA_DR7zGHftyO2sZH5wjaZLA@mail.gmail.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®