From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 202297] New: No longer able to add multiple tc filters. RTNETLINK answers: No space left on device
Date: Wed, 16 Jan 2019 10:01:34 -0800 [thread overview]
Message-ID: <20190116100134.50e2531e@shemminger-XPS-13-9360> (raw)
Is this still present in net-next?
Begin forwarded message:
Date: Tue, 15 Jan 2019 19:20:22 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 202297] New: No longer able to add multiple tc filters. RTNETLINK answers: No space left on device
https://bugzilla.kernel.org/show_bug.cgi?id=202297
Bug ID: 202297
Summary: No longer able to add multiple tc filters. RTNETLINK
answers: No space left on device
Product: Networking
Version: 2.5
Kernel Version: 4.20.2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: kbocharnikov@datacast.com
Regression: No
This is working in 4.5.5 and is not working in 4.18.12 onward. Not sure about
the versions in between:
example:
# tc filter add dev ipenc0 parent 1:0 handle ::102 protocol ip prio 1 u32 match
ip dst 224.44.44.4/32 flowid 1:5
//successfull, now every other addition will not be:
# tc filter add dev ipenc0 parent 2:0 handle ::102 protocol ip prio 1 u32 match
ip dst 224.44.44.4/32 flowid 2:102
RTNETLINK answers: No space left on device
We have an error talking to the kernel
This appears to be almost the same bug that was supposedly fixed, but does not
appear to be:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797669
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-01-16 18:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190116100134.50e2531e@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.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