From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0A2CDC34352 for ; Fri, 13 Dec 2019 20:41:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 47EFB24784 for ; Fri, 13 Dec 2019 20:41:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728946AbfLMTvf (ORCPT ); Fri, 13 Dec 2019 14:51:35 -0500 Received: from iolanthe.rowland.org ([192.131.102.54]:60488 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1728934AbfLMTve (ORCPT ); Fri, 13 Dec 2019 14:51:34 -0500 Received: (qmail 4151 invoked by uid 2102); 13 Dec 2019 14:51:33 -0500 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Dec 2019 14:51:33 -0500 Date: Fri, 13 Dec 2019 14:51:33 -0500 (EST) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Andrey Konovalov cc: syzbot , LKML , USB list , , syzkaller-bugs Subject: Re: Re: general protection fault in usb_set_interface In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org On Fri, 13 Dec 2019, Andrey Konovalov wrote: > > > Let's retry here: > > > > > #syz test: https://github.com/google/kasan.git f0df5c1b > > > > This bug is already marked as fixed. No point in testing. > > > > Hm, that explains some of the weirdness. It doesn't explain though > neither why the patch was actually tested when Alan requested it nor > why syzbot sent no reply. In the meantime, is there any way to get syzbot to test the new patch with the old reproducer? Perhaps tell it to re-open this bug? Alan Stern