Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\/2\]\s+IPVS\:\s+make\s+failure\s+of\s+netns\s+init\s+more\s+stable\s*$/: 11 ]

Total 11 documents matching your query.

1. Re: [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Mon, 23 Apr 2012 22:22:22 +0900
Hi, Julian is correct. I made a hack to the code to force it to fail in ip_vs_protocol_net_init() right after calling register_ip_vs_proto_netns() for TCP. With "netfilter: ipvs: Verify that IP_VS pr
/html/lvs-devel/2012-04/msg00093.html (13,400 bytes)

2. Re[3]: [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: "Hans Schillstrom" <hans@xxxxxxxxxxxxxxx>
Date: Thu, 19 Apr 2012 00:33:11 +0200 (CEST)
Hello, Thanks, It's a really odd case when you don't have enough memory to start the kernel I think it's cured now, it doesn't trigger any dumps now. Tested with and without CONFIG_NET_NS Well, I don
/html/lvs-devel/2012-04/msg00065.html (16,589 bytes)

3. Re[2]: [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 18 Apr 2012 23:27:02 +0300 (EEST)
Hello, I trigger it in this way (ip_vs in kernel, ip_vs_ftp as module): if (1 || ip_vs_app_net_init(net) < 0) goto app_fail; This causes ip_vs core to fail. I use NET_NS=n. The ip_vs_ftp part is fixe
/html/lvs-devel/2012-04/msg00064.html (15,168 bytes)

4. Re[2]: [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: "Hans Schillstrom" <hans@xxxxxxxxxxxxxxx>
Date: Wed, 18 Apr 2012 14:37:43 +0200 (CEST)
Hello I did test this with 4 netns loaded and modprobe ip_vs_ftp In the 4:th netns (ipvs->gen >= 4) fire a -ENOMEM The result was as expected, ip_vs_ftp was not loaded. All patches below was loaded.
/html/lvs-devel/2012-04/msg00063.html (15,090 bytes)

5. Re: [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Tue, 17 Apr 2012 23:57:13 +0300 (EEST)
Hello, Agreed Yes, ip_vs_init fails. It is this case that can happen, we can only guess how difficult is to get ENOMEM here. IIRC, we can generate only ENOMEM error on IPVS core load. I assume Simon
/html/lvs-devel/2012-04/msg00062.html (12,500 bytes)

6. Re: [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx>
Date: Tue, 17 Apr 2012 13:15:10 +0200
[snip] I wonder if we are chasing ghosts... With proper fault handling I can't even see a case when it (net->ipvs) can be used. Can you see a case when it could happen? Still we can set it to NULL on
/html/lvs-devel/2012-04/msg00061.html (11,687 bytes)

7. Re: [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx>
Date: Mon, 16 Apr 2012 19:45:15 +0200
Yes, you are right as allways :-) -- Regards Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to major
/html/lvs-devel/2012-04/msg00060.html (12,294 bytes)

8. Re: [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Mon, 16 Apr 2012 20:31:40 +0300 (EEST)
Hello, There is line here that registers current net for cleanup only after ops_init success: list_add_tail(&net->exit_list, &net_exit_list); If ops_init fails for first net then net_exit_list will b
/html/lvs-devel/2012-04/msg00059.html (12,322 bytes)

9. Re: [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx>
Date: Mon, 16 Apr 2012 19:16:31 +0200
Sorry, I'll revert that. True, when ip_vs(.ko) fails. I missed that. Are you sure ? In my code it does... static int __register_pernet_operations(struct list_head *list, struct pernet_operations *ops
/html/lvs-devel/2012-04/msg00058.html (17,542 bytes)

10. Re: [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Mon, 16 Apr 2012 17:25:23 +0300 (EEST)
Hello, While 1st patch looks ok, keeping net->ipvs after failure is not going to work. It seems you ignored the patch I already posted. We duplicate the pointer in net->ipvs but it should not be used
/html/lvs-devel/2012-04/msg00057.html (16,300 bytes)

11. [PATCH 2/2] IPVS: make failure of netns init more stable (score: 1)
Author: Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx>
Date: Mon, 16 Apr 2012 13:39:38 +0200
Add a IP_VS_F_NET_INIT_OK flag that other modules can use for check of a successful init of ip_vs Signed-off-by: Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx> -- include/net/ip_vs.h | 20 +++++++++
/html/lvs-devel/2012-04/msg00055.html (17,038 bytes)


This search system is powered by Namazu