From: Paulo Alcantara <pc@cjr.nz>
To: Ronnie Sahlberg <lsahlber@redhat.com>,
linux-cifs <linux-cifs@vger.kernel.org>
Cc: Steve French <smfrench@gmail.com>, Ronnie Sahlberg <lsahlber@redhat.com>
Subject: Re: [PATCH] cifs: revalidate mapping when doing direct writes
Date: Mon, 12 Sep 2022 08:57:17 -0700 [thread overview]
Message-ID: <874jxcoaaq.fsf@cjr.nz> (raw)
In-Reply-To: <20220912030446.173296-2-lsahlber@redhat.com>
Ronnie Sahlberg <lsahlber@redhat.com> writes:
> 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.
>
> Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
> ---
> fs/cifs/file.c | 3 +++
> 1 file changed, 3 insertions(+)
Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
prev parent reply other threads:[~2022-09-12 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 3:04 Cifs: fix kbz 216301: return corrupt/stale file content Ronnie Sahlberg
2022-09-12 3:04 ` [PATCH] cifs: revalidate mapping when doing direct writes Ronnie Sahlberg
[not found] ` <CAH2r5mvh5_XbVxu0idZgt5A=zEr=4k7DF8Omf4VZOdrgCNkOfA@mail.gmail.com>
2022-09-12 5:32 ` Fwd: " Steve French
2022-09-12 15:57 ` Paulo Alcantara [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jxcoaaq.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=linux-cifs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=smfrench@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).