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.6-rc1
Date: Fri, 7 Feb 2020 16:34:01 +0100	[thread overview]
Message-ID: <20200207153401.GC7822@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.6-rc1

- Fix a regression introduced in v5.1 that triggers WARNINGs for some fuse
filesystems.

- Fix an xfstest failure.

- Allow overlayfs to be used on top of fuse/virtiofs.

- Code and documentation cleanups.

Thanks,
Miklos

----------------------------------------------------------------
Daniel W. S. Almeida (1):
      Documentation: filesystems: convert fuse to RST

Miklos Szeredi (2):
      fix up iter on short count in fuse_direct_io()
      fuse: don't overflow LLONG_MAX with end offset

Vivek Goyal (1):
      fuse: Support RENAME_WHITEOUT flag

zhengbin (1):
      fuse: use true,false for bool variable

---
 Documentation/filesystems/{fuse.txt => fuse.rst} | 163 ++++++++++-------------
 Documentation/filesystems/index.rst              |   1 +
 MAINTAINERS                                      |   2 +-
 fs/fuse/cuse.c                                   |   4 +-
 fs/fuse/dir.c                                    |   2 +-
 fs/fuse/file.c                                   |  21 ++-
 fs/fuse/inode.c                                  |  14 +-
 fs/fuse/readdir.c                                |   2 +-
 8 files changed, 104 insertions(+), 105 deletions(-)
 rename Documentation/filesystems/{fuse.txt => fuse.rst} (80%)

             reply	other threads:[~2020-02-07 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 15:34 Miklos Szeredi [this message]
2020-02-08  2:05 ` [GIT PULL] fuse fixes for 5.6-rc1 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=20200207153401.GC7822@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).