linux-kernel - Re: [discuss] Re: Please pull x86-64 bug fixes

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, 06 Oct 2006 13:03:50 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Jeff Garzik <jeff@...zik.org>, Andi Kleen <ak@...e.de>,
	discuss@...-64.org, linux-kernel@...r.kernel.org
Subject: Re: [discuss] Re: Please pull x86-64 bug fixes

On Thu, 2006-10-05 at 15:45 -0700, Linus Torvalds wrote:
> 
> On Thu, 5 Oct 2006, Jeff Garzik wrote:
> 
> > Andi Kleen wrote:
> > > If the choice is between a secret NDA only card with dubious
> > > functionality and booting on lots of modern boards I know what to choose.
> > 
> > That's a strawman argument.  There is no need to choose.  You can clearly boot
> > on lots of modern boards with mmconfig just fine.  We just need to narrow down
> > which ones.
> 
> Jeff, _that_ is the strawman argument.
> 
> The thing is, nobody has been able to so far come up with a way to narrow 
> down which ones.
> 
> I think Andi's response was quite on the mark: if you have a patch to 
> narrow it down, please share. Until then, the fact is, we don't know 
> _how_, and you're barking up the wrong tree.


we can do a tiny bit better than the current code; some chipsets have
the address of the MMIO region stored in their config space; so we can
get to that using the old method and validate the acpi code with that.

I'm (in the background) working on collecting which chipsets have this;
it seems that at least several Intel ones do.



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