linux-kernel - Re: Conflict with FORCE_CON: Re: [PATCH v6 04/11] printk: Support toggling per-console loglevel via syslog() and cmdline

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: <ZzZPVp8_ZHbGgn5z@chrisdown.name>
Date: Thu, 14 Nov 2024 14:28:22 -0500
From: Chris Down <chris@...isdown.name>
To: Petr Mladek <pmladek@...e.com>
Cc: linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Sergey Senozhatsky <senozhatsky@...omium.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	John Ogness <john.ogness@...utronix.de>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Tony Lindgren <tony.lindgren@...ux.intel.com>, kernel-team@...com
Subject: Re: Conflict with FORCE_CON: Re: [PATCH v6 04/11] printk: Support
 toggling per-console loglevel via syslog() and cmdline

Petr Mladek writes:
>On Mon 2024-10-28 16:45:40, Chris Down wrote:
>> A new module parameter (ignore_per_console_loglevel) is added, which can
>> be set via the kernel command line or at runtime through
>> /sys/module/printk/parameters/ignore_per_console_loglevel. When set, the
>> per-console loglevels are ignored, and the global console loglevel
>> (console_loglevel) is used for all consoles.
>>
>> During sysrq, we temporarily disable per-console loglevels to ensure all
>> requisite messages are printed to the console. This is necessary because
>> sysrq is often used in dire circumstances where access to
>> /sys/class/console may not be trivially possible.
>
>I have just pushed a patchset which removed the console_loglevel
>manipulation from sysrq, see
>https://lore.kernel.org/r/20241105-printk-loud-con-v2-0-bd3ecdf7b0e4@suse.com
  
Noted, so would you like me to change this to be based on current 
printk/for-next, or is another branch preferred?