From: snitzer@redhat.com (Mike Snitzer)
Subject: nvme-fc: fix numa_node when dev is null
Date: Sat, 2 Mar 2019 00:29:50 -0500 [thread overview]
Message-ID: <20190302052950.GA32442@redhat.com> (raw)
In-Reply-To: <20190301211933.26297-1-jsmart2021@gmail.com>
On Fri, Mar 01 2019 at 4:19pm -0500,
James Smart <jsmart2021@gmail.com> wrote:
> A recent change added a numa_node field to the nvme controller
> and has the transport assign the node using dev_to_node().
> However, fcloop registers with a NULL device struct, so the
> dev_to_node() call oops.
>
> Revise the assignment to assign no node when device struct is null.
>
> Fixes: 103e515efa89b ("nvme: add a numa_node field to struct nvme_ctrl")
> Reported-by: Mike Snitzer <snitzer at redhat.com>
> Signed-off-by: James Smart <jsmart2021 at gmail.com>
Reviewed-by: Mike Snitzer <snitzer at redhat.com>
Thanks James.
next prev parent reply other threads:[~2019-03-02 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 21:19 [PATCH] nvme-fc: fix numa_node when dev is null James Smart
2019-03-01 22:05 ` Sagi Grimberg
2019-03-02 5:29 ` Mike Snitzer [this message]
2019-03-04 12:33 ` Hannes Reinecke
2019-03-12 15:01 ` Christoph Hellwig
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=20190302052950.GA32442@redhat.com \
--to=snitzer@redhat.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 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.