hwclock: fails to set time on glibc 2.31
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
busybox (Debian) |
Fix Released
|
Unknown
|
|||
busybox (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* With glibc 2.31, hwclock from busybox is unable to set the system time
due to the changes in settimeofday behavior.
[Test Case]
* Run:
sudo busybox hwclock -s
* It should succeed in the fixed version
[Where problems could occur]
* The fix calls the originally called glibc function twice, instead of passing both non-NULL parameters at once. If this compiles there should be no other issue.
[Original Bug Text]
With glibc 2.31, hwclock from busybox is unable to set the system time
due to the changes in settimeofday behavior.
The problem has been reported upstream in [1] which also contains a patch.
hwclock from busybox is important as it's used on the Raspberry Pi to set the system
time when an RTC is present.
This bug applies to focal and groovy.
Changed in busybox (Debian): | |
status: | Unknown → Confirmed |
Changed in busybox (Ubuntu Focal): | |
status: | New → Confirmed |
description: | updated |
Changed in busybox (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in busybox (Debian): | |
status: | Confirmed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.