From: Vlastimil Babka <vbabka@suse.cz>
To: Oscar Salvador <osalvador@suse.de>, n-horiguchi@ah.jp.nec.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/4] mm,hwpoison: take free pages off the buddy freelists for hugetlb
Date: Wed, 25 Nov 2020 17:36:25 +0100 [thread overview]
Message-ID: <440ab1e0-1b69-f2e5-a07a-31861aa2b633@suse.cz> (raw)
In-Reply-To: <20201013144447.6706-4-osalvador@suse.de>
On 10/13/20 4:44 PM, Oscar Salvador wrote:
> Currently, free hugetlb get dissolved, but we also need to make sure
> to take the poisoned subpage off the buddy frelists, so no one stumbles
> upon it (see previous patch for more information).
>
> Signed-off-by: Oscar Salvador <osalvador@suse.de>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
> ---
> mm/memory-failure.c | 19 +++++++++++++------
> 1 file changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
> index 181bed890c16..30aadeca97d2 100644
> --- a/mm/memory-failure.c
> +++ b/mm/memory-failure.c
> @@ -809,7 +809,7 @@ static int me_swapcache_clean(struct page *p, unsigned long pfn)
> */
> static int me_huge_page(struct page *p, unsigned long pfn)
> {
> - int res = 0;
> + int res;
> struct page *hpage = compound_head(p);
> struct address_space *mapping;
>
> @@ -820,6 +820,7 @@ static int me_huge_page(struct page *p, unsigned long pfn)
> if (mapping) {
> res = truncate_error_page(hpage, pfn, mapping);
> } else {
> + res = MF_FAILED;
> unlock_page(hpage);
> /*
> * migration entry prevents later access on error anonymous
> @@ -828,8 +829,10 @@ static int me_huge_page(struct page *p, unsigned long pfn)
> */
> if (PageAnon(hpage))
> put_page(hpage);
> - dissolve_free_huge_page(p);
> - res = MF_RECOVERED;
> + if (!dissolve_free_huge_page(p) && take_page_off_buddy(p)) {
> + page_ref_inc(p);
> + res = MF_RECOVERED;
> + }
> lock_page(hpage);
> }
>
> @@ -1198,9 +1201,13 @@ static int memory_failure_hugetlb(unsigned long pfn, int flags)
> }
> }
> unlock_page(head);
> - dissolve_free_huge_page(p);
> - action_result(pfn, MF_MSG_FREE_HUGE, MF_DELAYED);
> - return 0;
> + res = MF_FAILED;
> + if (!dissolve_free_huge_page(p) && take_page_off_buddy(p)) {
> + page_ref_inc(p);
> + res = MF_RECOVERED;
> + }
> + action_result(pfn, MF_MSG_FREE_HUGE, res);
> + return res == MF_RECOVERED ? 0 : -EBUSY;
> }
>
> lock_page(head);
>
next prev parent reply other threads:[~2020-11-25 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 14:44 [PATCH v5 0/4] HWpoison: further fixes and cleanups Oscar Salvador
2020-10-13 14:44 ` [PATCH v5 1/4] mm,hwpoison: drain pcplists before bailing out for non-buddy zero-refcount page Oscar Salvador
2020-11-25 16:26 ` Vlastimil Babka
2020-10-13 14:44 ` [PATCH v5 2/4] mm,hwpoison: take free pages off the buddy freelists Oscar Salvador
2020-11-25 16:35 ` Vlastimil Babka
2020-10-13 14:44 ` [PATCH v5 3/4] mm,hwpoison: take free pages off the buddy freelists for hugetlb Oscar Salvador
2020-10-14 0:05 ` HORIGUCHI NAOYA(堀口 直也)
2020-11-25 16:36 ` Vlastimil Babka [this message]
2020-10-13 14:44 ` [PATCH v5 4/4] mm,hwpoison: drop unneeded pcplist draining Oscar Salvador
2020-10-14 0:06 ` HORIGUCHI NAOYA(堀口 直也)
2020-11-25 16:38 ` Vlastimil Babka
2020-11-10 6:21 ` [PATCH v5 0/4] HWpoison: further fixes and cleanups Oscar Salvador
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=440ab1e0-1b69-f2e5-a07a-31861aa2b633@suse.cz \
--to=vbabka@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=osalvador@suse.de \
/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