[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.20.1707130820050.16810@namei.org>
Date: Thu, 13 Jul 2017 08:20:34 +1000 (AEST)
From: James Morris <jmorris@...ei.org>
To: "Serge E. Hallyn" <serge@...lyn.com>
cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Stefan Berger <stefanb@...ux.vnet.ibm.com>,
containers@...ts.linux-foundation.org, lkp@...org,
linux-kernel@...r.kernel.org, zohar@...ux.vnet.ibm.com,
tycho@...ker.com, James.Bottomley@...senPartnership.com,
vgoyal@...hat.com, christian.brauner@...lbox.org,
amir73il@...il.com, linux-security-module@...r.kernel.org,
casey@...aufler-ca.com
Subject: Re: [PATCH v2] xattr: Enable security.capability in user
namespaces
On Wed, 12 Jul 2017, Serge E. Hallyn wrote:
> Quoting Eric W. Biederman (ebiederm@...ssion.com):
> > Stefan Berger <"Stefan Bergerstefanb"@linux.vnet.ibm.com> writes:
> > > Signed-off-by: Stefan Berger <stefanb@...ux.vnet.ibm.com>
> > > Signed-off-by: Serge Hallyn <serge@...lyn.com>
> > > Reviewed-by: Serge Hallyn <serge@...lyn.com>
> >
> > It doesn't look like this is coming through Serge so I don't see how
> > the Signed-off-by tag is legtimate.
>
> This is mostly explained by the fact that there have been a *lot* of
> changes, many of them discussed in private emails.
Please try and keep technical discussions public or at least document them
when reposting the patches.
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists