Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RFC\s+PATCH\s+1\/1\]\s+IPVS\s+netns\s+shutdown\/startup\s+dead\-lock\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [RFC PATCH 1/1] IPVS netns shutdown/startup dead-lock (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Tue, 14 Jun 2011 00:25:31 +0300 (EEST)
Hello, So, sk_lock-AF_INET is locked before calling ip_vs_dst_event ? Do you have a backtrace for this case? I assume your patch is tested to fix the problem ? sk_release_kernel is called in thread c
/html/lvs-devel/2011-06/msg00031.html (10,831 bytes)

2. Re: [RFC PATCH 1/1] IPVS netns shutdown/startup dead-lock (score: 1)
Author: Simon Horman <horms@xxxxxxxxxxxx>
Date: Mon, 13 Jun 2011 20:11:29 +0900
I don't feel strongly either way. [snip] [snip] I'm not a huge fan of labels that only return. So I think it would be slightly easier on the eyes to just return here, not add out_nounlock, and possib
/html/lvs-devel/2011-06/msg00030.html (11,529 bytes)

3. [RFC PATCH 1/1] IPVS netns shutdown/startup dead-lock (score: 1)
Author: Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx>
Date: Mon, 13 Jun 2011 11:32:10 +0200
ip_vs_mutext is used by both netns shutdown code and startup and both implicit uses sk_lock-AF_INET mutex. cleanup CPU-1 startup CPU-2 ip_vs_dst_event() ip_vs_genl_set_cmd() sk_lock-AF_INET __ip_vs_m
/html/lvs-devel/2011-06/msg00026.html (17,057 bytes)


This search system is powered by Namazu