From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Ahern <dsahern@gmail.com>
Subject: netlink: 16 bytes leftover after parsing attributes in process `ip'.
Date: Mon, 24 Sep 2018 21:19:06 -0600
Message-ID: <6059bf4e-b1cf-2c7e-5529-9003bdd8a14b@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
        David Miller <davem@davemloft.net>
To: Christian Brauner <christian@brauner.io>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-pf1-f173.google.com ([209.85.210.173]:32837 "EHLO
        mail-pf1-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1725954AbeIYJYc (ORCPT
        <rfc822;netdev@vger.kernel.org>); Tue, 25 Sep 2018 05:24:32 -0400
Received: by mail-pf1-f173.google.com with SMTP id d4-v6so10202403pfn.0
        for <netdev@vger.kernel.org>; Mon, 24 Sep 2018 20:19:09 -0700 (PDT)
Content-Language: en-US
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

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.