From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
openembedded-core@lists.openembedded.org
Cc: Luca Boccassi <luca.boccassi@microsoft.com>
Subject: Re: [PATCH] systemd: dont spew hidepid mount errors for kernels < v5.8
Date: Fri, 15 Jan 2021 08:37:28 +0000 [thread overview]
Message-ID: <12145df57b9fdec6933497849a2d8b40fcb8a023.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210115052615.29893-1-paul.gortmaker@windriver.com>
On Fri, 2021-01-15 at 00:26 -0500, Paul Gortmaker wrote:
> Recent systemd started using ascii args to "hidepid=" mount options
> for proc fs - unconditionally -- even though kernels older than v5.8
> emit an error message on each attempt:
>
> root@qemux86-64:~# cat /proc/version
> Linux version 5.4.87-yocto-standard (oe-user@oe-host) (gcc version 10.2.0 (GCC)) #1 SMP PREEMPT Fri Jan 8 01:47:13 UTC 2021
> root@qemux86-64:~# dmesg|grep proc:
> [ 29.487995] proc: Bad value for 'hidepid'
> [ 43.170571] proc: Bad value for 'hidepid'
> [ 44.175615] proc: Bad value for 'hidepid'
> [ 46.213300] proc: Bad value for 'hidepid'
> root@qemux86-64:~#
>
> Simply ignoring them as the systemd maintainer unconditionally says
> is the resolution is clearly not acceptable, given the above.
>
> Add a kernel version check to avoid calling mount with invalid args.
> Further details are within the enclosed systemd commit.
>
> Cc: Luca Boccassi <luca.boccassi@microsoft.com>
> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>
> diff --git a/meta/recipes-core/systemd/systemd/0027-proc-dont-trigger-mount-error-with-invalid-options-o.patch b/meta/recipes-core/systemd/systemd/0027-proc-dont-trigger-mount-error-with-invalid-options-o.patch
> new file mode 100644
> index 000000000000..65e7eca32d05
> --- /dev/null
> +++ b/meta/recipes-core/systemd/systemd/0027-proc-dont-trigger-mount-error-with-invalid-options-o.patch
> @@ -0,0 +1,126 @@
> +From 297aba739cd689e4dc9f43bb1422ec88d481099a Mon Sep 17 00:00:00 2001
> +From: Paul Gortmaker <paul.gortmaker@windriver.com>
> +Date: Wed, 13 Jan 2021 21:09:33 +0000
> +Subject: [PATCH] proc: dont trigger mount error with invalid options on old
> + kernels
> +
> +As of commit 4e39995371738b04d98d27b0d34ea8fe09ec9fab ("core: introduce
> +ProtectProc= and ProcSubset= to expose hidepid= and subset= procfs
> +mount options") kernels older than v5.8 generate multple warnings at
> +boot, as seen in this Yocto build from today:
> +
> + qemux86-64 login: root
> + [ 65.829009] proc: Bad value for 'hidepid'
> + root@qemux86-64:~# dmesg|grep proc:
> + [ 16.990706] proc: Bad value for 'hidepid'
> + [ 28.060178] proc: Bad value for 'hidepid'
> + [ 28.874229] proc: Bad value for 'hidepid'
> + [ 32.685107] proc: Bad value for 'hidepid'
> + [ 65.829009] proc: Bad value for 'hidepid'
> + root@qemux86-64:~#
> +
> +The systemd maintainer has dismissed this as something people should
> +simply ignore[1] and has no interest in trying to avoid it by
> +proactively checking the kernel version, so people can safely assume
> +that they will never see this version check commit upstream.
> +
> +However, as can be seen above, telling people to just ignore it is not
> +an option, as we'll end up answering the same question and dealing with
> +the same bug over and over again.
> +
> +The commit that triggers this is systemd v247-rc1~378^2~3 -- so any
> +systemd 247 and above plus kernel v5.7 or older will need this.
> +
> +[1] https://github.com/systemd/systemd/issues/16896
> +
> +Upstream-Status: Actively hostile
The status needs to be
Upstream-Status: Denied [Actively hostile https://github.com/systemd/systemd/issues/16896]
(so our tools have an idea of what status patches are in)
https://wiki.yoctoproject.org/wiki/Best_Known_Methods_(BKMs)_for_Package_Updating#Patch_Comments
Cheers,
Richard
next prev parent reply other threads:[~2021-01-15 8:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 5:26 [PATCH] systemd: dont spew hidepid mount errors for kernels < v5.8 Paul Gortmaker
2021-01-15 6:02 ` [OE-core] " Konrad Weihmann
2021-01-15 8:37 ` Richard Purdie [this message]
2021-01-15 9:57 ` Luca Boccassi
2021-01-15 10:14 ` Richard Purdie
2021-01-15 10:20 ` Luca Boccassi
2021-01-15 14:47 ` Paul Gortmaker
2021-01-15 15:37 ` Luca Boccassi
2021-01-15 16:07 ` [OE-core] " Bruce Ashfield
2021-01-15 16:31 ` Luca Boccassi
2021-01-15 16:59 ` Bruce Ashfield
2021-01-15 17:35 ` Luca Boccassi
2021-01-18 11:07 ` Leon Woestenberg
2021-01-18 12:36 ` Richard Purdie
2021-01-15 15:27 ` Luca Boccassi
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=12145df57b9fdec6933497849a2d8b40fcb8a023.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=luca.boccassi@microsoft.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.gortmaker@windriver.com \
/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