[<prev] [next>] [day] [month] [year] [list]
Message-ID: <877g9zcdy2.fsf@xmission.com>
Date: Thu, 16 Jan 2014 22:36:21 -0800
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: <linux-kernel@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
Serge Hallyn <serge.hallyn@...onical.com>,
Aditya Kali <adityakali@...gle.com>,
Oleg Nesterov <oleg@...hat.com>,
Andy Lutomirski <luto@...capital.net>,
Gao feng <gaofeng@...fujitsu.com>,
Al Viro <viro@...IV.linux.org.uk>
Subject: [GIT PULL] namespace fixes
Linus,
Please pull the for-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-linus
HEAD: 41301ae78a99ead04ea42672a1ab72c6f44cc81d vfs: Fix a regression in mounting proc
This is a set of 3 regression fixes.
This fixes /proc/mounts when using "ip netns add <netns>" to display the
actual mount point.
This fixes a regression in clone that broke lxc-attach.
This fixes a regression in the permission checks for mounting /proc that
made proc unmountable if binfmt_misc was in use. Oops.
My apologies for sending this pull request so late. Al Viro gave
interesting review comments about the d_path fix that I wanted to
address in detail before I sent this pull request. Unfortunately a
bad round of colds kept from addressing that in detail until today.
The executive summary of the review was:
Al: Is patching d_path really sufficient?
The prepend_path, d_path, d_absolute_path, and __d_path family of
functions is a really mess.
Me: Yes, patching d_path is really sufficient. Yes, the code is mess.
No it is not appropriate to rewrite all of d_path for a regression
that has existed for entirely too long already, when a two line
change will do.
Eric W. Biederman (3):
vfs: In d_path don't call d_dname on a mount point
fork: Allow CLONE_PARENT after setns(CLONE_NEWPID)
vfs: Fix a regression in mounting proc
fs/dcache.c | 7 ++++++-
fs/namespace.c | 2 +-
kernel/fork.c | 2 +-
3 files changed, 8 insertions(+), 3 deletions(-)
--
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