From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next] system/skeleton: use uid/gid 65534 for nobody/nogroup
Date: Fri, 26 Aug 2016 15:39:49 +0200 [thread overview]
Message-ID: <20160826153949.1c0b5b7e@free-electrons.com> (raw)
In-Reply-To: <1472161636-2504-1-git-send-email-peter@korsgaard.com>
Hello,
On Thu, 25 Aug 2016 23:47:16 +0200, Peter Korsgaard wrote:
> As recently discussed on lwn.net: https://lwn.net/Articles/695478/
>
> The kernel has special behaviour for uid/gid 65534:
>
> 1. The kernel maps UIDs > 65535 to it when some subsystem/API/fs
> only supports 16bit UIDs, but a 32bit UID is passed to it.
>
> 2. it's used by the kernel's user namespacing as the internal UID
> that external UIDs are mapped to that don't have any local mapping.
>
> 3. It's used by NFS for all user IDs that cannot be mapped locally if
> UID mapping is enabled.
>
> Most distributions already map (or are in the progress of changing)
> nobody/nogroup to the 65534 uid/gid, so lets do so as well.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> system/skeleton/etc/group | 2 +-
> system/skeleton/etc/passwd | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-08-26 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 21:47 [Buildroot] [PATCH/next] system/skeleton: use uid/gid 65534 for nobody/nogroup Peter Korsgaard
2016-08-26 5:58 ` Arnout Vandecappelle
2016-08-26 13:39 ` Thomas Petazzoni [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=20160826153949.1c0b5b7e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.