Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+nf\]\s+ipvs\:\s+more\s+robust\s+refcounting\s+when\s+sync\s+thread\s+starts\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [PATCH nf] ipvs: more robust refcounting when sync thread starts (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 9 Oct 2019 22:28:55 +0300 (EEST)
Hello, I think, the problem should be in step 2 below: - step 1: try_stop_module -> try_release_module_ref -> atomic_sub_return sets module refcnt to 0. After this point the process to remove module
/html/lvs-devel/2019-10/msg00025.html (21,981 bytes)

2. Re: [PATCH nf] ipvs: more robust refcounting when sync thread starts (score: 1)
Author: Davide Caratti <dcaratti@xxxxxxxxxx>
Date: Wed, 09 Oct 2019 17:01:24 +0200
hello Julian, thanks a lot for reviewing this code. [...] Initially I believed that __ip_vs_dev_cleanup() was called when start_sync_thread() was already running (but it already released the RTNL loc
/html/lvs-devel/2019-10/msg00024.html (20,288 bytes)

3. Re: [PATCH nf] ipvs: more robust refcounting when sync thread starts (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Thu, 3 Oct 2019 22:28:57 +0300 (EEST)
Hello, May be this is not early enough. When control hooks are the first thing to disconnect with ip_vs_unregister_nl_ioctl() how start_sync_thread() is called concurrently? ip_vs_sockopts is protect
/html/lvs-devel/2019-10/msg00012.html (15,921 bytes)

4. [PATCH nf] ipvs: more robust refcounting when sync thread starts (score: 1)
Author: Davide Caratti <dcaratti@xxxxxxxxxx>
Date: Wed, 2 Oct 2019 12:05:35 +0200
if the IPVS module is removed while the sync daemon is starting, there is a small possibility for stop_sync_thread() to end successfully just after start_sync_thread() released sync_mutex, but before
/html/lvs-devel/2019-10/msg00011.html (13,336 bytes)


This search system is powered by Namazu