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=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no 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 CD5B1CA9EB9 for ; Wed, 23 Oct 2019 22:04:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9F48D21906 for ; Wed, 23 Oct 2019 22:04:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1571868258; bh=ZxZ2bjgrY8LxhC2gxwLipAEf5uWwjrnOAtpoB5RPRXI=; h=Date:From:To:Cc:Subject:In-Reply-To:References:List-ID:From; b=xOzPzPcohSb6BoFB2q3/LeqKYhzkLfuo77dVSRe+RTHt7kGfdNcVB7dbaTu8vIJRe dWZK8xFkEZ06t/CxhBQkmVfuhwwZtpLbXGL8fo3JtMYq12h++C7JlM1BeMwbR0xqhN t1pgMcQkjRkwiW9dshDgknuDM2yvHYg8gDLGqYpY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2436628AbfJWWER (ORCPT ); Wed, 23 Oct 2019 18:04:17 -0400 Received: from mail.kernel.org ([198.145.29.99]:50792 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2405661AbfJWWER (ORCPT ); Wed, 23 Oct 2019 18:04:17 -0400 Received: from akpm3.svl.corp.google.com (unknown [104.133.8.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 475632084C; Wed, 23 Oct 2019 22:04:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1571868254; bh=ZxZ2bjgrY8LxhC2gxwLipAEf5uWwjrnOAtpoB5RPRXI=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=nNtl5XCv0j9A48YnWaF5iTudfCQq33+QXJgRHWDYDg2YmEqbZCLDe+NCQQetvnR/b 3CtLgVZL25LnwIFN+itO3rrgLffBBVQHhKExtJ614qS8GnmXP7HXLzSds5ViMnMXX/ nrTddbLuRTbdz423kAsG34HKFcGZ+DmZP7edoe2A= Date: Wed, 23 Oct 2019 15:04:13 -0700 From: Andrew Morton To: Andrey Konovalov Cc: linux-usb@vger.kernel.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Dmitry Vyukov , Greg Kroah-Hartman , Alan Stern , "Michael S . Tsirkin" , Jason Wang , Arnd Bergmann , Steven Rostedt , David Windsor , Elena Reshetova , Anders Roxell , Alexander Potapenko , Marco Elver Subject: Re: [PATCH v2 0/3] kcov: collect coverage from usb and vhost Message-Id: <20191023150413.8aa05549bd840deccfed5539@linux-foundation.org> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 23 Oct 2019 17:24:28 +0200 Andrey Konovalov wrote: > This patchset extends kcov to allow collecting coverage from the USB > subsystem and vhost workers. See the first patch description for details > about the kcov extension. The other two patches apply this kcov extension > to USB and vhost. > > These patches have been used to enable coverage-guided USB fuzzing with > syzkaller for the last few years I find it surprising that this material is so focused on USB. Is there something unique about USB that gave rise to this situation, or is it expected that the new kcov feature will be used elsewhere in the kernel? If the latter, which are the expected subsystems?