Bug 14434

Summary:	[3.4 M1] dmesg: proc: Bad value for 'hidepid' with poky-altcfg distro
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Yi Zhao <yi.zhao>
Component:	core	Assignee:	Unassigned <unassigned>
Status:	RESOLVED OBSOLETE	QA Contact:	Yi Zhao <yi.zhao>
Severity:	normal
Priority:	Medium+	CC:	bruce.ashfield, meta.mr.watcher, meta.watcher, randy.macleod, richard.purdie, sangeeta.jain, yi.zhao
Version:	3.4
Target Milestone:	4.0 M3
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	Regression (Used to work)
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Yi Zhao 2021-06-16 07:22:59 UTC

Git rev: master/59d93693bf24e02ca0f05fe06d96a46f4f0f1bf8
Image location: https://autobuilder.yocto.io/pub/releases/yocto-3.4_M1.rc1

Boot up the system:
root@edgerouter:~# dmesg |  grep hidepid
[   18.707531] proc: Bad value for 'hidepid'
[   29.319659] proc: Bad value for 'hidepid'
[   30.504542] proc: Bad value for 'hidepid'
[   54.625119] proc: Bad value for 'hidepid'
[ 3653.270814] proc: Bad value for 'hidepid'
root@edgerouter:~# 

The root cause is we have dropped 0027-proc-dont-trigger-mount-error-with-invalid-options-o.patch in commit http://cgit.openembedded.org/openembedded-core/commit/?id=e8dd5a36bf2f1e645fb2ff15eb3b5e97c04776e6

Reference: https://github.com/systemd/systemd/issues/16896

Comment 1 Randy MacLeod 2021-06-17 14:43:50 UTC

Yi,
Can you reapply the patch and send this in?

Comment 2 Yi Zhao 2021-06-24 06:58:02 UTC

Do we still plan to keep kernel 5.4 in Yocot 3.4? If not, there is no need to rebase this patch.

Comment 3 Bruce Ashfield 2021-06-24 12:38:45 UTC

(In reply to comment #2)
> Do we still plan to keep kernel 5.4 in Yocot 3.4? If not, there is no need
> to rebase this patch.

5.4 won't be a reference in the final 3.4 release, it will be 5.10 and the 'latest'.

That being said, there could still be a custom kernel with an earlier version that is being used against the release. So if the patch isn't challenging or risky to port, it is ok from that point of view.

(But since that won't be a kernel version combination that we are validating in the 3.4 release, there is only so far we need to go in making sure it works without issues.)

Comment 4 Richard Purdie 2022-03-10 16:17:50 UTC

We removed linux 5.4 from the 3.4 release so this was no longer an issue.