Hey,
On Tue, Jun 16, 2015 at 06:21:20PM +0300, Faidon Liambotis wrote:
Any news about this? Can I help in any way?
Are there any objections/holdups here? It'd be great if this made it to
8.2, the deadline for which is this weekend AIUI. Let me know if I can
help! :)
Faidon
reopen 765577 !
found 765577 215-14
thanks
On Mon, Mar 30, 2015 at 06:06:47AM +0200, Marco d'Itri wrote:
I see that we have independently devised the same fix, I am attaching
a test case and a more refined version of your patch.
I tried Jessie RC3 today and immediately found that the fix is,
Hi Martin,
On Fri, Mar 27, 2015 at 04:40:25PM +0100, Martin Pitt wrote:
If so, a mere ipsec stop after that should be able to crash
systemd.
Not that, it just marks the unit as stopped but keeps the processes
running. But killing the two daemons manually makes the cgroup empty
and I get
Hi Martin!
On Thu, Mar 26, 2015 at 03:17:16PM +0100, Martin Pitt wrote:
Control: severity -1 important
I downgrade the severity to important as per
https://www.debian.org/Bugs/Developer#severities (and with #781209 we
have the bug that triggers this one); nevertheless, this is still an
Package: systemd
Version: 215-12
Severity: critical
I've managed to reproducibly crash systemd:
# grep systemd /var/log/syslog | tail -3
Mar 26 01:02:15 curium systemd[1]: Assertion 'path' failed at
../src/shared/cgroup-util.c:913, function cg_is_empty_recursive(). Aborting.
Mar 26 01:02:15
