All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: "Paul Walmsley" <pjw@kernel.org>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Alexandre Ghiti" <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	"André Almeida" <andrealmeid@igalia.com>,
	"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>
Subject: Re: [PATCH v2 0/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock()
Date: Thu, 02 Jul 2026 15:38:00 +0200	[thread overview]
Message-ID: <875x2xjyvb.fsf@yellow.woof> (raw)
In-Reply-To: <cover.1782998849.git.namcao@linutronix.de>

Nam Cao <namcao@linutronix.de> writes:
> This series adds new vdso futex entries, allowing user to address the robust
> futex race condition regarding clearing the robust_list_head::list_op_pending
> pointer.
>
> Thomas wrote a summary of the problem:
> https://lore.kernel.org/lkml/20260602084648.462672743@kernel.org/
>
> The core infrastructure has been implemented along with x86 support. This
> series adds RISC-V support.
>
> The first 4 patches prepare compat vdso Makefile. The final patch is the main
> show.

Sorry, I hit send before saving. This v2 addresses some of Sashiko's
comments, while the rest of the comments are addressed by Thomas in:

https://lore.kernel.org/linux-riscv/20260701-riscv-vdso-lto-v1-0-89db0cd82077@linutronix.de/
https://lore.kernel.org/linux-riscv/20260630-riscv-vdso32-alternative-v1-0-a32fd89b7b1c@linutronix.de/

Nam

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Nam Cao <namcao@linutronix.de>
To: "Paul Walmsley" <pjw@kernel.org>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Alexandre Ghiti" <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	"André Almeida" <andrealmeid@igalia.com>,
	"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>
Subject: Re: [PATCH v2 0/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock()
Date: Thu, 02 Jul 2026 15:38:00 +0200	[thread overview]
Message-ID: <875x2xjyvb.fsf@yellow.woof> (raw)
In-Reply-To: <cover.1782998849.git.namcao@linutronix.de>

Nam Cao <namcao@linutronix.de> writes:
> This series adds new vdso futex entries, allowing user to address the robust
> futex race condition regarding clearing the robust_list_head::list_op_pending
> pointer.
>
> Thomas wrote a summary of the problem:
> https://lore.kernel.org/lkml/20260602084648.462672743@kernel.org/
>
> The core infrastructure has been implemented along with x86 support. This
> series adds RISC-V support.
>
> The first 4 patches prepare compat vdso Makefile. The final patch is the main
> show.

Sorry, I hit send before saving. This v2 addresses some of Sashiko's
comments, while the rest of the comments are addressed by Thomas in:

https://lore.kernel.org/linux-riscv/20260701-riscv-vdso-lto-v1-0-89db0cd82077@linutronix.de/
https://lore.kernel.org/linux-riscv/20260630-riscv-vdso32-alternative-v1-0-a32fd89b7b1c@linutronix.de/

Nam

  parent reply	other threads:[~2026-07-02 13:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 13:34 [PATCH v2 0/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock() Nam Cao
2026-07-02 13:34 ` Nam Cao
2026-07-02 13:34 ` [PATCH v2 1/5] riscv: compat_vdso: switch to standard kbuild rule Nam Cao
2026-07-02 13:34   ` Nam Cao
2026-07-02 13:34 ` [PATCH v2 2/5] riscv: compat_vdso: Allow *.c source files Nam Cao
2026-07-02 13:34   ` Nam Cao
2026-07-02 13:34 ` [PATCH v2 3/5] riscv: compat_vdso: Introduce COMPAT_MARCH variable Nam Cao
2026-07-02 13:34   ` Nam Cao
2026-07-02 13:34 ` [PATCH v2 4/5] riscv: compat_vdso: Build with zacas if available Nam Cao
2026-07-02 13:34   ` Nam Cao
2026-07-02 13:34 ` [PATCH v2 5/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock() Nam Cao
2026-07-02 13:34   ` Nam Cao
2026-07-02 13:38 ` Nam Cao [this message]
2026-07-02 13:38   ` [PATCH v2 0/5] " Nam Cao

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=875x2xjyvb.fsf@yellow.woof \
    --to=namcao@linutronix.de \
    --cc=alex@ghiti.fr \
    --cc=andrealmeid@igalia.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=palmer@dabbelt.com \
    --cc=peterz@infradead.org \
    --cc=pjw@kernel.org \
    --cc=tglx@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    /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.