[PATCH 4.14 076/293] ipvs: fix tinfo memory leak in start_sync_thread

2019-07-29 Thread Greg Kroah-Hartman
[ Upstream commit 5db7c8b9f9fc2aeec671ae3ca6375752c162e0e7 ] 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 be released in thread. Fix this by

[PATCH 4.19 109/271] ipvs: fix tinfo memory leak in start_sync_thread

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 5db7c8b9f9fc2aeec671ae3ca6375752c162e0e7 ] 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 be released in thread. Fix this by

[PATCH 5.1 145/371] ipvs: fix tinfo memory leak in start_sync_thread

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 5db7c8b9f9fc2aeec671ae3ca6375752c162e0e7 ] 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 be released in thread. Fix this by

[PATCH 5.2 158/413] ipvs: fix tinfo memory leak in start_sync_thread

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 5db7c8b9f9fc2aeec671ae3ca6375752c162e0e7 ] 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 be released in thread. Fix this by

[PATCH AUTOSEL 4.14 075/105] ipvs: fix tinfo memory leak in start_sync_thread

2019-07-15 Thread Sasha Levin
From: Julian Anastasov [ Upstream commit 5db7c8b9f9fc2aeec671ae3ca6375752c162e0e7 ] 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 be

[PATCH AUTOSEL 4.19 107/158] ipvs: fix tinfo memory leak in start_sync_thread

2019-07-15 Thread Sasha Levin
From: Julian Anastasov [ Upstream commit 5db7c8b9f9fc2aeec671ae3ca6375752c162e0e7 ] 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 be

[PATCH AUTOSEL 5.1 143/219] ipvs: fix tinfo memory leak in start_sync_thread

2019-07-15 Thread Sasha Levin
From: Julian Anastasov [ Upstream commit 5db7c8b9f9fc2aeec671ae3ca6375752c162e0e7 ] 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 be

[PATCH AUTOSEL 5.2 161/249] ipvs: fix tinfo memory leak in start_sync_thread

2019-07-15 Thread Sasha Levin
From: Julian Anastasov [ Upstream commit 5db7c8b9f9fc2aeec671ae3ca6375752c162e0e7 ] 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 be

Re: memory leak in start_sync_thread

2019-06-11 Thread Julian Anastasov
Hello, On Mon, 10 Jun 2019, Eric Biggers wrote: > On Tue, May 28, 2019 at 11:28:05AM -0700, syzbot wrote: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:cd6c84d8 Linux 5.2-rc2 > > git tree: upstream > > console output: https://syzkaller.appspot.c

Re: memory leak in start_sync_thread

2019-06-10 Thread Eric Biggers
On Tue, May 28, 2019 at 11:28:05AM -0700, syzbot wrote: > 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=132bd44aa0 > kernel config: https://syzkaller.appspot.co

memory leak in start_sync_thread

2019-05-28 Thread syzbot
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=132bd44aa0 kernel config: https://syzkaller.appspot.com/x/.config?x=64479170dcaf0e11 dashboard link: https://syzkaller.appspo