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.4-rc6
Date: Tue, 29 Oct 2019 13:47:17 +0100 [thread overview]
Message-ID: <20191029124717.GA7805@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.4-rc6
Mostly virtiofs fixes, but also fixes a regression and couple of
longstanding data/metadata writeback ordering issues.
Thanks,
Miklos
----------------------------------------------------------------
Alan Somers (1):
fuse: Add changelog entries for protocols 7.1 - 7.8
Miklos Szeredi (5):
virtio-fs: don't show mount options
fuse: don't dereference req->args on finished request
fuse: don't advise readdirplus for negative lookup
fuse: flush dirty data/metadata before non-truncate setattr
fuse: truncate pending writes on O_TRUNC
Vasily Averin (1):
fuse: redundant get_fuse_inode() calls in fuse_writepages_fill()
Vivek Goyal (6):
virtio-fs: Change module name to virtiofs.ko
virtiofs: Do not end request in submission context
virtiofs: No need to check fpq->connected state
virtiofs: Set FR_SENT flag only after request has been sent
virtiofs: Count pending forgets as in_flight forgets
virtiofs: Retry request submission from worker context
zhengbin (1):
virtiofs: Remove set but not used variable 'fc'
---
fs/fuse/Makefile | 3 +-
fs/fuse/dev.c | 4 +-
fs/fuse/dir.c | 16 ++++-
fs/fuse/file.c | 14 ++--
fs/fuse/fuse_i.h | 4 ++
fs/fuse/inode.c | 4 ++
fs/fuse/virtio_fs.c | 169 +++++++++++++++++++++++++++++++---------------
include/uapi/linux/fuse.h | 37 ++++++++++
8 files changed, 186 insertions(+), 65 deletions(-)
next reply other threads:[~2019-10-29 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 12:47 Miklos Szeredi [this message]
2019-10-29 17:05 ` 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=20191029124717.GA7805@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®