** Description changed:
[impact]
systemd-networkd double-free causes crash under some circumstances, such
as adding/removing ip rules
[test case]
- see original description
+ Use networkd-dispatcher events to add and remove IP rules. The example
+ scripts below are contrived (and
The scripts for configured.d and configuring.d to add and remove IP
rules (included above) are likely the culprit. @ddstreet would you like
me to write that up more compactly?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
No crashes on my test machine for 12 days. Push it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881972
Title:
systemd-networkd crashes with invalid pointer
To manage notifications about this bug
So far so good running the latest package for 10 hours. I'll let it run
another day or two but previously I would have seen the issue by now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881972
Titl
I was not able to reproduce the original issue on
237-3ubuntu10.42~202007071725~ubuntu18.04.1 after letting it run for 12+
hours. I have now installed the newer
237-3ubuntu10.42~202007081907~ubuntu18.04.1 from the same PPA. I no
longer see a SEGV when the service first starts at boot, thanks! I wil
Here's one of the new coredumps I'm getting at boot now. Note that I don't have
debugging symbols installed for the PPA version of systemd.
# coredumpctl gdb 714
PID: 714 (systemd-network)
UID: 100 (systemd-network)
GID: 102 (systemd-network)
Signal: 11 (SE
I added the ppa and did a dist-upgrade then rebooted. systemd-networkd
now consistently crashes once at boot (looks like a different crash
though). But then everything appears to work after networkd restarts
once. I will let it run and see if the invalid pointer crash happens.
# journalctl -l -u s
I've gathered several core dumps now but the stacktraces are identical.
The logged reason for dumping core is "free(): invalid pointer".
I wonder if there is a race condition with whatever networkd itself is
doing when it reconfigures the interface (which it seems to do more
aggressively for DHCP
# coredumpctl gdb 28819
PID: 28819 (systemd-network)
UID: 100 (systemd-network)
GID: 102 (systemd-network)
Signal: 6 (ABRT)
Timestamp: Tue 2020-06-16 19:36:22 UTC (16min ago)
Command Line: /lib/systemd/systemd-networkd
Executable: /lib/systemd/sys
Also of note is that on systems with systemd-237-3ubuntu10.33 or older I
don't see the "ens5: Configured" log messages at all after initial
configuration, even though I'm sure DHCP renewals are happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
The system I pulled the networkd log from had not yet become unreachable
but here's a snippet from one that did:
May 27 07:38:18 ip-10-0-4-228 systemd[1]: systemd-networkd.service: Failed with
result 'core-dump'.
May 27 07:38:18 ip-10-0-4-228 systemd[1]: Failed to start Network Service.
May 27 07
Public bug reported:
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-ssd
/ubuntu-bionic-18.04-amd64-server-20200131 with systemd-237-3ubuntu10.33
does NOT have the problem, but the next most recent AWS AMI
ubun
12 matches
Mail list logo