- 1. Re: ipvs netns exit causes crash in conntrack. (score: 1)
- Author: Julian Anastasov <ja@xxxxxx>
- Date: Sat, 11 Jun 2011 02:10:09 +0300 (EEST)
- Hello, Correct, this should work because we clear the flag during device cleanup. Yes, may be this check will need smp_rmb, not atomic operations, sort of: if (cp->flags & IP_VS_CONN_F_NFCT) { smp_rm
- /html/lvs-devel/2011-06/msg00014.html (12,770 bytes)
- 2. Re: ipvs netns exit causes crash in conntrack. (score: 1)
- Author: Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx>
- Date: Fri, 10 Jun 2011 11:38:05 +0200
- Tested, with nf_conntrack_netlink loaded before ip_vs there is no problem. -- Regards Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lvs
- /html/lvs-devel/2011-06/msg00013.html (12,850 bytes)
- 3. Re: ipvs netns exit causes crash in conntrack. (score: 1)
- Author: Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx>
- Date: Fri, 10 Jun 2011 11:02:39 +0200
- This is a quite simple patch ... The enable flag is set to 0 already when an exit begins So it's just to check it maybe it should be atomic, but for my quick test "volatile" will do. diff --git a/net
- /html/lvs-devel/2011-06/msg00012.html (14,686 bytes)
- 4. Re: ipvs netns exit causes crash in conntrack. (score: 1)
- Author: Julian Anastasov <ja@xxxxxx>
- Date: Fri, 10 Jun 2011 00:13:33 +0300 (EEST)
- Hello, Yes, may be nfnetlink subsys is unregistered first, before ipvs and net->nfnl is already NULL. Note that nf_conntrack_find_get returns existing conntrack, so this module is still active for th
- /html/lvs-devel/2011-06/msg00009.html (11,804 bytes)
- 5. Re: ipvs netns exit causes crash in conntrack. (score: 1)
- Author: Hans Schillstrom <hans@xxxxxxxxxxxxxxx>
- Date: Thu, 9 Jun 2011 21:46:34 +0200
- Yes, i.e. nf_conntrack is loded first and then ip_vs and last nf_conntrack_netlink It's hard to tell exactly what was going on in user-space when the lxc container get killed.... Basically there is a
- /html/lvs-devel/2011-06/msg00008.html (16,708 bytes)
- 6. Re: ipvs netns exit causes crash in conntrack. (score: 1)
- Author: Patrick McHardy <kaber@xxxxxxxxx>
- Date: Thu, 09 Jun 2011 15:11:23 +0200
- This looks like nfnetlink.c excited and destroyed the nfnl socket, but ip_vs was still holding a reference to a conntrack. When the conntrack got destroyed it created a ctnetlink event, causing an oo
- /html/lvs-devel/2011-06/msg00007.html (14,896 bytes)
- 7. ipvs netns exit causes crash in conntrack. (score: 1)
- Author: Hans Schillstrom <hans@xxxxxxxxxxxxxxx>
- Date: Thu, 9 Jun 2011 14:57:28 +0200
- Hello I have a problem with ip_vs_conn_flush() and expiring timers ... After a couple of hours checking locks, I'm still not closer to a solution Conntrack differs a bit between 2.6.32 vs .2.6.39 but
- /html/lvs-devel/2011-06/msg00006.html (15,512 bytes)
This search system is powered by
Namazu