From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme-multipath: handle ANA log parse failures gracefully
Date: Tue, 21 May 2019 08:52:42 +0200 [thread overview]
Message-ID: <20190521065242.GF30402@lst.de> (raw)
In-Reply-To: <20190517112912.47055-1-hare@suse.de>
On Fri, May 17, 2019@01:29:12PM +0200, Hannes Reinecke wrote:
> When we're failing to parse the ANA log the ana log buffer will
> not be allocated, causing a crash in nvme_mpath_add_disk().
How can we even reach nvme_mpath_add_disk? If we fail to allocate the
buffer we error out in nvme_mpath_init, which leads to an error return
from nvme_init_identify, which should eventually lead to a probe
failure.
prev parent reply other threads:[~2019-05-21 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 11:29 [PATCH] nvme-multipath: handle ANA log parse failures gracefully Hannes Reinecke
2019-05-21 6:52 ` Christoph Hellwig [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=20190521065242.GF30402@lst.de \
--to=hch@lst.de \
/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