linux-kernel - Re: [RFC][PATCH] IO-APIC blacklist

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]

Message-ID: <alpine.LFD.0.98.0706021353430.23741@woody.linux-foundation.org>
Date:	Sat, 2 Jun 2007 13:55:15 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Tear <tarrqt@...oo.com>
cc:	Len Brown <lenb@...nel.org>, mingo@...hat.com,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] IO-APIC blacklist



On Sat, 2 Jun 2007, Tear wrote:
> > 
> > Wouldn't this also disable the IOAPIC in the (working) ACPI+IOAPIC case?
> 
> Yes, it would. However, I wanted to make my addition
> to the kernel generic so that other people with
> problematic IO-APIC implementations can blacklist
> their systems without checking whether ACPI is enabled
> or not.

But that's just wrong. First off, all distro kernels come with ACPI on, so 
the thing you're fixing is really just for somebody who compiles his own 
kernel in a particular (and unusual/strange) configuration, and you're 
making it _worse_ for everybody else.

And you're blacklisting it without even understaning _what_ is wrong. I 
really think we should figure that part out first,

		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/