linux-kernel - Re: dead(?) i386-related CONFIG variables

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]

Message-ID: <468E3579.1020109@s5r6.in-berlin.de>
Date:	Fri, 06 Jul 2007 14:28:41 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: dead(?) i386-related CONFIG variables

On 7/5/2007 1:27 PM, Robert P. J. Day wrote:
>   since it's not clear who a single contact person would be for
> i386-related stuff like this, here's what my script turned up for
> tests on non-existent CONFIG variables under arch/i386:
> 
> ========== BALANCED_IRQ_DEBUG ==========
> arch/i386/kernel/io_apic.c:356:#ifdef CONFIG_BALANCED_IRQ_DEBUG

-#ifdef CONFIG_BALANCED_IRQ_DEBUG
+#if 0 /* debug IRQ balancing */

> ========== DEBUG_PAGE_TYPE ==========
> arch/i386/kernel/vmi.c:238:#ifdef CONFIG_DEBUG_PAGE_TYPE

-#ifdef CONFIG_DEBUG_PAGE_TYPE
+#if 0 /* debug page type */

arch/i386/kernel/vmi.c:339

-#endif
+#endif /* debug page type */

> ========== SERIAL_DETECT_IRQ ==========
> arch/i386/kernel/legacy_serial.c:18:#ifdef CONFIG_SERIAL_DETECT_IRQ

Hmm, not sure about this.  The code section was taken from
include/asm-{i386,x86_64}/serial.h.  This is an option similar to other
CONFIG_SERIAL_ options in numerous places.

Serial drivers are orphaned, aren't they?

>   feel free to take this as seriously as you want.  :-)
> 
> rday

-- 
Stefan Richter
-=====-=-=== -=== --==-
http://arcgraph.de/sr/
-
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/