From 326836a1ebc6ce9b28c8f2bc1d177a444fba8ea6 Mon Sep 17 00:00:00 2001 From: Konstantin Belousov Date: Sat, 18 Nov 2023 11:23:22 +0200 Subject: [PATCH] nullfs: do not allow bypass on copy_file_range() There must be no callers of VOP_COPY_FILE_RANGE() except vn_copy_file_range(), which does enough to find the write-vnodes where to call the VOP. Reviewed by: markj, Olivier Certner Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D42603 --- sys/fs/nullfs/null_vnops.c | 1 + 1 file changed, 1 insertion(+) diff --git a/sys/fs/nullfs/null_vnops.c b/sys/fs/nullfs/null_vnops.c index c05e3394a9a6..4747b1dd5b82 100644 --- a/sys/fs/nullfs/null_vnops.c +++ b/sys/fs/nullfs/null_vnops.c @@ -1177,5 +1177,6 @@ struct vop_vector null_vnodeops = { .vop_vptofh = null_vptofh, .vop_add_writecount = null_add_writecount, .vop_vput_pair = null_vput_pair, + .vop_copy_file_range = VOP_PANIC, }; VFS_VOP_VECTOR_REGISTER(null_vnodeops);