From: Paul Moore <paul@paul-moore.com>
To: James Morris <jmorris@namei.org>
Cc: Vivek Goyal <vgoyal@redhat.com>,
linux-fsdevel@vger.kernel.org, virtio-fs@redhat.com,
Miklos Szeredi <miklos@szeredi.hu>, Dan Walsh <dwalsh@redhat.com>,
jlayton@kernel.org, idryomov@gmail.com,
ceph-devel@vger.kernel.org, linux-nfs@vger.kernel.org,
bfields@fieldses.org, chuck.lever@oracle.com,
anna.schumaker@netapp.com, trond.myklebust@hammerspace.com,
Stephen Smalley <stephen.smalley.work@gmail.com>,
casey@schaufler-ca.com, Ondrej Mosnacek <omosnace@redhat.com>,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
Serge Hallyn <serge@hallyn.com>
Subject: Re: [PATCH v2] security: Return xattr name from security_dentry_init_security()
Date: Tue, 19 Oct 2021 19:49:06 -0400 [thread overview]
Message-ID: <CAHC9VhRZyGYsFziXMfJQ=1OcLO52TGmAGMi5RaA3FXRgREsSeQ@mail.gmail.com> (raw)
In-Reply-To: <3bd86fa3-b3b0-754f-25a5-5e4f723babe4@namei.org>
On Tue, Oct 19, 2021 at 5:02 PM James Morris <jmorris@namei.org> wrote:
>
> On Mon, 18 Oct 2021, Vivek Goyal wrote:
>
> > Hi James,
> >
> > I am assuming this patch will need to be routed through security tree.
> > Can you please consider it for inclusion.
>
> I'm happy for this to go via Paul's tree as it impacts SELinux and is
> fairly minor in scope.
I'll take a look tomorrow, I ended up spending most of my day today
chasing a 32-bit MIPS (!!) bug in libseccomp and now it's dinner time.
--
paul moore
www.paul-moore.com
WARNING: multiple messages have this Message-ID (diff)
From: Paul Moore <paul@paul-moore.com>
To: James Morris <jmorris@namei.org>
Cc: bfields@fieldses.org, linux-nfs@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>,
selinux@vger.kernel.org, casey@schaufler-ca.com,
Stephen Smalley <stephen.smalley.work@gmail.com>,
jlayton@kernel.org, Ondrej Mosnacek <omosnace@redhat.com>,
anna.schumaker@netapp.com, virtio-fs@redhat.com,
trond.myklebust@hammerspace.com,
linux-security-module@vger.kernel.org, chuck.lever@oracle.com,
linux-fsdevel@vger.kernel.org, idryomov@gmail.com,
ceph-devel@vger.kernel.org, Vivek Goyal <vgoyal@redhat.com>,
Serge Hallyn <serge@hallyn.com>
Subject: Re: [Virtio-fs] [PATCH v2] security: Return xattr name from security_dentry_init_security()
Date: Tue, 19 Oct 2021 19:49:06 -0400 [thread overview]
Message-ID: <CAHC9VhRZyGYsFziXMfJQ=1OcLO52TGmAGMi5RaA3FXRgREsSeQ@mail.gmail.com> (raw)
In-Reply-To: <3bd86fa3-b3b0-754f-25a5-5e4f723babe4@namei.org>
On Tue, Oct 19, 2021 at 5:02 PM James Morris <jmorris@namei.org> wrote:
>
> On Mon, 18 Oct 2021, Vivek Goyal wrote:
>
> > Hi James,
> >
> > I am assuming this patch will need to be routed through security tree.
> > Can you please consider it for inclusion.
>
> I'm happy for this to go via Paul's tree as it impacts SELinux and is
> fairly minor in scope.
I'll take a look tomorrow, I ended up spending most of my day today
chasing a 32-bit MIPS (!!) bug in libseccomp and now it's dinner time.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2021-10-19 23:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 13:23 [PATCH v2] security: Return xattr name from security_dentry_init_security() Vivek Goyal
2021-10-12 13:23 ` [Virtio-fs] " Vivek Goyal
2021-10-15 9:07 ` Christian Brauner
2021-10-15 9:07 ` [Virtio-fs] " Christian Brauner
2021-10-18 12:35 ` Vivek Goyal
2021-10-18 12:35 ` [Virtio-fs] " Vivek Goyal
2021-10-19 20:52 ` James Morris
2021-10-19 20:52 ` [Virtio-fs] " James Morris
2021-10-19 23:49 ` Paul Moore [this message]
2021-10-19 23:49 ` Paul Moore
2021-10-20 12:24 ` Paul Moore
2021-10-20 12:24 ` [Virtio-fs] " Paul Moore
2021-10-20 12:31 ` Vivek Goyal
2021-10-20 12:31 ` [Virtio-fs] " 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='CAHC9VhRZyGYsFziXMfJQ=1OcLO52TGmAGMi5RaA3FXRgREsSeQ@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=casey@schaufler-ca.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dwalsh@redhat.com \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=omosnace@redhat.com \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.com \
--cc=trond.myklebust@hammerspace.com \
--cc=vgoyal@redhat.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 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.