From: Chris Mason <mason@kernel.org>
To: peterz@infradead.org, tglx@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH RFC] __futex_pivot_hash() race
Date: Mon, 17 Aug 2026 18:01:41 -0700 [thread overview]
Message-ID: <20260818011036.1138213-1-mason@kernel.org> (raw)
This is really just AI questioning how we synchronize mmph->batches and
mmph->hash. It looks real to me, and the repro with printks does fire,
so hopefully I've got things right.
The patch and description were also AI, meaning this is more bug
report in patch form. Testing was only done against the one repro.
(I may or may not have successfully switched over my git config to
mason@kernel.org, lets see...)
next reply other threads:[~2026-08-18 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 1:01 Chris Mason [this message]
2026-08-18 1:01 ` [PATCH] futex: sample poll cookie after publishing new hash Chris Mason
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=20260818011036.1138213-1-mason@kernel.org \
--to=mason@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.