Yocto Project Status 29 November 2022 (WW48)
Current Dev Position: YP 4.2 M1
Next Deadline: 5th December 2022 YP 4.2 Build
Next Team Meetings:
* Bug Triage meeting Thursday December 8th 7:30 am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Weekly Project Engineering Sync Tuesday December 6th at 8 am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
* Twitch - See <https://www.twitch.tv/theyoctojester>
https://www.twitch.tv/theyoctojester
Key Status/Updates:
* YP 3.1.21 has passed QA and will be released.
* It is Yocto Project Summit and OEDVM this week so many people will
be attending those events. Thanks to everyone participating or helping enable to happen.
* There is some discussion on the architecture list about some changes
to bitbake including adding new API to handle python libraries.
* In particular we have a dilemma on whether to accept a parsing
overhead for improved variable flag handling (export, unexport, network flags) or for better cache data to improve hash debugging.
* Unfs was upgraded and automated testing enabled. Being able to mount
a local filesystem into qemu images or real hardware as the rootfs over NFS can be a useful way to develop or debug issues so it is timely to remind people this is possible. No special user permissions are needed as it is handled in userspace.
* We'd welcome a proposal/series on how to move forward with the Y2038
work for 32 bit platforms.
* We have a growing number of bugs in bugzilla, any help with them is
appreciated.
Ways to contribute:
* There are bugs identified as possible for newcomers to the project:
<https://wiki.yoctoproject.org/wiki/Newcomers>
https://wiki.yoctoproject.org/wiki/Newcomers
* There are bugs that are currently unassigned for YP 4.2. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhan
cements.2FBugs
* We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:
<http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/mai
ntainers.inc>
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to "Unassigned" soon to help facilitate this.
* Help is very much welcome in trying to resolve our autobuilder
intermittent issues. You can see the list of failures we're continuing to see by searching for the "AB-INT" tag in bugzilla:
<https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT>
https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
* Help us resolve CVE issues:
<https://autobuilder.yocto.io/pub/non-release/patchmetrics/> CVE metrics
YP 4.2 Milestone Dates:
* YP 4.2 M1 build date 2022/12/05
* YP 4.2 M1 Release date 2022/12/16
* YP 4.2 M2 build date 2023/01/23
* YP 4.2 M2 Release date 2023/02/03
* YP 4.2 M3 build date 2023/02/20
* YP 4.2 M3 Release date 2023/03/03
* YP 4.2 M4 build date 2023/04/03
* YP 4.2 M4 Release date 2023/04/28
Upcoming dot releases:
* YP 3.1.21 is ready for release
* YP 4.0.6 build date 2022/12/12
* YP 4.0.6 Release date 2022/12/23
* YP 4.1.2 build date 2023/01/09
* YP 4.1.2 Release date 2023/01/20
* YP 3.1.22 build date 2023/01/16
* YP 3.1.22 Release date 2023/01/27
* YP 4.0.7 build date 2023/01/30
* YP 4.0.7 Release date 2023/02/10
* YP 3.1.23 build date 2023/02/13
* YP 3.1.23 Release date 2023/02/24
* YP 4.0.8 build date 2023/02/27
* YP 4.0.8 Release date 2023/03/10
* YP 4.1.3 build date 2023/03/06
* YP 4.1.3 Release date 2023/03/17
* YP 3.1.24 build date 2023/03/20
* YP 3.1.24 Release date 2023/03/31
* YP 4.0.9 build date 2023/04/10
* YP 4.0.9 Release date 2023/04/21
* YP 4.1.4 build date 2023/05/01
* YP 4.1.4 Release date 2023/05/13
* YP 3.1.25 build date 2023/05/08
* YP 3.1.25 Release date 2023/05/19
* YP 4.0.10 build date 2023/05/15
* YP 4.0.10 Release date 2023/05/26
Tracking Metrics:
* WDD 2446 (last week 2436) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
* Total patches found: 1175 (last week 1178)
* Patches in the Pending State: 288 (25%) [last week 289 (25%)]
* <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
https://autobuilder.yocto.io/pub/non-release/patchmetrics/
The Yocto Project's technical governance is through its Technical Steering Committee, more information is available at:
<https://wiki.yoctoproject.org/wiki/TSC>
https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at:
<https://wiki.yoctoproject.org/wiki/Weekly_Status>
https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you'd like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley
Yocto Project Program Manager
* Cell: (208) 244-4460
* Email: [email protected]
<mailto:[email protected]>
Y2038 proposal
Quoted 1 line · Stephen Jolley
We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms.
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally. b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
c. an additional runtime test verifies that both RTC clock and system clock report 2040.
2. This branch is run through a-full on the autobuilder. Any uncovered issues are filed as bugs.
3. Once *all* of the bugs are addressed, repeat point 2.
4. Once there are no more open bugs, 1a is merged into master.
Any fatal flaws in the plan?
It's not hard to see that Y2038 problem is real and serious, e.g. on qemux86 core-image-full-cmdline built from master:
root@qemux86:~# ls / bin boot dev etc home lib lost+found media mnt proc run sbin sys tmp usr var root@qemux86:~# date -s "2040-01-01" Sun Jan 1 00:00:00 UTC 2040 root@qemux86:~# ls / bin boot dev etc home lib lost+found media mnt proc run sbin sys tmp usr var root@qemux86:~# ls / -sh: ls: command not found
On qemux86_64 the same sequence works as expected, of course.
Alex
Re: [yocto] Y2038 proposal
Hi Alexander,
Quoted 5 lines
Quoted 2 lines · Stephen Jolley
We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms.
Quoted 9 lines
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally. b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
c. an additional runtime test verifies that both RTC clock and system clock report 2040.
Please find a few comments:
1. There is already provided meta-y2038 [1] to test if 32 bit systems correctly support Y2038 problem. It uses qemu machines from OE/Yocto
2. There are ptest available [2] to validate if the Y2038 problem works correctly.
3. Support for running ptests mentioned in point 2. is already available in the poky repository [3].
Quoted 23 lines
2. This branch is run through a-full on the autobuilder. Any uncovered issues are filed as bugs.
3. Once *all* of the bugs are addressed, repeat point 2.
4. Once there are no more open bugs, 1a is merged into master.
Any fatal flaws in the plan?
It's not hard to see that Y2038 problem is real and serious, e.g. on qemux86 core-image-full-cmdline built from master:
root@qemux86:~# ls / bin boot dev etc home lib lost+found media mnt proc run sbin sys tmp usr var root@qemux86:~# date -s "2040-01-01" Sun Jan 1 00:00:00 UTC 2040 root@qemux86:~# ls / bin boot dev etc home lib lost+found media mnt proc run sbin sys tmp usr var root@qemux86:~# ls / -sh: ls: command not found
Quoted 2 lines
On
qemux86_64the same sequence works as expected, of course.
Yes, y2038 is an important issue.
I would be more than happy if we could reuse the previous work [1].
I've used OE/Yocto to validate the code during developing support for '-D_TIME_BITS=64 ' flag in glibc.
It looks like the meta-y2038 can be used out of the box (after checking if it still works with newest poky) when added to the Yocto Project build/test infrastructure.
Quoted 1 line
Alex
Links:
[1] - https://github.com/lmajewski/meta-y2038
[2] - https://github.com/lmajewski/meta-y2038/blob/master/README#L201
[3] -
https://git.yoctoproject.org/poky/commit/?id=0e0c481a25f10f8f7ff1d69bda7f015186da0202
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: [email protected]
Re: [yocto] Y2038 proposal
Quoted 10 lines · Lukasz Majewski
Please find a few comments:
1. There is already provided meta-y2038 [1] to test if 32 bit systems correctly support Y2038 problem. It uses qemu machines from OE/Yocto
2. There are ptest available [2] to validate if the Y2038 problem works correctly.
3. Support for running ptests mentioned in point 2. is already available in the poky repository [3].
Thanks! So there should be a
d. 'glibc-tests-ptest' is executed across all architectures - probably as a machine-specific selftest, and as well with qemu time set into the future.
Quoted 3 lines
It looks like the meta-y2038 can be used out of the box (after checking if it still works with newest poky) when added to the Yocto Project build/test infrastructure.
Unfortunately I do not think that layer can be easily added into the test matrix. It has its own distro and images. No, we need to maintain a poky branch where the same tweaks and fixes happen. Besides, those fixes would need to be merged into oe-core proper eventually anyway.
Alex
Re: [yocto] Y2038 proposal
Hi Alexander,
Quoted 10 lines · Lukasz Majewski
Quoted 9 lines
Please find a few comments:
1. There is already provided meta-y2038 [1] to test if 32 bit systems correctly support Y2038 problem. It uses qemu machines from OE/Yocto
2. There are ptest available [2] to validate if the Y2038 problem works correctly.
Quoted 8 lines
Quoted 2 lines
3. Support for running ptests mentioned in point 2. is already available in the poky repository [3].
Thanks! So there should be a
d. 'glibc-tests-ptest' is executed across all architectures - probably as a machine-specific selftest, and as well with qemu time set into the future.
+1
Quoted 10 lines
Quoted 4 lines
It looks like the meta-y2038 can be used out of the box (after checking if it still works with newest poky) when added to the Yocto Project build/test infrastructure.
Unfortunately I do not think that layer can be easily added into the test matrix. It has its own distro and images. No, we need to maintain a poky branch where the same tweaks and fixes happen. Besides, those fixes would need to be merged into oe-core proper eventually anyway.
It would be even better if the meta-y2038 could be dropped and _all_ its functionality could be merged to poky.
That would be _awesome_.
Please just be aware that this meta layer has some fixes for some packages (for Y2038 ready glibc).
Quoted 1 line
Alex
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: [email protected]
Re: [yocto] Y2038 proposal
Quoted 7 lines · Lukasz Majewski
It would be even better if the meta-y2038 could be dropped and _all_ its functionality could be merged to poky.
That would be _awesome_.
Please just be aware that this meta layer has some fixes for some packages (for Y2038 ready glibc).
Little by little. As long as we have a well-defined test plan, a well-known list of issues, and follow a strict 'upstream first' policy in addressing them (e.g. no fixes in layers that are 'forever pending', un-upstreamable or have been rejected by upstreams), we'll eventually get there.
And absolutely no promise to make this available anywhere except master. If someone is using ancient yocto releases, they should run a retro computing museum rather than critical infrastructure.
Alex
Re: [yocto] Y2038 proposal
In reply to Alexander KanavinQuoted 5 lines · Alexander Kanavin
Quoted 1 line · Stephen Jolley
We’d welcome a proposal/series on how to move forward with the Y2038
work for 32 bit platforms.
Quoted 10 lines
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally. b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
c. an additional runtime test verifies that both RTC clock and system clock report 2040.
Going from various problems I saw with systems with smaller time wraps, setting a time after wrap occurs misses most of the problems which wall occur. Many systems will work fine with either 'negative' or 'smaller dates' but crash, burn, etc when running when the counter wraps around. I would suggest setting the test date to -N minutes before wrap over to run a first set of tests, and then N minutes after the wrap to run a second set of tests. This would hopefully catch programs which are worse off.
Signature · 3 lines
Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren
Re: [yocto] Y2038 proposal
In reply to Alexander KanavinQuoted 12 lines · Alexander Kanavin
Quoted 1 line · Stephen Jolley
We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms.
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally. b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
c. an additional runtime test verifies that both RTC clock and system clock report 2040.
Quoted 3 lines
2. This branch is run through a-full on the autobuilder. Any uncovered issues are filed as bugs.
I ran a-full with "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" last week, it didn't go too well gcc-sanitizer and pulseaudio being the main offenders but buildtools needs to be investigated.
Quoted 20 lines
3. Once *all* of the bugs are addressed, repeat point 2.
4. Once there are no more open bugs, 1a is merged into master.
Any fatal flaws in the plan?
It's not hard to see that Y2038 problem is real and serious, e.g. on qemux86 core-image-full-cmdline built from master:
root@qemux86:~# ls / bin boot dev etc home lib lost+found media mnt proc run sbin sys tmp usr var root@qemux86:~# date -s "2040-01-01" Sun Jan 1 00:00:00 UTC 2040 root@qemux86:~# ls / bin boot dev etc home lib lost+found media mnt proc run sbin sys tmp usr var root@qemux86:~# ls / -sh: ls: command not found
Quoted 2 lines
On
qemux86_64the same sequence works as expected, of course.
The main issue with the plan is that we are not running tests on 32 qemu anymore.
Signature · 3 lines
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Re: [yocto] Y2038 proposal
In reply to Stephen John SmoogenQuoted 19 lines · On Wed, 30 Nov 2022 05:52:03 -0500 "Stephen John Smoogen" <[email protected]>…
Quoted 6 lines · Alexander Kanavin
Quoted 2 lines · Stephen Jolley
We’d welcome a proposal/series on how to move forward with the Y2038
work for 32 bit platforms.
Quoted 10 lines
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally. b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
c. an additional runtime test verifies that both RTC clock and system clock report 2040.
Quoted 9 lines
Going from various problems I saw with systems with smaller time wraps, setting a time after wrap occurs misses most of the problems which wall occur. Many systems will work fine with either 'negative' or 'smaller dates' but crash, burn, etc when running when the counter wraps around. I would suggest setting the test date to -N minutes before wrap over to run a first set of tests, and then N minutes after the wrap to run a second set of tests. This would hopefully catch programs which are worse off.
IIRC ptests for y2038 covers this problem in this exact way.
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: [email protected]
Re: [OE-core] [yocto] Y2038 proposal
In reply to Alexandre BelloniQuoted 13 lines · Alexandre Belloni via lists.openembedded.org
Quoted 12 lines · Alexander Kanavin
Quoted 1 line · Stephen Jolley
We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms.
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally. b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
c. an additional runtime test verifies that both RTC clock and system clock report 2040.
Quoted 7 lines
Quoted 3 lines
2. This branch is run through a-full on the autobuilder. Any uncovered issues are filed as bugs.
I ran a-full with "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" last week, it didn't go too well gcc-sanitizer and pulseaudio being the main offenders but buildtools needs to be investigated.
What is the potential issue with builtools?
Quoted 20 lines
Quoted 20 lines
3. Once *all* of the bugs are addressed, repeat point 2.
4. Once there are no more open bugs, 1a is merged into master.
Any fatal flaws in the plan?
It's not hard to see that Y2038 problem is real and serious, e.g. on qemux86 core-image-full-cmdline built from master:
root@qemux86:~# ls / bin boot dev etc home lib lost+found media mnt proc run sbin sys tmp usr var root@qemux86:~# date -s "2040-01-01" Sun Jan 1 00:00:00 UTC 2040 root@qemux86:~# ls / bin boot dev etc home lib lost+found media mnt proc run sbin sys tmp usr var root@qemux86:~# ls / -sh: ls: command not found
Quoted 5 lines
Quoted 2 lines
On
qemux86_64the same sequence works as expected, of course.The main issue with the plan is that we are not running tests on 32 qemu anymore.
To be clear, we don't run ptests on 32 bit targets, only on qemux86-64 and qemuarm64 where we have KVM available. We do run image, sdk and eSDK tests on our supported qemu targets, 32 and 64 bit.
Cheers,
Richard
Re: [OE-core] [yocto] Y2038 proposal
Quoted 3 lines · Richard Purdie
To be clear, we don't run ptests on 32 bit targets, only on qemux86-64 and qemuarm64 where we have KVM available. We do run image, sdk and eSDK tests on our supported qemu targets, 32 and 64 bit.
I think kvm does allow 32 bit guest on a 64 bit host. But I can imagine making full ptests work on 32 bit guests would be a struggle for reasons unrelated to 2038, specifically lack of users outside of embedded world.
Alex
Re: [yocto] Y2038 proposal
In reply to Stephen John SmoogenQuoted 1 line · Stephen John Smoogen
Going from various problems I saw with systems with smaller time wraps, setting a time after wrap occurs misses most of the problems which wall occur. Many systems will work fine with either 'negative' or 'smaller dates' but crash, burn, etc when running when the counter wraps around. I would suggest setting the test date to -N minutes before wrap over to run a first set of tests, and then N minutes after the wrap to run a second set of tests. This would hopefully catch programs which are worse off.
Testing the rollover could be done in later stages. I can imagine we'll have enough just by setting the date in the future and getting those magic glibc flags to not cause build fails.
Alex
Re: [OE-core] [yocto] Y2038 proposal
In reply to Alexander KanavinQuoted 9 lines · On Wed, 30 Nov 2022 13:07:27 +0100 "Alexander Kanavin"…
Quoted 4 lines · Richard Purdie
To be clear, we don't run ptests on 32 bit targets, only on qemux86-64 and qemuarm64 where we have KVM available. We do run image, sdk and eSDK tests on our supported qemu targets, 32 and 64 bit.
I think kvm does allow 32 bit guest on a 64 bit host.
+1
IIRC the MACH=qemux86 was working correctly...
Quoted 2 lines
But I can
imagine making full ptests work on 32 bit guests
Maybe only subset of ptests - i.e. those related to Y2038 could be run?
Quoted 5 lines
would be a struggle
for reasons unrelated to 2038, specifically lack of users outside of embedded world.Alex
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: [email protected]
Re: [OE-core] [yocto] Y2038 proposal
In reply to Alexander KanavinQuoted 8 lines · Alexander Kanavin
Quoted 3 lines · Richard Purdie
To be clear, we don't run ptests on 32 bit targets, only on qemux86-64 and qemuarm64 where we have KVM available. We do run image, sdk and eSDK tests on our supported qemu targets, 32 and 64 bit.
I think kvm does allow 32 bit guest on a 64 bit host.
For x86, yes. For arm, it varies and I know at least one of our arm hosts doesn't support it, I don't know about the newer ones.
Quoted 3 lines
But I can imagine making full ptests work on 32 bit guests would be a struggle
for reasons unrelated to 2038, specifically lack of users outside of embedded world.
In general I think it shouldn't be too bad but we really do need to test it and see.
Cheers,
Richard
Re: [Openembedded-architecture] Y2038 proposal
In reply to Alexander KanavinQuoted 12 lines · Alexander Kanavin
Quoted 1 line · Stephen Jolley
We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms.
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally. b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
c. an additional runtime test verifies that both RTC clock and system clock report 2040.
Quoted 8 lines
2. This branch is run through a-full on the autobuilder. Any uncovered issues are filed as bugs.
3. Once *all* of the bugs are addressed, repeat point 2.
4. Once there are no more open bugs, 1a is merged into master.
Any fatal flaws in the plan?
Others have made some good comments. My thoughts:
* We need to add some runtime tests to oeqa for this (in addition to the ptests)
* We need to have a 32 bit ptest run on the autobuilder (qemux86 should work, not sure we can make qemuarm fast). Whether this is manually triggered, not sure. We could have a smaller set of ptests to run for it?
* Could we optionally disable some of the glibc 32 bit function calls to ensure they're not being used? We don't really want to diverge from upstream glibc much though.
* We need to work out how to communicate this change happened and have people "buy in" to it. The reason for that is that if someone has existing binaries, there could be problems using them after the change. We therefore need to be sure they are aware of it.
Cheers,
Richard
Re: [OE-core] [Openembedded-architecture] Y2038 proposal
Hi Richard,
Quoted 26 lines · Alexander Kanavin
Quoted 14 lines
Quoted 2 lines · Stephen Jolley
We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms.
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally. b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
c. an additional runtime test verifies that both RTC clock and system clock report 2040.Quoted 8 lines
2. This branch is run through a-full on the autobuilder. Any uncovered issues are filed as bugs.
3. Once *all* of the bugs are addressed, repeat point 2.
4. Once there are no more open bugs, 1a is merged into master.
Any fatal flaws in the plan?
Others have made some good comments. My thoughts:
Quoted 7 lines
* We need to add some runtime tests to oeqa for this (in addition to the ptests)
* We need to have a 32 bit ptest run on the autobuilder (qemux86 should work, not sure we can make qemuarm fast). Whether this is manually triggered, not sure. We could have a smaller set of ptests to run for it?
Y2038 ptests maybe?
Here is the list of integrated tests to ptests:
https://github.com/lmajewski/y2038-tests
Quoted 3 lines
* Could we optionally disable some of the glibc 32 bit function calls to ensure they're not being used?
Could you be more specific here? Would you like to disable some syscalls?
Quoted 2 lines
We don't really want to diverge from
upstream glibc much though.
Could you be more specific here? The glibc now supports the whole set of syscalls as of 2.34 version?
To enable them one needs to pass -D_TIME_BITS=64 flag when compiling programs.
This is now the official glibc ABI.
Quoted 3 lines
* We need to work out how to communicate this change happened and have people "buy in" to it.
Ok.
Quoted 3 lines
The reason for that is that if someone has
existing binaries, there could be problems using them after the change.
The binary shall work without issues on glibc 2.34+ and 5.10+ kernel without issues.
The only problem happens when new binaries with 64 bit time support are run on glibc or kernel not supporting 64 bit time.
Quoted 9 lines
We therefore need to be sure they are aware of it.
Cheers,
Richard
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: [email protected]
Re: [OE-core] [Openembedded-architecture] Y2038 proposal
Quoted 34 lines · Lukasz Majewski
Quoted 26 lines · Alexander Kanavin
Quoted 14 lines
Quoted 2 lines · Stephen Jolley
We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms.
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally. b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
c. an additional runtime test verifies that both RTC clock and system clock report 2040.Quoted 8 lines
2. This branch is run through a-full on the autobuilder. Any uncovered issues are filed as bugs.
3. Once *all* of the bugs are addressed, repeat point 2.
4. Once there are no more open bugs, 1a is merged into master.
Any fatal flaws in the plan?
Others have made some good comments. My thoughts:
Quoted 7 lines
* We need to add some runtime tests to oeqa for this (in addition to the ptests)
* We need to have a 32 bit ptest run on the autobuilder (qemux86 should work, not sure we can make qemuarm fast). Whether this is manually triggered, not sure. We could have a smaller set of ptests to run for it?
Quoted 4 lines
Y2038 ptests maybe?
Here is the list of integrated tests to ptests:
https://github.com/lmajewski/y2038-tests
Perhaps, yes.
Quoted 5 lines
Quoted 2 lines
* Could we optionally disable some of the glibc 32 bit function calls to ensure they're not being used?
Could you be more specific here? Would you like to disable some syscalls?
I'm meaning disabling the 32 bit glibc time functions.
Quoted 10 lines
Quoted 2 lines
We don't really want to diverge from
upstream glibc much though.Could you be more specific here? The glibc now supports the whole set of syscalls as of 2.34 version?
To enable them one needs to pass -D_TIME_BITS=64 flag when compiling programs.
This is now the official glibc ABI.
Right, but the 32 bit time functions/symbols are still available for older binaries. My point is that anything using those older functions is likely in need of attention so for Yocto Project/OE usage, identifying those would be helpful. If we were to disable them, that would make such usage very obvious.
Quoted 7 lines
Quoted 4 lines
The reason for that is that if someone has
existing binaries, there could be problems using them after the change.The binary shall work without issues on glibc 2.34+ and 5.10+ kernel without issues.
Not necessarily. If it were a binary library, compiled with 32 bit time_t, new binaries using it would use a different sized field.
Quoted 2 lines
The only problem happens when new binaries with 64 bit time support are run on glibc or kernel not supporting 64 bit time.
That is definitely not the only problem. Some of the problems are unlikely but we do need to consider them.
Cheers,
Richard
Re: [Openembedded-architecture] Y2038 proposal
In reply to Alexander KanavinQuoted 8 lines · Alexander Kanavin
Quoted 1 line · Stephen Jolley
We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms.
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally.
I have something like this on yoe/mut branch on contrib repo ( due to musl removing the LFS hacks).
However there are packages which need to be fixed at build time.
Quoted 2 lines
b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
this is a good time machine :)
Quoted 12 lines
c. an additional runtime test verifies that both RTC clock and system clock report 2040.
2. This branch is run through a-full on the autobuilder. Any uncovered issues are filed as bugs.
3. Once *all* of the bugs are addressed, repeat point 2.
4. Once there are no more open bugs, 1a is merged into master.
Any fatal flaws in the plan?
Not much issues except that package fixes may need to be carried locally for a while.
Quoted 26 lines
It's not hard to see that Y2038 problem is real and serious, e.g. on qemux86 core-image-full-cmdline built from master:
root@qemux86:~# ls / bin boot dev etc home lib lost+found media mnt proc run sbin sys tmp usr var root@qemux86:~# date -s "2040-01-01" Sun Jan 1 00:00:00 UTC 2040 root@qemux86:~# ls / bin boot dev etc home lib lost+found media mnt proc run sbin sys tmp usr var root@qemux86:~# ls / -sh: ls: command not foundOn
qemux86_64the same sequence works as expected, of course.Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1663): https://lists.openembedded.org/g/openembedded-architecture/message/1663
Mute This Topic: https://lists.openembedded.org/mt/95354042/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [OE-core] [Openembedded-architecture] Y2038 proposal
In reply to Richard PurdieQuoted 7 lines · Richard Purdie via lists.yoctoproject.org
Quoted 5 lines
Quoted 2 lines
* Could we optionally disable some of the glibc 32 bit function calls to ensure they're not being used?
Could you be more specific here? Would you like to disable some syscalls?
I'm meaning disabling the 32 bit glibc time functions.
Some time ago I filed https://bugzilla.yoctoproject.org/show_bug.cgi?id=6803 as Debian has a nice sanity check where it warns if non-LFS glibc functions are used. I imagine the same logic could be used to check for 32-bit time_t use.
Ross
Re: [yocto] [OE-core] [Openembedded-architecture] Y2038 proposal
Quoted 11 lines · Ross Burton
Quoted 7 lines · Richard Purdie via lists.yoctoproject.org
Quoted 5 lines
Quoted 2 lines
* Could we optionally disable some of the glibc 32 bit function calls to ensure they're not being used?
Could you be more specific here? Would you like to disable some syscalls?
I'm meaning disabling the 32 bit glibc time functions.
Some time ago I filed https://bugzilla.yoctoproject.org/show_bug.cgi?id=6803 as Debian has a nice sanity check where it warns if non-LFS glibc functions are used. I imagine the same logic could be used to check for 32-bit
time_tuse.
We can simply disable COMPAT_32BIT_TIME in the kernel config.
Quoted 11 lines
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58682): https://lists.yoctoproject.org/g/yocto/message/58682
Mute This Topic: https://lists.yoctoproject.org/mt/95357621/3617179
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Signature · 3 lines
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Re: [yocto] [OE-core] [Openembedded-architecture] Y2038 proposal
Quoted 8 lines · Alexandre Belloni
Quoted 7 lines · Ross Burton
Quoted 6 lines · Richard Purdie via lists.yoctoproject.org
Quoted 5 lines
Quoted 2 lines
* Could we optionally disable some of the glibc 32 bit function calls to ensure they're not being used?
Could you be more specific here? Would you like to disable some syscalls?
Quoted 7 lines
Quoted 7 lines
Quoted 1 line
I'm meaning disabling the 32 bit glibc time functions.
Some time ago I filed
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6803 as Debian has a nice sanity check where it warns if non-LFS glibc functions are used. I imagine the same logic could be used to check for 32- bittime_tuse.
That sounds interesting and something we should probably look into for both issues...
Quoted 3 lines
Quoted 1 line
We can simply disable
COMPAT_32BIT_TIMEin the kernel config.
That would cause runtime issues but not build time linking ones?
Cheers,
Richard
Re: [yocto] Y2038 proposal
In reply to Lukasz MajewskiQuoted 5 lines · Lukasz Majewski
2. There are ptest available [2] to validate if the Y2038 problem works correctly.
3. Support for running ptests mentioned in point 2. is already available in the poky repository [3].
I just ran these tests in (32 bit) qemux86 on top of poky master (e.g. no magic glibc flags), and they all passed. Do they need to be ran after setting the date to the 'post-2038 future' to reveal the issues and produce failures?
Alex
Re: [yocto] Y2038 proposal
Hi Alexander,
Quoted 11 lines · Lukasz Majewski
Quoted 5 lines
2. There are ptest available [2] to validate if the Y2038 problem works correctly.
3. Support for running ptests mentioned in point 2. is already available in the poky repository [3].
I just ran these tests in (32 bit) qemux86 on top of poky master (e.g. no magic glibc flags), and they all passed. Do they need to be ran after setting the date to the 'post-2038 future' to reveal the issues and produce failures?
Yes. You need to run them with adjusted date:
date +'%Y-%m-%d %T' -s "2038-01-19 03:14:07"
ptest-runner glibc-tests
More info:
https://github.com/lmajewski/meta-y2038/blob/master/README#L201
Quoted 2 lines
Alex
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: [email protected]
Re: [Openembedded-architecture] Y2038 proposal
In reply to Richard PurdieQuoted 4 lines · Richard Purdie
* We need to have a 32 bit ptest run on the autobuilder (qemux86 should work, not sure we can make qemuarm fast). Whether this is manually triggered, not sure. We could have a smaller set of ptests to run for it?
I just ran qemux86 full ptest locally. It took 4h:10m (same as qemuarm64 ptest on an arm worker). The fails were:
{'python3': ['test_deterministic_sets'],
'valgrind': ['gdbserver_tests/hgtls',
'gdbserver_tests/mcblocklistsearch',
'gdbserver_tests/mcbreak',
'gdbserver_tests/mcclean_after_fork',
'gdbserver_tests/mchelp',
'gdbserver_tests/mcinfcallRU',
'gdbserver_tests/mcinfcallWSRU',
'gdbserver_tests/mcinvokeRU',
'gdbserver_tests/mcinvokeWS',
'gdbserver_tests/mcleak',
'gdbserver_tests/mcmain_pic',
'gdbserver_tests/mcsignopass',
'gdbserver_tests/mcsigpass',
'gdbserver_tests/mcvabits',
'gdbserver_tests/mcwatchpoints',
'gdbserver_tests/mssnapshot',
'gdbserver_tests/nlcontrolc',
'gdbserver_tests/nlgone_abrt',
'gdbserver_tests/nlgone_exit',
'gdbserver_tests/nlgone_return',
'gdbserver_tests/nlpasssigalrm',
'gdbserver_tests/nlsigvgdb',
'gdbserver_tests/nlvgdbsigqueue',
'memcheck/tests/linux/memfd_create',
'memcheck/tests/linux/timerfd-syscall',
'memcheck/tests/origin5-bz2',
'massif/tests/mmapunmap']}So I think we could as well fix these, and add full qemux86 ptest to a-full? It is not heavy on the builder machine (mostly just runs a single qemu thread), it's just long.
Alex
Re: [Openembedded-architecture] Y2038 proposal
Quoted 39 lines · Alexander Kanavin
Quoted 4 lines · Richard Purdie
* We need to have a 32 bit ptest run on the autobuilder (qemux86 should work, not sure we can make qemuarm fast). Whether this is manually triggered, not sure. We could have a smaller set of ptests to run for it?
I just ran qemux86 full ptest locally. It took 4h:10m (same as qemuarm64 ptest on an arm worker). The fails were:
{'python3': ['
test_deterministic_sets'],
'valgrind': ['gdbserver_tests/hgtls','gdbserver_tests/mcblocklistsearch', 'gdbserver_tests/mcbreak', 'gdbserver_tests/mcclean_after_fork', 'gdbserver_tests/mchelp', 'gdbserver_tests/mcinfcallRU', 'gdbserver_tests/mcinfcallWSRU', 'gdbserver_tests/mcinvokeRU', 'gdbserver_tests/mcinvokeWS', 'gdbserver_tests/mcleak', 'gdbserver_tests/mcmain_pic', 'gdbserver_tests/mcsignopass', 'gdbserver_tests/mcsigpass', 'gdbserver_tests/mcvabits', 'gdbserver_tests/mcwatchpoints', 'gdbserver_tests/mssnapshot', 'gdbserver_tests/nlcontrolc', 'gdbserver_tests/nlgone_abrt', 'gdbserver_tests/nlgone_exit', 'gdbserver_tests/nlgone_return', 'gdbserver_tests/nlpasssigalrm', 'gdbserver_tests/nlsigvgdb', 'gdbserver_tests/nlvgdbsigqueue', 'memcheck/tests/linux/memfd_create', 'memcheck/tests/linux/timerfd-syscall', 'memcheck/tests/origin5-bz2', 'massif/tests/mmapunmap']}
Quoted 3 lines
So I think we could as well fix these, and add full qemux86 ptest to a-full? It is not heavy on the builder machine (mostly just runs a single qemu thread), it's just long.
I think we should fix those and we should add the target to the autobuilder but I'm reluctant to add a long test to a-full. The fact it is relatively clean suggests it doesn't regress that often. We could do something like a once a month trigger for it?
Cheers,
Richard
Re: [OE-core] Y2038 proposal
In reply to Alexander KanavinQuoted 14 lines · Alexander Kanavin
Quoted 14 lines
Quoted 14 lines
Quoted 14 lines
Quoted 2 lines · Stephen Jolley
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
We’d welcome a proposal/series on how to move forward with the Y2038 work for 32 bit platforms.
I have the following proposal:
1. A branch is made where:
a. "-D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" is enabled globally. b. qemu is always started with "-rtc base=2040-01-01", simulating Y2038 actually occurring.
c. an additional runtime test verifies that both RTC clock and system clock report 2040.
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
2. This branch is run through a-full on the autobuilder. Any uncovered
issues are filed as bugs.
Your email prompted me to check my own software (Dropbear) and it showed a few y2038 issues to fix. Those bugs wouldn't be noticed from a quick test - it "only" prevented auth and idle timeouts from occurring.
gcc and clang are able to flag truncated conversions for 64-bit time_t with -Wconversion, but that's very noisy. Comparing that against a 32-bit time_t build, however, gives a pretty clean list of code that needs attention.
As an experiment I've built OpenBMC with and without 64-bit time_t,
https://github.com/mkj/yocto-y2038 has the results and a description. There are a mix of false positives (particularly tv_usec/tv_nsec), but also some real-looking things. As an example, busybox using a uint32_t to copy a dhcpd lease expiry.
I'm not sure the best way to use these logs - they need manual review. Expanding the list of packages should be easy, but there will be more that need manual intervention to get rid of -Werror.
Cheers,
Matt
Re: [yocto] [OE-core] [Openembedded-architecture] Y2038 proposal
In reply to Richard PurdieQuoted 13 lines · Richard Purdie
Quoted 12 lines · Alexandre Belloni
Quoted 11 lines · Ross Burton
Quoted 7 lines · Richard Purdie via lists.yoctoproject.org
Quoted 5 lines
Quoted 2 lines
* Could we optionally disable some of the glibc 32 bit function calls to ensure they're not being used?
Could you be more specific here? Would you like to disable some syscalls?
I'm meaning disabling the 32 bit glibc time functions.
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Some time ago I filed
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6803 as Debian has a nice sanity check where it warns if non-LFS glibc functions are used. I imagine the same logic could be used to check for 32- bittime_tuse.That sounds interesting and something we should probably look into for both issues...
I have a working sanity checker that checks for any glibc functions affected by -D_FILE_OFFSET_BITS=64 or -D_TIME_BITS=64.
The INSANE_SKIP functionality needs some more polish but I'd be happy to contribute it.
Some libraries use both 32 and 64 bit APIs to glibc and needs exceptions in the checker.
I have not run any world builds with this checker, I've focused on the recipes we actually use so far so we could get to a testable system. My biggest worry at the moment is rust, I know to little to know if it is an actual problem and how to fix it.
I would like to be part of any "y2038 team" for Yocto.
Signature · 1 line
Ola x Nilsson
Re: [yocto] [OE-core] [Openembedded-architecture] Y2038 proposal
Quoted 32 lines · Ola x Nilsson
Quoted 13 lines · Richard Purdie
Quoted 12 lines · Alexandre Belloni
Quoted 11 lines · Ross Burton
Quoted 7 lines · Richard Purdie via lists.yoctoproject.org
Quoted 5 lines
Quoted 2 lines
* Could we optionally disable some of the glibc 32 bit function calls to ensure they're not being used?
Could you be more specific here? Would you like to disable some syscalls?
I'm meaning disabling the 32 bit glibc time functions.
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Some time ago I filed
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6803 as Debian has a nice sanity check where it warns if non-LFS glibc functions are used. I imagine the same logic could be used to check for 32- bittime_tuse.That sounds interesting and something we should probably look into for both issues...
I have a working sanity checker that checks for any glibc functions affected by -D_FILE_OFFSET_BITS=64 or -D_TIME_BITS=64.
TheINSANE_SKIPfunctionality needs some more polish but I'd be happy to contribute it.Some libraries use both 32 and 64 bit APIs to glibc and needs exceptions in the checker.
Quoted 6 lines
I have not run any world builds with this checker, I've focused on the recipes we actually use so far so we could get to a testable system. My biggest worry at the moment is rust, I know to little to know if it is an actual problem and how to fix it.
I would like to be part of any "y2038 team" for Yocto.
That does sound useful, perhaps sharing it as an RFC patch might be a good place to start? We might be able to run one of the autobuilder world targets against it, see how it looks for our core recipes?
Cheers,
Richard
Re: [yocto] [OE-core] [Openembedded-architecture] Y2038 proposal
Quoted 38 lines · Richard Purdie
Quoted 37 lines · Ola x Nilsson
Quoted 13 lines · Richard Purdie
Quoted 12 lines · Alexandre Belloni
Quoted 11 lines · Ross Burton
Quoted 7 lines · Richard Purdie via lists.yoctoproject.org
Quoted 5 lines
Quoted 2 lines
* Could we optionally disable some of the glibc 32 bit function calls to ensure they're not being used?
Could you be more specific here? Would you like to disable some syscalls?
I'm meaning disabling the 32 bit glibc time functions.
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Some time ago I filed
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6803 as Debian has a nice sanity check where it warns if non-LFS glibc functions are used. I imagine the same logic could be used to check for 32- bittime_tuse.That sounds interesting and something we should probably look into for both issues...
I have a working sanity checker that checks for any glibc functions affected by -D_FILE_OFFSET_BITS=64 or -D_TIME_BITS=64.
TheINSANE_SKIPfunctionality needs some more polish but I'd be happy to contribute it.Some libraries use both 32 and 64 bit APIs to glibc and needs exceptions in the checker.
I have not run any world builds with this checker, I've focused on the recipes we actually use so far so we could get to a testable system. My biggest worry at the moment is rust, I know to little to know if it is an actual problem and how to fix it.
Quoted 5 lines
Quoted 1 line
I would like to be part of any "y2038 team" for Yocto.
That does sound useful, perhaps sharing it as an RFC patch might be a good place to start? We might be able to run one of the autobuilder world targets against it, see how it looks for our core recipes?
That works for me. I've started preparing a patch for oe-core.
Signature · 1 line
Ola x Nilsson
Re: [OE-core] Y2038 proposal
In reply to Matt JohnstonQuoted 14 lines · Matt Johnston
Your email prompted me to check my own software (Dropbear) and it showed a few y2038 issues to fix. Those bugs wouldn't be noticed from a quick test - it "only" prevented auth and idle timeouts from occurring.
gcc and clang are able to flag truncated conversions for 64-bit
time_twith -Wconversion, but that's very noisy. Comparing that against a 32-bittime_tbuild, however, gives a pretty clean list of code that needs attention.As an experiment I've built OpenBMC with and without 64-bit
time_t,
https://github.com/mkj/yocto-y2038 has the results and a description. There are a mix of false positives (particularly tv_usec/tv_nsec), but also some real-looking things. As an example, busybox using auint32_tto copy a dhcpd lease expiry.
Quoted 3 lines
I'm not sure the best way to use these logs - they need manual review. Expanding the list of packages should be easy, but there will be more that need manual intervention to get rid of -Werror.
That is really interesting data as it confirmed there are real world issues which changing the compiler flags is going to break. Thanks for sharing.
What you describe is relatively easy for a maintainer to do as a one off check but not really something we can do at scale for all the software we build. It worries me :/. I guess the one upside is that whilst it did break some functionality, it didn't actually crash the runtime if I understand what happened correctly.
I'm not sure this should stop our plan to switch the flags but it is certainly something to think about and be aware of.
Cheers,
Richard