On 08/12/16 01:43, Thomas Haller wrote:
On Tue, 2016-12-06 at 17:12 -0600, Dan Williams wrote:
libnl1 rejects the IFLA_INFO_DATA attribute because it expects it
to
contain a sub-attribute. Since the payload size is zero it doesn't
match the policy and parsing fails.
There's no problem with libnl3 because its policy accepts empty
payloads for NLA_NESTED attributes (see libnl3 commit 4be02ace4826
Hi,
libnl1 is unmaintained these days. I don't think it makes sense to
backport that patch. The last upstream release was 3+ years ago, with
no upstream development since then.
IMHO netcf should drop libnl-1 support.
G'day Thomas,
I'm not sure anyone was suggesting fixing libnl1, it was more around a
discussion with regard to a change in the kernel breaking old userspace
and whether it needs to be fixed in the kernel.
Personally, now I have a solution to *my* immediate problem (that being
any kernel 4.7 or later prevented libvirtd starting on my servers
because my netcf was compiled against libnl1) I can upgrade the relevant
userspace components to work around the issue.
Also, now this issue is a number of months old and I appear to be the
only person reporting it, maybe it's not worth tackling. I would
absolutely say that netcf needs to drop libnl1 now though as it *is*
broken on newer kernels under the right circumstances.
I appreciate the assistance in tracking it down anyway. Thanks guys.
Regards,
Brad
