From: Chris Hofstaedtler <zeha@debian.org>
To: Karel Zak <kzak@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux@vger.kernel.org,
Christian Goeschel Ndjomouo <cgoesc2@wgu.edu>,
Helmut Grohne <helmut@subdivi.de>
Subject: unshare regression in 2.42-rc1
Date: Sun, 22 Mar 2026 12:37:47 +0100 [thread overview]
Message-ID: <ab_SfC1JDOhNmg6D@zeha.at> (raw)
In-Reply-To: <wid276gkq7tblvkfwc6kum4nacamstiigqjj5ux6j6zd4blz4l@jzq3sgfh6cj5>
Hi Karel, Christian,
Debian CI found a regression in the unshare command when using
--map-user with numeric UIDs. This worked in 2.41 and earlier:
% unshare --version && unshare --user --map-auto --map-user=65536 id
unshare from util-linux 2.41.3
uid=65536 gid=65534(nogroup) groups=65534(nogroup)
And is broken in 2.42-rc1:
% unshare --version && unshare --user --map-auto --map-user=65536 id
unshare from util-linux 2.42-rc1
unshare: failed to parse uid '65536'
Note the following (true in both cases):
$ grep 65536 /etc/passwd
%
I suspect (but did not verify yet) this was introduced in
commit 0a7fb806118bc4418e231081bd13c69bbc31b988
> unshare: use the new ul_get{grp,userpw}_str() routines
>
> This change refactors get_group() and get_user(), so that it
> uses the new routines ul_getgrp_str() and ul_getuserpw_str(),
> to simplify the code and remove the overkill mem allocations.
https://github.com/util-linux/util-linux/commit/0a7fb806118bc4418e231081bd13c69bbc31b988
Thanks to Helmut Grohne for reducing the failed debvm CI run to the
short unshare command.
Best,
Chris
next prev parent reply other threads:[~2026-03-22 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 12:53 [ANNOUNCE] util-linux v2.42-rc1 Karel Zak
2026-03-01 8:40 ` Chris Hofstaedtler
2026-03-02 9:16 ` Sumanth Korikkar
2026-03-02 15:59 ` Sumanth Korikkar
2026-03-22 11:37 ` Chris Hofstaedtler [this message]
2026-03-22 12:57 ` unshare regression in 2.42-rc1 Christian Albrecht Goeschel Ndjomouo
2026-03-26 14:01 ` Chris Hofstaedtler
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=ab_SfC1JDOhNmg6D@zeha.at \
--to=zeha@debian.org \
--cc=cgoesc2@wgu.edu \
--cc=helmut@subdivi.de \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=util-linux@vger.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