Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+nf\]\s+ipvs\:\s+don\'t\s+ignore\s+errors\s+in\s+case\s+refcounting\s+ip

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+nf\]\s+ipvs\:\s+don\'t\s+ignore\s+errors\s+in\s+case\s+refcounting\s+ip_vs\s+module\s+fails\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [PATCH nf] ipvs: don't ignore errors in case refcounting ip_vs module fails (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Sat, 12 Oct 2019 19:26:21 +0300 (EEST); Hello, This is ok. I'm just not sure yet which err is more suitable. __ip_vs_ftp_init() already returns -ENOENT from a place where register_ip_vs_app() is called, so may be -ENOENT is a good choice.; /html/lvs-devel/2019-10/msg00033.html (21,947 bytes)
2. [PATCH nf] ipvs: don't ignore errors in case refcounting ip_vs module fails (score: 1): Author: Davide Caratti <dcaratti@xxxxxxxxxx>; Date: Sat, 12 Oct 2019 00:10:17 +0200; if the IPVS module is removed while the sync daemon is starting, there is a small gap where try_module_get() might fail getting the refcount inside ip_vs_use_count_inc(). Then, the refcounts of IPVS; /html/lvs-devel/2019-10/msg00032.html (17,625 bytes)

Current List: 1 - 2
Page: [1]