Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <YlWWbpW5Foynjllo@rabbit.intern.cm-ag> <454834.1650373340@warthog.procyon.org.uk>
 <Yl7EyMLnqqDv63yW@rabbit.intern.cm-ag>
In-Reply-To: <Yl7EyMLnqqDv63yW@rabbit.intern.cm-ag>
From:   David Wysochanski <dwysocha@redhat.com>
Date:   Tue, 19 Apr 2022 11:23:42 -0400
Message-ID: <CALF+zOnxxvDPd6L=W6N0WnS_jbYLBDfENKTousT36jQ37h_Vnw@mail.gmail.com>
Subject: Re: [Linux-cachefs] fscache corruption in Linux 5.17?
To:     Max Kellermann <mk@cm4all.com>
Cc:     David Howells <dhowells@redhat.com>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>,
        linux-cachefs <linux-cachefs@redhat.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Apr 19, 2022 at 10:19 AM Max Kellermann <mk@cm4all.com> wrote:
>
> On 2022/04/19 15:02, David Howells <dhowells@redhat.com> wrote:
> > I presume you are actually using a cache?
>
> Yes, see:
>
> On 2022/04/12 17:10, Max Kellermann <max@rabbit.intern.cm-ag> wrote:
> > All web servers mount a storage via NFSv3 with fscache.
>
> At least one web server is still in this broken state right now.  So
> if you need anything from that server, tell me, and I'll get it.
>
> I will need to downgrade to 5.16 tomorrow to get rid of the corruption
> bug (I've delayed this for a week, waiting for your reply).  After
> tomorrow, I can no longer help debugging this.
>
> Max
>

FWIW, I just noticed one of my unit tests is failing with data
corruption with NFSv3 only (NFS4.x does not fail) on 5.18.0-rc3 - not
sure how repeatable it is.
I'll see what I can find out.