[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230118164208.GA7584@lst.de>
Date: Wed, 18 Jan 2023 17:42:08 +0100
From: Christoph Hellwig <hch@....de>
To: Ryusuke Konishi <konishi.ryusuke@...il.com>
Cc: Christoph Hellwig <hch@....de>,
Andrew Morton <akpm@...ux-foundation.org>,
Matthew Wilcox <willy@...radead.org>,
Hugh Dickins <hughd@...gle.com>, linux-afs@...ts.infradead.org,
linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org,
cluster-devel@...hat.com, linux-mm@...ck.org,
linux-xfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-nilfs@...r.kernel.org
Subject: Re: [PATCH 9/9] mm: return an ERR_PTR from __filemap_get_folio
On Wed, Jan 18, 2023 at 09:39:08PM +0900, Ryusuke Konishi wrote:
> > Also pass through the error through the direct callers:
>
> > filemap_get_folio, filemap_lock_folio filemap_grab_folio
> > and filemap_get_incore_folio.
>
> As for the comments describing the return values of these callers,
> isn't it necessary to rewrite the value from NULL in case of errors ?
Yes, thanks for catching this.
Powered by blists - more mailing lists