From: james.smart@broadcom.com (James Smart)
Subject: [PATCH v2] nvmet_fc: support target port removal with nvmet layer
Date: Wed, 5 Sep 2018 13:12:29 -0700 [thread overview]
Message-ID: <9fab9189-19ba-e81b-83bc-8c7c0c764763@broadcom.com> (raw)
In-Reply-To: <20180905195652.GA2560@infradead.org>
The patch is good - but did bring out an error in lpfc.? So we're hosed
either way:? w/o it - we have fc transport using a pointer after free
corrupting whatever it is; w/ it lpfc doesn't clean up so the controller
hangs.
I guess I would prefer to pick up the fix and I'll work on getting lpfc
fixed.
-- james
On 9/5/2018 12:56 PM, Christoph Hellwig wrote:
> Ewan, James: what is the conclusion on this patch? The discussion
> seems to have faded.
next prev parent reply other threads:[~2018-09-05 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 23:48 [PATCH v2] nvmet_fc: support target port removal with nvmet layer James Smart
2018-08-10 17:53 ` Ewan D. Milne
2018-08-10 23:21 ` James Smart
2018-08-13 16:38 ` Ewan D. Milne
2018-08-10 20:50 ` Ewan D. Milne
2018-08-10 23:04 ` James Smart
2018-09-05 19:56 ` Christoph Hellwig
2018-09-05 20:12 ` James Smart [this message]
2018-09-11 7:17 ` Christoph Hellwig
2018-09-05 20:24 ` Ewan D. Milne
2018-09-05 20:40 ` James Smart
2018-09-11 7:35 ` Christoph Hellwig
2018-09-11 17:01 ` James Smart
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=9fab9189-19ba-e81b-83bc-8c7c0c764763@broadcom.com \
--to=james.smart@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.