From: David Ahern <dsahern@gmail.com>
To: Christian Brauner <christian@brauner.io>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: netlink: 16 bytes leftover after parsing attributes in process `ip'.
Date: Mon, 24 Sep 2018 21:19:06 -0600 [thread overview]
Message-ID: <6059bf4e-b1cf-2c7e-5529-9003bdd8a14b@gmail.com> (raw)
On top of net-next I am see a dmesg error:
netlink: 16 bytes leftover after parsing attributes in process `ip'.
I traced it to address lists and commit:
commit 6ecf4c37eb3e89b0832c9616089a5cdca3747da7
Author: Christian Brauner <christian@brauner.io>
Date: Tue Sep 4 21:53:50 2018 +0200
ipv6: enable IFA_TARGET_NETNSID for RTM_GETADDR
Per the commit you are trying to guess whether the ancillary header is
an ifinfomsg or a ifaddrmsg. I am guessing you are guessing wrong. :-)
I don't have time to take this to ground, but address listing is not the
only area subject to iproute2's SNAFU of infomsg everywhere on dumps. I
have thought about this for route dumps, but its solution does not work
here. You'll need to find something because the current warning on every
address dump is not acceptable.
next reply other threads:[~2018-09-25 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 3:19 David Ahern [this message]
2018-09-25 9:49 ` netlink: 16 bytes leftover after parsing attributes in process `ip' Christian Brauner
2018-09-25 12:07 ` Stephen Hemminger
[not found] ` <CAHrFyr55vt78akhC+WE5maDPLzmurUeB6wT-DmHcCmnAfPKrgw@mail.gmail.com>
2018-09-25 13:16 ` Stephen Hemminger
2018-09-26 10:45 ` Christian Brauner
2018-09-25 14:47 ` Jiri Benc
2018-09-25 15:37 ` David Ahern
2018-09-26 5:51 ` Jiri Benc
2018-09-26 14:54 ` David Ahern
2018-09-26 15:02 ` Stephen Hemminger
2018-09-26 9:49 ` Christian Brauner
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=6059bf4e-b1cf-2c7e-5529-9003bdd8a14b@gmail.com \
--to=dsahern@gmail.com \
--cc=christian@brauner.io \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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.