From: Max Kellermann <mk@cm4all.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Max Kellermann <mk@cm4all.com>,
dhowells@redhat.com, linux-cachefs@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: fscache corruption in Linux 5.17?
Date: Sat, 16 Apr 2022 21:55:54 +0200 [thread overview]
Message-ID: <YlsfSqysfKJqwDVz@rabbit.intern.cm-ag> (raw)
In-Reply-To: <c6b80014-846d-cd90-7e67-d72959ffabe1@leemhuis.info>
On 2022/04/16 13:38, Thorsten Leemhuis <regressions@leemhuis.info> wrote:
> Thx for the report. Maybe a bisection is what's needed here, but lets
> see what David says, maybe he has a idea already.
I wish I could do that, but it's very hard to reproduce; the first
reports came after a week or so. That way, a bisect would take
months. So yes, wait for David, because he might give a clue how to
trigger the problem more quickly to make a bisect practical.
next prev parent reply other threads:[~2022-04-16 19:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 15:10 fscache corruption in Linux 5.17? Max Kellermann
2022-04-16 11:38 ` Thorsten Leemhuis
2022-04-16 19:55 ` Max Kellermann [this message]
2022-04-19 13:02 ` David Howells
2022-04-19 14:18 ` Max Kellermann
2022-04-19 15:23 ` [Linux-cachefs] " David Wysochanski
2022-04-19 16:17 ` David Howells
2022-04-19 16:41 ` Max Kellermann
2022-04-19 16:47 ` David Howells
2022-04-19 15:56 ` David Howells
2022-04-19 16:06 ` Max Kellermann
2022-04-19 16:42 ` David Howells
2022-04-19 18:01 ` Max Kellermann
2022-04-19 21:27 ` Max Kellermann
2022-04-20 13:55 ` David Howells
2022-05-04 8:38 ` Max Kellermann
2022-05-31 8:35 ` David Howells
2022-05-31 8:41 ` Max Kellermann
2022-05-31 9:13 ` David Howells
2022-06-20 7:11 ` Thorsten Leemhuis
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=YlsfSqysfKJqwDVz@rabbit.intern.cm-ag \
--to=mk@cm4all.com \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).