From: keith.busch@intel.com (Keith Busch)
Subject: Should I submit bugs against RC kernels?
Date: Wed, 21 Nov 2018 12:19:13 -0700 [thread overview]
Message-ID: <20181121191913.GJ26707@localhost.localdomain> (raw)
In-Reply-To: <af0de79e5ac94be7ad4594fdace103d7@ausx13mps321.AMER.DELL.COM>
On Wed, Nov 21, 2018@06:21:49PM +0000, Alex_Gagniuc@Dellteam.com wrote:
> Hi,
>
> I'm not sure if submitting bugs against RC is a good idea. I am seeing
> more issues with SURPRISE!!! removal of drives under v4.20-rc3.
>
> Alex
Hi Alex,
Yes, you can (and should!) report sightings for issues on rc kernels to
the appropriate subsystems.
The following should resolve the issue you're seeing. I won't be able to
test it till next Monday, though.
---
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 4f504e8f0669..b1ce747411de 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -1495,6 +1495,7 @@ static void nvme_dev_remove_admin(struct nvme_dev *dev)
blk_mq_unquiesce_queue(dev->ctrl.admin_q);
blk_cleanup_queue(dev->ctrl.admin_q);
blk_mq_free_tag_set(&dev->admin_tagset);
+ dev->ctrl.admin_q = NULL;
}
}
--
next prev parent reply other threads:[~2018-11-21 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 18:21 Should I submit bugs against RC kernels? Alex_Gagniuc
2018-11-21 19:19 ` Keith Busch [this message]
2018-11-23 16:08 ` Igor Konopko
2018-11-22 8:38 ` Ming Lei
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=20181121191913.GJ26707@localhost.localdomain \
--to=keith.busch@intel.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