Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750960AbdGMBBk (ORCPT ); Wed, 12 Jul 2017 21:01:40 -0400 Received: from h2.hallyn.com ([78.46.35.8]:60336 "EHLO h2.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750741AbdGMBBj (ORCPT ); Wed, 12 Jul 2017 21:01:39 -0400 Date: Wed, 12 Jul 2017 20:01:38 -0500 From: "Serge E. Hallyn" To: "Eric W. Biederman" Cc: James Morris , "Serge E. Hallyn" , Stefan Berger , containers@lists.linux-foundation.org, lkp@01.org, linux-kernel@vger.kernel.org, zohar@linux.vnet.ibm.com, tycho@docker.com, James.Bottomley@HansenPartnership.com, vgoyal@redhat.com, christian.brauner@mailbox.org, amir73il@gmail.com, linux-security-module@vger.kernel.org, casey@schaufler-ca.com Subject: Re: [PATCH v2] xattr: Enable security.capability in user namespaces Message-ID: <20170713010137.GA23575@mail.hallyn.com> References: <1499785511-17192-1-git-send-email-stefanb@linux.vnet.ibm.com> <1499785511-17192-2-git-send-email-stefanb@linux.vnet.ibm.com> <87mv89iy7q.fsf@xmission.com> <20170712170346.GA17974@mail.hallyn.com> <87o9spfa5v.fsf@xmission.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87o9spfa5v.fsf@xmission.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1313 Lines: 34 Quoting Eric W. Biederman (ebiederm@xmission.com): > James Morris writes: > > > On Wed, 12 Jul 2017, Serge E. Hallyn wrote: > > > >> Quoting Eric W. Biederman (ebiederm@xmission.com): > >> > Stefan Berger <"Stefan Bergerstefanb"@linux.vnet.ibm.com> writes: > >> > > Signed-off-by: Stefan Berger > >> > > Signed-off-by: Serge Hallyn > >> > > Reviewed-by: Serge Hallyn > >> > > >> > 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. I wasn't clear here. There were a lot of changes between the first mention of the approach and the posting of v1. My point was that I did in fact agree to Reviewed-by, and the fact that I've found a few more things to point out only reflects my missing them before. I don't think my name is being mis-used. > > Please try and keep technical discussions public or at least document them > > when reposting the patches. > > Yes please. > > A public discussion helps to understand what the challenges are. Yes, all discussion (that I can find in my mbox) since v1 has been public. -serge