From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: linux-kernel@vger.kernel.org, patches@lists.linux.dev
Cc: linux-crypto@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH v4 1/3] random: add vgetrandom_alloc() syscall
Date: Sat, 19 Nov 2022 01:20:05 +0100 [thread overview]
Message-ID: <Y3ghNUQ8WDROiVHh@zx2c4.com> (raw)
In-Reply-To: <20221118172839.2653829-2-Jason@zx2c4.com>
On Fri, Nov 18, 2022 at 06:28:37PM +0100, Jason A. Donenfeld wrote:
> diff --git a/arch/x86/entry/syscalls/syscall_32.tbl b/arch/x86/entry/syscalls/syscall_32.tbl
> index 320480a8db4f..ea0fbc2ded5e 100644
> --- a/arch/x86/entry/syscalls/syscall_32.tbl
> +++ b/arch/x86/entry/syscalls/syscall_32.tbl
This also needs to be wired into unistd.h, sys_ni.c, and
checksyscalls.sh, with its definition dependent on a new
__ARCH_WANT_VGETRANDOM_ALLOC macro symbol, like all the other new
syscalls that get added arch-by-arch. I'll do this for v+1.
Jason
next prev parent reply other threads:[~2022-11-19 1:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 17:28 [PATCH v4 0/3] implement getrandom() in vDSO Jason A. Donenfeld
2022-11-18 17:28 ` [PATCH v4 1/3] random: add vgetrandom_alloc() syscall Jason A. Donenfeld
2022-11-19 0:20 ` Jason A. Donenfeld [this message]
2022-11-18 17:28 ` [PATCH v4 2/3] random: introduce generic vDSO getrandom() implementation Jason A. Donenfeld
2022-11-18 19:34 ` Christophe Leroy
2022-11-18 23:55 ` Jason A. Donenfeld
2022-11-19 0:04 ` Jason A. Donenfeld
2022-11-19 7:51 ` Christophe Leroy
2022-11-19 11:43 ` Jason A. Donenfeld
2022-11-19 12:12 ` Jason A. Donenfeld
2022-11-18 17:28 ` [PATCH v4 3/3] x86: vdso: Wire up getrandom() vDSO implementation Jason A. Donenfeld
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=Y3ghNUQ8WDROiVHh@zx2c4.com \
--to=jason@zx2c4.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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