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;
Date:   Tue, 19 Apr 2022 16:18:48 +0200
From:   Max Kellermann <mk@cm4all.com>
To:     David Howells <dhowells@redhat.com>
Cc:     Max Kellermann <mk@cm4all.com>, linux-cachefs@redhat.com,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: fscache corruption in Linux 5.17?
Message-ID: <Yl7EyMLnqqDv63yW@rabbit.intern.cm-ag>
References: <YlWWbpW5Foynjllo@rabbit.intern.cm-ag>
 <454834.1650373340@warthog.procyon.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <454834.1650373340@warthog.procyon.org.uk>
Precedence: bulk

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