linux-kernel - Re: [Bug #13175] sata_nv incompatible with async scsi scan

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A1C1B08.2080600@panasas.com>
Date:	Tue, 26 May 2009 19:38:32 +0300
From:	Benny Halevy <bhalevy@...asas.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	Jeff Garzik <jeff@...zik.org>, Matthew Wilcox <matthew@....cx>
Subject: Re: [Bug #13175] sata_nv incompatible with async scsi scan

On May. 24, 2009, 22:31 +0300, "Rafael J. Wysocki" <rjw@...k.pl> wrote:
> This message has been generated automatically as a part of a report
> of regressions introduced between 2.6.28 and 2.6.29.
> 
> The following bug entry is on the current list of known regressions
> introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> be listed and let me know (either way).

Verified to still exist with 2.6.30-rc7 :-(

[The bug description is misleading though.  More testing
lead to post-kernel boot problems where initrd cannot find the sata
devices during its init phase]

Benny

> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13175
> Subject		: sata_nv incompatible with async scsi scan
> Submitter	: Benny Halevy <bhalevy@...asas.com>
> Date		: 2009-04-21 7:03 (34 days old)
> References	: http://marc.info/?l=linux-kernel&m=124029746431777&w=4
> 
> 
--
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/