From: Naoya Horiguchi <nao.horiguchi@gmail.com>
To: Oscar Salvador <osalvador@suse.de>,
Muchun Song <songmuchun@bytedance.com>,
linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Michal Hocko <mhocko@suse.com>, Tony Luck <tony.luck@intel.com>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] hwpoison: fix race with compound page allocation
Date: Wed, 12 May 2021 00:10:14 +0900 [thread overview]
Message-ID: <20210511151016.2310627-1-nao.horiguchi@gmail.com> (raw)
Hi everyone,
I updated the patch for the issue reported by Muchun Song in [1]. I
separated into two patches (to reduce the size of core fix for stable):
patch 1/2 focuses on preventing VM_BUG_ON_PAGE() in the reported race.
Patch 2/2 includes some code improvement like calling retry code, revising
the function comment, and some refactoring.
Any comment and testing would be appreciated.
Thanks,
Naoya Horiguchi
[1] https://lore.kernel.org/linux-mm/20210421060259.67554-1-songmuchun@bytedance.com/T/
---
Summary:
Naoya Horiguchi (2):
mm,hwpoison: fix race with compound page allocation
mm,hwpoison: make get_hwpoison_page call get_any_page()
mm/memory-failure.c | 169 +++++++++++++++++++++++++++++-----------------------
1 file changed, 96 insertions(+), 73 deletions(-)
next reply other threads:[~2021-05-11 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 15:10 Naoya Horiguchi [this message]
2021-05-11 15:10 ` [PATCH v3 1/2] mm,hwpoison: fix race with compound page allocation Naoya Horiguchi
2021-05-12 8:33 ` Oscar Salvador
2021-05-13 0:00 ` HORIGUCHI NAOYA(堀口 直也)
2021-05-12 12:19 ` Michal Hocko
2021-05-12 23:51 ` HORIGUCHI NAOYA(堀口 直也)
2021-05-11 15:10 ` [PATCH v3 2/2] mm,hwpoison: make get_hwpoison_page call get_any_page() Naoya Horiguchi
2021-05-12 8:55 ` Oscar Salvador
2021-05-13 0:03 ` HORIGUCHI NAOYA(堀口 直也)
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=20210511151016.2310627-1-nao.horiguchi@gmail.com \
--to=nao.horiguchi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=songmuchun@bytedance.com \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).