linux-kernel - mismatch between default and defconfig LOG_BUF

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-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0611280451010.13481@localhost.localdomain>
Date:	Tue, 28 Nov 2006 05:02:41 -0500 (EST)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: mismatch between default and defconfig LOG_BUF_SHIFT values

  not like it's a big deal, but there's a minor incongruity between
the default values for LOG_BUF_SHIFT for IA64 depending on whether
you're configuring for the first time or not.

  if i'm configuring with a fresh tree for the first time (so that
there's no .config file) and i run:

  $ make ARCH=ia64 menuconfig    (on my x86 system, just for fun)

then the initial value for LOG_BUF_SHIFT is obtained from
arch/ia64/defconfig:

  CONFIG_LOG_BUF_SHIFT=20

however, once i do that initial config, if i deselect "Kernel
debugging" and later reselect it, the new default value of 16 for that
config option comes from lib/Kconfig.debug:

...
config LOG_BUF_SHIFT
        int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
        range 12 21
        default 17 if S390 || LOCKDEP
        default 16 if X86_NUMAQ || IA64     <-- 16, not 20
...

  is it worth trying to bring the Kconfig.debug default values into
line with the defconfig file values, to avoid any possible confusion?

rday

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