mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tautschnig, Michael" <tautschn@amazon.co.uk>
To: "x86@kernel.org" <x86@kernel.org>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Jaswinder Singh <jaswinder@infradead.org>,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] x86: always use SYSCALL_DEFINE*
Date: Sat, 10 Mar 2018 20:59:46 +0000	[thread overview]
Message-ID: <6490B647-209A-4CE6-BFDC-5EC2F62B466D@amazon.com> (raw)
In-Reply-To: <14A5C8D0-3F9D-486F-A20C-55849D70FC80@amazon.com>

On 10 Mar 2018, at 20:55, Tautschnig, Michael <tautschn@amazon.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*.
[...]

Additional context: I had previously made an attempt to ensure type
consistency of sys_ioperm as "Syscall arguments are unsigned long (full
registers)" (https://lkml.org/lkml/2016/7/4/336). I hope the new proposal
is more acceptable.

Best,
Michael



Amazon Web Services UK Limited. Registered in England and Wales with registration number 08650665 with its registered office at 1 Principal Place, Worship Street, London, EC2A 2FA, United Kingdom.




  reply	other threads:[~2018-03-10 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-10 20:55 Tautschnig, Michael
2018-03-10 20:59 ` Tautschnig, Michael [this message]
2018-03-11  9:43 ` [PATCH v2] " Tautschnig, Michael
2018-03-13 21:16 ` [PATCH] " Jann Horn
2018-03-13 23:18   ` Andy Lutomirski
2018-03-14  5:48     ` Dominik Brodowski
2018-03-14  9:43       ` Tautschnig, Michael

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=6490B647-209A-4CE6-BFDC-5EC2F62B466D@amazon.com \
    --to=tautschn@amazon.co.uk \
    --cc=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jaswinder@infradead.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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

all inboxes | Powered by JetHome®