From: Wanpeng Li <wanpeng.li@hotmail.com>
To: 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>
Subject: Re: [PATCH v2 5/5] mm/hwpoison: replace most of put_page in memory error handling by put_hwpoison_page
Date: Wed, 12 Aug 2015 17:13:39 +0800 [thread overview]
Message-ID: <BLU436-SMTP111993C22274095EC6F2FAE807E0@phx.gbl> (raw)
In-Reply-To: <20150812085525.GD32192@hori1.linux.bs1.fc.nec.co.jp>
On 8/12/15 4:55 PM, Naoya Horiguchi wrote:
> On Mon, Aug 10, 2015 at 07:28:23PM +0800, Wanpeng Li wrote:
>> Replace most of put_page in memory error handling by put_hwpoison_page,
>> except the ones at the front of soft_offline_page since the page maybe
>> THP page and the get refcount in madvise_hwpoison is against the single
>> 4KB page instead of the logic in get_hwpoison_page.
>>
>> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com>
> # Sorry for my late response.
>
> If I read correctly, get_user_pages_fast() (called by madvise_hwpoison)
> for a THP tail page takes a refcount from each of head and tail page.
> gup_huge_pmd() does this in the fast path, and get_page_foll() does this
> in the slow path (maybe via the following code path)
>
> get_user_pages_unlocked
> __get_user_pages_unlocked
> __get_user_pages_locked
> __get_user_pages
> follow_page_mask
> follow_trans_huge_pmd (with FOLL_GET set)
> get_page_foll
>
> So this should be equivalent to what get_hwpoison_page() does for thp pages
> with regard to refcounting.
>
> And I'm expecting that a refcount taken by get_hwpoison_page() is released
> by put_hwpoison_page() even if the page's status is changed during error
> handling (the typical (or only?) case is successful thp split.)
Indeed. :-)
>
> So I think you can apply put_hwpoison_page() for 3 more callsites in
> mm/memory-failure.c.
> - MF_MSG_POISONED_HUGE case
I have already done this in my patch.
> - "soft offline: %#lx page already poisoned" case (you mentioned above)
> - "soft offline: %#lx: failed to split THP" case (you mentioned above)
You are right, I will send a patch rebased on this one since they are
merged.
Regards,
Wanpeng Li
>
> Thanks,
> Naoya Horiguchi
--
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-12 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1439206103-86829-1-git-send-email-wanpeng.li@hotmail.com>
2015-08-10 11:28 ` [PATCH v2 2/5] mm/hwpoison: fix PageHWPoison test/set race Wanpeng Li
2015-08-10 11:28 ` [PATCH v2 3/5] mm/hwpoison: introduce put_hwpoison_page to put refcount for memory error handling Wanpeng Li
2015-08-11 23:24 ` Andrew Morton
2015-08-11 23:51 ` Wanpeng Li
2015-08-12 2:30 ` Wanpeng Li
2015-08-12 8:58 ` Naoya Horiguchi
2015-08-10 11:28 ` [PATCH v2 4/5] mm/hwpoison: fix refcount of THP head page in no-injection case Wanpeng Li
2015-08-12 8:58 ` Naoya Horiguchi
2015-08-10 11:28 ` [PATCH v2 5/5] mm/hwpoison: replace most of put_page in memory error handling by put_hwpoison_page Wanpeng Li
2015-08-12 8:55 ` Naoya Horiguchi
2015-08-12 9:13 ` Wanpeng Li [this message]
2015-08-12 9:35 ` Wanpeng Li
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-SMTP111993C22274095EC6F2FAE807E0@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