[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrVzkDi2tUZV6qtXrFtD+dDtkrR5dVL_Sij=9DVEqsOWmg@mail.gmail.com>
Date: Fri, 14 Dec 2012 10:47:13 -0800
From: Andy Lutomirski <luto@...capital.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
"Serge E. Hallyn" <serge@...lyn.com>,
containers@...ts.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
LSM List <linux-security-module@...r.kernel.org>
Subject: Re: [RFC][PATCH] Fix cap_capable to only allow owners in the parent
user namespace to have caps.
On Fri, Dec 14, 2012 at 10:43 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Fri, Dec 14, 2012 at 10:12 AM, Eric W. Biederman
> <ebiederm@...ssion.com> wrote:
>>
>> That said Serge I think I have lost track of the point of your question.
>
> .. and I'm a bit unsure what I should do about this all. Including
> pulling the pull request that actually can make this all matter.
>
> Hmm? Any consensus?
I think that, if Eric submits a newer version that renames the loop
variable for added comprehensibility, I'm okay with it.
Changing the semantics to a more expansive version like Serge was
talking about later on wouldn't break anything. But I don't think
there's any reason to change it.
--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists