Re: [libvirt] [PATCH v2 16/17] vircgroupv2: use dummy process to workaround kernel bug with systemd

2019-01-24 Thread Pavel Hrdina
On Thu, Jan 24, 2019 at 11:06:51AM +, Daniel P. Berrangé wrote: > On Mon, Jan 14, 2019 at 04:47:50PM +0100, Pavel Hrdina wrote: > > If some program is attached to cgroup and that cgroup is removed before > > detaching the program it might not be freed and will remain in the > > system until

Re: [libvirt] [PATCH v2 16/17] vircgroupv2: use dummy process to workaround kernel bug with systemd

2019-01-24 Thread Daniel P . Berrangé
On Mon, Jan 14, 2019 at 04:47:50PM +0100, Pavel Hrdina wrote: > If some program is attached to cgroup and that cgroup is removed before > detaching the program it might not be freed and will remain in the > system until it's rebooted. > > This would not be that big deal to workaround if we

Re: [libvirt] [PATCH v2 16/17] vircgroupv2: use dummy process to workaround kernel bug with systemd

2019-01-24 Thread Michal Privoznik
On 1/14/19 4:47 PM, Pavel Hrdina wrote: > If some program is attached to cgroup and that cgroup is removed before > detaching the program it might not be freed and will remain in the > system until it's rebooted. > > This would not be that big deal to workaround if we wouldn't use > machined to

[libvirt] [PATCH v2 16/17] vircgroupv2: use dummy process to workaround kernel bug with systemd

2019-01-14 Thread Pavel Hrdina
If some program is attached to cgroup and that cgroup is removed before detaching the program it might not be freed and will remain in the system until it's rebooted. This would not be that big deal to workaround if we wouldn't use machined to track our guests. Systemd tries to be the nice guy