linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: miklos@szeredi.hu
Cc: linux-fsdevel@vger.kernel.org, selinux@vger.kernel.org,
	linux-security-module@vger.kernel.org, virtio-fs@redhat.com,
	chirantan@chromium.org, vgoyal@redhat.com,
	stephen.smalley.work@gmail.com, dwalsh@redhat.com,
	casey@schaufler-ca.com, omosnace@redhat.com
Subject: [PATCH v3 0/1] fuse: Send file/inode security context during creation
Date: Wed, 10 Nov 2021 17:55:27 -0500	[thread overview]
Message-ID: <20211110225528.48601-1-vgoyal@redhat.com> (raw)

Hi,

This is V3 of the patch. V2 was posted here.

https://lore.kernel.org/linux-fsdevel/20210924192442.916927-1-vgoyal@redhat.com/

I took care of feedback from Miklos. Changes since v2 are.

- Merged two patches into one. (Miklos)
- Renamed fuse_secctxs to fuse_secctx_header (Miklos)
- Added total size of all contexts (including fuse_secctx_header) field
  in fuse_secctx_header. (Miklos)
- Fixed changelogs (Casey Schaufler)
- Removed one unnecessary if condition check (Miklos)
- Removed a function argument to function create_new_entry() (Miklos)

Thanks
Vivek

Vivek Goyal (1):
  fuse: Send security context of inode on file creation

 fs/fuse/dir.c             | 103 ++++++++++++++++++++++++++++++++++++++
 fs/fuse/fuse_i.h          |   3 ++
 fs/fuse/inode.c           |   4 +-
 include/uapi/linux/fuse.h |  31 +++++++++++-
 4 files changed, 139 insertions(+), 2 deletions(-)

-- 
2.31.1


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 22:55 Vivek Goyal [this message]
2021-11-10 22:55 ` [PATCH v3 1/1] fuse: Send security context of inode on file creation Vivek Goyal
2021-11-11 14:32   ` Vivek Goyal
2021-11-11 14:32   ` 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=20211110225528.48601-1-vgoyal@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=casey@schaufler-ca.com \
    --cc=chirantan@chromium.org \
    --cc=dwalsh@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=omosnace@redhat.com \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@gmail.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).