[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201015140631.GZ20115@casper.infradead.org>
Date: Thu, 15 Oct 2020 15:06:31 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
v9fs-developer@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
linux-afs@...ts.infradead.org, ceph-devel@...r.kernel.org,
linux-cifs@...r.kernel.org, ecryptfs@...r.kernel.org,
linux-um@...ts.infradead.org, linux-mtd@...ts.infradead.org,
Richard Weinberger <richard@....at>, linux-xfs@...r.kernel.org
Subject: Re: [PATCH v2 01/16] mm: Add AOP_UPDATED_PAGE return value
On Thu, Oct 15, 2020 at 10:06:51AM +0100, Christoph Hellwig wrote:
> Don't we also need to handle the new return value in a few other places
> like cachefiles_read_reissue swap_readpage? Maybe those don't get
> called on the currently converted instances, but just leaving them
> without handling AOP_UPDATED_PAGE seems like a time bomb.
Er, right. And nobh_truncate_page(), and read_page(). And then I
noticed the bug in cachefiles_read_reissue(). Sigh.
Updated patch series coming soon.
Powered by blists - more mailing lists