Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: "André Almeida" <andrealmeid@igalia.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Darren Hart <dvhart@infradead.org>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Arnd Bergmann <arnd@arndb.de>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Waiman Long <longman@redhat.com>,
	Ryan Houdek <Sonicadvance1@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-api@vger.kernel.org, kernel-dev@igalia.com
Subject: Re: [PATCH v6 0/9] futex: Create {set,get}_robust_list2() syscalls
Date: Sat, 22 Nov 2025 11:25:44 -0300	[thread overview]
Message-ID: <32cbcdbf-c98e-4075-b5cd-a7e001de05b3@igalia.com> (raw)
In-Reply-To: <20251122-tonyk-robust_futex-v6-0-05fea005a0fd@igalia.com>

Em 22/11/2025 02:50, André Almeida escreveu:
> Hello,
> 
> This version is a complete rewrite of the syscall (thanks Thomas for the
> suggestions!).
> 
>   * Use case
> 
> The use-case for the new syscalls is detailed in the last patch version:
> 
>    https://lore.kernel.org/lkml/20250626-tonyk-robust_futex-v5-0-179194dbde8f@igalia.com
> 
>   * The syscall interface
> 
> Documented at patches 3/9 "futex: Create set_robust_list2() syscall" and
> 4/9 "futex: Create get_robust_list2() syscall".
> 
>   * Testing
> 
> I expanded the current robust list selftest to use the new interface,
> and also ported the original syscall to use the new syscall internals,
> and everything survived the tests.
> 
>   * Changelog
> 
> Changes from v5:
>   - Complete interface rewrite, there are so many changes but the main
>     ones are the following points
>   - Array of robust lists now has a static size, allocated once during the
>     first usage of the list
>   - Now that the list of robust lists have a fixed size, I removed the
>     logic of having a command for creating a new index on the list. To
>     simplify things for everyone, userspace just need to call
>     set_robust_list2(head, 32-bit/64-bit type, index).

Actually, this won't work well. The application that calls 
set_robust_list2() may be using glibc, that will also want to call 
set_robust_list2(), and there's no way to know which lists are being by 
each library. I will re-add the create/modify logic for the next version.

      parent reply	other threads:[~2025-11-22 14:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-22  5:50 [PATCH v6 0/9] futex: Create {set,get}_robust_list2() syscalls André Almeida
2025-11-22  5:50 ` [PATCH v6 1/9] futex: Use explicit sizes for compat_robust_list structs André Almeida
2025-11-22  5:50 ` [PATCH v6 2/9] futex: Make exit_robust_list32() unconditionally available for 64-bit kernels André Almeida
2025-11-22  5:50 ` [PATCH v6 3/9] futex: Create set_robust_list2() syscall André Almeida
2025-11-22  5:50 ` [PATCH v6 4/9] futex: Create get_robust_list2() syscall André Almeida
2025-11-23  7:16   ` kernel test robot
2025-11-23 10:02   ` kernel test robot
2025-11-22  5:50 ` [PATCH v6 5/9] futex: Wire up set_robust_list2 syscall André Almeida
2025-11-22  5:50 ` [PATCH v6 6/9] futex: Wire up get_robust_list2 syscall André Almeida
2025-11-22  6:49   ` kernel test robot
2025-11-23 18:47     ` Thomas Gleixner
2025-11-23 19:19       ` Arnd Bergmann
2025-11-23 20:02         ` Thomas Gleixner
2025-11-22  7:32   ` kernel test robot
2025-11-22  7:44   ` kernel test robot
2025-11-22  5:50 ` [PATCH v6 7/9] selftests/futex: Expand for set_robust_list2() André Almeida
2025-11-22  5:50 ` [PATCH v6 8/9] selftests/futex: Expand for get_robust_list2() André Almeida
2025-11-22  5:50 ` [PATCH v6 9/9] futex: Use new robust list API internally André Almeida
2025-11-22 14:25 ` André Almeida [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=32cbcdbf-c98e-4075-b5cd-a7e001de05b3@igalia.com \
    --to=andrealmeid@igalia.com \
    --cc=Sonicadvance1@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bigeasy@linutronix.de \
    --cc=dave@stgolabs.net \
    --cc=dvhart@infradead.org \
    --cc=kernel-dev@igalia.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox