From: keith.busch@intel.com (Keith Busch)
Subject: nvme_free_ns_head: ida_remove called for id=1 which is not allocated
Date: Tue, 3 Apr 2018 15:07:35 -0600 [thread overview]
Message-ID: <20180403210734.GC4485@localhost.localdomain> (raw)
In-Reply-To: <6fe0bfff-0ca3-a752-6faa-3d36796977e0@gmail.com>
On Tue, Apr 03, 2018@12:46:34PM -0500, Alex G. wrote:
> I noticed a new and interesting error. While it's ominous, it doesn't
> seem to cause any ill side-effects. This is reproduced with
> firmware-first error handling, so I'm not sure if it's even an issue of
> concern to nvme_core. Log files attached
Does this reproduce if you're not using CONFIG_NVME_MULTIPATH?
next prev parent reply other threads:[~2018-04-03 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 17:46 nvme_free_ns_head: ida_remove called for id=1 which is not allocated Alex G.
2018-04-03 21:07 ` Keith Busch [this message]
2018-04-04 15:51 ` Alex G.
2018-04-04 15:56 ` Keith Busch
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=20180403210734.GC4485@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