linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Containers <containers@lists.linux-foundation.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"libvir-list@redhat.com" <libvir-list@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [GIT PULL] namespace updates for v3.17-rc1
Date: Thu, 21 Aug 2014 06:12:57 -0700	[thread overview]
Message-ID: <20140821131257.GA4264@infradead.org> (raw)
In-Reply-To: <87vbpm4f4y.fsf@x220.int.ebiederm.org>

On Wed, Aug 20, 2014 at 09:53:49PM -0700, Eric W. Biederman wrote:
> Richard Weinberger <richard.weinberger@gmail.com> writes:
> 
> > On Wed, Aug 6, 2014 at 2:57 AM, Eric W. Biederman <ebiederm@xmission.com> wrote:
> >
> > This commit breaks libvirt-lxc.
> > libvirt does in lxcContainerMountBasicFS():
> 
> The bugs fixed are security issues, so if we have to break a small
> number of userspace applications we will.  Anything that we can
> reasonably do to avoid regressions will be done.

Can you explain the security issues in detail?  Breaking common
userspace like libvirt-lxc with just a little bit of handwaiving is
entirely unacceptable.


  parent reply	other threads:[~2014-08-21 13:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06  0:57 [GIT PULL] namespace updates for v3.17-rc1 Eric W. Biederman
2014-08-06  4:46 ` Stephen Rothwell
2014-08-06  5:16   ` Eric W. Biederman
2014-08-06  6:06     ` Stephen Rothwell
2014-08-06  6:30       ` Eric W. Biederman
2014-08-07 13:28       ` Theodore Ts'o
2014-08-13  2:46 ` Andy Lutomirski
2014-08-13  4:17   ` Eric W. Biederman
2014-08-13  4:38     ` Andy Lutomirski
     [not found]     ` <CAOP=4widH1rMZ1O=hzAT+M_8exdzRPA8pJ+wH29AQ9L0ogu9nw@mail.gmail.com>
2014-08-13 10:24       ` Eric W. Biederman
2014-08-13 17:03         ` Andy Lutomirski
2014-08-14  0:03           ` [PATCH] fs: Remove implicit nodev for new mounts in non-root userns Andy Lutomirski
2014-08-15 19:05             ` Serge Hallyn
2014-08-15 19:16               ` Andy Lutomirski
2014-08-15 19:37                 ` Serge Hallyn
2014-08-15 19:56                   ` Andy Lutomirski
2014-08-15 20:16                     ` Serge Hallyn
2014-08-15 20:16             ` Serge Hallyn
2014-08-28  1:35             ` Andy Lutomirski
2014-08-15 18:41         ` [GIT PULL] namespace updates for v3.17-rc1 Andy Lutomirski
2014-08-20 15:06 ` Richard Weinberger
2014-08-21  4:53   ` Eric W. Biederman
2014-08-21  6:29     ` Richard Weinberger
2014-08-21  7:24       ` Richard Weinberger
2014-08-21 13:54         ` Eric W. Biederman
2014-08-21 13:12     ` Christoph Hellwig [this message]
2014-08-21 13:22       ` Richard Weinberger
2014-08-21 14:09         ` Eric W. Biederman
2014-09-03 21:18           ` Richard Weinberger
2014-11-25 23:15           ` Richard Weinberger
2014-11-29 16:58             ` Richard Weinberger
2014-08-21 13:43       ` Eric W. Biederman

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=20140821131257.GA4264@infradead.org \
    --to=hch@infradead.org \
    --cc=berrange@redhat.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=libvir-list@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=torvalds@linux-foundation.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 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).