qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: qemu-devel@nongnu.org, virtio-fs@redhat.com, dgilbert@redhat.com
Cc: chirantan@chromium.org, casey@schaufler-ca.com,
	omosnace@redhat.com, vgoyal@redhat.com
Subject: [PATCH v3 0/6] virtiofsd: Add support for file security context at creation
Date: Wed, 10 Nov 2021 18:17:22 -0500	[thread overview]
Message-ID: <20211110231728.50385-1-vgoyal@redhat.com> (raw)

Hi,

This is V3 of the patches. I posted V2 here.

https://lore.kernel.org/qemu-devel/20211014153126.575173-1-vgoyal@redhat.com/

Kernel patches are not upstream yet. So header files will need to be
updated once kernel patches are merged. I posted V3 of kernel patches
here.

https://lore.kernel.org/linux-fsdevel/20211110225528.48601-1-vgoyal@redhat.com/T/#m08352d3d46f948c6c507c28f9db83098d175ca54

Changes since v2:

- Renamed "struct fuse_secctxs" to "struct fuse_secctx_header".
- Added a size field to fuse_secctx_header.    

Thanks
Vivek

Vivek Goyal (6):
  fuse: Header file changes for FUSE_SECURITY_CTX
  virtiofsd, fuse_lowlevel.c: Add capability to parse security context
  virtiofsd: Move core file creation code in separate function
  virtiofsd: Create new file with fscreate set
  virtiofsd: Create new file using O_TMPFILE and set security context
  virtiofsd: Add an option to enable/disable security label

 docs/tools/virtiofsd.rst              |   7 +
 include/standard-headers/linux/fuse.h |  19 +-
 tools/virtiofsd/fuse_common.h         |   5 +
 tools/virtiofsd/fuse_i.h              |   7 +
 tools/virtiofsd/fuse_lowlevel.c       |  91 ++++++
 tools/virtiofsd/helper.c              |   1 +
 tools/virtiofsd/passthrough_ll.c      | 414 ++++++++++++++++++++++++--
 7 files changed, 514 insertions(+), 30 deletions(-)

-- 
2.31.1



             reply	other threads:[~2021-11-10 23:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 23:17 Vivek Goyal [this message]
2021-11-10 23:17 ` [PATCH v3 1/6] fuse: Header file changes for FUSE_SECURITY_CTX Vivek Goyal
2021-11-10 23:17 ` [PATCH v3 2/6] virtiofsd, fuse_lowlevel.c: Add capability to parse security context Vivek Goyal
2021-11-10 23:17 ` [PATCH v3 3/6] virtiofsd: Move core file creation code in separate function Vivek Goyal
2021-11-10 23:17 ` [PATCH v3 4/6] virtiofsd: Create new file with fscreate set Vivek Goyal
2021-11-10 23:17 ` [PATCH v3 5/6] virtiofsd: Create new file using O_TMPFILE and set security context Vivek Goyal
2021-11-10 23:17 ` [PATCH v3 6/6] virtiofsd: Add an option to enable/disable security label 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=20211110231728.50385-1-vgoyal@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=casey@schaufler-ca.com \
    --cc=chirantan@chromium.org \
    --cc=dgilbert@redhat.com \
    --cc=omosnace@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).