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 5.2
Date: Tue, 14 May 2019 09:51:36 +0200 [thread overview]
Message-ID: <20190514075136.GA7850@veci.piliscsaba.redhat.com> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git tags/fuse-update-5.2
Add more caching controls for userspace filesystems to use, as well as bug
fixes and cleanups.
Thanks,
Miklos
---
Alan Somers (3):
fuse: document fuse_fsync_in.fsync_flags
fuse: fix changelog entry for protocol 7.12
fuse: fix changelog entry for protocol 7.9
David Howells (1):
fuse: Convert fusectl to use the new mount API
Ian Abbott (1):
fuse: Add ioctl flag for x32 compat ioctl
Kirill Smelkov (5):
fuse: convert printk -> pr_*
fuse: allow filesystems to have precise control over data cache
fuse: retrieve: cap requested size to negotiated max_write
fuse: require /dev/fuse reads to have enough buffer capacity
fuse: Add FOPEN_STREAM to use stream_open()
Liu Bo (1):
fuse: honor RLIMIT_FSIZE in fuse_file_fallocate
Miklos Szeredi (1):
fuse: fix writepages on 32bit
zhangliguang (1):
fuse: clean up fuse_alloc_inode
---
fs/fuse/control.c | 20 +++++++++++++++-----
fs/fuse/cuse.c | 13 +++++++------
fs/fuse/dev.c | 16 +++++++++++++---
fs/fuse/file.c | 22 ++++++++++++++++++----
fs/fuse/fuse_i.h | 7 +++++++
fs/fuse/inode.c | 23 ++++++++++++-----------
include/uapi/linux/fuse.h | 22 ++++++++++++++++++++--
7 files changed, 92 insertions(+), 31 deletions(-)
next reply other threads:[~2019-05-14 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 7:51 Miklos Szeredi [this message]
2019-05-14 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=20190514075136.GA7850@veci.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®