From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme: avoid crashes when node 0 is memoryless node.
Date: Mon, 20 Jun 2016 11:44:39 -0400 [thread overview]
Message-ID: <20160620154439.GE12936@localhost.localdomain> (raw)
In-Reply-To: <576739CD.2010002@jp.fujitsu.com>
On Mon, Jun 20, 2016@09:33:17AM +0900, Masayoshi Mizuma wrote:
> When CONFIG_NUMA is enabled and node 0 is memoryless, the system
> crashes because nvme_probe() sets the device->numa_node to 0 by
> set_dev_node(&pdev->dev, 0), so it tries to allocate memory from node 0.
> To avoid the crash, we should change the 0 to first_memory_node.
>
> Signed-off-by: Masayoshi Mizuma <m.mizuma at jp.fujitsu.com>
Thanks for the fix.
Reviewed-by: Keith Busch <keith.busch at intel.com>
next prev parent reply other threads:[~2016-06-20 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 0:33 [PATCH] nvme: avoid crashes when node 0 is memoryless node Masayoshi Mizuma
2016-06-20 7:08 ` Johannes Thumshirn
2016-06-20 15:44 ` Keith Busch [this message]
2016-07-13 6:13 ` Masayoshi Mizuma
2016-07-13 16:18 ` Jens Axboe
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=20160620154439.GE12936@localhost.localdomain \
--to=keith.busch@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).