[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc8225b1fbdde38867f41955f34b748bb9f4f898.camel@web.de>
Date: Sun, 31 Aug 2025 17:21:13 +0200
From: Bert Karwatzki <spasswolf@....de>
To: seanjc@...gle.com
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rt-devel@...ts.linux.dev, Andrew Morton <akpm@...ux-foundation.org>,
linux-mm@...ck.org, Jakub Kicinski <kuba@...nel.org>, Peter Zijlstra
<peterz@...radead.org>, torvalds@...ux-foundation.org, x86@...nel.org,
tglx@...utronix.de, bp@...en8.de, spasswolf@....de
Subject: Re: (Re)boot hangs and refcount errors on next-20250829
I've found the missing piece of the patch here:
https://lore.kernel.org/all/175664303766.1920.13212322629796216488.tip-bot2@tip-bot2/#t
diff --git a/kernel/futex/core.c b/kernel/futex/core.c
index fb63c13aa66f..125804fbb5cb 100644
--- a/kernel/futex/core.c
+++ b/kernel/futex/core.c
@@ -1722,6 +1722,7 @@ int futex_mm_init(struct mm_struct *mm)
RCU_INIT_POINTER(mm->futex_phash, NULL);
mm->futex_phash_new = NULL;
/* futex-ref */
+ mm->futex_ref = NULL;
atomic_long_set(&mm->futex_atomic, 0);
mm->futex_batches = get_state_synchronize_rcu();
return 0;
This solves all the mentioned Problems!
Bert Karwatzki
Powered by blists - more mailing lists