linux-kernel - Re: PROBLEM: CONFIG_DEFAULT_MESSAGE_LOGLEVEL option seems not to work

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

Message-ID: <5143FB1F.9010509@infradead.org>
Date:	Fri, 15 Mar 2013 21:54:55 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Manolo Díaz <diaz.manolo@...il.com>
CC:	linux-kbuild@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: PROBLEM: CONFIG_DEFAULT_MESSAGE_LOGLEVEL option seems not to
 work

On 03/15/13 14:56, Manolo Díaz wrote:
> Hi,
> 
> It seems that the kernel loglevel is set to 7 ignoring the
> CONFIG_DEFAULT_MESSAGE_LOGLEVEL option (set to 4 in my config file)
> 
> The /proc/sys/kernel/printk output is 
> 
> 7	4	1	7
> 
> Passing the boot parameter "loglevel=4" or echoing "4 4 1 7"
> to /proc/sys/kernel/printk solves my problem and then this proc file
> contains
> 
> 4	4	1	7
> 
> as expected.
> 
> kernel version:
> Linux version 3.8.3 (root@...yone) (gcc version 4.7.2 (Debian 4.7.2-5)
> ) #2 SMP Fri Mar 15 08:23:50 CET 2013
> 
> config file is gziped and attached.


Hi,

CONFIG_DEFAULT_MESSAGE_LOGLEVEL modifies the second field (value) in /proc/sys/kernel/printk,
not the first value.  OTOH, the "loglevel" kernel parameter modifies the first value in
that /proc file, not the second value.

Does that clarify/help?

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