From: Greg KH <gregkh@linuxfoundation.org>
To: Jack Wang <jinpu.wang@cloud.ionos.com>
Cc: sashal@kernel.org, stable@vger.kernel.org,
Deepak Ukey <deepak.ukey@microchip.com>,
Viswas G <Viswas.G@microchip.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [stable-4.19 2/2] scsi: pm80xx: Fixed kernel panic during error recovery for SATA drive
Date: Tue, 10 Mar 2020 12:42:24 +0100 [thread overview]
Message-ID: <20200310114224.GF3106483@kroah.com> (raw)
In-Reply-To: <20200309101739.32483-3-jinpu.wang@cloud.ionos.com>
On Mon, Mar 09, 2020 at 11:17:39AM +0100, Jack Wang wrote:
> From: Deepak Ukey <deepak.ukey@microchip.com>
>
> commit 196ba6629cf95e51403337235d09742fcdc3febd upstream
>
> Disabling the SATA drive interface cause kernel panic. When the drive
> Interface is disabled, device should be deregistered after aborting all
> pending I/Os. Also changed the port recovery timeout to 10000 ms for
> PM8006 controller.
>
> Signed-off-by: Deepak Ukey <deepak.ukey@microchip.com>
> Signed-off-by: Viswas G <Viswas.G@microchip.com>
> Reviewed-by: Jack Wang <jinpu.wang@cloud.ionos.com>
> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
> ---
> drivers/scsi/pm8001/pm8001_sas.c | 6 +++++-
> drivers/scsi/pm8001/pm80xx_hwi.c | 2 +-
> drivers/scsi/pm8001/pm80xx_hwi.h | 2 ++
> 3 files changed, 8 insertions(+), 2 deletions(-)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2020-03-10 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 10:17 [stable-4.19 0/2] 2 stable fix for pm80xx Jack Wang
2020-03-09 10:17 ` [stable-4.19 1/2] scsi: pm80xx: panic on ncq error cleaning up the read log Jack Wang
2020-03-10 11:41 ` Greg KH
2020-03-10 11:41 ` Greg KH
2020-03-10 11:47 ` Jinpu Wang
2020-03-09 10:17 ` [stable-4.19 2/2] scsi: pm80xx: Fixed kernel panic during error recovery for SATA drive Jack Wang
2020-03-10 11:42 ` Greg KH [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=20200310114224.GF3106483@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Viswas.G@microchip.com \
--cc=deepak.ukey@microchip.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=martin.petersen@oracle.com \
--cc=sashal@kernel.org \
--cc=stable@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 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.