From: Ben Hutchings <ben@decadent.org.uk>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: "Bruno Prémont" <bonbons@linux-vserver.org>,
netdev@vger.kernel.org, "Greg Rose" <gregory.v.rose@intel.com>
Subject: Re: netlink: 12 bytes leftover after parsing attributes - triggered by iproute2 libnetlink's rtnl_dump_request()
Date: Tue, 20 Mar 2012 15:00:30 +0000 [thread overview]
Message-ID: <1332255630.8043.11.camel@deadeye> (raw)
In-Reply-To: <20120320074140.39a1b3f0@nehalam.linuxnetplumber.net>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Tue, 2012-03-20 at 07:41 -0700, Stephen Hemminger wrote:
>
> >
> > Should this get fixed at kernel level, iproute2 libnetlink level or
> > at end-user level (e.g. collectd)?
> > Three lines every 10 seconds is a damn lot!
> >
> > Thanks,
> > Bruno
>
> Netlink is supposed to be encoded as Type-Length-Value and correctly written
> programs ignore types they don't understand. So either the library is getting
> confused by the type or the attribute is not encoded correctly.
>
>
> The issue could be in libnetlink library. What version of collectd and libnetlink
> are you using?
This was also reported as provoked by a client using the ntrack
rtnetlink code: http://thread.gmane.org/gmane.linux.network/224236
Ben.
--
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-03-20 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 12:41 netlink: 12 bytes leftover after parsing attributes - triggered by iproute2 libnetlink's rtnl_dump_request() Bruno Prémont
2012-03-20 14:41 ` Stephen Hemminger
2012-03-20 15:00 ` Bruno Prémont
2012-03-20 15:09 ` Stephen Hemminger
2012-03-20 15:00 ` Ben Hutchings [this message]
2012-03-21 0:02 ` Stephen Hemminger
2012-04-03 10:01 ` Thomas Graf
2012-04-03 10:17 ` Bruno Prémont
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=1332255630.8043.11.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=bonbons@linux-vserver.org \
--cc=gregory.v.rose@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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.