linux-kernel - Re: [PATCH 2/3] hung_task: extend hung task blocker tracking to rwsems

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: <twh66isgxspp72gz7u6bbfxkcyzxgggzqfma7cl37xrvd5k2aa@ibfr6ogn5ylk>
Date: Fri, 22 Aug 2025 17:25:27 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Lance Yang <ioworker0@...il.com>, akpm@...ux-foundation.org, 
	zi.li@...ux.dev, anna.schumaker@...cle.com, boqun.feng@...il.com, 
	joel.granados@...nel.org, jstultz@...gle.com, kent.overstreet@...ux.dev, 
	leonylgao@...cent.com, linux-kernel@...r.kernel.org, longman@...hat.com, 
	mhiramat@...nel.org, mingo@...hat.com, mingzhe.yang@...com, peterz@...radead.org, 
	rostedt@...dmis.org, senozhatsky@...omium.org, tfiga@...omium.org, will@...nel.org, 
	Lance Yang <lance.yang@...ux.dev>, Eero Tamminen <oak@...sinkinet.fi>, 
	linux-m68k <linux-m68k@...ts.linux-m68k.org>
Subject: Re: [PATCH 2/3] hung_task: extend hung task blocker tracking to
 rwsems

Hi Greet,

On (25/08/22 09:34), Geert Uytterhoeven wrote:
> WARNING: CPU: 0 PID: 39 at include/linux/hung_task.h:48
> __down_common+0x13a/0x1be
> CPU: 0 UID: 0 PID: 39 Comm: getty Not tainted
> 6.15.0-rc6hatari-00018-g194a9b9e843b #1986 NONE
> Stack from 01633d00:
>         01633d00 00366e9e 00366e9e 00000000 002c9762 00360cb5 01633d24 0000873e
>         00366e9e 01633d40 0002e0d4 00360cb5 00000030 00000009 0039c79a 00061408
>         01633d78 000028e0 00360cb5 00000030 002c9762 00000009 00000000 00000000
>         7fffffff 00000002 1185d266 01633eb0 01326c58 00000080 01633dc0 002c9762
>         00360cb5 00000030 00000009 00000000 00002014 01326c00 1185d266 01633eb0
>         002c93ea 00053d60 00061408 01326c58 0038db90 0038db90 01633e32 01633fb8
> Call Trace: [<002c9762>] __down_common+0x13a/0x1be
>  [<0000873e>] dump_stack+0x10/0x16
>  [<0002e0d4>] __warn+0x7a/0xbc
>  [<00061408>] msleep+0x0/0x2c
>  [<000028e0>] warn_slowpath_fmt+0x42/0x62
>  [<002c9762>] __down_common+0x13a/0x1be
>  [<002c9762>] __down_common+0x13a/0x1be
>  [<00002014>] arch_local_irq_enable+0xe/0x22
>  [<002c93ea>] mutex_lock+0x0/0x28
>  [<00053d60>] other_cpu_in_panic+0x0/0x26
>  [<00061408>] msleep+0x0/0x2c
>  [<002c97fc>] __down+0x16/0x1e
>  [<002c9832>] down+0x2e/0x30
>  [<00053dac>] console_lock+0x26/0x4c
>  [<001aae4e>] do_con_write+0x3a/0x16d4
>  [<002c93ea>] mutex_lock+0x0/0x28
>  [<0004fa70>] __add_wait_queue+0x3a/0x6a
>  [<001ac520>] con_write+0x1a/0x30
>  [<0019cafa>] n_tty_write+0x2c6/0x35e
>  [<00199456>] signal_pending+0x0/0x26
>  [<000aba2a>] __kvmalloc_node_noprof+0x3a/0x114
>  [<00004cc0>] io_uring_try_cancel_requests+0x98/0x318
>  [<0004fb2e>] woken_wake_function+0x0/0x24
>  [<0019a180>] file_tty_write.isra.0+0x144/0x1b8
>  [<0019a206>] tty_write+0x12/0x16
>  [<000b97c2>] vfs_write+0xec/0x148
>  [<00028000>] fp_getdest+0x1b8/0x224
>  [<00010000>] g_trace+0x16/0x28
>  [<000b9916>] ksys_write+0x54/0x8a
>  [<000b9962>] sys_write+0x16/0x1a
>  [<000093da>] syscall+0x8/0xc
>  [<0000c001>] arch_dma_prep_coherent+0x51/0x58

I'm struggling to make any sense out of this backtrace, this looks
like random ksyms names.  Any chance you can get more reliable/informative
backtrace?  config-debug maybe, or something.