This bug was fixed in the package systemd - 237-3ubuntu10.42
---
systemd (237-3ubuntu10.42) bionic; urgency=medium
[ Dan Streetman ]
*
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,
the reproducer from description causes the coredump rather easily on
bionic:
ubuntu@lp1881972-b:~$ dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.41 amd64system and service manager
from journal:
Jul 30 17:49:08 lp1881972-b systemd-networkd[705]: munmap_chunk(): invalid
Hello John, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.42 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: systemd (Ubuntu Bionic)
Status: Incomplete => In Progress
--
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
** 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
@r-2ohn-d please do write up a test case for @vorlon, thanks
--
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
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.
"see original description" is inadequate as a test case. I am reading
the original description and it does not describe a step-by-step
reproducer.
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of
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
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
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
thanks! i'd missed a patch in backporting for another bug.
a new version is building now in the same ppa, could you test with it
once it's built? Specifically, version
237-3ubuntu10.42~202007081907~ubuntu18.04.1 (or later)
--
You received this bug notification because you are a member of
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
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
@r-2ohn-d can you test with systemd from this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd
--
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
** Description changed:
+ [impact]
+
+ systemd-networkd double-free causes crash under some circumstances, such
+ as adding/removing ip rules
+
+ [test case]
+
+ see original description
+
+ [regression potential]
+
+ this strdup's strings during addition of routing policy rules, so any
+
I think this is fixed by upstream commit
eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Bionic)
Assignee:
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:
can you attach one of the coredumps? That will significantly help with
finding where exactly the problem is.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
22 matches
Mail list logo
