From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Lei Lei2 Yin <yinlei2@lenovo.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>, "hch@lst.de" <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"cybeyond@foxmail.com" <cybeyond@foxmail.com>
Subject: Re: [PATCH v2] nvme: fix double blk_mq_complete_request for timeout request with low probability
Date: Sat, 8 Apr 2023 08:14:46 +0000 [thread overview]
Message-ID: <ce8d7dce-ac20-91d7-bbb5-db80997b0730@nvidia.com> (raw)
In-Reply-To: <a5cfe4e4-62b8-5cea-c4bc-06d905ffccf1@nvidia.com>
On 4/8/23 01:04, Chaitanya Kulkarni wrote:
>
>> [ 2777.253091] <TASK>
>> [ 2777.253102] nvme_failover_req+0x10a/0x120 [nvme_core]
>> [ 2777.255302] blk_complete_reqs+0x3e/0x60
>> [ 2777.255726] __do_softirq+0xb6/0x2ad
>> [ 2777.256139] ? __pfx_smpboot_thread_fn+0x10/0x10
>> [ 2777.256556] run_ksoftirqd+0x28/0x40
>> [ 2777.256978] smpboot_thread_fn+0xdb/0x1d0
>> [ 2777.257399] kthread+0xd7/0x100
>> [ 2777.257827] ? __pfx_kthread+0x10/0x10
>> [ 2777.258253] ret_from_fork+0x29/0x50
>> [ 2777.258695] </TASK>
>>
>> Signed-off-by: Lei Yin <yinlei2@lenovo.com>
>> ---
>>
> Can you please add blktests for this fix under nvme category ?
>
>
When you do please CC me and Shinichiro (shinichiro.kawasaki@wdc.com).
-ck
prev parent reply other threads:[~2023-04-08 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 7:44 [PATCH v2] nvme: fix double blk_mq_complete_request for timeout request with low probability Lei Lei2 Yin
2023-04-08 8:04 ` Chaitanya Kulkarni
2023-04-08 8:14 ` Chaitanya Kulkarni [this message]
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=ce8d7dce-ac20-91d7-bbb5-db80997b0730@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@fb.com \
--cc=cybeyond@foxmail.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=yinlei2@lenovo.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