From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Luca Bocassi <luca.boccassi@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3 1/5] systemd: update 246 -> 247
Date: Sat, 19 Dec 2020 11:18:43 +0000 [thread overview]
Message-ID: <940d5e33d09579fc46372bfedbd0b76ee285a8e9.camel@linuxfoundation.org> (raw)
In-Reply-To: <1652194C9AF53BB2.13568@lists.openembedded.org>
On Sat, 2020-12-19 at 11:03 +0000, Richard Purdie via
lists.openembedded.org wrote:
> On Sat, 2020-12-19 at 10:33 +0000, Richard Purdie via
> lists.openembedded.org wrote:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1662/steps/14/logs/stdio
> >
> > (there is a second issue there from other patches in master-next
> > too).
> >
> > We do need a green build to be able to merge so this may depend on
> > someone else looking into that reproducibility issue. I did try and
> > give some hints in my previous email, I'd need to look at the code
> > to
> > be able to give any more pointers.
>
> Looking at the output in
> https://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20201219-fqxxqel9/packages/diff-html/
>
> you can see that the .text section in the binary changes size.
> Ignoring
> the offset changes, the actual change is the change in size of
> the maybe_emit_login_defs_warning function from 256 to 275 bytes.
>
> That function is in the systemd sources in
> git/src/sysusers/sysusers.c.
>
> It uses a variety of configuration options such as:
>
> SYSTEM_ALLOC_UID_MIN
> SYSTEM_UID_MAX
> SYSTEM_ALLOC_GID_MIN
> SYSTEM_GID_MAX
>
> My best guess is that we're not setting one of these and its falling
> back to a host system value which varies by host distro.
>
> Obviously we need to prove that and figure out the correct value for
> OE
> usage but its maybe a pointer as to the possible problem (or I could
> be
> totally wrong!).
I was far enough into this I kept going. The defaults for these are set
in meson.build from:
foreach tuple : [['system-alloc-uid-min', 'SYS_UID_MIN', 1], # Also see login.defs(5).
['system-uid-max', 'SYS_UID_MAX', 999],
['system-alloc-gid-min', 'SYS_GID_MIN', 1],
['system-gid-max', 'SYS_GID_MAX', 999]]
which if they're not set, looks at the host system /etc/login.defs file
which is host contamination and is bad. On my ubuntu system, these
aren't set by default. For Centos7 and 8:
[rpurdie@centos8-ty-1 ~]$ grep SYS /etc/login.defs
SYS_UID_MIN 201
SYS_UID_MAX 999
SYS_GID_MIN 201
SYS_GID_MAX 999
so I think we have our trigger. I have a simply patch to specify
defaults in the recipe which I think should resolve this. I'll add it
to master-next and see if that helps.
Cheers,
Richard
next prev parent reply other threads:[~2020-12-19 11:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 12:53 [PATCH 1/5] systemd: update 246 -> 247 Luca Bocassi
2020-12-10 12:53 ` [PATCH 2/5] systemd: add package config for systemd-oomd Luca Bocassi
2020-12-10 17:05 ` [OE-core] " Khem Raj
2020-12-10 18:01 ` Luca Boccassi
2020-12-10 12:53 ` [PATCH 3/5] systemd: ship new systemd-dissect in -extra-utils Luca Bocassi
2020-12-10 12:53 ` [PATCH 4/5] systemd: set -Dmode=release as recommended by NEWS Luca Bocassi
2020-12-10 12:53 ` [PATCH 5/5] systemd: add RRECOMMENDS for weak dependencies, if enabled Luca Bocassi
2020-12-11 20:34 ` [OE-core] " Peter Kjellerstedt
2020-12-14 10:33 ` Luca Bocassi
2020-12-11 20:55 ` Andre McCurdy
2020-12-14 10:05 ` Luca Bocassi
2020-12-10 17:08 ` [OE-core] [PATCH 1/5] systemd: update 246 -> 247 Khem Raj
2020-12-10 18:05 ` Luca Boccassi
2020-12-10 20:40 ` Khem Raj
2020-12-11 9:32 ` Luca Boccassi
2020-12-11 16:50 ` Khem Raj
2020-12-11 20:17 ` Saul Wold
2020-12-14 12:34 ` [PATCH v2 " Luca Bocassi
2020-12-14 12:34 ` [PATCH v2 2/5] systemd: add package config for systemd-oomd Luca Bocassi
2020-12-14 12:34 ` [PATCH v2 3/5] systemd: ship new systemd-dissect in -extra-utils Luca Bocassi
2020-12-14 12:34 ` [PATCH v2 4/5] systemd: set -Dmode=release as recommended by NEWS Luca Bocassi
2020-12-14 12:34 ` [PATCH v2 5/5] systemd: add RRECOMMENDS for weak dependencies, if enabled Luca Bocassi
2020-12-16 17:57 ` [OE-core] [PATCH v2 1/5] systemd: update 246 -> 247 Richard Purdie
2020-12-16 18:07 ` Richard Purdie
2020-12-17 17:25 ` Luca Bocassi
2020-12-17 17:46 ` Richard Purdie
2020-12-18 9:47 ` Luca Bocassi
2020-12-18 1:46 ` Chen Qi
2020-12-18 2:00 ` Anuj Mittal
2020-12-18 9:43 ` Luca Bocassi
[not found] ` <165144ABA68FE046.22063@lists.openembedded.org>
2020-12-16 18:48 ` Richard Purdie
2020-12-18 9:42 ` [PATCH v3 " Luca Bocassi
2020-12-18 9:42 ` [PATCH v3 2/5] systemd: add package config for systemd-oomd Luca Bocassi
2020-12-18 9:42 ` [PATCH v3 3/5] systemd: ship new systemd-dissect in -extra-utils Luca Bocassi
2020-12-18 9:42 ` [PATCH v3 4/5] systemd: set -Dmode=release as recommended by NEWS Luca Bocassi
2020-12-18 9:42 ` [PATCH v3 5/5] systemd: add RRECOMMENDS for weak dependencies, if enabled Luca Bocassi
2020-12-19 10:33 ` [OE-core] [PATCH v3 1/5] systemd: update 246 -> 247 Richard Purdie
[not found] ` <165217A789F1A918.13568@lists.openembedded.org>
2020-12-19 11:03 ` Richard Purdie
[not found] ` <1652194C9AF53BB2.13568@lists.openembedded.org>
2020-12-19 11:18 ` Richard Purdie [this message]
2020-12-19 14:09 ` Peter Kjellerstedt
2020-12-19 14:55 ` Richard Purdie
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=940d5e33d09579fc46372bfedbd0b76ee285a8e9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=luca.boccassi@gmail.com \
--cc=openembedded-core@lists.openembedded.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.