linux-kernel - Re: 2.6.21-rc5-mm2 - compile error on x86-64

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: <m14po3jozn.fsf@ebiederm.dsl.xmission.com>
Date:	Thu, 29 Mar 2007 23:10:20 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Helge Hafting <helgehaf@...el.hist.no>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.21-rc5-mm2 - compile error on x86-64

Andrew Morton <akpm@...ux-foundation.org> writes:

>
> config PROC_SYSCTL
>         bool "Sysctl support (/proc/sys)" if EMBEDDED
>         depends on PROC_FS
>         select SYSCTL
>         default y
>
> CONFIG_PROC_SYSCTL depends on CONFIG_PROC_FS
> CONFIG_PROC_SYSCTL selects CONFIG_SYSCTL
>
> So I don't see anything preventing CONFIG_SYSCTL=y, CONFIG_PROC_FS=y,
> CONFIG_PROC_SYSCTL=n.  I assume we can make this combination compile, link
> and run easily enough.  I dunno if it makes any actual sense though?
>
>
> I'd have thought that PROC_SYSCTL should just depend on SYSCTL.  But
> SYSCTL's Kconfig setup is weird.

Yes. My memory is now coming back.  I did a few weird things in there 
when I was making the binary interface optional, and it looks like
I never updated the #ifdef in fs/proc/root.c  The primary intent
was to allow the proc support without the binary interface but I
guess the other configuration makes some sense as well in an embedded
scenario when you are trying to be as efficient as possible.  As I
recall the binary interface is less resource intensive then the /proc
interface.

Eric

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