From: mr.nuke.me@gmail.com (Alex G.)
Subject: IRQ/nvme_pci_complete_rq: NULL pointer dereference yet again
Date: Thu, 5 Apr 2018 18:44:21 -0500 [thread overview]
Message-ID: <d9497570-5e5e-cc4d-2c63-ff273a48725a@gmail.com> (raw)
In-Reply-To: <75edea4e-b961-82a1-3612-fc682a248819@gmail.com>
On 04/05/2018 06:39 PM, Alex G. wrote:
> On 04/05/2018 06:05 PM, Keith Busch wrote:
>> Just trying to confirm a suspicion, could you retry with the following?
>
> Started the test. Will let you know tomorrow of result.
Actually, it crashed very fast [1]
[1] http://gtech.myftp.org/~mrnuke/nvme_logs/log-20180405-1838.log
>
> Alex
>> ---
>> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
>> index b6f43b738f03..f9847a9f2973 100644
>> --- a/drivers/nvme/host/pci.c
>> +++ b/drivers/nvme/host/pci.c
>> @@ -890,12 +890,23 @@ static blk_status_t nvme_queue_rq(struct blk_mq_hw_ctx *hctx,
>> if (unlikely(nvmeq->cq_vector < 0)) {
>> ret = BLK_STS_IOERR;
>> spin_unlock_irq(&nvmeq->q_lock);
>> - goto out_cleanup_iod;
>> + goto out_unmap_iod;
>> }
>> __nvme_submit_cmd(nvmeq, &cmnd);
>> nvme_process_cq(nvmeq);
>> spin_unlock_irq(&nvmeq->q_lock);
>> return BLK_STS_OK;
>> +
>> +out_unmap_iod:
>> + nvme_unmap_data(dev, req);
>> + {
>> + struct nvme_iod *iod = blk_mq_rq_to_pdu(req);
>> + iod->nents = 0;
>> + iod->sg = NULL;
>> + iod->npages = -1;
>> + }
>> + return ret;
>> +
>> out_cleanup_iod:
>> nvme_free_iod(dev, req);
>> out_free_cmd:
>> --
>>
next prev parent reply other threads:[~2018-04-05 23:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d6d1a8c-6490-4046-0fba-da0a0df3d00c@gmail.com>
2018-04-05 21:38 ` IRQ/nvme_pci_complete_rq: NULL pointer dereference yet again Keith Busch
2018-04-05 21:22 ` Scott Bauer
2018-04-05 22:21 ` Alex G.
2018-04-05 22:41 ` Keith Busch
2018-04-05 22:48 ` Keith Busch
2018-04-05 23:05 ` Keith Busch
2018-04-05 23:39 ` Alex G.
2018-04-05 23:44 ` Alex G. [this message]
2018-04-06 15:32 ` Keith Busch
2018-04-06 15:46 ` Alex G.
[not found] ` <94d77cb7-759f-595a-2264-37305dfa96c4@gmail.com>
2018-04-06 17:16 ` Scott Bauer
2018-04-06 17:46 ` Alex G.
2018-04-06 18:04 ` Keith Busch
2018-04-06 19:00 ` Scott Bauer
2018-04-06 19:34 ` Keith Busch
2018-04-06 19:08 ` Alex G.
2018-04-06 22:00 ` Keith Busch
2018-04-09 18:23 ` Alex G.
2018-04-09 19:11 ` Keith Busch
2018-04-09 19:36 ` Alex G.
2018-04-09 19:47 ` Keith Busch
2018-04-10 0:07 ` Alex G.
2018-04-10 14:19 ` Alex G.
2018-05-02 15:39 ` Alex G.
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=d9497570-5e5e-cc4d-2c63-ff273a48725a@gmail.com \
--to=mr.nuke.me@gmail.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