From: Wanpeng Li <wanpeng.li@hotmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Subject: Re: [PATCH] mm/hwpoison: fix panic due to split huge zero page
Date: Wed, 12 Aug 2015 06:20:33 +0800 [thread overview]
Message-ID: <BLU436-SMTP1324E8C8AB9AA60DBF9C748807F0@phx.gbl> (raw)
In-Reply-To: <20150811141404.ecb19c1a66c32abf60d6663c@linux-foundation.org>
On 8/12/15 5:14 AM, Andrew Morton wrote:
> On Tue, 11 Aug 2015 18:47:57 +0800 Wanpeng Li <wanpeng.li@hotmail.com> wrote:
>
>> ...
>>
>> Huge zero page is allocated if page fault w/o FAULT_FLAG_WRITE flag.
>> The get_user_pages_fast() which called in madvise_hwpoison() will get
>> huge zero page if the page is not allocated before. Huge zero page is
>> a tranparent huge page, however, it is not an anonymous page. memory_failure
>> will split the huge zero page and trigger BUG_ON(is_huge_zero_page(page));
>> After commit (98ed2b0: mm/memory-failure: give up error handling for
>> non-tail-refcounted thp), memory_failure will not catch non anon thp
>> from madvise_hwpoison path and this bug occur.
> So I'm assuming this patch is needed for 4.2 but not in earlier
> kernels.
I think so. :-) Btw, how about my other hwpoison patches?
Regards,
Wanpeng Li
>
--
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 prev parent reply other threads:[~2015-08-11 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 10:47 Wanpeng Li
2015-08-11 21:14 ` Andrew Morton
2015-08-11 22:20 ` Wanpeng Li [this message]
2015-08-12 9:16 ` 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=BLU436-SMTP1324E8C8AB9AA60DBF9C748807F0@phx.gbl \
--to=wanpeng.li@hotmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox