From: Raphael Philipe Mendes da Silva <raphasil@linux.vnet.ibm.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org, james.smart@broadcom.com,
dick.kennedy@broadcom.com, jsmart2021@gmail.com,
porcusbr@gmail.com
Subject: Re: [PATCH] scsi: lpfc: Fix crash on PCI hotplug remove path
Date: Mon, 29 May 2017 18:32:37 -0300 [thread overview]
Message-ID: <20170529213236.GA14650@raphasil> (raw)
In-Reply-To: <cdc85e21-caf1-aeb6-a24f-dac063e66c5a@suse.de>
On Mon, May 29, 2017 at 09:56:09AM +0200, Johannes Thumshirn wrote:
> On 05/28/2017 11:45 PM, Guilherme G. Piccoli wrote:
> > During a PCI hotplug remove event we could have a NULL pointer
> > dereference on lpfc_sli_abort_iocb(), if pring is NULL. This
> > patch adds a check for this case and is able to circumvent the
> > failure and continue the hotplug remove process with success.
> >
> > This issue was introduced after the driver refactor made on
> > commit 895427bd012c ("scsi: lpfc: NVME Initiator: Base modifications").
> >
> > Fixes: 895427bd012c ("scsi: lpfc: NVME Initiator: Base modifications")
> > Reported-by: Naresh Bannoth <nbannoth@in.ibm.com>
> > Signed-off-by: Guilherme G. Piccoli <gpiccoli@linux.vnet.ibm.com>
> > ---
>
> Looks good,
> Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Tested-by: Raphael Silva <raphasil@linux.vnet.ibm.com>
next prev parent reply other threads:[~2017-05-29 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 21:45 [PATCH] scsi: lpfc: Fix crash on PCI hotplug remove path Guilherme G. Piccoli
2017-05-29 7:56 ` Johannes Thumshirn
2017-05-29 21:32 ` Raphael Philipe Mendes da Silva [this message]
2017-05-29 23:11 ` James Smart
2017-05-31 16:55 ` 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=20170529213236.GA14650@raphasil \
--to=raphasil@linux.vnet.ibm.com \
--cc=dick.kennedy@broadcom.com \
--cc=gpiccoli@linux.vnet.ibm.com \
--cc=james.smart@broadcom.com \
--cc=jsmart2021@gmail.com \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=porcusbr@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 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.