public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Smart <james.smart@emulex.com>
To: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Cc: <linux-scsi@vger.kernel.org>, <JBottomley@parallels.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi/lpfc: use remove handler as shutdown handler
Date: Mon, 16 Feb 2015 14:41:58 -0500	[thread overview]
Message-ID: <54E24806.5030605@emulex.com> (raw)
In-Reply-To: <1422285538-487-1-git-send-email-cascardo@linux.vnet.ibm.com>

Looks good.

Acked-By: James Smart  <james.smart@emulex.com>

-- james



On 1/26/2015 10:18 AM, Thadeu Lima de Souza Cascardo wrote:
> Without a shutdown handler, some cards behave very badly after a kexec.
> During probe, pending DMA writes will corrupt kernel memory, for
> example.
>
> Using the remove handler guarantees we will use a well tested path.
>
> With this patch I applied, I managed to use kexec multiple times and
> probe and SCSI scan worked every time.
>
> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
> ---
>   drivers/scsi/lpfc/lpfc_init.c |    1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/drivers/scsi/lpfc/lpfc_init.c b/drivers/scsi/lpfc/lpfc_init.c
> index 0b2c53a..8aa804a 100644
> --- a/drivers/scsi/lpfc/lpfc_init.c
> +++ b/drivers/scsi/lpfc/lpfc_init.c
> @@ -11248,6 +11248,7 @@ static struct pci_driver lpfc_driver = {
>   	.id_table	= lpfc_id_table,
>   	.probe		= lpfc_pci_probe_one,
>   	.remove		= lpfc_pci_remove_one,
> +	.shutdown	= lpfc_pci_remove_one,
>   	.suspend        = lpfc_pci_suspend_one,
>   	.resume		= lpfc_pci_resume_one,
>   	.err_handler    = &lpfc_err_handler,


      reply	other threads:[~2015-02-16 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 15:18 [PATCH] scsi/lpfc: use remove handler as shutdown handler Thadeu Lima de Souza Cascardo
2015-02-16 19:41 ` James Smart [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=54E24806.5030605@emulex.com \
    --to=james.smart@emulex.com \
    --cc=JBottomley@parallels.com \
    --cc=cascardo@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /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