Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chirantan Ekbote <chirantan@chromium.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Vivek Goyal <vgoyal@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	virtio-fs-list <virtio-fs@redhat.com>,
	Dylan Reid <dgreid@chromium.org>,
	Suleiman Souhlal <suleiman@chromium.org>
Subject: Re: [PATCH v2] RFC: fuse: Call security hooks on new inodes
Date: Mon, 15 Jun 2020 16:37:48 +0900	[thread overview]
Message-ID: <CAJFHJrq6aeVkKaYL2jcYjxFkcnEp_T6wc1tQ8pZYbwsubKW66A@mail.gmail.com> (raw)
In-Reply-To: <20200610092744.140038-1-chirantan@chromium.org>

Friendly ping.  Are there any concerns with this patch?  I know I
probably need to split it up into 2 patches: one that adds the flag
and one that implements support.  Since v2 adds a new flag to the
init_out struct I'd really like to get this merged upstream as
carrying it locally would effectively mean forking the protocol.

Thanks,
Chirantan

  reply	other threads:[~2020-06-15  7:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01  5:32 [PATCH] RFC: fuse: virtiofs: " Chirantan Ekbote
2020-06-02 18:23 ` Vivek Goyal
2020-06-10  9:27 ` [PATCH v2] RFC: fuse: " Chirantan Ekbote
2020-06-15  7:37   ` Chirantan Ekbote [this message]
2020-06-16  9:29   ` Miklos Szeredi
2020-06-16  9:41     ` Chirantan Ekbote
2020-06-16 10:27       ` Miklos Szeredi
2020-07-13  9:09   ` [PATCHv3 1/2] uapi: fuse: Add FUSE_SECURITY_CTX Chirantan Ekbote
2020-07-13  9:09     ` [PATCHv3 2/2] fuse: Call security hooks on new inodes Chirantan Ekbote
2020-07-13  9:56     ` [PATCHv4 1/2] uapi: fuse: Add FUSE_SECURITY_CTX Chirantan Ekbote
2020-07-13  9:57       ` [PATCHv4 2/2] fuse: Call security hooks on new inodes Chirantan Ekbote
2020-07-21  8:07         ` Chirantan Ekbote
2020-07-21 14:23           ` Miklos Szeredi

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=CAJFHJrq6aeVkKaYL2jcYjxFkcnEp_T6wc1tQ8pZYbwsubKW66A@mail.gmail.com \
    --to=chirantan@chromium.org \
    --cc=dgreid@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=stefanha@redhat.com \
    --cc=suleiman@chromium.org \
    --cc=vgoyal@redhat.com \
    --cc=virtio-fs@redhat.com \
    --subject='Re: [PATCH v2] RFC: fuse: Call security hooks on new inodes' \
    /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

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).