From: Rick Jones <rick.jones2@hp.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
Dave Jones <davej@codemonkey.org.uk>,
netdev@vger.kernel.org
Subject: Re: Fwd: [Bug 447812] New: Netlink messages from "tc" to sch_netem module are not interpreted correctly
Date: Wed, 21 May 2008 17:57:34 -0700 [thread overview]
Message-ID: <4834C4FE.4060502@hp.com> (raw)
In-Reply-To: <20080522002155.GP20815@postel.suug.ch>
> Could you try this patch?
I'm not sure what it does to the tc case, unless I botched applying the
patch, my rtnetlink case doesn't seem to change:
izzy:~/netperf2_trunk# ./testfoo 16.89.133.212
destination address is 16.89.133.212
egress interface 0x6000000000004010 eth6
izzy:~/netperf2_trunk# ./testfoo 16.89.133.212 10.208.0.17
netlink: 8 bytes leftover after parsing attributes.
destination address is 16.89.133.212
egress interface 0x6000000000004010 eth6
izzy:~/netperf2_trunk# uname -a
Linux izzy 2.6.26-rc1-netlink #1 SMP Wed May 21 17:36:53 PDT 2008 ia64
GNU/Linux
rick jones
next prev parent reply other threads:[~2008-05-22 0:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 21:45 Fwd: [Bug 447812] New: Netlink messages from "tc" to sch_netem module are not interpreted correctly Dave Jones
2008-05-21 22:10 ` Stephen Hemminger
2008-05-22 0:21 ` Thomas Graf
2008-05-22 0:57 ` Rick Jones [this message]
2008-05-22 11:18 ` Thomas Graf
2008-05-22 16:32 ` Rick Jones
2008-05-22 11:37 ` [NETLINK]: Fix nla_parse_nested_compat() to call nla_parse() directly Thomas Graf
2008-05-22 12:45 ` Patrick McHardy
2008-05-22 17:49 ` David Miller
2008-05-22 18:02 ` Stephen Hemminger
2008-05-22 18:11 ` David Miller
2008-05-21 22:16 ` Fwd: [Bug 447812] New: Netlink messages from "tc" to sch_netem module are not interpreted correctly Rick Jones
2008-05-21 22:36 ` Rick Jones
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=4834C4FE.4060502@hp.com \
--to=rick.jones2@hp.com \
--cc=davej@codemonkey.org.uk \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--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.