linux-kernel - Re: [PATCH] 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 6 Mar 2009 17:24:02 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Daniel Yeisley <dan.yeisley@...sys.com>,
	Yinghai Lu <yinghai@...nel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH] MSI: check for BIOS assigned addresses


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

> When creating MSI addresses the kernel makes them up and 
> writes them to the hardware without first checking for what 
> the system BIOS may have assigned.  The patch below checks for 
> already assigned values, and leaves them alone if they exist.
> 
> Signed-off-by: Dan Yeisley <dan.yeisley@...sys.com>

What happens without this fix - do you get non-working cards? 
Boot hang? Or a suboptimal layout?

	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/