summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2013-03-09 00:14:45 -0800
committerEric W. Biederman <ebiederm@xmission.com>2013-03-09 00:14:45 -0800
commitdb04dc679bcc780ad6907943afe24a30de974a1b (patch)
treeb90e13dc98a5217968a3035470d34744bf72d1c2 /drivers
parent9141770548d529b9d32d5b08d59b65ee65afe0d4 (diff)
downloadop-kernel-dev-db04dc679bcc780ad6907943afe24a30de974a1b.zip
op-kernel-dev-db04dc679bcc780ad6907943afe24a30de974a1b.tar.gz
proc: Use nd_jump_link in proc_ns_follow_link
Update proc_ns_follow_link to use nd_jump_link instead of just manually updating nd.path.dentry. This fixes the BUG_ON(nd->inode != parent->d_inode) reported by Dave Jones and reproduced trivially with mkdir /proc/self/ns/uts/a. Sigh it looks like the VFS change to require use of nd_jump_link happend while proc_ns_follow_link was baking and since the common case of proc_ns_follow_link continued to work without problems the need for making this change was overlooked. Cc: stable@vger.kernel.org Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud