All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: linux-fsdevel@vger.kernel.org, miklos@szeredi.hu
Cc: virtio-fs@redhat.com
Subject: Re: [PATCH v2 0/6] fuse: Implement FUSE_HANDLE_KILLPRIV_V2 and enable SB_NOSEC
Date: Wed, 16 Sep 2020 12:38:40 -0400	[thread overview]
Message-ID: <20200916163840.GA6124@redhat.com> (raw)
In-Reply-To: <20200916161737.38028-1-vgoyal@redhat.com>

On Wed, Sep 16, 2020 at 12:17:31PM -0400, Vivek Goyal wrote:
> Hi All,
> 
> Please find attached V2 of the patches to enable SB_NOSEC for fuse. I
> posted V1 here.

I have posted corresonding qemu/virtiofsd change patch here.

https://www.redhat.com/archives/virtio-fs/2020-September/msg00061.html

Thanks
Vivek

> 
> https://lore.kernel.org/linux-fsdevel/20200724183812.19573-1-vgoyal@redhat.com/
> 
> I have generated these patches on top of.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git/log/?h=for-next
> 
> Previously I was not keen on implementing FUSE_HANDLE_KILLPRIV_V2 and
> implemented another idea to enable SB_NOSEC conditional on server
> declaring that filesystem is not shared. But that did not go too
> far when it came to requirements for virtiofs.
> 
> https://lore.kernel.org/linux-fsdevel/20200901204045.1250822-1-vgoyal@redhat.com/
> 
> So I went back to having another look at implementing FUSE_HANDLE_KILLPRIV_V2
> and I think it fits nicely and should work nicely with wide variety of
> use cases.
> 
> 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.
> 
> 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: Kill suid/sgid using ATTR_MODE if it is not truncate
>   fuse: Add a flag FUSE_OPEN_KILL_PRIV for open() request
>   virtiofs: Support SB_NOSEC flag to improve direct write performance
> 
>  fs/fuse/dir.c             | 19 ++++++++++++++++++-
>  fs/fuse/file.c            |  7 +++++++
>  fs/fuse/fuse_i.h          |  6 ++++++
>  fs/fuse/inode.c           | 17 ++++++++++++++++-
>  include/uapi/linux/fuse.h | 18 +++++++++++++++++-
>  5 files changed, 64 insertions(+), 3 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: virtio-fs@redhat.com
Subject: Re: [Virtio-fs] [PATCH v2 0/6] fuse: Implement FUSE_HANDLE_KILLPRIV_V2 and enable SB_NOSEC
Date: Wed, 16 Sep 2020 12:38:40 -0400	[thread overview]
Message-ID: <20200916163840.GA6124@redhat.com> (raw)
In-Reply-To: <20200916161737.38028-1-vgoyal@redhat.com>

On Wed, Sep 16, 2020 at 12:17:31PM -0400, Vivek Goyal wrote:
> Hi All,
> 
> Please find attached V2 of the patches to enable SB_NOSEC for fuse. I
> posted V1 here.

I have posted corresonding qemu/virtiofsd change patch here.

https://www.redhat.com/archives/virtio-fs/2020-September/msg00061.html

Thanks
Vivek

> 
> https://lore.kernel.org/linux-fsdevel/20200724183812.19573-1-vgoyal@redhat.com/
> 
> I have generated these patches on top of.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git/log/?h=for-next
> 
> Previously I was not keen on implementing FUSE_HANDLE_KILLPRIV_V2 and
> implemented another idea to enable SB_NOSEC conditional on server
> declaring that filesystem is not shared. But that did not go too
> far when it came to requirements for virtiofs.
> 
> https://lore.kernel.org/linux-fsdevel/20200901204045.1250822-1-vgoyal@redhat.com/
> 
> So I went back to having another look at implementing FUSE_HANDLE_KILLPRIV_V2
> and I think it fits nicely and should work nicely with wide variety of
> use cases.
> 
> 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.
> 
> 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: Kill suid/sgid using ATTR_MODE if it is not truncate
>   fuse: Add a flag FUSE_OPEN_KILL_PRIV for open() request
>   virtiofs: Support SB_NOSEC flag to improve direct write performance
> 
>  fs/fuse/dir.c             | 19 ++++++++++++++++++-
>  fs/fuse/file.c            |  7 +++++++
>  fs/fuse/fuse_i.h          |  6 ++++++
>  fs/fuse/inode.c           | 17 ++++++++++++++++-
>  include/uapi/linux/fuse.h | 18 +++++++++++++++++-
>  5 files changed, 64 insertions(+), 3 deletions(-)
> 
> -- 
> 2.25.4
> 


  parent reply	other threads:[~2020-09-16 19:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 16:17 [PATCH v2 0/6] fuse: Implement FUSE_HANDLE_KILLPRIV_V2 and enable SB_NOSEC Vivek Goyal
2020-09-16 16:17 ` [Virtio-fs] " Vivek Goyal
2020-09-16 16:17 ` [PATCH v2 1/6] fuse: Introduce the notion of FUSE_HANDLE_KILLPRIV_V2 Vivek Goyal
2020-09-16 16:17   ` [Virtio-fs] " Vivek Goyal
2020-09-16 16:17 ` [PATCH v2 2/6] fuse: Set FUSE_WRITE_KILL_PRIV in cached write path Vivek Goyal
2020-09-16 16:17   ` [Virtio-fs] " Vivek Goyal
2020-09-16 16:17 ` [PATCH v2 3/6] fuse: setattr should set FATTR_KILL_PRIV upon size change Vivek Goyal
2020-09-16 16:17   ` [Virtio-fs] " Vivek Goyal
2020-09-16 16:17 ` [PATCH v2 4/6] fuse: Kill suid/sgid using ATTR_MODE if it is not truncate Vivek Goyal
2020-09-16 16:17   ` [Virtio-fs] " Vivek Goyal
2020-09-22 13:56   ` Miklos Szeredi
2020-09-22 13:56     ` [Virtio-fs] " Miklos Szeredi
2020-09-22 20:08     ` Vivek Goyal
2020-09-22 20:08       ` [Virtio-fs] " Vivek Goyal
2020-09-22 21:25       ` Miklos Szeredi
2020-09-22 21:25         ` [Virtio-fs] " Miklos Szeredi
2020-09-22 21:31         ` Vivek Goyal
2020-09-22 21:31           ` [Virtio-fs] " Vivek Goyal
2020-09-16 16:17 ` [PATCH v2 5/6] fuse: Add a flag FUSE_OPEN_KILL_PRIV for open() request Vivek Goyal
2020-09-16 16:17   ` [Virtio-fs] " Vivek Goyal
2020-09-16 16:17 ` [PATCH v2 6/6] virtiofs: Support SB_NOSEC flag to improve direct write performance Vivek Goyal
2020-09-16 16:17   ` [Virtio-fs] " Vivek Goyal
2020-09-16 16:38 ` Vivek Goyal [this message]
2020-09-16 16:38   ` [Virtio-fs] [PATCH v2 0/6] fuse: Implement FUSE_HANDLE_KILLPRIV_V2 and enable SB_NOSEC 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=20200916163840.GA6124@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.