From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Thomas Gleixner <tglx@kernel.org>
Cc: "André Almeida" <andrealmeid@igalia.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Carlos O'Donell" <carlos@redhat.com>,
"Florian Weimer" <fweimer@redhat.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Thomas Weißschuh" <linux@weissschuh.net>,
linux-kernel@vger.kernel.org, kernel-dev@igalia.com
Subject: Re: [PATCH 0/2] futex: Docs and tests for robust futex unlock race
Date: Fri, 27 Mar 2026 08:18:41 +0100 [thread overview]
Message-ID: <20260327071841.1dtzTPR-@linutronix.de> (raw)
In-Reply-To: <87mrzuczre.ffs@tglx>
On 2026-03-26 17:38:13 [+0100], Thomas Gleixner wrote:
> > Ideally I would like to inject some error to the vDSO test, so we can really
> > test the mechanism of it being interrupted and the kernel cleaning the
> > list_op_pending, using ASM injection or ptrace(), but I have left for a next
> > patch for now.
>
> Please sync with Sebastian. He wanted to look into this ptrace thing
> too.
I did send you something. I just need to figure out why the kernel side
is not updating it after the cmpxchg()…
> Thanks,
>
> tglx
Sebastian
prev parent reply other threads:[~2026-03-27 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 14:31 [PATCH 0/2] futex: Docs and tests for robust futex unlock race André Almeida
2026-03-26 14:31 ` [PATCH 1/2] Documentation: futex: Add a note about robust list race condition André Almeida
2026-03-26 14:31 ` [PATCH 2/2] selftests: futex: Add tests for robust release operations André Almeida
2026-03-27 16:04 ` Thomas Gleixner
2026-03-26 16:38 ` [PATCH 0/2] futex: Docs and tests for robust futex unlock race Thomas Gleixner
2026-03-27 7:18 ` Sebastian Andrzej Siewior [this message]
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=20260327071841.1dtzTPR-@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andrealmeid@igalia.com \
--cc=arnd@arndb.de \
--cc=carlos@redhat.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=fweimer@redhat.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox