Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+1\/2\]\s+ipvs\:\s+reset\s+ipvs\s+pointer\s+in\s+netns\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+1\/2\]\s+ipvs\:\s+reset\s+ipvs\s+pointer\s+in\s+netns\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [PATCH 1/2] ipvs: reset ipvs pointer in netns (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Fri, 13 Apr 2012 15:41:50 +0300 (EEST); Hello, This is not true. __ip_vs_init must free everything on error as a netns init handler. What will happen if net_generic fails and netns tries cleanup on such failed subsys? __ip_vs_cleanup is ca; /html/lvs-devel/2012-04/msg00031.html (12,209 bytes)
2. Re: [PATCH 1/2] ipvs: reset ipvs pointer in netns (score: 1): Author: Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx>; Date: Fri, 13 Apr 2012 11:29:09 +0200; You can't do this since name space cleanup will call __ip_vs_cleanup later and that will cause NULL pointer problems Note that any netns init faiulure will be rolled back later by net_namespace.c And; /html/lvs-devel/2012-04/msg00029.html (11,281 bytes)
3. [PATCH 1/2] ipvs: reset ipvs pointer in netns (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Fri, 13 Apr 2012 11:44:01 +0300; Make sure net->ipvs is reset on netns cleanup or failed initialization. It is needed for IPVS applications to know that IPVS core is not loaded in netns. Signed-off-by: Julian Anastasov <ja@xxxxxx> -; /html/lvs-devel/2012-04/msg00027.html (9,894 bytes)

Current List: 1 - 3
Page: [1]