[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHc6FU4G5S+5S+1OdatY3apQvmDcvzOQSPPPQdQZTwMNjSq5tw@mail.gmail.com>
Date: Tue, 7 Mar 2023 16:23:50 +0100
From: Andreas Gruenbacher <agruenba@...hat.com>
To: Christoph Hellwig <hch@....de>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Matthew Wilcox <willy@...radead.org>,
Hugh Dickins <hughd@...gle.com>, linux-xfs@...r.kernel.org,
linux-nilfs@...r.kernel.org, cluster-devel@...hat.com,
linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-afs@...ts.infradead.org,
linux-btrfs@...r.kernel.org
Subject: Re: [Cluster-devel] return an ERR_PTR from __filemap_get_folio v3
On Tue, Mar 7, 2023 at 4:07 PM Christoph Hellwig <hch@....de> wrote:
> __filemap_get_folio and its wrappers can return NULL for three different
> conditions, which in some cases requires the caller to reverse engineer
> the decision making. This is fixed by returning an ERR_PTR instead of
> NULL and thus transporting the reason for the failure. But to make
> that work we first need to ensure that no xa_value special case is
> returned and thus return the FGP_ENTRY flag. It turns out that flag
> is barely used and can usually be deal with in a better way.
Thanks for working on this cleanup; looking good at a first glance.
Andreas
Powered by blists - more mailing lists