From: Thomas Haller <thaller@redhat.com>
To: Dan Williams <dcbw@redhat.com>,
Guillaume Nault <g.nault@alphalink.fr>,
Brad Campbell <lists2009@fnarfbargle.com>
Cc: netdev <netdev@vger.kernel.org>, Thomas Graf <tgraf@suug.ch>,
David Miller <davem@davemloft.net>
Subject: Re: commit : ppp: add rtnetlink device creation support - breaks netcf on my machine.
Date: Wed, 07 Dec 2016 18:43:42 +0100 [thread overview]
Message-ID: <1481132622.4116.6.camel@redhat.com> (raw)
In-Reply-To: <1481065966.11028.3.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
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.
best,
Thomas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-12-07 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 9:06 commit : ppp: add rtnetlink device creation support - breaks netcf on my machine Brad Campbell
2016-12-05 17:53 ` Guillaume Nault
2016-12-06 1:28 ` Brad Campbell
2016-12-06 7:47 ` Brad Campbell
2016-12-06 23:08 ` Guillaume Nault
2016-12-06 23:12 ` Dan Williams
2016-12-07 17:43 ` Thomas Haller [this message]
2016-12-08 2:29 ` Brad Campbell
2016-12-08 9:54 ` Guillaume Nault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1481132622.4116.6.camel@redhat.com \
--to=thaller@redhat.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=g.nault@alphalink.fr \
--cc=lists2009@fnarfbargle.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.