summaryrefslogtreecommitdiffstats
path: root/python
diff options
context:
space:
mode:
authorVivek Goyal2022-07-29 15:17:06 +0200
committerDr. David Alan Gilbert2022-08-02 17:46:52 +0200
commita21ba54dd5ca38cd05da9035fc65374d7af54f13 (patch)
tree46fb2b1949255b48cb481a580b9c8f62cb857e37 /python
parentmigration: Define BLK_MIG_BLOCK_SIZE as unsigned long long (diff)
downloadqemu-a21ba54dd5ca38cd05da9035fc65374d7af54f13.tar.gz
qemu-a21ba54dd5ca38cd05da9035fc65374d7af54f13.tar.xz
qemu-a21ba54dd5ca38cd05da9035fc65374d7af54f13.zip
virtiofsd: Disable killpriv_v2 by default
We are having bunch of issues with killpriv_v2 enabled by default. First of all it relies on clearing suid/sgid bits as needed by dropping capability CAP_FSETID. This does not work for remote filesystems like NFS (and possibly others). Secondly, we are noticing other issues related to clearing of SGID which leads to failures for xfstests generic/355 and generic/193. Thirdly, there are other issues w.r.t caching of metadata (suid/sgid) bits in fuse client with killpriv_v2 enabled. Guest can cache that data for sometime even if cleared on server. Second and Third issue are fixable. Just that it might take a little while to get it fixed in kernel. First one will probably not see any movement for a long time. Given these issues, killpriv_v2 does not seem to be a good candidate for enabling by default. We have already disabled it by default in rust version of virtiofsd. Hence this patch disabled killpriv_v2 by default. User can choose to enable it by passing option "-o killpriv_v2". Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Message-Id: <YuPd0itNIAz4tQRt@redhat.com> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions