From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Subject: [GIT PULL] namespace related fixes for 4.10-rc3
Date: Sat, 07 Jan 2017 18:30:05 +1300 [thread overview]
Message-ID: <87d1fzzbc2.fsf@xmission.com> (raw)
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: cd293bfacd57928627ef7da6194e0cbe24db3291 sysctl: Drop reference added by grab_header in proc_sys_readdir
This tree contains 5 fixes.
The first is a fix for a race that can causes oopses under the right
circumstances, and that someone just recently encountered.
The second is a fix that removes the possibility of creating unbounded
chains in the mount hash table. After a lot of back and forth this fix
has finally matured into something mergeable.
Past that are several small trivial correct fixes. A real issue that
was blocking development of an out of tree driver, but does not appear
to have caused any actual problems for in-tree code. A potential
deadlock that was reported by lockdep. And a deadlock people have
experienced and took the time to track down caused by a cleanup that
removed the code to drop a reference count.
Andrei Vagin (1):
pid: fix lockdep deadlock warning due to ucount_lock
Eric W. Biederman (3):
mnt: Protect the mountpoint hashtable with mount_lock
mnt: Tuck mounts under others instead of creating shadow/side mounts.
libfs: Modify mount_pseudo_xattr to be clear it is not a userspace mount
Zhou Chengming (1):
sysctl: Drop reference added by grab_header in proc_sys_readdir
fs/dcache.c | 7 +-
fs/libfs.c | 3 +-
fs/mount.h | 1 -
fs/namespace.c | 174 +++++++++++++++++++++++++++++--------------------
fs/pnode.c | 27 ++++++--
fs/pnode.h | 2 +
fs/proc/proc_sysctl.c | 3 +-
kernel/pid_namespace.c | 10 +--
8 files changed, 142 insertions(+), 85 deletions(-)
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Containers <containers@lists.linux-foundation.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: [GIT PULL] namespace related fixes for 4.10-rc3
Date: Sat, 07 Jan 2017 18:30:05 +1300 [thread overview]
Message-ID: <87d1fzzbc2.fsf@xmission.com> (raw)
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: cd293bfacd57928627ef7da6194e0cbe24db3291 sysctl: Drop reference added by grab_header in proc_sys_readdir
This tree contains 5 fixes.
The first is a fix for a race that can causes oopses under the right
circumstances, and that someone just recently encountered.
The second is a fix that removes the possibility of creating unbounded
chains in the mount hash table. After a lot of back and forth this fix
has finally matured into something mergeable.
Past that are several small trivial correct fixes. A real issue that
was blocking development of an out of tree driver, but does not appear
to have caused any actual problems for in-tree code. A potential
deadlock that was reported by lockdep. And a deadlock people have
experienced and took the time to track down caused by a cleanup that
removed the code to drop a reference count.
Andrei Vagin (1):
pid: fix lockdep deadlock warning due to ucount_lock
Eric W. Biederman (3):
mnt: Protect the mountpoint hashtable with mount_lock
mnt: Tuck mounts under others instead of creating shadow/side mounts.
libfs: Modify mount_pseudo_xattr to be clear it is not a userspace mount
Zhou Chengming (1):
sysctl: Drop reference added by grab_header in proc_sys_readdir
fs/dcache.c | 7 +-
fs/libfs.c | 3 +-
fs/mount.h | 1 -
fs/namespace.c | 174 +++++++++++++++++++++++++++++--------------------
fs/pnode.c | 27 ++++++--
fs/pnode.h | 2 +
fs/proc/proc_sysctl.c | 3 +-
kernel/pid_namespace.c | 10 +--
8 files changed, 142 insertions(+), 85 deletions(-)
Eric
next reply other threads:[~2017-01-07 5:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 5:30 Eric W. Biederman [this message]
2017-01-07 5:30 ` [GIT PULL] namespace related fixes for 4.10-rc3 Eric W. Biederman
[not found] ` <87d1fzzbc2.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2017-01-07 6:29 ` Al Viro
2017-01-10 23:25 ` [GIT PULL] namespace related fixes for 4.10-rc4 Eric W. Biederman
2017-01-10 23:25 ` Eric W. Biederman
2017-01-07 6:29 ` [GIT PULL] namespace related fixes for 4.10-rc3 Al Viro
[not found] ` <20170107062952.GH1555-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2017-01-07 6:40 ` Al Viro
2017-01-07 6:40 ` Al Viro
[not found] ` <20170107064012.GI1555-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2017-01-10 23:23 ` Eric W. Biederman
2017-01-10 23:23 ` 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=87d1fzzbc2.fsf@xmission.com \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@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.