From: Vivek Goyal <vgoyal@redhat.com>
To: linux-fsdevel@vger.kernel.org, miklos@szeredi.hu
Cc: virtio-fs@redhat.com, vgoyal@redhat.com
Subject: [Virtio-fs] [PATCH v3 0/6] fuse: Implement FUSE_HANDLE_KILLPRIV_V2 and enable SB_NOSEC
Date: Fri, 9 Oct 2020 14:15:06 -0400 [thread overview]
Message-ID: <20201009181512.65496-1-vgoyal@redhat.com> (raw)
Hi All,
Please find attached V3 of the patches to enable SB_NOSEC for fuse. I
posted V1 and V2 here.
v2:
https://lore.kernel.org/linux-fsdevel/20200916161737.38028-1-vgoyal@redhat.com/
v1:
https://lore.kernel.org/linux-fsdevel/20200724183812.19573-1-vgoyal@redhat.com/
Changes since v2:
- Based on Miklos's feedback, dropped a patch where we send ATTR_MODE as
that's racy. To help the case of writeback_cache with killpriv_v2, I
fallback to a synchronous WRITE if suid/sgid is set on file.
I have generated these patches on top of.
https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git/log/?h=for-nex
+t
I have taken care of feedback from last round. For the case of random
write peformance has jumped from 50MB/s to 250MB/s. So I am really
looking forward to these changes so that fuse/virtiofs performance
can be improved for direct random writes.
Thanks
Vivek
Vivek Goyal (6):
fuse: Introduce the notion of FUSE_HANDLE_KILLPRIV_V2
fuse: Set FUSE_WRITE_KILL_PRIV in cached write path
fuse: setattr should set FATTR_KILL_PRIV upon size change
fuse: Don't send ATTR_MODE to kill suid/sgid for handle_killpriv_v2
fuse: Add a flag FUSE_OPEN_KILL_PRIV for open() request
fuse: Support SB_NOSEC flag to improve direct write performance
fs/fuse/dir.c | 4 +++-
fs/fuse/file.c | 16 +++++++++++++++-
fs/fuse/fuse_i.h | 6 ++++++
fs/fuse/inode.c | 17 ++++++++++++++++-
include/uapi/linux/fuse.h | 18 +++++++++++++++++-
5 files changed, 57 insertions(+), 4 deletions(-)
--
2.25.4
WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: linux-fsdevel@vger.kernel.org, miklos@szeredi.hu
Cc: vgoyal@redhat.com, virtio-fs@redhat.com
Subject: [PATCH v3 0/6] fuse: Implement FUSE_HANDLE_KILLPRIV_V2 and enable SB_NOSEC
Date: Fri, 9 Oct 2020 14:15:06 -0400 [thread overview]
Message-ID: <20201009181512.65496-1-vgoyal@redhat.com> (raw)
Hi All,
Please find attached V3 of the patches to enable SB_NOSEC for fuse. I
posted V1 and V2 here.
v2:
https://lore.kernel.org/linux-fsdevel/20200916161737.38028-1-vgoyal@redhat.com/
v1:
https://lore.kernel.org/linux-fsdevel/20200724183812.19573-1-vgoyal@redhat.com/
Changes since v2:
- Based on Miklos's feedback, dropped a patch where we send ATTR_MODE as
that's racy. To help the case of writeback_cache with killpriv_v2, I
fallback to a synchronous WRITE if suid/sgid is set on file.
I have generated these patches on top of.
https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git/log/?h=for-nex
+t
I have taken care of feedback from last round. For the case of random
write peformance has jumped from 50MB/s to 250MB/s. So I am really
looking forward to these changes so that fuse/virtiofs performance
can be improved for direct random writes.
Thanks
Vivek
Vivek Goyal (6):
fuse: Introduce the notion of FUSE_HANDLE_KILLPRIV_V2
fuse: Set FUSE_WRITE_KILL_PRIV in cached write path
fuse: setattr should set FATTR_KILL_PRIV upon size change
fuse: Don't send ATTR_MODE to kill suid/sgid for handle_killpriv_v2
fuse: Add a flag FUSE_OPEN_KILL_PRIV for open() request
fuse: Support SB_NOSEC flag to improve direct write performance
fs/fuse/dir.c | 4 +++-
fs/fuse/file.c | 16 +++++++++++++++-
fs/fuse/fuse_i.h | 6 ++++++
fs/fuse/inode.c | 17 ++++++++++++++++-
include/uapi/linux/fuse.h | 18 +++++++++++++++++-
5 files changed, 57 insertions(+), 4 deletions(-)
--
2.25.4
next reply other threads:[~2020-10-09 18:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 18:15 Vivek Goyal [this message]
2020-10-09 18:15 ` [PATCH v3 0/6] fuse: Implement FUSE_HANDLE_KILLPRIV_V2 and enable SB_NOSEC Vivek Goyal
2020-10-09 18:15 ` [Virtio-fs] [PATCH v3 1/6] fuse: Introduce the notion of FUSE_HANDLE_KILLPRIV_V2 Vivek Goyal
2020-10-09 18:15 ` Vivek Goyal
2020-10-09 18:15 ` [Virtio-fs] [PATCH v3 2/6] fuse: Set FUSE_WRITE_KILL_PRIV in cached write path Vivek Goyal
2020-10-09 18:15 ` Vivek Goyal
2020-10-09 18:15 ` [Virtio-fs] [PATCH v3 3/6] fuse: setattr should set FATTR_KILL_PRIV upon size change Vivek Goyal
2020-10-09 18:15 ` Vivek Goyal
2020-11-06 14:39 ` [Virtio-fs] " Miklos Szeredi
2020-11-06 14:39 ` Miklos Szeredi
2020-11-06 17:18 ` [Virtio-fs] " Vivek Goyal
2020-11-06 17:18 ` Vivek Goyal
2020-11-11 13:54 ` [Virtio-fs] " Miklos Szeredi
2020-11-11 13:54 ` Miklos Szeredi
2020-11-11 14:27 ` [Virtio-fs] " Harry G. Coin
2020-11-11 16:24 ` Miklos Szeredi
2020-11-11 16:24 ` Miklos Szeredi
2020-11-11 22:09 ` [Virtio-fs] " Vivek Goyal
2020-11-11 22:09 ` Vivek Goyal
2020-11-11 19:16 ` [Virtio-fs] " Vivek Goyal
2020-11-11 19:16 ` Vivek Goyal
2020-10-09 18:15 ` [Virtio-fs] [PATCH v3 4/6] fuse: Don't send ATTR_MODE to kill suid/sgid for handle_killpriv_v2 Vivek Goyal
2020-10-09 18:15 ` Vivek Goyal
2020-10-09 18:15 ` [Virtio-fs] [PATCH v3 5/6] fuse: Add a flag FUSE_OPEN_KILL_PRIV for open() request Vivek Goyal
2020-10-09 18:15 ` Vivek Goyal
2020-11-06 13:55 ` [Virtio-fs] " Miklos Szeredi
2020-11-06 13:55 ` Miklos Szeredi
2020-11-06 16:00 ` [Virtio-fs] " Vivek Goyal
2020-11-06 16:00 ` Vivek Goyal
2020-11-06 16:33 ` [Virtio-fs] " Miklos Szeredi
2020-11-06 16:33 ` Miklos Szeredi
2020-11-06 18:41 ` [Virtio-fs] " Vivek Goyal
2020-11-06 18:41 ` Vivek Goyal
2020-10-09 18:15 ` [Virtio-fs] [PATCH v3 6/6] fuse: Support SB_NOSEC flag to improve direct write performance Vivek Goyal
2020-10-09 18:15 ` Vivek Goyal
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=20201009181512.65496-1-vgoyal@redhat.com \
--to=vgoyal@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.