[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aXo9DO9OCJ0I7ID5@gmail.com>
Date: Wed, 28 Jan 2026 08:46:10 -0800
From: Breno Leitao <leitao@...ian.org>
To: John Ogness <john.ogness@...utronix.de>
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>, pmladek@...e.com,
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
Hello John,
On Wed, Jan 28, 2026 at 04:09:07PM +0106, John Ogness wrote:
> On 2026-01-28, Breno Leitao <leitao@...ian.org> 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>
>
> Reviewed-by: John Ogness <john.ogness@...utronix.de>
Thank you so much for all the reviews and your support throughout this
migration. I really appreciate it!
---breno
Powered by blists - more mailing lists