linux-kernel - Re: [PATCH] hpsa: retry commands completing with status of UNSOLICITED

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110804143930.GD18468@kroah.com>
Date:	Thu, 4 Aug 2011 07:39:30 -0700
From:	Greg KH <greg@...ah.com>
To:	"Stephen M. Cameron" <scameron@...rdog.cce.hp.com>
Cc:	james.bottomley@...senpartnership.com, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org, mikem@...rdog.cce.hp.com,
	stephenmcameron@...il.com, thenzl@...hat.com,
	akpm@...ux-foundation.org, stable@...nel.org
Subject: Re: [PATCH] hpsa: retry commands completing with status of
 UNSOLICITED_ABORT

On Tue, Jul 26, 2011 at 11:08:52AM -0500, Stephen M. Cameron wrote:
> From: Stephen M. Cameron <scameron@...rdog.cce.hp.com>
> 
> In a shared SAS setup, target devices may be reset by one of
> several hosts, and outstanding commands on that device will be
> completed to corresponding hosts with status of UNSOLICITED_ABORT.
> Such commands should be retried instead of being treated as i/o
> errors.  Also fixed a nearby spelling error.
> 
> Signed-off-by: Stephen M. Cameron <scameron@...rdog.cce.hp.com>
> ---
>  drivers/scsi/hpsa.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/