From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Sean Christopherson <seanjc@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] locking/urgent for v6.17-rc1
Date: Fri, 22 Aug 2025 16:16:54 +0200 [thread overview]
Message-ID: <20250822141654.Sjoffo8F@linutronix.de> (raw)
In-Reply-To: <aKd3cNJqj6_g_ATE@google.com>
On 2025-08-21 12:45:52 [-0700], Sean Christopherson wrote:
> Piggybacking the futex private hashing attention, the new fanciness is causing
> crashes in my testing. The crashes are 100% reproducible, but my reproducer is
> simply running a variety of tests in parallel, i.e. isn't very debug-friendly,
> and the code itself is black magic to me, so all I've done is bisect.
>
> I reported the issue on the original thread, but haven't seen any follow-up.
>
> https://lore.kernel.org/all/aJ_vEP2EHj6l0xRT@google.com
I somehow missed it. Can you try rc2 with the patch I just sent?
Sebastian
next prev parent reply other threads:[~2025-08-22 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 18:02 Borislav Petkov
2025-08-10 5:58 ` pr-tracker-bot
2025-08-21 18:19 ` Linus Torvalds
2025-08-21 19:45 ` Sean Christopherson
2025-08-22 14:16 ` Sebastian Andrzej Siewior [this message]
2025-08-23 0:28 ` Sean Christopherson
2025-08-25 16:04 ` Sebastian Andrzej Siewior
2025-08-25 23:55 ` Sean Christopherson
2025-08-22 10:57 ` Sebastian Andrzej Siewior
2025-08-22 14:12 ` [PATCH] futex: Move futex_hash_free() back to __mmput() Sebastian Andrzej Siewior
2025-08-27 11:34 ` [tip: locking/urgent] " tip-bot2 for Sebastian Andrzej Siewior
2025-08-31 12:23 ` tip-bot2 for Sebastian Andrzej Siewior
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=20250822141654.Sjoffo8F@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®