Re: net: memory leak in socket

2018-01-10 Thread Sergei Shtylyov
Hello! On 1/9/2018 11:53 PM, Al Viro wrote: Argh... Got broken by "make sock_alloc_file() do sock_release() on failures" - cleanup after sock_map_fd() failure got pulled all the way into sock_alloc_file(), but it used to serve the case when sock_map_fd() failed *before* getting to sock_alloc_

Re: net: memory leak in socket

2018-01-09 Thread Al Viro
On Tue, Jan 09, 2018 at 07:58:08PM +0100, Dmitry Vyukov wrote: > > Argh... Got broken by "make sock_alloc_file() do sock_release() on > > failures" - > > cleanup after sock_map_fd() failure got pulled all the way into > > sock_alloc_file(), > > but it used to serve the case when sock_map_fd() fa

Re: net: memory leak in socket

2018-01-09 Thread Dmitry Vyukov
On Tue, Jan 9, 2018 at 7:53 PM, Al Viro wrote: > On Tue, Jan 09, 2018 at 07:39:50PM +0100, Dmitry Vyukov wrote: >> Hello, >> >> syzkaller has hit the following memory leak on 4.15-rc7: >> >> unreferenced object 0x88002713fb20 (size 16): >> comm "syz-executor3", pid 6576, jiffies 4295029354 (

Re: net: memory leak in socket

2018-01-09 Thread Al Viro
On Tue, Jan 09, 2018 at 07:39:50PM +0100, Dmitry Vyukov wrote: > Hello, > > syzkaller has hit the following memory leak on 4.15-rc7: > > unreferenced object 0x88002713fb20 (size 16): > comm "syz-executor3", pid 6576, jiffies 4295029354 (age 10.166s) > hex dump (first 16 bytes): > 69 6

net: memory leak in socket

2018-01-09 Thread Dmitry Vyukov
Hello, syzkaller has hit the following memory leak on 4.15-rc7: unreferenced object 0x88002713fb20 (size 16): comm "syz-executor3", pid 6576, jiffies 4295029354 (age 10.166s) hex dump (first 16 bytes): 69 6e 73 6d 6f 64 5f 74 00 00 d9 1c 00 88 ff ff insmod_t backtrace: