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, 31 May 2022 10:41:17 +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: <YpXUrclhwN+oOlfj@rabbit.intern.cm-ag>
References: <YnI7lgazkdi6jcve@rabbit.intern.cm-ag>
 <Yl75D02pXj71kQBx@rabbit.intern.cm-ag>
 <Yl7d++G25sNXIR+p@rabbit.intern.cm-ag>
 <YlWWbpW5Foynjllo@rabbit.intern.cm-ag>
 <507518.1650383808@warthog.procyon.org.uk>
 <509961.1650386569@warthog.procyon.org.uk>
 <705278.1650462934@warthog.procyon.org.uk>
 <263652.1653986121@warthog.procyon.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <263652.1653986121@warthog.procyon.org.uk>
Precedence: bulk

On 2022/05/31 10:35, David Howells <dhowells@redhat.com> wrote:
> Max Kellermann <mk@cm4all.com> wrote:
> 
> > On 2022/04/20 15:55, David Howells <dhowells@redhat.com> wrote:
> > > I have a tentative patch for this - see attached.
> > 
> > Quick feedback: your patch has been running on our servers for two
> > weeks, and I have received no new complaints about corrupted files.
> > That doesn't prove the patch is correct or that it really solves my
> > problem, but anyway it's a good sign.  Thanks so far.
> 
> Can I put that down as a Tested-by?

Yes.  A month later, still no new corruption.