[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230717120002.8da3920c4006295bfb5234cb@linux-foundation.org>
Date: Mon, 17 Jul 2023 12:00:02 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Sidhartha Kumar <sidhartha.kumar@...cle.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
willy@...radead.org, linmiaohe@...wei.com, naoya.horiguchi@....com,
stable@...r.kernel.org
Subject: Re: [PATCH] mm/memory-failure: fix hardware poison check in
unpoison_memory()
On Mon, 17 Jul 2023 11:18:12 -0700 Sidhartha Kumar <sidhartha.kumar@...cle.com> wrote:
> It was pointed out[1] that using folio_test_hwpoison() is wrong
> as we need to check the indiviual page that has poison.
> folio_test_hwpoison() only checks the head page so go back to using
> PageHWPoison().
Please describe the user-visible effects of the bug, especially
when proposing a -stable backport.
Powered by blists - more mailing lists