From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: uid16: fix __kernel_old_{gid,uid}_t definitions
Date: Mon, 02 Jun 2014 13:45:39 +0200 [thread overview]
Message-ID: <24318565.Hg3EHrYVE1@wuerfel> (raw)
In-Reply-To: <1401706049-1787-1-git-send-email-will.deacon@arm.com>
On Monday 02 June 2014 11:47:29 Will Deacon wrote:
> Whilst native arm64 applications don't have the 16-bit UID/GID syscalls
> wired up, compat tasks can still access them. The 16-bit wrappers for
> these syscalls use __kernel_old_uid_t and __kernel_old_gid_t, which must
> be 16-bit data types to maintain compatibility with the 16-bit UIDs used
> by compat applications.
>
> This patch defines 16-bit __kernel_old_{gid,uid}_t types for arm64
> instead of using the 32-bit types provided by asm-generic.
>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Is this a theoretical problem, or did you actually encounter binaries
with old uid syscalls?
Arnd
next prev parent reply other threads:[~2014-06-02 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 10:47 [PATCH] arm64: uid16: fix __kernel_old_{gid,uid}_t definitions Will Deacon
2014-06-02 11:45 ` Arnd Bergmann [this message]
2014-06-02 12:35 ` Will Deacon
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=24318565.Hg3EHrYVE1@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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