This is a note to let you know that I've just added the patch titled cifs: revalidate mapping when doing direct writes to the 5.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: cifs-revalidate-mapping-when-doing-direct-writes.patch and it can be found in the queue-5.4 subdirectory. If you, or anyone else, feels it should not be added to the stable tree, please let <stable@xxxxxxxxxxxxxxx> know about it. >From 7500a99281dfed2d4a84771c933bcb9e17af279b Mon Sep 17 00:00:00 2001 From: Ronnie Sahlberg <lsahlber@xxxxxxxxxx> Date: Mon, 12 Sep 2022 13:04:46 +1000 Subject: cifs: revalidate mapping when doing direct writes From: Ronnie Sahlberg <lsahlber@xxxxxxxxxx> commit 7500a99281dfed2d4a84771c933bcb9e17af279b upstream. Kernel bugzilla: 216301 When doing direct writes we need to also invalidate the mapping in case we have a cached copy of the affected page(s) in memory or else subsequent reads of the data might return the old/stale content before we wrote an update to the server. Cc: stable@xxxxxxxxxxxxxxx Reviewed-by: Paulo Alcantara (SUSE) <pc@xxxxxx> Signed-off-by: Ronnie Sahlberg <lsahlber@xxxxxxxxxx> Signed-off-by: Steve French <stfrench@xxxxxxxxxxxxx> Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> --- fs/cifs/file.c | 3 +++ 1 file changed, 3 insertions(+) --- a/fs/cifs/file.c +++ b/fs/cifs/file.c @@ -3194,6 +3194,9 @@ static ssize_t __cifs_writev( ssize_t cifs_direct_writev(struct kiocb *iocb, struct iov_iter *from) { + struct file *file = iocb->ki_filp; + + cifs_revalidate_mapping(file->f_inode); return __cifs_writev(iocb, from, true); } Patches currently in stable-queue which might be from lsahlber@xxxxxxxxxx are queue-5.4/cifs-don-t-send-down-the-destination-address-to-sendmsg-for-a-sock_stream.patch queue-5.4/cifs-revalidate-mapping-when-doing-direct-writes.patch