linux-fsdevel.vger.kernel.org archive mirror
 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 fixes for 5.8-rc6
Date: Fri, 17 Jul 2020 14:31:39 +0200	[thread overview]
Message-ID: <20200717123139.GE6171@miu.piliscsaba.redhat.com> (raw)

Hi Linus,

Please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git tags/fuse-fixes-5.8-rc6

Fix the following:

 - two regressions in this cycle caused by the conversion of writepage list
   to an rb_tree

 - two regressions in v5.4 cause by the conversion to the new mount API

 - saner behavior of fsconfig(2) for the reconfigure case

 - an ancient issue with FS_IOC_{GET,SET}FLAGS ioctls.


Thanks,
Miklos

----------------------------------------------------------------
Chirantan Ekbote (1):
      fuse: Fix parameter for FS_IOC_{GET,SET}FLAGS

Miklos Szeredi (6):
      fuse: move rb_erase() before tree_insert()
      fuse: fix warning in tree_insert() and clean up writepage insertion
      fuse: use ->reconfigure() instead of ->remount_fs()
      fuse: ignore 'data' argument of mount(..., MS_REMOUNT)
      fuse: reject options on reconfigure via fsconfig(2)
      fuse: clean up condition for writepage sending

Vasily Averin (1):
      fuse: don't ignore errors from fuse_writepages_fill()

---
 fs/fuse/file.c             | 132 ++++++++++++++++++++++++++-------------------
 fs/fuse/inode.c            |  19 +++++--
 fs/namespace.c             |   1 +
 include/linux/fs_context.h |   1 +
 4 files changed, 96 insertions(+), 57 deletions(-)

             reply	other threads:[~2020-07-17 12:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 12:31 Miklos Szeredi [this message]
2020-07-17 17:40 ` [GIT PULL] fuse fixes for 5.8-rc6 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=20200717123139.GE6171@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).