From: Greg KH <greg@kroah.com>
To: Andrey Grodzovsky <andrey2805@gmail.com>
Cc: stable@vger.kernel.org,
Sreekanth Reddy <Sreekanth.Reddy@broadcom.com>,
Hannes Reinecke <hare@suse.de>,
PDL-MPT-FUSIONLINUX <MPT-FusionLinux.pdl@broadcom.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] [SCSI] mpt2sas: Fix secure erase premature termination
Date: Thu, 17 Nov 2016 08:11:45 +0100 [thread overview]
Message-ID: <20161117071145.GA14526@kroah.com> (raw)
In-Reply-To: <1479345308-27261-1-git-send-email-andrey2805@gmail.com>
On Wed, Nov 16, 2016 at 08:15:08PM -0500, Andrey Grodzovsky wrote:
> Problem:
> This is a work around for a bug with LSI Fusion MPT SAS2 when
> pefroming secure erase. Due to the very long time the operation
> takes commands issued during the erase will time out and will trigger
> execution of abort hook. Even though the abort hook is called for
> the specific command which timed out this leads to entire device halt
> (scsi_state terminated) and premature termination of the secured erase.
>
> Fix:
> Set device state to busy while erase in progress to reject any incoming
> commands until the erase is done. The device is blocked any way during
> this time and cannot execute any other command.
> More data and logs can be found here -
> https://drive.google.com/file/d/0B9ocOHYHbbS1Q3VMdkkzeWFkTjg/view
>
> P.S
> This is a backport from the same fix for mpt3sas driver intended
> for pre-4.4 stable trees.
What is "the same fix"? What is the git commit id in Linus's tree for
this?
thanks,
greg k-h
prev parent reply other threads:[~2016-11-17 7:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 12:43 [PATCH] [SCSI] mpt3sas: Fix secure erase premature termination Andrey Grodzovsky
2016-10-30 12:43 ` Andrey Grodzovsky
2016-10-30 18:43 ` Hannes Reinecke
2016-10-30 18:43 ` Hannes Reinecke
2016-11-02 0:09 ` [PATCH] [SCSI] mpt3sas: Fix secure erase premature termination (v2) Andrey Grodzovsky
2016-11-02 0:09 ` Andrey Grodzovsky
2016-11-02 2:07 ` Hannes Reinecke
2016-11-02 2:07 ` Hannes Reinecke
2016-11-02 10:05 ` Sreekanth Reddy
[not found] ` <CAJphD_qrQftfCOn_uzXCfdX=Xv9BYvVQ60AZ4DR2rc3gfXQa_Q@mail.gmail.com>
[not found] ` <30w645ulbhlofxrk1h4a9q3s.1478144944778@email.android.com>
2016-11-04 12:45 ` Sreekanth Reddy
2016-11-04 14:51 ` Hannes Reinecke
2016-11-04 16:35 ` Martin K. Petersen
2016-11-04 16:35 ` Martin K. Petersen
2018-04-24 9:09 ` Steffen Maier
2018-04-24 12:33 ` Hannes Reinecke
2016-11-05 13:17 ` Andrey Grodzovsky
2016-11-10 12:07 ` Sreekanth Reddy
2016-11-10 13:42 ` [PATCH] [SCSI] mpt3sas: Fix secure erase premature termination (v3) Andrey Grodzovsky
2016-11-10 13:42 ` Andrey Grodzovsky
2016-11-10 13:54 ` Greg KH
2016-11-10 14:35 ` [PATCH] [SCSI] mpt3sas: Fix secure erase premature termination (v4) Andrey Grodzovsky
2016-11-10 14:35 ` Andrey Grodzovsky
2016-11-11 4:38 ` Sreekanth Reddy
2018-04-23 18:28 ` Igor Rybak
2018-04-24 7:25 ` Greg KH
2016-11-12 15:29 ` Martin K. Petersen
2016-11-12 15:29 ` Martin K. Petersen
2016-11-12 16:36 ` Andrey Grodzovsky
2016-11-14 23:30 ` Martin K. Petersen
2016-11-17 1:15 ` [PATCH] [SCSI] mpt2sas: Fix secure erase premature termination Andrey Grodzovsky
2016-11-17 7:11 ` 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=20161117071145.GA14526@kroah.com \
--to=greg@kroah.com \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=Sreekanth.Reddy@broadcom.com \
--cc=andrey2805@gmail.com \
--cc=hare@suse.de \
--cc=martin.petersen@oracle.com \
--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.