[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZzczYMMePV3oWFON@pathway.suse.cz>
Date: Fri, 15 Nov 2024 12:41:20 +0100
From: Petr Mladek <pmladek@...e.com>
To: Chris Down <chris@...isdown.name>
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
On Thu 2024-11-14 14:28:22, Chris Down wrote:
> 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?
Please, make v7 based on linux-next. It seems that the merge window
for 6.13 opens the following week. So that the other patchset should
reach the mainline in 6.13. The per-console loglevels would need to
wait for 6.14.
Best Regards,
Petr
Powered by blists - more mailing lists