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-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] fuse update for 6.3
Date: Mon, 27 Feb 2023 17:23:04 +0100	[thread overview]
Message-ID: <Y/zYyN7NeLKusmSj@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.3

 - Fix regression in fileattr permission checking

 - Fix possible hang during PID namespace destruction

 - Add generic support for request extensions

 - Add supplementary group list extension

 - Add limited support for supplying supplementary groups in create
   requests

 - Documentation fixes

Thanks,
Miklos

---
Alexander Mikhalitsyn (1):
      fuse: add inode/permission checks to fileattr_get/fileattr_set

Eric W. Biederman (1):
      fuse: in fuse_flush only wait if someone wants the return code

Miklos Szeredi (2):
      fuse: add request extension
      fuse: optional supplementary group in create requests

Randy Dunlap (1):
      fuse: fix all W=1 kernel-doc warnings

---
 fs/fuse/cuse.c            |   2 +-
 fs/fuse/dev.c             |   4 +-
 fs/fuse/dir.c             | 126 +++++++++++++++++++++++++++++++++++-----------
 fs/fuse/file.c            |  91 +++++++++++++++++++++++----------
 fs/fuse/fuse_i.h          |   9 +++-
 fs/fuse/inode.c           |   4 +-
 fs/fuse/ioctl.c           |   6 +++
 include/uapi/linux/fuse.h |  45 ++++++++++++++++-
 8 files changed, 225 insertions(+), 62 deletions(-)

             reply	other threads:[~2023-02-27 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 16:23 Miklos Szeredi [this message]
2023-02-27 18:18 ` 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=Y/zYyN7NeLKusmSj@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®