[systemd-devel] [systemd][cgroup in container] problem with cgroup hierarchy in container

[Lennart Poettering]

On Thu, 06.03.14 10:51, Dariusz Michaluk (d.michaluk at samsung.com) wrote:

> Program received signal SIGSEGV, Segmentation fault.
> sd_bus_message_unref (m=0x80000000) at
> ../src/libsystemd/sd-bus/bus-message.c:800
> 800	        m->n_ref--;
> (gdb) bt
> #0  sd_bus_message_unref (m=0x80000000) at
> ../src/libsystemd/sd-bus/bus-message.c:800
> #1  0x80043950 in sd_bus_message_unrefp (p=0xbfffedd8) at
> ../src/libsystemd/sd-bus/bus-util.h:141
> #2  show_one.3172 (verb=<optimized out>, bus=bus at entry=0x80098880,
> path=path at entry=0x8007548e "/org/freedesktop/systemd1",
> show_properties=show_properties at entry=true,
> new_line=new_line at entry=0xbffff18a,
>     ellipsized=ellipsized at entry=0xbffff18b) at
> ../src/systemctl/systemctl.c:3672
> #3  0x8005957b in show (bus=0x80098880, args=0xbffff458) at
> ../src/systemctl/systemctl.c:3965
> #4  0x80007dbb in systemctl_main (bus_error=<optimized out>,
> argv=0xbffff454, argc=2, bus=0x80098880) at
> ../src/systemctl/systemctl.c:6167
> #5  main (argc=2, argv=0xbffff454) at ../src/systemctl/systemctl.c:6422

I#d still be curious to track down this issue. It doesn't make sense to
me I must say though... Appears to be some misparsing resulting in
memory corruption somewhere...

Which version of systemd is this? any chance you can reproduce this with
systemctl compiled fresh from current git? Or could you run "gdbus
introspect --system --dest org.freedesktop.systemd1 --object-path
/org/freedesktop/systemd1" and see if any of the props (and in
partciular the "Controlgroup" one look weird?

Thanks!

Lennart

-- 
Lennart Poettering, Red Hat