From: ebiederm@xmission.com (Eric W. Biederman)
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the userns tree with the vfs tree
Date: Mon, 06 Aug 2018 12:35:20 -0500 [thread overview]
Message-ID: <87lg9j8kkn.fsf@xmission.com> (raw)
In-Reply-To: <20180806175047.5b612a77@canb.auug.org.au> (Stephen Rothwell's message of "Mon, 6 Aug 2018 17:50:47 +1000")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> On Wed, 20 Jun 2018 12:39:05 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Are there any comments on this resolution. I just had to do it all
> again due to slight changes in the vfs tree. What are you guys going
> to tell Linus when he comes to merge this?
Currently that the fscontext changes have a gaping security hole in it's
userspace API. Granted the security hole is copied from the existing
mount api. But I have had multiple real world problems with the
existing behavior, and I have reported it to David Howells multiple
times.
So I honestly don't think David Howells changes are ready to be merged.
The changes to proc exhibit the security holet and I expect they will
have to be redone to make the patch functional.
Eric
next prev parent reply other threads:[~2018-08-06 17:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 2:39 linux-next: manual merge of the userns tree with the vfs tree Stephen Rothwell
2018-08-06 7:50 ` Stephen Rothwell
2018-08-06 17:35 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-20 1:44 Stephen Rothwell
2018-06-20 3:31 ` Stephen Rothwell
2018-06-19 4:56 Stephen Rothwell
2018-06-19 10:11 ` Eric W. Biederman
2015-05-25 9:49 Stephen Rothwell
2014-12-16 3:21 Stephen Rothwell
2014-12-16 4:40 ` Eric W. Biederman
2014-12-10 6:27 Stephen Rothwell
2014-12-10 6:21 Stephen Rothwell
2013-11-08 6:50 Stephen Rothwell
2013-11-08 6:50 Stephen Rothwell
2013-11-08 6:49 Stephen Rothwell
2013-11-08 6:49 Stephen Rothwell
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=87lg9j8kkn.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@ZenIV.linux.org.uk \
/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.