From: Steve French <smfrench@gmail.com>
To: Forest <forestix@nom.one>
Cc: David Howells <dhowells@redhat.com>,
Steve French <sfrench@samba.org>,
Shyam Prasad N <nspmangalore@gmail.com>,
Rohith Surabattula <rohiths.msft@gmail.com>,
Jeff Layton <jlayton@kernel.org>,
linux-cifs@vger.kernel.org, netfs@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] cifs: triggers bad flatpak & ostree signatures, corrupts ffmpeg & mkvmerge outputs
Date: Thu, 5 Sep 2024 19:46:40 -0500 [thread overview]
Message-ID: <CAH2r5muWjARBd67oXMCgZAkOekEd=naX6x_4aDhb8YXYBMm5Cw@mail.gmail.com> (raw)
In-Reply-To: <6jnidjladjose5gvv7nmofs008dlrd4cn3@sonic.net>
On Thu, Sep 5, 2024 at 2:32 AM Forest <forestix@nom.one> wrote:
>
> On Wed, 04 Sep 2024 23:01:51 +0100, David Howells wrote:
>
> >Forest <forestix@nom.one> wrote:
> >
> >> Write corruption still exists in 6.11.0-rc6.
> >
> >Can you try adding this:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c26096ee0278c5e765009c5eee427bbafe6dc090
>
>
> That patch looks promising. With it, I've run my tests 2-3 times more than
> usual, and there has been no sign of the corrupt writes so far. Thank you!
>
> >Unfortunately, it managed to miss -rc6 because Linus released early before the
> >PR could be sent to him.
>
> Will these fixes be applied to the 6.10 series as well?
It is queued for 6.10 stable based on recent email from Greg KH - see
email titled:
[PATCH 6.10 181/184] mm: Fix filemap_invalidate_inode() to use
invalidate_inode_pages2_range()
--
Thanks,
Steve
prev parent reply other threads:[~2024-09-06 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 1:50 Forest
2024-08-27 18:38 ` Forest
2024-09-04 21:02 ` Forest
2024-09-04 22:01 ` David Howells
2024-09-05 7:32 ` Forest
2024-09-06 0:46 ` Steve French [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='CAH2r5muWjARBd67oXMCgZAkOekEd=naX6x_4aDhb8YXYBMm5Cw@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=dhowells@redhat.com \
--cc=forestix@nom.one \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netfs@lists.linux.dev \
--cc=nspmangalore@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=rohiths.msft@gmail.com \
--cc=sfrench@samba.org \
--cc=stable@vger.kernel.org \
/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