Thread (18 messages) 18 messages, 4 authors, 2026-02-03

Re: [PATCH net-next v5 4/4] netconsole: Use printk context for CPU and task information

From: John Ogness <john.ogness@linutronix.de>
Date: 2026-01-28 15:03:12
Also in: lkml

On 2026-01-28, Breno Leitao [off-list ref] 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@debian.org>
Reviewed-by: John Ogness <john.ogness@linutronix.de>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help