linux-kernel - Re: [PATCH] thunderbolt: log path activation failures without WARN backtraces

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20260105111657.GL2275908@black.igk.intel.com>
Date: Mon, 5 Jan 2026 12:16:57 +0100
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: "Chia-Lin Kao (AceLan)" <acelan.kao@...onical.com>
Cc: Andreas Noever <andreas.noever@...il.com>,
	Mika Westerberg <westeri@...nel.org>,
	Yehezkel Bernat <YehezkelShB@...il.com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] thunderbolt: log path activation failures without WARN
 backtraces

On Fri, Jan 02, 2026 at 11:19:05AM +0800, Chia-Lin Kao (AceLan) wrote:
> tb_path_activate() currently logs failures with tb_WARN(), which triggers
> a stack trace. Transient conditions such as lane bonding or Type-C link
> hiccups can fail path activation briefly, and the resulting backtraces are
> noisy without aiding diagnosis.
> 
> Switch to tb_warn() for all path activation failures. The error code is
> already returned to callers, and the warning still shows the message
> without the backtrace.
> 
> Signed-off-by: Chia-Lin Kao (AceLan) <acelan.kao@...onical.com>

Applied to thunderbolt.git/next, thanks!