All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Linux Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>
Subject: Re: User namespace feature freeze lifted
Date: Tue, 15 Sep 2015 13:23:12 -0500	[thread overview]
Message-ID: <20150915182312.GD146373@ubuntu-hedt> (raw)
In-Reply-To: <87io7bd23x.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>

On Tue, Sep 15, 2015 at 12:27:46PM -0500, Eric W. Biederman wrote:
> 
> As of v4.3-rc1 all of the security issues I am aware of with the user
> namespace have been addressed.  If someone knows of something I have
> overlooked please let me know.
> 
> As much as humanly possible I want to avoid security bugs in the future
> so I will endeavour to ensure any future user namespace patches receive
> a close review.
> 
> As for merging features I expect I will likley start with Seth's code
> for associating superblock with user namespaces, and then move on to
> Lukasz's code for figuring out how to add namespace for smack.

As for my patches, I'm in the process of testing after rebasing onto
4.3-rc1. I should be sending an update in the next day or so, though
nothing will change except for resolving merge conflicts and fixing
that one inadvertent change I introduced in v2.

Seth

      parent reply	other threads:[~2015-09-15 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 17:27 User namespace feature freeze lifted Eric W. Biederman
     [not found] ` <87io7bd23x.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2015-09-15 17:36   ` Serge Hallyn
2015-09-15 18:05     ` Eric W. Biederman
     [not found]       ` <874mivd0ct.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2015-09-15 18:44         ` Serge E. Hallyn
2015-09-15 18:23   ` Seth Forshee [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=20150915182312.GD146373@ubuntu-hedt \
    --to=seth.forshee-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
    --cc=luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org \
    /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.