linux-kernel - Re: [tip:x86/apic] x86: MSI: check for BIOS assigned addresses

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:	Fri, 6 Mar 2009 19:45:14 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	yinghai@...nel.org, stable@...nel.org, dan.yeisley@...sys.com,
	tglx@...utronix.de
Cc:	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/apic] x86: MSI: check for BIOS assigned addresses

* Daniel Yeisley <dan.yeisley@...sys.com> wrote:

> Commit-ID:  affd49d36e2e2df4cbb3e07a57db901c23823b6a
> Gitweb:     http://git.kernel.org/tip/affd49d36e2e2df4cbb3e07a57db901c23823b6a
> Author:     "Daniel Yeisley" <dan.yeisley@...sys.com>
> AuthorDate: Fri, 6 Mar 2009 10:11:49 -0500
> Commit:     Ingo Molnar <mingo@...e.hu>
> CommitDate: Fri, 6 Mar 2009 19:32:44 +0100
> 
> x86: MSI: check for BIOS assigned addresses
> 
> Impact: fix ACPI hotplug on certain systems

Note, this commit means that i moved the commit over from 
tip:x86/urgent into tip:x86/apic - i.e. with a 2.6.30 merge 
date. When exactly was this regression introduced? I think this 
code never really accepted the MSI settings from the firmware, 
so changing that behavior might affect a lot of systems.

So i'm uneasy about applying this fix this late in the .29 
cycle, but marked it for -stable backport so it could hit 
2.6.29.1 if it stays problem-free.

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