All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "André Almeida" <andrealmeid@igalia.com>,
	kernel-dev@igalia.com,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	linux-api@vger.kernel.org, "Darren Hart" <dvhart@infradead.org>,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Torvald Riegel" <triegel@redhat.com>,
	"Davidlohr Bueso" <dave@stgolabs.net>,
	"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
	"Rich Felker" <dalias@aerifal.cx>,
	"Carlos O'Donell" <carlos@redhat.com>,
	"Michal Hocko" <mhocko@suse.com>,
	linux-kernel@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [RFC PATCH 0/2] futex: how to solve the robust_list race condition?
Date: Mon, 02 Mar 2026 08:31:24 +0100	[thread overview]
Message-ID: <lhufr6ihelv.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <694424f4-20d1-4473-8955-859acbad466f@efficios.com> (Mathieu Desnoyers's message of "Sun, 1 Mar 2026 10:49:15 -0500")

* Mathieu Desnoyers:

> Of course, we'd have to implement the whole transaction in assembler
> for each architecture.

Could this be hidden ina vDSO call?  It would have to receive a pointer
to the rseq area in addition to other arguments that identify the unlock
operation to be performed.  The advantage is that the kernel would now
the addresses involved, so a single rseq flag should be sufficient.  It
could also vary the LL/SC sequence based on architecture capabilities.

The question is whether we can model the unlock operation so that it's
sufficiently generic.

Thanks,
Florian


  reply	other threads:[~2026-03-02  7:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 20:26 [RFC PATCH 0/2] futex: how to solve the robust_list race condition? André Almeida
2026-02-20 20:26 ` [RFC PATCH 1/2] futex: Create reproducer for robust_list race condition André Almeida
2026-03-12  9:04   ` Sebastian Andrzej Siewior
2026-03-12 13:36     ` André Almeida
2026-02-20 20:26 ` [RFC PATCH 2/2] futex: hack: Add debug delays André Almeida
2026-02-20 20:51 ` [RFC PATCH 0/2] futex: how to solve the robust_list race condition? Liam R. Howlett
2026-02-27 19:15   ` André Almeida
2026-02-20 21:42 ` Mathieu Desnoyers
2026-02-20 22:41   ` Mathieu Desnoyers
2026-02-20 23:17     ` Mathieu Desnoyers
2026-02-23 11:13       ` Florian Weimer
2026-02-23 13:37         ` Mathieu Desnoyers
2026-02-23 13:47           ` Rich Felker
2026-02-27 19:16       ` André Almeida
2026-02-27 19:59         ` Mathieu Desnoyers
2026-02-27 20:41           ` Suren Baghdasaryan
2026-03-01 15:49           ` Mathieu Desnoyers
2026-03-02  7:31             ` Florian Weimer [this message]
2026-03-02 14:57               ` Mathieu Desnoyers
2026-03-02 15:32                 ` Florian Weimer
2026-03-02 16:32                   ` Mathieu Desnoyers
2026-03-02 16:42                     ` Florian Weimer
2026-03-02 16:56                       ` Mathieu Desnoyers

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=lhufr6ihelv.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=andrealmeid@igalia.com \
    --cc=carlos@redhat.com \
    --cc=dalias@aerifal.cx \
    --cc=dave@stgolabs.net \
    --cc=dvhart@infradead.org \
    --cc=kernel-dev@igalia.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhocko@suse.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@kernel.org \
    --cc=triegel@redhat.com \
    /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.