I tried removing security=selinux from the kernel command-line and then systemd doesn't crash.

I downgraded to 257.7-1 (current testing) and that also doesn't crash.

I don't have systemd-coredump installed.

I think there's three bugs total here. One bug is that the crash handling was bad, it just froze systemd without any log message written anywhere, even "systemctl status" just returned an error message about being unable to contact systemd. The second bug is the strlen crash while trying to log an error inside sd_varlink_get_peer_uid. That might be an outside bug if systemd is not getting a NUL terminated string from another library. The third bug is why selinux is failing in the first place, which might or might not be a systemd problem, but would be probably be helped by seeing the log message.

Please let me know if there's any more info I can provide.

Reply via email to