From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: netlink regression (since 2.6.18)
Date: Thu, 8 Mar 2007 13:28:18 -0800 [thread overview]
Message-ID: <20070308132818.4c12830c@freekitty> (raw)
In-Reply-To: <20070307142830.307979e6@freekitty>
On Wed, 7 Mar 2007 14:28:30 -0800
Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> On a Ubuntu x86_64 machine the command:
> tc qdisc ls
> gets a RTNETLINK error. It looks like some data structure alignment
> issue got introduced between 2.6.18 and 2.6.19-rc1 and continues on.
> Since netlink data structure layout is part of the user ABI, we need to go back
> and keep compatibility.
>
> Still working out the bisect to find where the problem started.
Never mind, it turned out that NET_SCHED wasn't configured on that machine.
--
Stephen Hemminger <shemminger@linux-foundation.org>
prev parent reply other threads:[~2007-03-08 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 22:28 netlink regression (since 2.6.18) Stephen Hemminger
2007-03-08 21:28 ` Stephen Hemminger [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=20070308132818.4c12830c@freekitty \
--to=shemminger@linux-foundation.org \
--cc=bunk@stusta.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).