linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bert Karwatzki <spasswolf@web.de>
To: seanjc@google.com
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	 linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-rt-devel@lists.linux.dev,
	Andrew Morton <akpm@linux-foundation.org>,
	 linux-mm@kvack.org, Jakub Kicinski <kuba@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	torvalds@linux-foundation.org, x86@kernel.org,
	 tglx@linutronix.de, bp@alien8.de, spasswolf@web.de
Subject: Re: (Re)boot hangs and refcount errors on next-20250829
Date: Sun, 31 Aug 2025 17:21:13 +0200	[thread overview]
Message-ID: <cc8225b1fbdde38867f41955f34b748bb9f4f898.camel@web.de> (raw)
In-Reply-To: <20250831141426.2786-1-spasswolf@web.de>

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


  reply	other threads:[~2025-08-31 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-31 14:14 Bert Karwatzki
2025-08-31 15:21 ` Bert Karwatzki [this message]
2025-08-31 15:39 ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc8225b1fbdde38867f41955f34b748bb9f4f898.camel@web.de \
    --to=spasswolf@web.de \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox