3 ms·
Haven't looked at this too closely, but iptables are unlikely to help. The bug appears to be in the recvmmsg() syscall, which is where the packet leaves the ker
by zzzcpan 10y ago
Haven't looked at this too closely, but iptables are unlikely to help. The bug appears to be in the recvmmsg() syscall, which is where the packet leaves the kernel and enters the userspace. The syscall itself is not that widely used, only for some unusually optimized UDP servers, you are unlikely to have one running. But you can check with strace just to be sure.
- mkj 10y agoYep. Though I assume this needs some interesting network traffic to trigger it.
- caf 10y agohttps://codesearch.debian.net/search?q=[^_]recvmmsg\%28[^\%29]&perpkg=1&page=1 https://codesearch.debian.net/search?q=[^_]recvmmsg\%28[^\%2... (Many of the results are for code like language runtimes and debugging tools that don't actually use recvmmsg() themselves)
- ajb 10y agoOuch, it's in chromium though.