linux-kernel - Re: [PATCH net-next v5 1/4] printk: Add execution context (task name/CPU) to printk

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] [day] [month] [year] [list]

Message-ID: <20260130173243.4e3fff89@kernel.org>
Date: Fri, 30 Jan 2026 17:32:43 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Breno Leitao <leitao@...ian.org>
Cc: Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
 <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
 <pabeni@...hat.com>, pmladek@...e.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 1/4] printk: Add execution context (task
 name/CPU) to printk_info

On Wed, 28 Jan 2026 06:17:37 -0800 Breno Leitao wrote:
> +config CONSOLE_HAS_EXECUTION_CTX
> +	bool
> +	help
> +	  Selected by console drivers that support execution context
> +	  (task name/CPU) in their output. This enables PRINTK_EXECUTION_CTX
> +	  to provide the necessary infrastructure.
> +
> +config PRINTK_EXECUTION_CTX
> +	bool "Include execution context (task/CPU) in printk messages"
> +	depends on PRINTK && CONSOLE_HAS_EXECUTION_CTX
> +	default CONSOLE_HAS_EXECUTION_CTX

AFAIU the double-symbol thing serves no practical purpose?
If none of the console drivers uses the metadata what would be the
point of capturing it?

Conversely if some console driver wants this data there's no option 
for the user to disable it.

AFAICT this patch should only add one invisible symbol for capturing
the context and have netcons enable it. I don't see a reason at this
stage to prompt users with netcons disabled whether they want
PRINTK_EXECUTION_CTX
-- 
pw-bot: cr