From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Eugene Syromyatnikov <evgsyr@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/asm/64: do not clear high 32 bits of syscall number when CONFIG_X86_X32=y
Date: Thu, 14 Sep 2017 23:24:30 +0300 [thread overview]
Message-ID: <20170914202429.GB16764@altlinux.org> (raw)
In-Reply-To: <CACGkJdsGVwqdE6MqZqG4hxGuqOL5aOeJR+PhLvwcWmfFmjkyyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
On Thu, Sep 14, 2017 at 07:40:43PM +0000, Eugene Syromyatnikov wrote:
> On Wed, Sep 13, 2017 at 4:49 PM, Oleg Nesterov <oleg@redhat.com> wrote:
> > IOW, why do we want to silently ignore the upper bits in $rax ?
>
> By the way, they are ignored elsewhere, in audit[1] or seccomp[2], for example.
>
> [1] include/linux/audit.h
> [2] include/uapi/linux/seccomp.h, definition of struct seccomp_data
Yes, unfortunately, they are ignored later, but that is another story.
--
ldv
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-09-14 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 22:57 Dmitry V. Levin
2017-09-13 16:49 ` Oleg Nesterov
2017-09-14 19:40 ` Eugene Syromyatnikov
2017-09-14 20:24 ` Dmitry V. Levin [this message]
2017-09-14 20:21 ` Dmitry V. Levin
2017-09-15 16:12 ` Oleg Nesterov
2017-09-14 21:05 ` Andy Lutomirski
2017-09-14 21:33 ` Dmitry V. Levin
2017-09-14 21:38 ` Andy Lutomirski
2017-09-15 5:31 ` Ingo Molnar
2017-09-15 5:46 ` hpa
2017-09-17 16:45 ` Dmitry V. Levin
2017-09-15 5:47 ` hpa
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=20170914202429.GB16764@altlinux.org \
--to=ldv@altlinux.org \
--cc=evgsyr@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@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
Powered by JetHome