linux-kernel - Re: [stable] [PATCH 0/2] x86: check correctness of IRQ0 override on systems with ATI/AMD SB450/SB600 chipsets

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]

Date:	Thu, 16 Oct 2008 14:06:15 +0200
From:	Andreas Herrmann <andreas.herrmann3@....com>
To:	Greg KH <greg@...ah.com>
CC:	stable@...nel.org, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [stable] [PATCH 0/2] x86: check correctness of IRQ0 override
	on systems with ATI/AMD SB450/SB600 chipsets

On Wed, Oct 15, 2008 at 12:17:20PM -0700, Greg KH wrote:
> On Wed, Oct 15, 2008 at 12:41:18PM +0200, Andreas Herrmann wrote:
> > Hi,
> > 
> > following patches should go into 2.6.27-stable tree.
> > 
> > They fix issues with HP Laptops that provide a wrong override for IRQ0
> > and which change the thermal trip point as soon as Linux unmasks
> > IOAPIC INT2.
> 
> Are these patches in the upstream Linus kernel already?
> 
> If so, can you please give us the git commit ids?

The one for SB450 is upstream. It's commit
33fb0e4eb53f16af312f9698f974e2e64af39c12

The second one was posted yesterday and it is not yet commited.

BTW, I just posted another patch to remove superfluos DMI-quirks
that are related to HP Laptops with SB450/SB600.
IMHO this patch should go into stable as well. But first I'd like
to get a response from Ingo here.


Regards,

Andreas


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