> Can this be backported to Focal?
If I'm understanding the upstream bug correctly, this only affects those
using a really large number of interfaces and/or vlans and/or bridges on
a single system, and in that situation this can be worked around just by
increasing the socket receive buffer size for systemd-networkd.socket,
right?
If that's the case, I don't really think this is something valid for
backporting; the buffer increase is just delaying the ENOBUF, and if
more interfaces are added it may still happen. I believe the buffer size
adjustment is a configuration issue for anyone using such a large number
of interfaces.
However, if I've misunderstood the bug or patch, or if there are
problems with my evaluation of it, please provide specific steps and/or
config to reproduce the problem, so we can evaluate what's needed for
backporting to focal.
For now, marking as wontfix.
** Changed in: systemd (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1912331
Title:
Many interfaces lead to "kernel receive buffer overrun"
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Won't Fix
Status in systemd source package in Groovy:
Fix Released
Bug description:
This is about a systemd-networkd bug, described here:
https://github.com/systemd/systemd/issues/14417
There's a patch available:
https://github.com/systemd/systemd/pull/16982
Can this be backported to Focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
