From: Sasha Levin <sashal@kernel.org>
To: Shyam Prasad N <nspmangalore@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
David Howells <dhowells@redhat.com>,
Bharath SM <bharathsm.hsk@gmail.com>,
Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
Enzo Matsumiya <ematsumiya@suse.de>
Subject: Re: Request to backport data corruption fix to stable
Date: Fri, 14 Nov 2025 10:00:23 -0500 [thread overview]
Message-ID: <aRdEB6L0_vYwEsNT@laps> (raw)
In-Reply-To: <CANT5p=q22P+zXHW2vH-n+W-zRe7ZWNORgh9gvoUOGpV6VMF8Fg@mail.gmail.com>
On Fri, Nov 14, 2025 at 04:42:57PM +0530, Shyam Prasad N wrote:
>Hi Greg/Sasha,
>
>Over the last few months, a few users have reported a data corruption
>with Linux SMB kernel client filesystem. This is one such report:
>https://lore.kernel.org/linux-cifs/36fb31bf2c854cdc930a3415f5551dcd@izw-berlin.de/
>
>The issue is now well understood. Attached is a fix for this issue.
>I've made sure that the fix is stopping the data corruption and also
>not regressing other write patterns.
>
>The regression seems to have been introduced during a refactoring of
>this code path during the v6.3 and continued to exist till v6.9,
>before the code was refactored again with netfs helper library
>integration in v6.10.
>
>I request you to include this change in all stable trees for
>v6.3..v6.9. I've done my testing on stable-6.6. Please let me know if
>you want this tested on any other kernels.
I'll queue it up for 6.6, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-11-14 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 11:12 Request to backport data corruption fix to stable Shyam Prasad N
2025-11-14 15:00 ` Sasha Levin [this message]
2025-11-14 18:35 ` Steve French
2025-11-15 13:34 ` Sasha Levin
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=aRdEB6L0_vYwEsNT@laps \
--to=sashal@kernel.org \
--cc=bharathsm.hsk@gmail.com \
--cc=dhowells@redhat.com \
--cc=ematsumiya@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-cifs@vger.kernel.org \
--cc=nspmangalore@gmail.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