From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Wang Xiaoqiang <wangxq10@lzu.edu.cn>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] memory_failure: remove redundant check for the PG_HWPoison flag of 'hpage'
Date: Wed, 29 Jul 2015 09:17:32 +0000 [thread overview]
Message-ID: <20150729091725.GA1256@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <20150729155246.2fed1b96@hp>
# CC:ed linux-mm
Hi Xiaoqiang,
On Wed, Jul 29, 2015 at 03:52:46PM +0800, Wang Xiaoqiang wrote:
> Hi,
>
> I find a little problem in the memory_failure function in
> mm/memory-failure.c . Please check it.
>
> memory_failure: remove redundant check for the PG_HWPoison flag of
> `hpage'.
>
> Since we have check the PG_HWPoison flag by `PageHWPoison' before,
> so the later check by `TestSetPageHWPoison' must return true, there
> is no need to check again!
I'm afraid that this TestSetPageHWPoison is not redundant, because this code
serializes the concurrent memory error events over the same hugetlb page
(, where 'p' indicates the 4kB error page and 'hpage' indicates the head page.)
When an error hits a hugetlb page, set_page_hwpoison_huge_page() sets
PageHWPoison flags over all subpages of the hugetlb page in the ascending
order of pfn. So if we don't have this TestSet, memory error handler can
run more than once on concurrent errors when the 1st memory error hits
(for example) the 100th subpage and the 2nd memory error hits (for example)
the 50th subpage.
Thanks,
Naoya Horiguchi
> Signed-off-by: Wang Xiaoqiang <wangxq10@lzu.edu.cn>
> ---
> mm/memory-failure.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index 1cf7f29..7794fd8 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -1115,7 +1115,7 @@ int memory_failure(unsigned long pfn, int trapno, int flags)
> lock_page(hpage);
> if (PageHWPoison(hpage)) {
> if ((hwpoison_filter(p) && TestClearPageHWPoison(p))
> - || (p != hpage && TestSetPageHWPoison(hpage))) {
> + || p != hpage) {
> atomic_long_sub(nr_pages, &num_poisoned_pages);
> unlock_page(hpage);
> return 0;
> --
> 1.7.10.4
>
>
>
> --
> thx!
> Wang Xiaoqiang
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2015-07-29 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150729155246.2fed1b96@hp>
2015-07-29 9:17 ` Naoya Horiguchi [this message]
2015-07-30 2:52 ` Wang Xiaoqiang
2015-07-31 8:12 ` Naoya Horiguchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150729091725.GA1256@hori1.linux.bs1.fc.nec.co.jp \
--to=n-horiguchi@ah.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wangxq10@lzu.edu.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox