diff options
author | Miklos Szeredi <mszeredi@redhat.com> | 2019-05-27 09:08:12 +0200 |
---|---|---|
committer | Miklos Szeredi <mszeredi@redhat.com> | 2019-05-27 11:42:36 +0200 |
commit | 4a2abf99f9c2877039006b8dfb3ec4e0d1278fe8 (patch) | |
tree | 01872fd7aac66a14a0aaaccb7f74289e1603eccf /drivers/block | |
parent | 35d6fcbb7c3e296a52136347346a698a35af3fda (diff) | |
download | linux-4a2abf99f9c2877039006b8dfb3ec4e0d1278fe8.tar.gz linux-4a2abf99f9c2877039006b8dfb3ec4e0d1278fe8.tar.bz2 linux-4a2abf99f9c2877039006b8dfb3ec4e0d1278fe8.zip |
fuse: add FUSE_WRITE_KILL_PRIV
In the FOPEN_DIRECT_IO case the write path doesn't call file_remove_privs()
and that means setuid bit is not cleared if unpriviliged user writes to a
file with setuid bit set.
pjdfstest chmod test 12.t tests this and fails.
Fix this by adding a flag to the FUSE_WRITE message that requests clearing
privileges on the given file. This needs
This better than just calling fuse_remove_privs(), because the attributes
may not be up to date, so in that case a write may miss clearing the
privileges.
Test case:
$ passthrough_ll /mnt/pasthrough-mnt -o default_permissions,allow_other,cache=never
$ mkdir /mnt/pasthrough-mnt/testdir
$ cd /mnt/pasthrough-mnt/testdir
$ prove -rv pjdfstests/tests/chmod/12.t
Reported-by: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Tested-by: Vivek Goyal <vgoyal@redhat.com>
Diffstat (limited to 'drivers/block')
0 files changed, 0 insertions, 0 deletions