From: Chris Hofstaedtler <zeha@debian.org>
To: Christian Albrecht Goeschel Ndjomouo <cgoesc2@wgu.edu>
Cc: Karel Zak <kzak@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"util-linux@vger.kernel.org" <util-linux@vger.kernel.org>,
Helmut Grohne <helmut@subdivi.de>
Subject: Re: unshare regression in 2.42-rc1
Date: Thu, 26 Mar 2026 15:01:16 +0100 [thread overview]
Message-ID: <acU7uB76HwZlBu6B@zeha.at> (raw)
In-Reply-To: <SJ0P220MB05417CC33D6BA305A9CEE320E94AA@SJ0P220MB0541.NAMP220.PROD.OUTLOOK.COM>
Hi Christian,
* Christian Albrecht Goeschel Ndjomouo <cgoesc2@wgu.edu> [260322 13:57]:
>Thank you for pointing out this regression.
>
>The problem is that if ul_getuserpw_str() cannot find any user with the provided
>UID or username, the unshare internal helper function get_user() will error out
>and stop argument parsing, even if a valid numeric value was provided. Previously,
>the code would fallback to simply converting the string to an unsigned int and use
>it for the uid_t, so I added that behavior back.
>
>I found this issue to be true for the --map-group option as well, so I went ahead and fixed
>both cases in this latest patch: https://github.com/util-linux/util-linux/pull/4134/changes/c74df906b67b2f9930662ca4e1ba04c21569d529
>
>Please let us know if this fixed the problem on your end.
With the patch applied, the debvm tests succeed once again.
So this seems good.
I see Karel has in the meantime merged a different approach. I'll
recheck with 2.42-rc2.
Thank you,
Chris
next prev parent reply other threads:[~2026-03-26 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 12:53 [ANNOUNCE] util-linux v2.42-rc1 Karel Zak
2026-02-27 0:28 ` Samuel Thibault
2026-03-03 11:46 ` Karel Zak
2026-03-03 13:13 ` Samuel Thibault
2026-03-01 8:40 ` Chris Hofstaedtler
2026-03-02 9:16 ` Sumanth Korikkar
2026-03-02 15:59 ` Sumanth Korikkar
2026-03-03 10:08 ` Karel Zak
2026-03-03 12:51 ` Sumanth Korikkar
2026-03-04 13:34 ` Chris Hofstaedtler
2026-03-22 11:37 ` unshare regression in 2.42-rc1 Chris Hofstaedtler
2026-03-22 12:57 ` Christian Albrecht Goeschel Ndjomouo
2026-03-26 14:01 ` Chris Hofstaedtler [this message]
2026-03-29 10:54 ` 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=acU7uB76HwZlBu6B@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