[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZENO4vZzmN8lJocK@bombadil.infradead.org>
Date: Fri, 21 Apr 2023 20:05:06 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: hughd@...gle.com, akpm@...ux-foundation.org, brauner@...nel.org,
djwong@...nel.org, p.raghav@...sung.com, da.gomez@...sung.com,
a.manzanares@...sung.com, dave@...olabs.net, yosryahmed@...gle.com,
keescook@...omium.org, hare@...e.de, kbusch@...nel.org,
patches@...ts.linux.dev, linux-block@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC 2/8] shmem: convert to use folio_test_hwpoison()
On Fri, Apr 21, 2023 at 11:42:53PM +0100, Matthew Wilcox wrote:
> On Fri, Apr 21, 2023 at 02:43:54PM -0700, Luis Chamberlain wrote:
> > The PageHWPoison() call can be converted over to the respective folio call
> > folio_test_hwpoison(). This introduces no functional changes.
>
> Um, no. Nobody should use folio_test_hwpoison(), it's a nonsense.
>
> Individual pages are hwpoisoned. You're only testing the head page
> if you use folio_test_hwpoison(). There's folio_has_hwpoisoned() to
> test if _any_ page in the folio is poisoned. But blindly converting
> PageHWPoison to folio_test_hwpoison() is wrong.
Thanks! I don't see folio_has_hwpoisoned() though.
Luis
Powered by blists - more mailing lists