[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aXt71R8OVszVvu_X@pathway.suse.cz>
Date: Thu, 29 Jan 2026 16:25:09 +0100
From: Petr Mladek <pmladek@...e.com>
To: Breno Leitao <leitao@...ian.org>
Cc: Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
john.ogness@...utronix.de,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, asantostc@...il.com, efault@....de,
gustavold@...il.com, calvin@...nvd.org, jv@...sburgh.net,
mpdesouza@...e.com, kernel-team@...a.com
Subject: Re: [PATCH net-next v5 4/4] netconsole: Use printk context for CPU
and task information
On Wed 2026-01-28 06:17:40, Breno Leitao wrote:
> Use the CPU and task name captured at printk() time from
> nbcon_write_context instead of querying the current execution context.
> This provides accurate information about where the message originated,
> rather than where netconsole happens to be running.
>
> For CPU, use wctxt->cpu instead of raw_smp_processor_id().
>
> For taskname, use wctxt->comm directly which contains the task
> name captured at printk time.
>
> This change ensures netconsole outputs reflect the actual context that
> generated the log message, which is especially important when the
> console driver runs asynchronously in a dedicated thread.
>
> Signed-off-by: Breno Leitao <leitao@...ian.org>
LGTM, feel free to use:
Reviewed-by: Petr Mladek <pmladek@...e.com>
Best Regards,
Petr
Powered by blists - more mailing lists