linux-kernel - __put_task_struct() WARN_ON(!tsk->exit

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

Date:   Sat, 3 Dec 2022 11:24:43 -0800
From:   "Paul E. McKenney" <paulmck@...nel.org>
To:     linux-kernel@...r.kernel.org
Cc:     akpm@...ux-foundation.org, ebiederm@...ssion.com,
        tglx@...utronix.de, bigeasy@...utronix.de, luto@...nel.org,
        Liam.Howlett@...cle.com, fenghua.yu@...el.com, peterz@...radead.org
Subject: __put_task_struct() WARN_ON(!tsk->exit_state)?

Hello!

One of last night's rcutorture TREE03 runs triggered the
__put_task_struct() function's first WARN_ON() complaining that
the tasks's ->exit_state was zero.  This was on mainline merged
into RCU's "dev" branch.  There immediately follows a splat from
refcount_warn_saturate(), so there are two interlaced stack dumps.  :-/

What I do have seems to implicate rt_mutex priority boosting triggered
by RCU's prioritiy boosting.

Left to myself, my next steps are to try to reproduce this.  It happened
once in 150 hours of TREE03, so who knows?

But I figured I should check to see if anyone else is hitting this.

						Thanx, Paul