Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\]\s+ipvs\:\s+fix\s+WARNING\s+in\s+__ip_vs_cleanup

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\]\s+ipvs\:\s+fix\s+WARNING\s+in\s+__ip_vs_cleanup_batch\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [PATCH net] ipvs: fix WARNING in __ip_vs_cleanup_batch() (score: 1): Author: shaozhengchao <shaozhengchao@xxxxxxxxxx>; Date: Mon, 31 Oct 2022 18:46:01 +0800; Hello, During the initialization of ip_vs_conn_net_init(), if file ip_vs_conn or ip_vs_conn_sync fails to be created, the initialization is successful by default. Therefore, the ip_vs_conn or ip_vs_c; /html/lvs-devel/2022-10/msg00044.html (12,549 bytes)
2. Re: [PATCH net] ipvs: fix WARNING in __ip_vs_cleanup_batch() (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Mon, 31 Oct 2022 12:35:27 +0200 (EET); Hello, Good catch. But can you add some #ifdef CONFIG_PROC_FS as done in commit 4bc3c8dc9f5f ("ipvs: fix possible memory leak in ip_vs_control_net_init") ? You can also extend it to include ifdefs an; /html/lvs-devel/2022-10/msg00043.html (12,791 bytes)
3. [PATCH net] ipvs: fix WARNING in __ip_vs_cleanup_batch() (score: 1): Author: Zhengchao Shao <shaozhengchao@xxxxxxxxxx>; Date: Mon, 31 Oct 2022 14:49:56 +0800; During the initialization of ip_vs_conn_net_init(), if file ip_vs_conn or ip_vs_conn_sync fails to be created, the initialization is successful by default. Therefore, the ip_vs_conn or ip_vs_conn_syn; /html/lvs-devel/2022-10/msg00042.html (11,463 bytes)

Current List: 1 - 3
Page: [1]