lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 20 Nov 2020 12:00:55 -0500 From: Alan Stern <stern@...land.harvard.edu> To: Andrey Konovalov <andreyknvl@...gle.com> Cc: balbi@...nel.org, gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org, syzkaller-bugs@...glegroups.com Subject: Re: Re: memory leak in hub_event On Fri, Nov 20, 2020 at 08:56:11AM -0800, syzbot wrote: > > On Fri, Nov 20, 2020 at 07:15:20AM -0800, syzbot wrote: > >> Hello, > >> > >> syzbot found the following issue on: > >> > >> HEAD commit: 4d02da97 Merge tag 'net-5.10-rc5' of git://git.kernel.org/.. > >> git tree: upstream > >> console output: https://syzkaller.appspot.com/x/log.txt?x=13a7d2b6500000 > >> kernel config: https://syzkaller.appspot.com/x/.config?x=c5353ac514ca5a43 > >> dashboard link: https://syzkaller.appspot.com/bug?extid=44e64397bd81d5e84cba > >> compiler: gcc (GCC) 10.1.0-syz 20200507 > >> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14925089500000 > >> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16810051500000 > > #syz test: upstream 4d02da97 > > "upstream" does not look like a valid git repo address. Okay, Andrey. If "upstream" is not accepted as a valid git repo address, why does syzkaller list it on the "git tree:" line? It seems to me that syzkaller should be willing to accept as input anything it produces as output. And what repo should I put here? Alan Stern
Powered by blists - more mailing lists