Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp1422705pxb; Fri, 20 Nov 2020 09:05:59 -0800 (PST) X-Google-Smtp-Source: ABdhPJx1Nzi6w2tXOm+L67Ui9OOG8hIetnSVUDk4eKmYvvAWH6I3kV+tsxM9alvB6XFZJVYfsVJ/ X-Received: by 2002:aa7:c904:: with SMTP id b4mr4443874edt.161.1605891959393; Fri, 20 Nov 2020 09:05:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605891959; cv=none; d=google.com; s=arc-20160816; b=IGkk2QN9wTdRoBfabYKewadJA6Bhq+lo6/pMQc2Rjp1+WET4a5a8QzdhmXCKdsoC8j KwfDVCWMWTrzMZb3/8vo29lGk87ejLkUWkaKr6BzW0+w92P5+mpTdzhaIxoqPpYcJsY2 25LGqwN/wG/FLc+7iHREs8ebDkLK93Kc+ZhtW4EF2j36twFlXJD9huu/KFUicSmXSFXJ 840KLmcOxZiGz+zbPDHR1tZTG7+Cbtpn0t1o8QuuCTT9FyZm+zqu+30FQHohbEIWIdi9 B51K438M69chEpsc9pcTzX/25aNFH9D3XPB2ea8c3k4jMKMOy3p85Xpz4NNT3vOauCCL WGHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=Kt+KzLty21N+RZif+Q/l+gijRKA+ODV3noM5YyGmk10=; b=nNush6wJy4LzDei8nin87morSvCOxrcTh4/89bPFjgsaZNmnpISuQ8COtIqFEL4/Bd W+KDpNFPMbuGUBI0aN6WHFHZ6uVupmC+4z1NwfQoHHlb9O7aMFbN6g0WijVxmdcS2rBm VhnTt0IF46VL+4hWNv5A97a1Fu18i51XXfApYaypRAUBl+QKFNRz1FrQ0AirrChKzZp5 FjMzmplKtKeNNaYpxKCzaoITjXGdMdgAliZxB3I8SleSmgB6LAkCsSMuRQM7hYr1Hha8 FsuHx/+o+NfxpiBeR0EmI/q7QvHdHPilTOoeSCgPrTt7OM7ap7Ku+yzW0n0SQKRuEyu4 VgLA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id rs27si1425830ejb.25.2020.11.20.09.05.27; Fri, 20 Nov 2020 09:05:59 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730203AbgKTRA5 (ORCPT + 99 others); Fri, 20 Nov 2020 12:00:57 -0500 Received: from netrider.rowland.org ([192.131.102.5]:38501 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1729967AbgKTRA4 (ORCPT ); Fri, 20 Nov 2020 12:00:56 -0500 Received: (qmail 622202 invoked by uid 1000); 20 Nov 2020 12:00:55 -0500 Date: Fri, 20 Nov 2020 12:00:55 -0500 From: Alan Stern To: Andrey Konovalov Cc: balbi@kernel.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: Re: Re: memory leak in hub_event Message-ID: <20201120170055.GF619708@rowland.harvard.edu> References: <20201120165609.GE619708@rowland.harvard.edu> <000000000000c49c8b05b48cb833@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000000000000c49c8b05b48cb833@google.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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