Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\]\s+ipvs\:\s+orphan\s+skb\s+on\s+LOCAL

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\]\s+ipvs\:\s+orphan\s+skb\s+on\s+LOCAL_IN\s+path\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [PATCH net-next] ipvs: orphan skb on LOCAL_IN path (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Thu, 22 Jan 2015 00:43:27 +0200 (EET); Hello, Good idea. But there is a case where for traffic to local real server we return NF_ACCEPT. In this case we have to preserve the skb->sk. I guess skb_orphan should be used as follows. skb->dev; /html/lvs-devel/2015-01/msg00018.html (10,474 bytes)
2. [PATCH net-next] ipvs: orphan skb on LOCAL_IN path (score: 1): Author: Alex Gartrell <agartrell@xxxxxx>; Date: Tue, 20 Jan 2015 14:55:16 -0800; may be a time-wait socket, which will blow up in the ip6_output path when we try to pull out the non-existent pinet6 pointer (the type-punning causes that pointer to be garbage). This patch orphans; /html/lvs-devel/2015-01/msg00014.html (10,181 bytes)

Current List: 1 - 2
Page: [1]