Bug#884784: systemd-network segfaults

[Rémi Denis-Courmont]

tags 884784 - moreinfo
thanks

Le keskiviikkona 20. joulukuuta 2017, 0.05.02 EET Michael Biebl a écrit :
> Control: severity -1 important
> Control: tags -1 moreinfo
> Control: found -1 236-1
> Control: notfound -1 235-3
> 
> Am 19.12.2017 um 18:50 schrieb Rémi Denis-Courmont:
> > Package: systemd
> > Version: 235-3
> > Severity: critical
> > Justification: breaks unrelated software
> > 
> > Dear Maintainer,
> > 
> > systemd-networkd from version 236-1 systematically segfaults at start-up.
> > Eventually, systemd gives up on starting the service. As neither the
> > DHCPv4 lease nor the IPv6 Prefix Delegation are performed, the entire
> > system becomes unreachable.
> > 
> > Downgrading to 235-3 fixes the problem. Bug is reported while running the
> > downgraded version for obvious reasons.
> > 
> > syslog extract:
> > 
> > Dec 18 23:09:23 basile systemd-networkd[275]:
> > /etc/systemd/network/mv1.netdev:7: Unknown section 'MACVTAP'. Ignoring.
> > Dec 18 23:09:23 basile systemd-networkd[275]:
> > /etc/systemd/network/mv0.netdev:7: Unknown section 'MACVLAN'. Ignoring.
> Your configuration seems to be incorrect. Please fix that and try again.

The warnings vanish, the crash and complete loss of networking remains.

> > Dec 18 23:09:23 basile systemd-networkd[275]: Enumeration completed
> > Dec 18 23:09:23 basile systemd-networkd[275]: eth0: IPv6 successfully
> > enabled Dec 18 23:09:23 basile systemd-networkd[275]: eth0: Could not
> > bring up interface: Invalid argument Dec 18 23:09:23 basile kernel: [   
> > 1.954336] systemd-network[275]: segfault at 80000562e ip 00007f88725c2f36
> > sp 00007ffe8dbd8b48 error 4 in libc-2.25.so[7f8872541000+199000]
> Please try to provide a backtrace of the crash.

eth0: Gained IPv6LL

Program received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/x86_64/strlen.S:106
106     ../sysdeps/x86_64/strlen.S: Aucun fichier ou dossier de ce type.
(gdb) bt
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
#1  0x00005555555a6334 in routing_policy_rule_hash_func.lto_priv.498 (
    b=0x55555586b8d0, state=0x7fffffffe1b0)
    at ../src/network/networkd-routing-policy-rule.c:99
#2  0x00005555555e49b7 in base_bucket_hash.lto_priv.254 (h=0x55555585c670, 
    p=0x55555586b8d0) at ../src/basic/hashmap.c:346
#3  0x0000555555577938 in set_put (s=<optimized out>, key=<optimized out>)
    at ../src/basic/hashmap.c:1247
#4  0x00005555555a963c in routing_policy_rule_add_internal.lto_priv.500 (
    rules=rules at entry=0x55555585ce60, family=2, 
    from=from at entry=0x7fffffffe320, from_prefixlen=<optimized out>, 
    to=to at entry=0x7fffffffe330, to_prefixlen=<optimized out>, tos=0 '\000', 
    fwmark=0, table=300, iif=0x7fffffffe340 "\005", 
    oif=0x5c2f6839 <error: Cannot access memory at address 0x5c2f6839>, 
    ret=0x7fffffffe318) at ../src/network/networkd-routing-policy-rule.c:276
#5  0x00005555555a9b6c in routing_policy_rule_add_foreign (ret=0x7fffffffe318, 
    oif=<optimized out>, iif=<optimized out>, table=<optimized out>, 
    fwmark=<optimized out>, tos=<optimized out>, to_prefixlen=<optimized out>, 
    to=0x7fffffffe330, from_prefixlen=<optimized out>, from=0x7fffffffe320, 
    family=<optimized out>, m=0x55555585cd30)
    at ../src/network/networkd-routing-policy-rule.c:316
#6  manager_rtnl_process_rule (rtnl=<optimized out>, message=<optimized out>, 
    userdata=0x55555585cd30) at ../src/network/networkd-manager.c:821
#7  0x000055555556db07 in manager_rtnl_enumerate_rules (m=0x55555585cd30)
    at ../src/network/networkd-manager.c:1450
#8  main (argc=<optimized out>, argv=<optimized out>)
    at ../src/network/networkd.c:136

> That kernel is not provided by Debian. Can you reproduce the issue with
> a Debian kernel as well?

Yes, it crashes the same with 4.12.0-1-amd64 *and* the configuration fixes 
above.

-- 
雷米‧德尼-库尔蒙
https://www.remlab.net/