summaryrefslogtreecommitdiff
path: root/kernel/stop_machine.c
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2014-07-29 15:50:44 -0700
committerJiri Slaby <jslaby@suse.cz>2014-09-17 16:55:10 +0200
commit4194b9700ce41ff2f7031aa0c6108c2539028ab5 (patch)
tree2fcb1c4433bd8eaf870c4961aa3ca79d70234925 /kernel/stop_machine.c
parentfafbc9412b8f2dae04bc3ca233ae7b49482c8df8 (diff)
downloadlwn-4194b9700ce41ff2f7031aa0c6108c2539028ab5.tar.gz
lwn-4194b9700ce41ff2f7031aa0c6108c2539028ab5.zip
mnt: Add tests for unprivileged remount cases that have found to be faulty
commit db181ce011e3c033328608299cd6fac06ea50130 upstream. Kenton Varda <kenton@sandstorm.io> discovered that by remounting a read-only bind mount read-only in a user namespace the MNT_LOCK_READONLY bit would be cleared, allowing an unprivileged user to the remount a read-only mount read-write. Upon review of the code in remount it was discovered that the code allowed nosuid, noexec, and nodev to be cleared. It was also discovered that the code was allowing the per mount atime flags to be changed. The first naive patch to fix these issues contained the flaw that using default atime settings when remounting a filesystem could be disallowed. To avoid this problems in the future add tests to ensure unprivileged remounts are succeeding and failing at the appropriate times. Acked-by: Serge E. Hallyn <serge.hallyn@ubuntu.com> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Diffstat (limited to 'kernel/stop_machine.c')
0 files changed, 0 insertions, 0 deletions