linux-kernel - Re: [RFC PATCH] sched/core: Enhanced debug logs in do_task

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

Message-ID: <20241210141823.GU35539@noisy.programming.kicks-ass.net>
Date: Tue, 10 Dec 2024 15:18:23 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Zhongqiu Han <quic_zhonhan@...cinc.com>
Cc: mingo@...hat.com, juri.lelli@...hat.com, vincent.guittot@...aro.org,
	dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
	mgorman@...e.de, vschneid@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] sched/core: Enhanced debug logs in do_task_dead()

On Tue, Dec 10, 2024 at 09:45:13PM +0800, Zhongqiu Han wrote:
> If BUG() is a NOP, dump the problematic stack for debugging purposes.
> 
> Signed-off-by: Zhongqiu Han <quic_zhonhan@...cinc.com>
> ---
> If BUG() is a NOP, it should make sense for debugging purposes. However,
> just arising the patch with RFC, because at least for now, I haven't found
> a definition of BUG() as NOP in various architectures. Thanks~

Yeah, this don't make sense. If you want a stack-trace you shouldn't
have killed BUG.

And yeah, having done a quick peek, I don't see how you can kill BUG
these days other than explicitly modyfing your source, in which case you
get to keep the pieces.