From: Matthew Wilcox <willy@infradead.org>
To: Daniel Dao <dqminh@cloudflare.com>
Cc: Dave Chinner <david@fromorbit.com>,
djwong@kernel.org, kernel-team <kernel-team@cloudflare.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: Backporting of series xfs/iomap: fix data corruption due to stale cached iomap
Date: Thu, 29 Jun 2023 17:34:00 +0100 [thread overview]
Message-ID: <ZJ2yeJR5TB4AyQIn@casper.infradead.org> (raw)
In-Reply-To: <CA+wXwBRdcjHW2zxDABdFU3c26mc1u+g6iWG7HrXJRL7Po3Qp0w@mail.gmail.com>
On Thu, Jun 29, 2023 at 05:09:41PM +0100, Daniel Dao wrote:
> Hi Dave and Derrick,
>
> We are tracking down some corruptions on xfs for our rocksdb workload,
> running on kernel 6.1.25. The corruptions were
> detected by rocksdb block checksum. The workload seems to share some
> similarities
> with the multi-threaded write workload described in
> https://lore.kernel.org/linux-fsdevel/20221129001632.GX3600936@dread.disaster.area/
>
> Can we backport the patch series to stable since it seemed to fix data
> corruptions ?
For clarity, are you asking for permission or advice about doing this
yourself, or are you asking somebody else to do the backport for you?
next prev parent reply other threads:[~2023-06-29 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 16:09 Backporting of series xfs/iomap: fix data corruption due to stale cached iomap Daniel Dao
2023-06-29 16:34 ` Matthew Wilcox [this message]
2023-06-29 18:14 ` Darrick J. Wong
2023-06-29 19:30 ` Ignat Korchagin
2023-06-30 10:39 ` Amir Goldstein
2023-06-30 12:30 ` Ignat Korchagin
2023-06-30 13:05 ` Amir Goldstein
2023-06-30 15:16 ` Darrick J. Wong
2023-07-19 20:37 ` Ignat Korchagin
2023-07-20 6:45 ` Amir Goldstein
2023-07-20 18:30 ` Luis Chamberlain
2023-07-20 18:38 ` Frederick Lawler
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=ZJ2yeJR5TB4AyQIn@casper.infradead.org \
--to=willy@infradead.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=dqminh@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).