diff options
| author | Aleksa Sarai <cyphar@cyphar.com> | 2019-12-07 01:13:26 +1100 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2019-12-08 19:09:36 -0500 |
| commit | 2b98149c2377bff12be5dd3ce02ae0506e2dd613 (patch) | |
| tree | 95fb705a14f99ab1b6ca600a529a66c8793f7dcc /include/linux/proc_ns.h | |
| parent | e42617b825f8073569da76dc4510bfa019b1c35a (diff) | |
namei: only return -ECHILD from follow_dotdot_rcu()
It's over-zealous to return hard errors under RCU-walk here, given that
a REF-walk will be triggered for all other cases handling ".." under
RCU.
The original purpose of this check was to ensure that if a rename occurs
such that a directory is moved outside of the bind-mount which the
resolution started in, it would be detected and blocked to avoid being
able to mess with paths outside of the bind-mount. However, triggering a
new REF-walk is just as effective a solution.
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Fixes: 397d425dc26d ("vfs: Test for and handle paths that are unreachable from their mnt_root")
Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'include/linux/proc_ns.h')
0 files changed, 0 insertions, 0 deletions