diff options
| author |   Vivek Goyal <vgoyal@redhat.com> | 2020-10-09 14:15:08 -0400 |
|---|---|---|
| committer |   Miklos Szeredi <mszeredi@redhat.com> | 2020-11-11 17:22:33 +0100 |
| commit | b866739596ae3c3c60c43f1cf04a516c5aa20fd1 (patch) | |
| tree | f069020d9cdb3f3ba378bc97650605ab7369a84b /fs/fuse/dir.c | |
| parent | fuse: rename FUSE_WRITE_KILL_PRIV to FUSE_WRITE_KILL_SUIDGID (diff) | |
| download | linux-dev-b866739596ae3c3c60c43f1cf04a516c5aa20fd1.tar.xz linux-dev-b866739596ae3c3c60c43f1cf04a516c5aa20fd1.zip | |
fuse: set FUSE_WRITE_KILL_SUIDGID in cached write path
With HANDLE_KILLPRIV_V2, server will need to kill suid/sgid if caller does
not have CAP_FSETID. We already have a flag FUSE_WRITE_KILL_SUIDGID in
WRITE request and we already set it in direct I/O path.
To make it work in cached write path also, start setting
FUSE_WRITE_KILL_SUIDGID in this path too.
Set it only if fc->handle_killpriv_v2 is set. Otherwise client is
responsible for kill suid/sgid.
In case of direct I/O we set FUSE_WRITE_KILL_SUIDGID unconditionally
because we don't call file_remove_privs() in that path (with cache=none
option).
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'fs/fuse/dir.c')
0 files changed, 0 insertions, 0 deletions