Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797669 Title: tc filter add after delete get error "No space left on device" Status in linux package in Ubuntu: Incomplete Bug description: tc filter seems still leak with ubuntu kernel 4.15.0-36-generic, it can be reproduced with the following steps. ``` tc qdisc add dev eth0 ingress tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter add dev eth0 ingress protocol ip prio 1 handle 800::2 u32 match ip dst 192.168.5.46/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter del dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1 ``` the last command will get this error ``` RTNETLINK answers: No space left on device We have an error talking to the kernel ``` upstream 4.15(eol) also have this issue, but 4.16.2 fixed, and ubuntu 4.15.0-36 already patched upstream 4.16.2 fix patch. however this issue still exist, I think the difference between 4.15 and 4.16 caused this issue. please kindly help check it. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
