Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932362AbcLLVFq (ORCPT ); Mon, 12 Dec 2016 16:05:46 -0500 Received: from iolanthe.rowland.org ([192.131.102.54]:49536 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S932216AbcLLVFo (ORCPT ); Mon, 12 Dec 2016 16:05:44 -0500 Date: Mon, 12 Dec 2016 16:05:43 -0500 (EST) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Andrey Konovalov cc: Greg Kroah-Hartman , USB list , LKML , Dmitry Vyukov , Kostya Serebryany , syzkaller Subject: Re: usb/core: warning in usb_create_ep_devs/sysfs_create_dir_ns In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 669 Lines: 20 On Mon, 12 Dec 2016, Andrey Konovalov wrote: > Hi! > > While running the syzkaller fuzzer I've got the following error report. > > On commit 3c49de52d5647cda8b42c4255cf8a29d1e22eff5 (Dev 2). > > WARNING: CPU: 2 PID: 865 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x8a/0xa0 > gadgetfs: disconnected > sysfs: cannot create duplicate filename > '/devices/platform/dummy_hcd.0/usb2/2-1/2-1:64.0/ep_05' > Kernel panic - not syncing: panic_on_warn set ... I suppose we could check for USB devices that claim to have two endpoints with the same address. But is it really worthwhile? A kernel warning isn't so bad when you're dealing with buggy device firmware. Alan Stern