vboxsf: explicitly deny setlease attempts
authorJeff Layton <jlayton@kernel.org>
Tue, 19 Mar 2024 16:32:04 +0000 (12:32 -0400)
committerHans de Goede <hdegoede@redhat.com>
Wed, 3 Apr 2024 14:06:39 +0000 (16:06 +0200)
vboxsf does not break leases on its own, so it can't properly handle the
case where the hypervisor changes the data. Don't allow file leases on
vboxsf.

Signed-off-by: Jeff Layton <jlayton@kernel.org>
Link: https://lore.kernel.org/r/20240319-setlease-v1-1-5997d67e04b3@kernel.org
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
fs/vboxsf/file.c

index 2307f8037efc3d3da4b6150fae4c42e125886005..118dedef8ebe8d4c8825ee1fff4e5b0a9ad9ff62 100644 (file)
@@ -218,6 +218,7 @@ const struct file_operations vboxsf_reg_fops = {
        .release = vboxsf_file_release,
        .fsync = noop_fsync,
        .splice_read = filemap_splice_read,
+       .setlease = simple_nosetlease,
 };
 
 const struct inode_operations vboxsf_reg_iops = {