From: Michal Hocko <mhocko@kernel.org>
To: Qian Cai <cai@lca.pw>
Cc: akpm@linux-foundation.org, brho@google.com, kernelfans@gmail.com,
dave.hansen@intel.com, rppt@linux.ibm.com, peterz@infradead.org,
mpe@ellerman.id.au, mingo@elte.hu, osalvador@suse.de,
luto@kernel.org, tglx@linutronix.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next v2] mm/hotplug: fix a null-ptr-deref during NUMA boot
Date: Fri, 21 Jun 2019 15:55:07 +0200 [thread overview]
Message-ID: <20190621135507.GE3429@dhcp22.suse.cz> (raw)
In-Reply-To: <1561123078.5154.41.camel@lca.pw>
On Fri 21-06-19 09:17:58, Qian Cai wrote:
> Sigh...
>
> I don't see any benefit to keep the broken commit,
>
> "x86, numa: always initialize all possible nodes"
>
> for so long in linux-next that just prevent x86 NUMA machines with any memory-
> less node from booting.
>
> Andrew, maybe it is time to drop this patch until Michal found some time to fix
> it properly.
Yes, please drop the patch for now, Andrew. I thought I could get to
this but time is just scarce.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-06-21 13:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 5:48 [PATCH -next v2] mm/hotplug: fix a null-ptr-deref during NUMA boot Qian Cai
2019-05-13 12:41 ` Michal Hocko
2019-05-13 13:43 ` Qian Cai
2019-05-13 14:04 ` Michal Hocko
2019-05-13 15:20 ` Qian Cai
2019-05-13 15:31 ` Michal Hocko
2019-05-22 7:12 ` Pingfan Liu
2019-05-22 11:16 ` Michal Hocko
2019-05-23 3:58 ` Pingfan Liu
2019-05-23 4:00 ` Pingfan Liu
2019-05-28 18:21 ` Michal Hocko
2019-05-30 13:01 ` Pingfan Liu
2019-05-28 18:20 ` Michal Hocko
2019-05-30 12:55 ` Pingfan Liu
2019-05-31 9:03 ` Michal Hocko
2019-06-03 4:17 ` Pingfan Liu
2019-06-21 13:17 ` Qian Cai
2019-06-21 13:55 ` Michal Hocko [this message]
2019-06-24 8:42 ` Pingfan Liu
2019-06-26 13:57 ` Michal Hocko
2019-06-27 3:11 ` Pingfan Liu
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=20190621135507.GE3429@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brho@google.com \
--cc=cai@lca.pw \
--cc=dave.hansen@intel.com \
--cc=kernelfans@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@elte.hu \
--cc=mpe@ellerman.id.au \
--cc=osalvador@suse.de \
--cc=peterz@infradead.org \
--cc=rppt@linux.ibm.com \
--cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.