[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG48ez1RBhBbH8jHwseeZMQwdKciLdjYhoy3O9yDs8WEpMk2TQ@mail.gmail.com>
Date: Tue, 13 Mar 2018 14:16:01 -0700
From: Jann Horn <jannh@...gle.com>
To: "Tautschnig, Michael" <tautschn@...zon.co.uk>
Cc: "x86@...nel.org" <x86@...nel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Jaswinder Singh <jaswinder@...radead.org>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH] x86: always use SYSCALL_DEFINE*
On Sat, Mar 10, 2018 at 12:55 PM, Tautschnig, Michael
<tautschn@...zon.co.uk> wrote:
> All syscall arguments are passed in as types of the same byte size as
> unsigned long (width of full registers). Using a smaller type without a
> cast may result in losing bits of information. SYSCALL_DEFINE* introduce
> adequate type casts. All definitions of syscalls in x86 except for those
> patched here have already been using the appropriate SYSCALL_DEFINE*.
[...]
> diff --git a/arch/x86/kernel/ioport.c b/arch/x86/kernel/ioport.c
> index 2f72330..d98b2a3 100644
> --- a/arch/x86/kernel/ioport.c
> +++ b/arch/x86/kernel/ioport.c
> @@ -23,7 +23,8 @@
> /*
> * this changes the io permissions bitmap in the current task.
> */
> -asmlinkage long sys_ioperm(unsigned long from, unsigned long num, int turn_on)
> +SYSCALL_DEFINE3(sys_ioperm, unsigned long, from, unsigned long, num, int,
> + turn_on)
Shouldn't this be "SYSCALL_DEFINE3(ioperm, [...]", without the "sys_"?
Powered by blists - more mailing lists