From: Ingo Molnar <mingo@kernel.org>
To: peterz@infradead.org
Cc: tglx@linutronix.de, axboe@kernel.dk,
linux-kernel@vger.kernel.org, mingo@redhat.com,
dvhart@infradead.org, dave@stgolabs.net, andrealmeid@igalia.com,
Andrew Morton <akpm@linux-foundation.org>,
urezki@gmail.com, hch@infradead.org, lstoakes@gmail.com,
Arnd Bergmann <arnd@arndb.de>,
linux-api@vger.kernel.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, malteskarupke@web.de,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH v3 10/15] futex: Add sys_futex_requeue()
Date: Fri, 22 Sep 2023 11:35:03 +0200 [thread overview]
Message-ID: <ZQ1fx29+b8PmLVk6@gmail.com> (raw)
In-Reply-To: <20230921105248.511860556@noisy.programming.kicks-ass.net>
* peterz@infradead.org <peterz@infradead.org> wrote:
> --- linux-2.6.orig/kernel/futex/syscalls.c
> +++ linux-2.6/kernel/futex/syscalls.c
> @@ -396,6 +396,44 @@ SYSCALL_DEFINE6(futex_wait,
> return ret;
> }
>
> +/*
> + * sys_futex_requeue - Requeue a waiter from one futex to another
> + * @waiters: array describing the source and destination futex
> + * @flags: unused
> + * @nr_wake: number of futexes to wake
> + * @nr_requeue: number of futexes to requeue
> + *
> + * Identical to the traditional FUTEX_CMP_REQUEUE op, except it is part of the
> + * futex2 family of calls.
> + */
> +
> +SYSCALL_DEFINE4(futex_requeue,
> + struct futex_waitv __user *, waiters,
> + unsigned int, flags,
> + int, nr_wake,
> + int, nr_requeue)
> +{
> + struct futex_vector futexes[2];
> + u32 cmpval;
> + int ret;
> +
> + if (flags)
> + return -EINVAL;
Small detail, but isn't -ENOSYS the canonical error code for functionality
not yet implemented - which the unused 'flags' ABI is arguably?
-EINVAL is for recognized but incorrect parameters, such as:
> + if (!waiters)
> + return -EINVAL;
Thanks,
Ingo
next prev parent reply other threads:[~2023-09-22 9:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 10:45 [PATCH v3 00/15] futex: More futex2 bits peterz
2023-09-21 10:45 ` [PATCH v3 04/15] futex: Validate futex value against futex size peterz
2023-09-21 10:45 ` [PATCH v3 05/15] futex: Add sys_futex_wake() peterz
2023-09-21 10:45 ` [PATCH v3 07/15] futex: Add sys_futex_wait() peterz
2023-09-21 10:45 ` [PATCH v3 08/15] futex: Propagate flags into get_futex_key() peterz
2023-09-21 10:45 ` [PATCH v3 09/15] futex: Add flags2 argument to futex_requeue() peterz
2023-09-21 10:45 ` [PATCH v3 10/15] futex: Add sys_futex_requeue() peterz
2023-09-22 9:35 ` Ingo Molnar [this message]
2023-09-22 11:03 ` Peter Zijlstra
2023-09-22 13:56 ` Jens Axboe
2023-09-21 10:45 ` [PATCH v3 11/15] mm: Add vmalloc_huge_node() peterz
2023-09-21 10:45 ` [PATCH v3 12/15] futex: Implement FUTEX2_NUMA peterz
2023-09-21 10:45 ` [PATCH v3 13/15] futex: Propagate flags into futex_get_value_locked() peterz
2023-09-21 10:45 ` [PATCH v3 14/15] futex: Enable FUTEX2_{8,16} peterz
2023-09-21 10:45 ` [PATCH v3 15/15] futex,selftests: Extend the futex selftests peterz
2023-09-21 11:41 ` Peter Zijlstra
[not found] ` <20230921105248.048643656@noisy.programming.kicks-ass.net>
2023-09-21 15:14 ` [PATCH v3 06/15] futex: FLAGS_STRICT Thomas Gleixner
2023-09-22 20:01 ` futex2 numa stuff Peter Zijlstra
2023-09-22 20:01 ` [PATCH 15/15] futex,selftests: Extend the futex selftests Peter Zijlstra
2023-09-22 20:01 ` [PATCH 16/15] futex,selftests: Extend the futex selftests for NUMA Peter Zijlstra
2023-09-22 20:01 ` [PATCH 17/15] [HACK] futex: Force futex hash collision Peter Zijlstra
2023-09-28 13:40 ` futex2 numa stuff Davidlohr Bueso
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=ZQ1fx29+b8PmLVk6@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@igalia.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=malteskarupke@web.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).