David Howells 61ea6b3a31 cifs: Fix setting of zero_point after DIO write ... At the moment, at the end of a DIO write, cifs calls netfs_resize_file() to adjust the size of the file if it needs it. This will reduce the zero_point (the point above which we assume a read will just return zeros) if it's more than the new i_size, but won't increase it. With DIO writes, however, we definitely want to increase it as we have clobbered the local pagecache and then written some data that's not available locally. Fix cifs to make the zero_point above the end of a DIO or unbuffered write. This fixes corruption seen occasionally with the generic/708 xfs-test. In that case, the read-back of some of the written data is being short-circuited and replaced with zeroes. Fixes: 3ee1a1fc39 ("cifs: Cut over to using netfslib") Cc: stable@vger.kernel.org Reported-by: Steve French <sfrench@samba.org> Signed-off-by: David Howells <dhowells@redhat.com> Reviewed-by: Paulo Alcantara (Red Hat) <pc@manguebit.com> cc: Jeff Layton <jlayton@kernel.org> cc: linux-cifs@vger.kernel.org cc: netfs@lists.linux.dev cc: linux-fsdevel@vger.kernel.org Signed-off-by: Steve French <stfrench@microsoft.com>		2024-07-19 11:08:57 -05:00
..
client	cifs: Fix setting of zero_point after DIO write	2024-07-19 11:08:57 -05:00
common	ksmbd: return FILE_DEVICE_DISK instead of super magic	2024-07-03 23:21:41 -05:00
server	ksmbd: discard write access to the directory open	2024-07-05 09:56:13 -05:00
Kconfig
Makefile