[lxc/lxc] 0f5852: cgfsng: fix reboots when using dbus

0 views
Skip to first unread message

Stéphane Graber

unread,
Dec 23, 2025, 3:10:31 PM12/23/25
to lxc-...@lists.linuxcontainers.org
Branch: refs/heads/main
Home: https://github.com/lxc/lxc
Commit: 0f5852edfad06fe4e9f00aaddd3d93576269729e
https://github.com/lxc/lxc/commit/0f5852edfad06fe4e9f00aaddd3d93576269729e
Author: Serge Hallyn <se...@hallyn.com>
Date: 2025-12-23 (Tue, 23 Dec 2025)

Changed paths:
M src/lxc/cgroups/cgfsng.c

Log Message:
-----------
cgfsng: fix reboots when using dbus

When using dbus on a systemd system, we ask systemd to create a
"scope" for us to run in. We send a dbus message, and wait
for the reply saying it is created.

When we reboot, we were re-sending the request to create the
scope. However, the scope still exists, because or single
lxc-monitor (originally lxc-start) thread is still under the
'lxc.pivot' sub-directory of the scope.

But, on reboot, our lxc_conf already has our scope recorded!
So, just check whether that is set, and skip scope creation
if so.

With this patch, i can reboot ad nauseum with no apparent
problems.

We could probably move this check to the top of the function,
but for now this fixes the bug.

Signed-off-by: Serge Hallyn <se...@hallyn.com>


Commit: 9674e1fbcb914a08b9b354ae5c08e275a40c3104
https://github.com/lxc/lxc/commit/9674e1fbcb914a08b9b354ae5c08e275a40c3104
Author: Stéphane Graber <stgr...@stgraber.org>
Date: 2025-12-23 (Tue, 23 Dec 2025)

Changed paths:
M src/lxc/cgroups/cgfsng.c

Log Message:
-----------
Merge pull request #4628 from hallyn/2025-12-23/fix-dbus-scope-reboot

cgfsng: fix reboots when using dbus


Compare: https://github.com/lxc/lxc/compare/1311e1b47d9b...9674e1fbcb91

To unsubscribe from these emails, change your notification settings at https://github.com/lxc/lxc/settings/notifications
Reply all
Reply to author
Forward
0 new messages