From: osalvador@suse.de
To: akpm@linux-foundation.org
Cc: naoya.horiguchi@nec.com, mhocko@kernel.org, tony.luck@intel.com,
cai@lca.pw, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 0/5] HWpoison: further fixes and cleanups
Date: Thu, 10 Sep 2020 22:07:48 +0200 [thread overview]
Message-ID: <861ca491140488d42d85ec7cef76ca0a@suse.de> (raw)
In-Reply-To: <20200908075626.11976-1-osalvador@suse.de>
On 2020-09-08 09:56, Oscar Salvador wrote:
> The important bit of this patchset is patch#1, which is a fix to take
> off
> HWPoison pages off a buddy freelist since it can lead us to having
> HWPoison
> pages back in the game without no one noticing it.
> So fix it (we did that already for soft_offline_page [1]).
>
> The other patches are clean-ups and not that important, so if anything,
> consider patch#1 for inclusion.
>
> [1] https://patchwork.kernel.org/cover/11704083/
>
> Thanks
>
> Oscar Salvador (5):
> mm,hwpoison: Take free pages off the buddy freelists
> mm,hwpoison: Refactor madvise_inject_error
> mm,hwpoison: Drain pcplists before bailing out for non-buddy
> zero-refcount page
> mm,hwpoison: Drop unneeded pcplist draining
> mm,hwpoison: Remove stale code
Naoya, any insight?
Thanks
prev parent reply other threads:[~2020-09-10 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 7:56 Oscar Salvador
2020-09-08 7:56 ` [PATCH v2 1/5] mm,hwpoison: Take free pages off the buddy freelists Oscar Salvador
2020-09-11 2:37 ` HORIGUCHI NAOYA(堀口 直也)
2020-09-08 7:56 ` [PATCH v2 2/5] mm,hwpoison: Refactor madvise_inject_error Oscar Salvador
2020-09-08 7:56 ` [PATCH v2 3/5] mm,hwpoison: Drain pcplists before bailing out for non-buddy zero-refcount page Oscar Salvador
2020-09-08 7:56 ` [PATCH v2 4/5] mm,hwpoison: Drop unneeded pcplist draining Oscar Salvador
2020-09-08 7:56 ` [PATCH v2 5/5] mm,hwpoison: Remove stale code Oscar Salvador
2020-09-10 20:07 ` osalvador [this message]
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=861ca491140488d42d85ec7cef76ca0a@suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=naoya.horiguchi@nec.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