From: Vlastimil Babka <vbabka@suse.cz>
To: Mel Gorman <mgorman@techsingularity.net>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Naoya Horiguchi <nao.horiguchi@gmail.com>
Subject: Re: [PATCH v2] mm: check_new_page_bad() directly returns in __PG_HWPOISON case
Date: Fri, 20 May 2016 16:27:12 +0200 [thread overview]
Message-ID: <573F1EC0.6030801@suse.cz> (raw)
In-Reply-To: <20160518140337.GG2527@techsingularity.net>
On 05/18/2016 04:03 PM, Mel Gorman wrote:
> On Wed, May 18, 2016 at 10:09:50AM +0000, Naoya Horiguchi wrote:
>> From c600b1ee6c36b3df6973f5365b4179c92f3c08e3 Mon Sep 17 00:00:00 2001
>> From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
>> Date: Wed, 18 May 2016 18:42:57 +0900
>> Subject: [PATCH v2] mm: check_new_page_bad() directly returns in __PG_HWPOISON
>> case
>>
>> Currently we check page->flags twice for "HWPoisoned" case of
>> check_new_page_bad(), which can cause a race with unpoisoning.
>> This race unnecessarily taints kernel with "BUG: Bad page state".
>> check_new_page_bad() is the only caller of bad_page() which is interested
>> in __PG_HWPOISON, so let's move the hwpoison related code in bad_page()
>> to it.
>>
>> Signed-off-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
>
> Acked-by: Mel Gorman <mgorman@techsingularity.net>
>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz>
To: Mel Gorman <mgorman@techsingularity.net>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Naoya Horiguchi <nao.horiguchi@gmail.com>
Subject: Re: [PATCH v2] mm: check_new_page_bad() directly returns in __PG_HWPOISON case
Date: Fri, 20 May 2016 16:27:12 +0200 [thread overview]
Message-ID: <573F1EC0.6030801@suse.cz> (raw)
In-Reply-To: <20160518140337.GG2527@techsingularity.net>
On 05/18/2016 04:03 PM, Mel Gorman wrote:
> On Wed, May 18, 2016 at 10:09:50AM +0000, Naoya Horiguchi wrote:
>> From c600b1ee6c36b3df6973f5365b4179c92f3c08e3 Mon Sep 17 00:00:00 2001
>> From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
>> Date: Wed, 18 May 2016 18:42:57 +0900
>> Subject: [PATCH v2] mm: check_new_page_bad() directly returns in __PG_HWPOISON
>> case
>>
>> Currently we check page->flags twice for "HWPoisoned" case of
>> check_new_page_bad(), which can cause a race with unpoisoning.
>> This race unnecessarily taints kernel with "BUG: Bad page state".
>> check_new_page_bad() is the only caller of bad_page() which is interested
>> in __PG_HWPOISON, so let's move the hwpoison related code in bad_page()
>> to it.
>>
>> Signed-off-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
>
> Acked-by: Mel Gorman <mgorman@techsingularity.net>
>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
next prev parent reply other threads:[~2016-05-20 14:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 7:42 [PATCH v1] mm: bad_page() checks bad_flags instead of page->flags for hwpoison page Naoya Horiguchi
2016-05-17 7:42 ` Naoya Horiguchi
2016-05-18 7:30 ` Vlastimil Babka
2016-05-18 7:30 ` Vlastimil Babka
2016-05-18 9:21 ` Mel Gorman
2016-05-18 9:21 ` Mel Gorman
2016-05-18 9:31 ` Vlastimil Babka
2016-05-18 9:31 ` Vlastimil Babka
2016-05-18 9:52 ` Mel Gorman
2016-05-18 9:52 ` Mel Gorman
2016-05-18 10:17 ` Naoya Horiguchi
2016-05-18 10:17 ` Naoya Horiguchi
2016-05-18 10:09 ` [PATCH v2] mm: check_new_page_bad() directly returns in __PG_HWPOISON case Naoya Horiguchi
2016-05-18 10:09 ` Naoya Horiguchi
2016-05-18 14:03 ` Mel Gorman
2016-05-18 14:03 ` Mel Gorman
2016-05-20 14:27 ` Vlastimil Babka [this message]
2016-05-20 14:27 ` Vlastimil Babka
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=573F1EC0.6030801@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=nao.horiguchi@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.