linux-kernel - Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)

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:	Wed, 8 Nov 2006 10:36:54 -0800 (PST)
From:	Linus Torvalds <torvalds@...l.org>
To:	Adrian Bunk <bunk@...sta.de>, Jeff Chua <jeff.chua.linux@...il.com>
cc:	Matthew Wilcox <matthew@....cx>, Andi Kleen <ak@...e.de>,
	Aaron Durbin <adurbin@...gle.com>,
	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	gregkh@...e.de, linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)

On Wed, 8 Nov 2006, Linus Torvalds wrote:
> 
> I'm going to revert that totally bogus commit that added that broken 
> "pci_mmcfg_insert_resources()" function.

Pushed out. Jeff, can you verify that current git does the right thing.

Andi - I also ported the x86 io-apic cleanup and fixes to x86-64. I'll 
push those out too once I've verified them on the machines I have access 
to.

I'm still not 100% happy about the io-apic thing (for example, I was 
thinking that maybe we should just automatically choose the order of 
writes in apic_write_entry() by just checking whether "mask" was set or 
not), but the code really is cleaner, and on x86 it was verified to fix 
some things.

Keeping in sync is still better than having two different approaches, one 
of which was confirmed broken. And the i386 code is definitely more tested 
over the years than the x86-64 code could ever have hoped to be, so going 
back to the original ordering makes sense.

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