| 2024-06-03 15:23:14 |
Jean-Baptiste Lallement |
bug |
|
|
added bug |
| 2024-06-03 15:23:22 |
Jean-Baptiste Lallement |
nominated for series |
|
Ubuntu Noble |
|
| 2024-06-03 15:23:22 |
Jean-Baptiste Lallement |
bug task added |
|
systemd (Ubuntu Noble) |
|
| 2024-06-03 15:35:30 |
Nick Rosbrook |
tags |
|
systemd-sru-next |
|
| 2024-06-05 07:39:40 |
Jean-Baptiste Lallement |
attachment added |
|
8e57759d6d80ef772d8e17a4559a6797e09af93a.patch https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067922/+attachment/5786231/+files/8e57759d6d80ef772d8e17a4559a6797e09af93a.patch |
|
| 2024-06-05 07:40:13 |
Jean-Baptiste Lallement |
attachment added |
|
systemd_255.4-1ubuntu8_255.4-1ubuntu9.debdiff https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2067922/+attachment/5786232/+files/systemd_255.4-1ubuntu8_255.4-1ubuntu9.debdiff |
|
| 2024-06-05 07:40:30 |
Jean-Baptiste Lallement |
systemd (Ubuntu Noble): importance |
Undecided |
Critical |
|
| 2024-06-05 07:40:42 |
Jean-Baptiste Lallement |
systemd (Ubuntu Noble): status |
New |
Triaged |
|
| 2024-06-05 08:28:24 |
Ubuntu Foundations Team Bug Bot |
tags |
systemd-sru-next |
patch systemd-sru-next |
|
| 2024-06-05 08:28:31 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2024-06-14 16:50:10 |
Nick Rosbrook |
systemd (Ubuntu): status |
New |
Fix Committed |
|
| 2024-06-14 17:53:43 |
Nick Rosbrook |
description |
WSL 24.04 / systemd 255.4-1ubuntu8
* Upstream report: https://github.com/microsoft/WSL/issues/8879
* Upstream PR: https://github.com/systemd/systemd/pull/32534
* Upstream commit: https://github.com/systemd/systemd-stable/commit/8e57759d6d80ef772d8e17a4559a6797e09af93a.patch
In WSL, the cgroup.procs PID list for some reason contain a ton of zeros everywhere from unmapped PIDs.
Whenever cg_read_pid encounters such a zero, it throws an error. This makes systemd near unusable inside of WSL.
# Test Case
install Ubuntu WSL 24.04 from the MS STore. This version has systemd already enabled.
## Expected Behavior
systemctl status command to work
## Actual Behavior
toor@XPS:~$ systemctl status
Failed to dump process list for 'XPS', ignoring: Input/output error
● XPS
State: degraded
Units: 318 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 1 units
Since: Sat 2022-09-24 08:43:15 PDT; 14min ago
systemd: 251.4-1ubuntu6
Tainted: cgroupsv1
CGroup: / |
[Impact]
WSL 24.04 / systemd 255.4-1ubuntu8
* Upstream report: https://github.com/microsoft/WSL/issues/8879
* Upstream PR: https://github.com/systemd/systemd/pull/32534
* Upstream commit: https://github.com/systemd/systemd-stable/commit/8e57759d6d80ef772d8e17a4559a6797e09af93a.patch
In WSL, the cgroup.procs PID list for some reason contain a ton of zeros everywhere from unmapped PIDs.
Whenever cg_read_pid encounters such a zero, it throws an error. This makes systemd near unusable inside of WSL.
[Test Plan]
On WSL running Ubuntu 24.04, run systemctl status. On an affected system, there will be an error saying "Failed to dump process list [...]". On a patched system, the command should work as expected.
[Where problems could occur]
This patch adds a flags parameter to cg_read_pid(), and adds a new flag, CGROUP_DONT_SKIP_UNMAPPED. The new default behavior of cg_read_pid() is that unmapped pids *will* be skipped. When this flag is set in a call to cg_read_pid(), encountering an unmapped pid will leave the caller to deal with it.
There are several places where cg_read_pid() is called in systemd, so there are several places where this would come up. If we did see problems, it would likely because a caller is skipping the unmapped pids when it should not be. For callers that do not skip (i.e. pass CGROUP_DONT_SKIP_UNMAPPED), they either handle it cleanly, or propagate a different error to signal this case.
[Original Description]
WSL 24.04 / systemd 255.4-1ubuntu8
* Upstream report: https://github.com/microsoft/WSL/issues/8879
* Upstream PR: https://github.com/systemd/systemd/pull/32534
* Upstream commit: https://github.com/systemd/systemd-stable/commit/8e57759d6d80ef772d8e17a4559a6797e09af93a.patch
In WSL, the cgroup.procs PID list for some reason contain a ton of zeros everywhere from unmapped PIDs.
Whenever cg_read_pid encounters such a zero, it throws an error. This makes systemd near unusable inside of WSL.
# Test Case
install Ubuntu WSL 24.04 from the MS STore. This version has systemd already enabled.
## Expected Behavior
systemctl status command to work
## Actual Behavior
toor@XPS:~$ systemctl status
Failed to dump process list for 'XPS', ignoring: Input/output error
● XPS
State: degraded
Units: 318 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 1 units
Since: Sat 2022-09-24 08:43:15 PDT; 14min ago
systemd: 251.4-1ubuntu6
Tainted: cgroupsv1
CGroup: / |
|
| 2024-06-17 17:47:59 |
Bpkroth |
bug |
|
|
added subscriber Bpkroth |
| 2024-06-23 11:47:09 |
Max Bowsher |
bug |
|
|
added subscriber Max Bowsher |
| 2024-07-05 10:16:31 |
Timo Aaltonen |
systemd (Ubuntu Noble): status |
Triaged |
Fix Committed |
|
| 2024-07-05 10:16:33 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-07-05 10:16:36 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2024-07-05 10:16:41 |
Timo Aaltonen |
tags |
patch systemd-sru-next |
patch systemd-sru-next verification-needed verification-needed-noble |
|
| 2024-07-08 08:44:59 |
Jean-Baptiste Lallement |
tags |
patch systemd-sru-next verification-needed verification-needed-noble |
patch systemd-sru-next verification-done verification-done-noble |
|
| 2024-07-15 10:05:58 |
Launchpad Janitor |
systemd (Ubuntu Noble): status |
Fix Committed |
Fix Released |
|
| 2024-07-15 10:06:15 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
