linux-kernel - Re: [stable][PATCH] pci: quirk disable MSI on via vt3351

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: <20070527002052.GM3899@stusta.de>
Date:	Sun, 27 May 2007 02:20:52 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Jay Cliburn <jacliburn@...lsouth.net>
Cc:	gregkh@...e.de, chrisw@...s-sol.org, csnook@...hat.com,
	ebiederm@...ssion.com, linux-kernel@...r.kernel.org,
	stable@...nel.org
Subject: Re: [stable][PATCH] pci: quirk disable MSI on via vt3351

On Sat, May 26, 2007 at 05:01:04PM -0500, Jay Cliburn wrote:
> 
> The Via VT3351 APIC does not play well with MSI and unleashes a flood
> of APIC errors when MSI is used to deliver interrupts.  The problem
> was recently exposed when the atl1 network device driver, which enables
> MSI by default, stimulated APIC errors on an Asus M2V mainboard, which
> employs the Via VT3351.
> See http://bugzilla.kernel.org/show_bug.cgi?id=8472 for additional
> details on this bug.
>...

Please get patches included in Linus' tree _before_ submitting them for 
-stable.

Adding a fix to 2.6.21 that is not yet in 2.6.22-rc would create a 
regression in 2.6.22.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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