From: Greg Kurz <groug@kaod.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Vivek Goyal <vgoyal@redhat.com>,
virtio-fs@redhat.com, Greg Kurz <groug@kaod.org>
Subject: [PATCH 0/4] fuse: Some fixes for submounts
Date: Tue, 25 May 2021 17:02:26 +0200 [thread overview]
Message-ID: <20210525150230.157586-1-groug@kaod.org> (raw)
While working on adding syncfs() support in FUSE, I've hit some severe
bugs with submounts (a crash and an infinite loop). The fix for the
crash is straightforward (patch 1), but the fix for the infinite loop
is more invasive : as suggested by Miklos, a simple bug fix is applied
first (patch 2) and the final fix (patch 3) is applied on top.
Greg Kurz (4):
fuse: Fix crash in fuse_dentry_automount() error path
fuse: Fix infinite loop in sget_fc()
fuse: Call vfs_get_tree() for submounts
fuse: Make fuse_fill_super_submount() static
fs/fuse/dir.c | 46 ++++++++++---------------------------------
fs/fuse/fuse_i.h | 9 +++------
fs/fuse/inode.c | 48 +++++++++++++++++++++++++++++++++++++++++++--
fs/fuse/virtio_fs.c | 3 +++
4 files changed, 62 insertions(+), 44 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-25 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 15:02 Greg Kurz [this message]
2021-05-25 15:02 ` [PATCH 1/4] fuse: Fix crash in fuse_dentry_automount() error path Greg Kurz
2021-05-27 9:51 ` [Virtio-fs] " Max Reitz
2021-05-25 15:02 ` [PATCH 2/4] fuse: Fix infinite loop in sget_fc() Greg Kurz
2021-05-27 10:08 ` [Virtio-fs] " Max Reitz
2021-05-27 12:31 ` Greg Kurz
2021-05-25 15:02 ` [PATCH 3/4] fuse: Call vfs_get_tree() for submounts Greg Kurz
2021-05-27 13:24 ` [Virtio-fs] " Max Reitz
2021-06-03 7:34 ` Greg Kurz
2021-05-25 15:02 ` [PATCH 4/4] fuse: Make fuse_fill_super_submount() static Greg Kurz
2021-05-27 13:28 ` [Virtio-fs] " Max Reitz
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=20210525150230.157586-1-groug@kaod.org \
--to=groug@kaod.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=vgoyal@redhat.com \
--cc=virtio-fs@redhat.com \
/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).