All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: uid16: fix __kernel_old_{gid,uid}_t definitions
Date: Mon, 2 Jun 2014 13:35:17 +0100	[thread overview]
Message-ID: <20140602123517.GC13968@arm.com> (raw)
In-Reply-To: <24318565.Hg3EHrYVE1@wuerfel>

Hi Arnd,

On Mon, Jun 02, 2014 at 12:45:39PM +0100, Arnd Bergmann wrote:
> 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>

Cheers!

> Is this a theoretical problem, or did you actually encounter binaries
> with old uid syscalls?

I hit it during an AArch32 LTP run which passes '-1' for some parameters
to the 16-bit flavours of setreuid etc. So I suppose it's theoretical in
the sense that I've only observed the issue within a testsuite as opposed
to a real application.

Will

      reply	other threads:[~2014-06-02 12:35 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
2014-06-02 12:35   ` 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=20140602123517.GC13968@arm.com \
    --to=will.deacon@arm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.