On Sun, 2 Aug 2020 21:59:05 +0200 Michael Biebl <bi...@debian.org> wrote:
> Am 02.08.20 um 21:41 schrieb Mart van de Wege: > > Package: systemd > > Version: 245.7-1 > > Severity: normal > > > > With SELinux enabled (booting with selinux=1 security=selinux), as > > soon as systemd wants to clean up /run/user/<UID> for a session, > > the kernel will oops, leaving the systemd-user-runtime-dir process > > that's trying to clean up the directory in an uninterruptible sleep > > (D) state. > > I fail to see how this is a systemd bug. This looks more like a kernel > and/or Selinux issue to me. > You have a point there. I selected systemd because it at first appeared to be a systemd bug (process hangs), but of course, if it causes an oops reliably with selinux enabled (which it does), it should be retargeted to those packages. Is that still possible, or should we close this one and let me refile? Regards, Mart
