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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\]\s+ipvs\:\s+fix\s+tinfo\s+memory\s+leak\s+in\s+start_sync_thread\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [PATCH net] ipvs: fix tinfo memory leak in start_sync_thread (score: 1): Author: Simon Horman <horms@xxxxxxxxxxxx>; Date: Thu, 20 Jun 2019 14:09:11 +0200; Thanks Julian. Pablo, please consider this for inclusion in nf. Acked-by: Simon Horman <horms@xxxxxxxxxxxx>; /html/lvs-devel/2019-06/msg00009.html (11,729 bytes)
2. [PATCH net] ipvs: fix tinfo memory leak in start_sync_thread (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Tue, 18 Jun 2019 23:07:36 +0300; syzkaller reports for memory leak in start_sync_thread [1] As Eric points out, kthread may start and stop before the threadfn function is called, so there is no chance the data (tinfo in our case) to; /html/lvs-devel/2019-06/msg00007.html (23,907 bytes)

Current List: 1 - 2
Page: [1]