Bug 99091
Summary: | Kernel panic while sending network packets over TAP interface | ||
---|---|---|---|
Product: | Networking | Reporter: | Ramon Schwammberger (ras) |
Component: | Other | Assignee: | Stephen Hemminger (stephen) |
Status: | NEW --- | ||
Severity: | normal | CC: | david, doj, szg00000 |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 3.11 and higher | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Ramon Schwammberger
2015-05-28 11:44:58 UTC
It seems that this bug has been fixed in Kernel 3.18.14. To be precise, it looks like the fix happened somewhere in between 3.18.8 and 3.18.14. This commit which is part of 3.18.14 most likely circumvents the crash, as it drops the packet early. commit 7aca2472093e9353793faeede03c94d00ce42fb1 Author: Sebastian Pöhn <sebastian.poehn@gmail.com> Date: Mon Apr 20 09:19:20 2015 +0200 ip_forward: Drop frames with attached skb->sk [ Upstream commit 2ab957492d13bb819400ac29ae55911d50a82a13 ] Initial discussion was: [FYI] xfrm: Don't lookup sk_policy for timewait sockets Forwarded frames should not have a socket attached. Especially tw sockets will lead to panics later-on in the stack. This was observed with TPROXY assigning a tw socket and broken policy routing (misconfigured). As a result frame enters forwarding path instead of input. We cannot solve this in TPROXY as it cannot know that policy routing is broken. v2: Remove useless comment Signed-off-by: Sebastian Poehn <sebastian.poehn@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Sasha Levin <sasha.levin@oracle.com> |