diff options
author | Tyler Hicks <tyhicks@canonical.com> | 2012-06-11 15:42:32 -0700 |
---|---|---|
committer | Tyler Hicks <tyhicks@canonical.com> | 2012-07-08 12:51:43 -0500 |
commit | 069ddcda37b2cf5bb4b6031a944c0e9359213262 (patch) | |
tree | c47a199c2a84947a3f98370008c001c85e05b2e6 /tools/perf/perf-archive.sh | |
parent | bd0a521e88aa7a06ae7aabaed7ae196ed4ad867a (diff) | |
download | talos-obmc-linux-069ddcda37b2cf5bb4b6031a944c0e9359213262.tar.gz talos-obmc-linux-069ddcda37b2cf5bb4b6031a944c0e9359213262.zip |
eCryptfs: Copy up POSIX ACL and read-only flags from lower mount
When the eCryptfs mount options do not include '-o acl', but the lower
filesystem's mount options do include 'acl', the MS_POSIXACL flag is not
flipped on in the eCryptfs super block flags. This flag is what the VFS
checks in do_last() when deciding if the current umask should be applied
to a newly created inode's mode or not. When a default POSIX ACL mask is
set on a directory, the current umask is incorrectly applied to new
inodes created in the directory. This patch ignores the MS_POSIXACL flag
passed into ecryptfs_mount() and sets the flag on the eCryptfs super
block depending on the flag's presence on the lower super block.
Additionally, it is incorrect to allow a writeable eCryptfs mount on top
of a read-only lower mount. This missing check did not allow writes to
the read-only lower mount because permissions checks are still performed
on the lower filesystem's objects but it is best to simply not allow a
rw mount on top of ro mount. However, a ro eCryptfs mount on top of a rw
mount is valid and still allowed.
https://launchpad.net/bugs/1009207
Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
Reported-by: Stefan Beller <stefanbeller@googlemail.com>
Cc: John Johansen <john.johansen@canonical.com>
Diffstat (limited to 'tools/perf/perf-archive.sh')
0 files changed, 0 insertions, 0 deletions