From: Oscar Salvador <osalvador@suse.de>
To: Michal Hocko <mhocko@kernel.org>
Cc: David Hildenbrand <david@redhat.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <OSalvador@suse.com>
Subject: Re: [PATCH v2 2/2] mm/memory-failure.c: Don't access uninitialized memmaps in memory_failure()
Date: Tue, 15 Oct 2019 16:23:44 +0200 [thread overview]
Message-ID: <20191015142340.GA5686@linux> (raw)
In-Reply-To: <20191014133617.GJ317@dhcp22.suse.cz>
On Mon, Oct 14, 2019 at 03:36:17PM +0200, Michal Hocko wrote:
> I do agree. The two should be really using the same code. My
> understanding was that MADV_HWPOISON was there to test the actual MCE
> behavior (and the man page seems to agree with that).
>
> Oscar is working on a rewrite. Not sure he has considered this as well.
Yeah, I came across hwpoison-inject module when doing my re-write,
and I felt like this is begging for a clean up.
Since unpoison_memory needs some adjustments after my re-write, I will go ahead
and clean that up, otherwise it will be inconsistent.
I expect to be ready fo send the v2 by the end of this week.
Thanks
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2019-10-15 14:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 14:24 [PATCH v2 0/2] mm: Don't access uninitialized memmaps in PFN walkers David Hildenbrand
2019-10-09 14:24 ` [PATCH v2 1/2] mm: Don't access uninitialized memmaps in fs/proc/page.c David Hildenbrand
2019-10-09 14:41 ` Michal Hocko
2019-10-14 8:44 ` David Hildenbrand
2019-10-09 14:24 ` [PATCH v2 2/2] mm/memory-failure.c: Don't access uninitialized memmaps in memory_failure() David Hildenbrand
2019-10-09 14:43 ` Michal Hocko
2019-10-10 7:27 ` David Hildenbrand
2019-10-10 7:35 ` Michal Hocko
2019-10-10 7:52 ` David Hildenbrand
2019-10-10 7:58 ` David Hildenbrand
2019-10-11 6:02 ` Naoya Horiguchi
2019-10-11 10:13 ` David Hildenbrand
2019-10-14 13:36 ` Michal Hocko
2019-10-15 14:23 ` Oscar Salvador [this message]
2019-10-10 0:26 ` Naoya Horiguchi
2019-10-10 7:17 ` David Hildenbrand
2019-10-11 6:50 ` Naoya Horiguchi
2019-10-19 2:05 ` Andrew Morton
2019-10-21 9:44 ` David Hildenbrand
2019-10-14 8:41 ` David Hildenbrand
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=20191015142340.GA5686@linux \
--to=osalvador@suse.de \
--cc=OSalvador@suse.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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;
as well as URLs for NNTP newsgroup(s).