From: "Malte Schröder" <malte.schroeder@tnxip.de>
To: Matthew Wilcox <willy@infradead.org>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Miklos Szeredi <mszeredi@redhat.com>,
Josef Bacik <josef@toxicpanda.com>,
Joanne Koong <joannelkoong@gmail.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: silent data corruption in fuse in rc1
Date: Sun, 8 Dec 2024 21:02:37 +0100 [thread overview]
Message-ID: <68a165ea-e58a-40ef-923b-43dfd85ccd68@tnxip.de> (raw)
In-Reply-To: <Z1T09X8l3H5Wnxbv@casper.infradead.org>
On 08/12/2024 02:23, Matthew Wilcox wrote:
> On Sun, Dec 08, 2024 at 12:01:11AM +0100, Malte Schröder wrote:
>> Reverting fb527fc1f36e252cd1f62a26be4906949e7708ff fixes the issue for
>> me.
> That's a merge commit ... does the problem reproduce if you run
> d1dfb5f52ffc? And if it does, can you bisect the problem any further
> back? I'd recommend also testing v6.12-rc1; if that's good, bisect
> between those two.
>
> If the problem doesn't show up with d1dfb5f52ffc? then we have a dilly
> of an interaction to debug ;-(
I spent half a day compiling kernels, but bisect was non-conclusive.
There are some steps where the failure mode changes slightly, so this is
hard. It ended up at 445d9f05fa149556422f7fdd52dacf487cc8e7be which is
the nfsd-6.13 merge ...
d1dfb5f52ffc also shows the issue. I will try to narrow down from there.
/Malte
next prev parent reply other threads:[~2024-12-08 20:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 21:58 silent data corruption in fuse in rc1 Kent Overstreet
2024-12-07 23:01 ` Malte Schröder
2024-12-07 23:39 ` Kent Overstreet
2024-12-08 0:11 ` Malte Schröder
2024-12-08 1:23 ` Matthew Wilcox
2024-12-08 20:02 ` Malte Schröder [this message]
2024-12-08 22:32 ` Malte Schröder
2024-12-09 1:57 ` Jingbo Xu
2024-12-09 6:42 ` Malte Schröder
2024-12-09 8:06 ` Bernd Schubert
2024-12-09 9:07 ` Malte Schröder
2024-12-09 13:06 ` Bernd Schubert
2024-12-09 13:45 ` Malte Schröder
2024-12-09 14:49 ` Josef Bacik
2024-12-09 15:28 ` Matthew Wilcox
2024-12-09 15:48 ` Josef Bacik
2024-12-09 17:07 ` Malte Schröder
2024-12-09 18:47 ` Joanne Koong
2024-12-09 19:52 ` Joanne Koong
2024-12-10 5:14 ` Joanne Koong
2024-12-10 16:54 ` Kent Overstreet
2024-12-10 17:08 ` Matthew Wilcox
2024-12-10 17:43 ` Kent Overstreet
2024-12-10 17:31 ` Josef Bacik
2024-12-10 17:48 ` Kent Overstreet
2024-12-10 17:53 ` Malte Schröder
2024-12-11 2:57 ` Joanne Koong
2024-12-11 6:43 ` Kent Overstreet
2024-12-11 20:32 ` Joanne Koong
2024-12-11 14:01 ` Malte Schröder
2024-12-11 19:43 ` Joanne Koong
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=68a165ea-e58a-40ef-923b-43dfd85ccd68@tnxip.de \
--to=malte.schroeder@tnxip.de \
--cc=joannelkoong@gmail.com \
--cc=josef@toxicpanda.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=willy@infradead.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