From: Will Deacon <will@kernel.org>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
clang-built-linux@googlegroups.com, linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] arm64: compat: Fix syscall number of compat_clock_getres
Date: Thu, 19 Mar 2020 18:42:59 +0000 [thread overview]
Message-ID: <20200319184258.GC27141@willie-the-truck> (raw)
In-Reply-To: <20200319141138.19343-1-vincenzo.frascino@arm.com>
On Thu, Mar 19, 2020 at 02:11:38PM +0000, Vincenzo Frascino wrote:
> The syscall number of compat_clock_getres was erroneously set to 247
> instead of 264. This causes the vDSO fallback of clock_getres to land
> on the wrong syscall.
>
> Address the issue fixing the syscall number of compat_clock_getres.
>
> Fixes: 53c489e1dfeb6 ("arm64: compat: Add missing syscall numbers")
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
> ---
> arch/arm64/include/asm/unistd.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/include/asm/unistd.h b/arch/arm64/include/asm/unistd.h
> index 1dd22da1c3a9..803039d504de 100644
> --- a/arch/arm64/include/asm/unistd.h
> +++ b/arch/arm64/include/asm/unistd.h
> @@ -25,8 +25,8 @@
> #define __NR_compat_gettimeofday 78
> #define __NR_compat_sigreturn 119
> #define __NR_compat_rt_sigreturn 173
> -#define __NR_compat_clock_getres 247
> #define __NR_compat_clock_gettime 263
> +#define __NR_compat_clock_getres 264
> #define __NR_compat_clock_gettime64 403
> #define __NR_compat_clock_getres_time64 406
Ha, what a howler. I'll queue this one as a fix.
Will
prev parent reply other threads:[~2020-03-19 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 14:11 [PATCH] arm64: compat: Fix syscall number of compat_clock_getres Vincenzo Frascino
2020-03-19 15:39 ` Nick Desaulniers
2020-03-19 17:03 ` Vincenzo Frascino
2020-03-19 18:12 ` Catalin Marinas
2020-03-19 18:52 ` Will Deacon
2020-03-20 12:30 ` Vincenzo Frascino
2020-03-19 18:42 ` Will Deacon [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=20200319184258.GC27141@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vincenzo.frascino@arm.com \
--cc=will.deacon@arm.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).