public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Shaohua Li <shli@kernel.org>,
	linux-block@vger.kernel.org, axboe@kernel.dk
Subject: Re: [BUG] nvme driver crash
Date: Wed, 26 Jul 2017 12:12:21 -0700	[thread overview]
Message-ID: <20170726191221.GA22421@vader.DHCP.thefacebook.com> (raw)
In-Reply-To: <20170726173443.GA25527@infradead.org>

On Wed, Jul 26, 2017 at 10:34:43AM -0700, Christoph Hellwig wrote:
> On Tue, Jul 25, 2017 at 03:24:08PM -0700, Shaohua Li wrote:
> > Disable CONIFG_SMP, kernel crashes at boot time, here is the log.
> 
> I can reproduce the issue.  Unfortunately the addresss in the bug
> doesn't make any sense to me when resolving it using gdb, as t just
> points to the line where blk_mq_init_queue calls
> blk_alloc_queue_node.
> 
> Can you check if you get better results in your build?

It's crashing on that line because ctrl->tagset is NULL, which is
because...

irq_create_affinity_masks() returns NULL on !CONFIG_SMP
-> pci_irq_get_affinity() returns NULL
-> blk_mq_pci_map_queues() returns -EINVAL
-> blk_mq_alloc_tag_set() returns -EINVAL
-> nvme_dev_add() doesn't set ctrl->tagset

The two-fold fix would be to make the nvme driver handle
blk_mq_alloc_tag_set() failing and to fall back to a dumb mapping in
blk_mq_pci_map_queues(), but I don't know what the best way to do those
is.

  reply	other threads:[~2017-07-26 19:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 22:24 [BUG] nvme driver crash Shaohua Li
2017-07-26 17:34 ` Christoph Hellwig
2017-07-26 19:12   ` Omar Sandoval [this message]
2017-07-26 22:29     ` Shaohua Li
2017-07-27 13:26       ` Christoph Hellwig
2017-07-27 13:52     ` Max Gurtovoy
2017-07-27 14:05       ` Sagi Grimberg

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=20170726191221.GA22421@vader.DHCP.thefacebook.com \
    --to=osandov@osandov.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=shli@kernel.org \
    /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