[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190709074344.76049d02@hermes.lan>
Date: Tue, 9 Jul 2019 07:43:44 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: netdev@...r.kernel.org
Subject: Fw: [Bug 204099] New: systemd-networkd fails on 5.2 - same version
works on 5.1.16
Looks like the stricter netlink validation broke userspace.
This is bad.
Begin forwarded message:
Date: Tue, 09 Jul 2019 00:44:01 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.org
Subject: [Bug 204099] New: systemd-networkd fails on 5.2 - same version works on 5.1.16
https://bugzilla.kernel.org/show_bug.cgi?id=204099
Bug ID: 204099
Summary: systemd-networkd fails on 5.2 - same version works on
5.1.16
Product: Networking
Version: 2.5
Kernel Version: 5.2
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Other
Assignee: stephen@...workplumber.org
Reporter: Ian.kumlien@...il.com
Regression: No
This is more FYI, I haven't had time to properly debug it.
Booting 5.2 causes systemd-networkd to fail to bring any interface up, it will
fail with: "Could not bring up interface: Invalid argument"
However, booting 5.1.16 with the same software works just fine.
Sounds like something was changed in, what I assume is, the netlink API
--
You are receiving this mail because:
You are the assignee for the bug.
Powered by blists - more mailing lists