Netdev List
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Marcel Holtmann <marcel@holtmann.org>,
	Network Development <netdev@vger.kernel.org>
Cc: Michal Schmidt <mschmidt@redhat.com>
Subject: Re: Useless debug warning "netlink: 16 bytes leftover after parsing attributes"
Date: Wed, 19 Oct 2016 17:50:50 +0200	[thread overview]
Message-ID: <04216bf5-84a7-b6ea-57ff-9cb29a706510@6wind.com> (raw)
In-Reply-To: <0756CFFC-5BF7-4685-A1E2-0D88B2898454@holtmann.org>

Le 18/10/2016 à 07:06, Marcel Holtmann a écrit :
> Hi,
> 
> so lately I am seeing a bunch of these warnings:
> 
> netlink: 16 bytes leftover after parsing attributes..
> 
> While they give you the process name, they are still useless to track down the message that causes them. I find them even more useless since an updated userspace on an older kernel can trigger the nla_policy warning here. And that updated userspace program is doing nothing wrong by including extra attributes. So what purpose is this warning serving?
Usually, it means that a netlink message is malformed, for example that the
header of the family has the wrong size. An unknown attribute should not trigger
this kind of message.
Here is an example:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e5eca6d41f53d


Regards,
Nicolas

      reply	other threads:[~2016-10-19 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18  5:06 Useless debug warning "netlink: 16 bytes leftover after parsing attributes" Marcel Holtmann
2016-10-19 15:50 ` Nicolas Dichtel [this message]

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=04216bf5-84a7-b6ea-57ff-9cb29a706510@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=marcel@holtmann.org \
    --cc=mschmidt@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox