From: ebiederm@xmission.com (Eric W. Biederman)
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Seth Forshee <seth.forshee@canonical.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-api@vger.kernel.org
Subject: Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic
Date: Sat, 10 Dec 2016 12:29:07 +1300 [thread overview]
Message-ID: <87h96c8yws.fsf@xmission.com> (raw)
In-Reply-To: <878trokcjc.fsf@xmission.com> (Eric W. Biederman's message of "Sat, 10 Dec 2016 10:39:19 +1300")
ebiederm@xmission.com (Eric W. Biederman) writes:
> "Serge E. Hallyn" <serge@hallyn.com> writes:
>
>> Quoting Eric W. Biederman (ebiederm@xmission.com):
>>> "Serge E. Hallyn" <serge@hallyn.com> writes:
>>>
>>> > On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote:
>>> >> "Serge E. Hallyn" <serge@hallyn.com> writes:
>>>
>>> >> Any chance of a singed-off-by?
>>> >
>>> > Yes, sorry, Stéphane had pointed out that I'd apparently forgotten to do
>>> > -s. Do you want me to resend the whole shebang, or does
>>> >
>>> > Signed-off-by: Serge Hallyn <serge@hallyn.com>
>>> >
>>> > suffice? (My previous iterations did have it fwiw so I don't think I could
>>> > legally disavow it now :)
>>>
>>> I was really hoping to get this in this for 4.10, but I am seeing a couple
>>> of little things in my review. Comments referring to a non-existent v4
>>> and a few other niggling little things so I am going to target this for
>>> the next kernel release so there is time review. With a little luck I
>>> can place this patch in my for-next tree just after the merge window
>>> closes and 4.10-rc1 ships.
>>
>> Ok, thanks. This is not something I'd want to rush :)
>
> Sure. This is just something we get merged.
By which I meant to say this is something we need to get merged, and
hopefully before all of the developers forget what is going on. Not
having this is clearly a pain point for people working with file
capabilities.
Eric
prev parent reply other threads:[~2016-12-09 23:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 15:17 [PATCH RFC] user-namespaced file capabilities - now with even more magic Serge E. Hallyn
2016-11-23 23:01 ` Eric W. Biederman
2016-11-24 8:15 ` Michael Kerrisk (man-pages)
2016-11-24 22:52 ` Serge E. Hallyn
2016-11-25 8:33 ` Michael Kerrisk (man-pages)
2016-11-25 17:50 ` Serge E. Hallyn
2016-11-25 20:43 ` Michael Kerrisk (man-pages)
2016-11-29 21:29 ` Serge E. Hallyn
2016-12-08 4:43 ` Eric W. Biederman
2016-12-08 4:56 ` Serge E. Hallyn
2016-12-08 5:13 ` Eric W. Biederman
2016-12-09 8:03 ` Eric W. Biederman
2016-12-09 13:42 ` Serge E. Hallyn
2016-12-09 21:39 ` Eric W. Biederman
2016-12-09 23:29 ` Eric W. Biederman [this message]
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=87h96c8yws.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=seth.forshee@canonical.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 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).