public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Voegtle <tv@lio96.de>
Cc: stable@vger.kernel.org, David Howells <dhowells@redhat.com>,
	Steve French <stfrench@microsoft.com>
Subject: Re: 6.6.y: cifs broken since 6.6.23 writing big files with vers=1.0 and 2.0
Date: Wed, 12 Jun 2024 14:50:07 +0200	[thread overview]
Message-ID: <2024061242-supervise-uncaring-b8ed@gregkh> (raw)
In-Reply-To: <e519a2f6-eb49-e7e6-ab2e-beabc6cad090@lio96.de>

On Tue, Jun 11, 2024 at 09:20:33AM +0200, Thomas Voegtle wrote:
> 
> Hello,
> 
> a machine booted with Linux 6.6.23 up to 6.6.32:
> 
> writing /dev/zero with dd on a mounted cifs share with vers=1.0 or
> vers=2.0 slows down drastically in my setup after writing approx. 46GB of
> data.
> 
> The whole machine gets unresponsive as it was under very high IO load. It
> pings but opening a new ssh session needs too much time. I can stop the dd
> (ctrl-c) and after a few minutes the machine is fine again.
> 
> cifs with vers=3.1.1 seems to be fine with 6.6.32.
> Linux 6.10-rc3 is fine with vers=1.0 and vers=2.0.
> 
> Bisected down to:
> 
> cifs-fix-writeback-data-corruption.patch
> which is:
> Upstream commit f3dc1bdb6b0b0693562c7c54a6c28bafa608ba3c
> and
> linux-stable commit e45deec35bf7f1f4f992a707b2d04a8c162f2240
> 
> Reverting this patch on 6.6.32 fixes the problem for me.

Odd, that commit is kind of needed :(

Is there some later commit that resolves the issue here that we should
pick up for the stable trees?

thanks,

greg k-h

  reply	other threads:[~2024-06-12 12:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  7:20 6.6.y: cifs broken since 6.6.23 writing big files with vers=1.0 and 2.0 Thomas Voegtle
2024-06-12 12:50 ` Greg KH [this message]
2024-06-12 14:44   ` Thomas Voegtle
2024-06-12 14:53     ` Greg KH
2024-06-12 17:38       ` [EXTERNAL] " Steven French
2024-06-12 19:21         ` Thomas Voegtle
2024-06-13 18:38           ` Steven French
2024-06-13 19:21             ` Thomas Voegtle
2024-06-13 20:07               ` Steven French

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=2024061242-supervise-uncaring-b8ed@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dhowells@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=stfrench@microsoft.com \
    --cc=tv@lio96.de \
    /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