linux-kernel - Re: [PATCH 9/12] scsi: megaraid_sas - Fix the fix for fw hang caused by megaraid sas application

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: <1255454817.2855.211.camel@localhost.localdomain>
Date:	Tue, 13 Oct 2009 17:26:57 +0000
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	"Yang, Bo" <Bo.Yang@....com>
Cc:	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	"akpm@...l.org" <akpm@...l.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Austria, Winston" <Winston.Austria@....com>,
	"Mukker, Atul" <Atul.Mukker@....com>
Subject: Re: [PATCH 9/12] scsi: megaraid_sas - Fix the fix for fw hang
 caused by megaraid sas application

On Tue, 2009-10-06 at 14:47 -0600, Yang, Bo wrote:
> RESUBMIT:
> 
> Added the fix for FW and OS hang by using MSM.  Also add the fix for pending cmd in fw, after deleting the lds.

This is practically unintelligible as a changelog.  These logs get used
by distibutions and other people trying to determine if they need the
patch based on bug reports they're seeing

>>From the patch I think what you've done is:

1. Added a lock to the skinny firmware initialisation sequence to
prevent the two stage write being non atomic if multiple instances use
it.
2. Added a flag to the driver shutdown sequence to prevent aen ioctls
being called after shutdown begins.

For the future, could we also have separate bug fixes in separate
patches, please.

Also, does this need to go to stable?

Thanks,

James

--
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/