- 1. Re: memory leak in start_sync_thread (score: 1)
- Author: Julian Anastasov <ja@xxxxxx>
- Date: Tue, 11 Jun 2019 22:52:54 +0300 (EEST)
- Hello, Thanks! It explains the problem. It was not obvious from the fact that only tinfo was reported as a leak, nothing for tinfo->sock. Moving sock_release to owner complicates the locking but I'll
- /html/lvs-devel/2019-06/msg00006.html (14,004 bytes)
- 2. Re: memory leak in start_sync_thread (score: 1)
- Author: Eric Biggers <ebiggers@xxxxxxxxxx>
- Date: Mon, 10 Jun 2019 18:06:13 -0700
- The bug is that ownership of some memory is passed to a kthread started by kthread_run(), but the kthread can be stopped before it actually executes the threadfn. See the code in kernel/kthread.c: re
- /html/lvs-devel/2019-06/msg00005.html (13,013 bytes)
- 3. memory leak in start_sync_thread (score: 1)
- Author: syzbot <syzbot+7e2e50c8adfccd2e5041@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 28 May 2019 11:28:05 -0700
- Hello, syzbot found the following crash on: HEAD commit: cd6c84d8 Linux 5.2-rc2 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=132bd44aa00000 kernel config: https://syzk
- /html/lvs-devel/2019-05/msg00037.html (25,287 bytes)
This search system is powered by
Namazu