public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: "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>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
	"Carlos O'Donell" <carlos@redhat.com>,
	"Florian Weimer" <fweimer@redhat.com>,
	"Darren Hart" <dvhart@infradead.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Thomas Weißschuh" <linux@weissschuh.net>
Cc: linux-kernel@vger.kernel.org, kernel-dev@igalia.com,
	"André Almeida" <andrealmeid@igalia.com>
Subject: Re: [PATCH 2/2] selftests: futex: Add tests for robust release operations
Date: Fri, 27 Mar 2026 17:04:04 +0100	[thread overview]
Message-ID: <87y0jdb6ob.ffs@tglx> (raw)
In-Reply-To: <20260326-tonyk-vdso_test-v1-2-30a6f78c8bc3@igalia.com>

On Thu, Mar 26 2026 at 11:31, André Almeida wrote:
> +
> +	ret = sys_futex_robust_unlock(futex, FUTEX_ROBUST_UNLOCK | variant->op, tid,
> +				      &head.list_op_pending, variant->val3);

You need FUTEX_ROBUST_UNLOCK32 for 32-bit builds too.

  reply	other threads:[~2026-03-27 16:04 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 [this message]
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

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=87y0jdb6ob.ffs@tglx \
    --to=tglx@kernel.org \
    --cc=andrealmeid@igalia.com \
    --cc=arnd@arndb.de \
    --cc=bigeasy@linutronix.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 \
    /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