From: Ming Lei <ming.lei@redhat.com>
To: Wen Xiong <wenxiong@us.ibm.com>
Cc: dwagner@suse.de, james.smart@broadcom.com,
linux-kernel@vger.kernel.org, sagi@grimberg.me
Subject: Re: [PATCH 1/1] block: System crashes when cpu hotplug + bouncing port
Date: Tue, 29 Jun 2021 10:56:59 +0800 [thread overview]
Message-ID: <YNqL+3LDsIPKm1ol@T590> (raw)
In-Reply-To: <OFE573413D.44652DC5-ON00258703.000DB949-00258703.000EFCD4@ibm.com>
Hi Wen Xiong,
On Tue, Jun 29, 2021 at 02:43:42AM +0000, Wen Xiong wrote:
> >>NVMe users have to pass correct hctx_idx to blk_mq_alloc_request_hctx(),
> but
> >>from the info you provided, they don't provide valid hctx_idx to blk-mq,
> so
> >>q->queue_hw_ctx[hctx_idx] is NULL and kernel panic.
>
> Hi Ming,
>
> Daniel's two patches didn't fix the crash issue. My patch is on top of two
> patches.
> That is the reason why I am continue debugging the issue.
Can you provide the dmesg log after applying Daniel's patches?
Yeah, one known issue is that the following line in blk_mq_alloc_request_hctx()
won't work well even though Daniel's patches are applied:
data.ctx = __blk_mq_get_ctx(q, cpu);
Is that the kernel crash in your observation?
>
> What hctx_idx you suggest to provide to blk-mq for this issue?
>
> Before cpu hotplug, num_online_cpus() is 16: 0-15 are online.
> After cpu hotplug, num_online_cpus() is 8: 0,1,2,3,8,9, 10,11 are online
> 4,5,6,7,12,13,14,15 are offline.
>
> What hctx_idx you suggest to provide to blk-mq by calling
> blk_mq_alloc_request_hctx() in this case?
At least the hctx_idx shouldn't be >= q->nr_hw_queues/set->nr_hw_queues.
Also can you collect the queue mapping log?
#./dump-qmap /dev/nvme1n1
[1] http://people.redhat.com/minlei/tests/tools/dump-qmap
Thanks,
Ming
next prev parent reply other threads:[~2021-06-29 2:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 3:14 [PATCH 1/1] block: System crashes when cpu hotplug + bouncing port wenxiong
2021-06-28 9:07 ` Daniel Wagner
2021-06-28 9:59 ` Ming Lei
[not found] ` <71d1ce491ed5056bfa921f0e14fa646d@imap.linux.ibm.com>
2021-06-29 1:20 ` Ming Lei
[not found] ` <OFE573413D.44652DC5-ON00258703.000DB949-00258703.000EFCD4@ibm.com>
2021-06-29 2:56 ` Ming Lei [this message]
[not found] ` <OF8889275F.DC758B38-ON00258703.001297BC-00258703.00143502@ibm.com>
2021-06-29 3:47 ` Ming Lei
2021-06-29 8:25 ` Daniel Wagner
2021-06-29 8:35 ` Daniel Wagner
2021-06-29 9:01 ` Ming Lei
2021-06-29 9:27 ` Daniel Wagner
2021-06-29 9:35 ` Ming Lei
2021-06-29 9:49 ` Daniel Wagner
2021-06-29 10:06 ` Ming Lei
2021-06-29 11:50 ` Daniel Wagner
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=YNqL+3LDsIPKm1ol@T590 \
--to=ming.lei@redhat.com \
--cc=dwagner@suse.de \
--cc=james.smart@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=wenxiong@us.ibm.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.