From: Andrew Morton <akpm@linux-foundation.org>
To: Joao Correia <joaomiguelcorreia@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: some tc commands fail on 2.6.29-rc6-git5, works on 2.6.28.7
Date: Sun, 1 Mar 2009 16:57:29 -0800 [thread overview]
Message-ID: <20090301165729.8e08e1d7.akpm@linux-foundation.org> (raw)
In-Reply-To: <a5d9929e0903011636w6bff1032y28ab58c0ff8c8052@mail.gmail.com>
(cc netdev)
On Mon, 2 Mar 2009 00:36:03 +0000 Joao Correia <joaomiguelcorreia@gmail.com> wrote:
> Hello all
>
> On a Fedora 9 box, with a 2.6.29-rc6-git5 compiled with the same
> .config as the previously running 2.6.28.7, i get:
>
> [root@duron ~]# /sbin/tc qdisc add dev eth2 handle ffff: ingress
> [root@duron ~]# /sbin/tc filter add dev eth2 parent ffff: protocol ip
> prio 50 u32 match ip src 0.0.0.0/0 police rate 30320kbit burst 500k
> drop flowid :1
> RTNETLINK answers: Invalid argument
> We have an error talking to the kernel
> [root@duron ~]# uname -a
> Linux duron 2.6.29-rc6-git5 #3 SMP Sun Mar 1 00:02:56 WET 2009 i686
> athlon i386 GNU/Linux
> [root@duron ~]#
>
> There is no information regarding this event on dmesg or /var/log/messages.
> eth2 exists and is working properly, under 2.6.28.7 it works (without
> complaints).
>
> Please advise on what steps I may take to provide more information. I have
> both kernel sources and availability to apply patches/recompile as needed.
>
next parent reply other threads:[~2009-03-02 0:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a5d9929e0903011636w6bff1032y28ab58c0ff8c8052@mail.gmail.com>
2009-03-02 0:57 ` Andrew Morton [this message]
2009-03-02 18:44 ` some tc commands fail on 2.6.29-rc6-git5, works on 2.6.28.7 Jarek Poplawski
2009-03-03 23:10 ` Joao Correia
2009-03-04 0:06 ` Jarek Poplawski
2009-03-04 2:50 ` John Dykstra
2009-03-04 14:09 ` Joao Correia
2009-03-04 17:59 ` Denys Fedoryschenko
2009-03-04 23:34 ` [PATCH] " Jarek Poplawski
2009-03-05 0:32 ` Joao Correia
2009-03-05 1:38 ` David Miller
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=20090301165729.8e08e1d7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=joaomiguelcorreia@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).