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.15
Date: Tue, 7 Sep 2021 09:26:45 +0200 [thread overview]
Message-ID: <YTcUNWiS2+m705i7@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-5.15
- Allow mounting an active fuse device. Previously the fuse device would
always be mounted during initialization, and sharing a fuse superblock
was only possible through mount or namespace cloning
- Fix data flushing in syncfs (virtiofs only)
- Fix data flushing in copy_file_range()
- Fix a possible deadlock in atomic O_TRUNC
- Misc fixes and cleanups
The recent commit dates for the two head commits are due to a trival bug
fix being folded in.
Thanks,
Miklos
---
Miklos Szeredi (9):
fuse: fix use after free in fuse_read_interrupt()
fuse: name fs_context consistently
fuse: move option checking into fuse_fill_super()
fuse: move fget() to fuse_get_tree()
fuse: allow sharing existing sb
fuse: truncate pagecache on atomic_o_trunc
fuse: flush extending writes
fuse: wait for writepages in syncfs
fuse: remove unused arg in fuse_write_file_get()
---
fs/fuse/control.c | 10 +--
fs/fuse/dev.c | 4 +-
fs/fuse/file.c | 45 ++++++++----
fs/fuse/fuse_i.h | 20 ++++++
fs/fuse/inode.c | 203 ++++++++++++++++++++++++++++++++++++++--------------
fs/fuse/virtio_fs.c | 12 ++--
6 files changed, 214 insertions(+), 80 deletions(-)
next reply other threads:[~2021-09-07 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 7:26 Miklos Szeredi [this message]
2021-09-07 20:14 ` [GIT PULL] fuse update for 5.15 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=YTcUNWiS2+m705i7@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).