From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: upgrading kernel breaks tc ?
Date: Thu, 20 Aug 2015 10:34:38 +0000 [thread overview]
Message-ID: <55D5AD3E.7020308@gmail.com> (raw)
In-Reply-To: <CAA5aLPgtEPvQqJXuiRbtu-TOKRMBi6ns5THNkmrAxOC1FQJY=g@mail.gmail.com>
Akshat Kakkar wrote:
> I am running sl6.3 (i.e. kernel 2.6.32-279). I upgraded the kernel
> (and only kernel) using elrepo to kernel 4.1.4.
You won't get new features without updating TC - but your test case on
my setup still deletes all the filters with matching tc.
> Now when I boot with this new kernel, and try to delete specific tc
> filter, it is not happening. It is instead deleting all the filters.
> Following is the commanf I am trying,
>
> tc filter del dev eth1 protocol ip parent 1: prio 5 handle 800:0:3
> u32
But earlier you found that handle alone wasn't unique so you should have
used the whole command line that you added.
Saying that it still deletes all, so that wasn't it.
> It is behaving exactily as the command without handle, i.e. like
>
> tc filter del dev eth1 protocol ip parent 1: prio 5
It maybe a bug or it maybe that old kernel was unsafe letting you delete
something that is going to get hashed to.
FWIW using replace/change + full command (with eg. flowid changed) works
for me, but I didn't find a way to change anything else - which doesn't
mean there isn't a way, just that I am not familiar with
hashing/advanced tc.
Historically I always used to just remove the root qdisc and start again
to change something, as it was safer/less error prone. If you have 000s
of rules then use batch mode which will be way, way, faster than
inputting them with a script.
next prev parent reply other threads:[~2015-08-20 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 8:30 upgrading kernel breaks tc ? Akshat Kakkar
2015-08-20 9:59 ` Akshat Kakkar
2015-08-20 10:34 ` Andy Furniss [this message]
2015-08-20 11:51 ` Akshat Kakkar
2015-08-20 12:35 ` Akshat Kakkar
2015-08-20 16:10 ` Martin A. Brown
2015-08-21 10:38 ` Akshat Kakkar
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=55D5AD3E.7020308@gmail.com \
--to=adf.lists@gmail.com \
--cc=lartc@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 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.