From: Andrew Morton <akpm@linux-foundation.org>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>
Subject: Re: [PATCH v1 0/3] kcov: collect coverage from usb soft interrupts
Date: Wed, 26 Feb 2020 17:41:41 -0800 [thread overview]
Message-ID: <20200226174141.d1c938e7962a4fc09060eba9@linux-foundation.org> (raw)
In-Reply-To: <cover.1582742673.git.andreyknvl@google.com>
On Wed, 26 Feb 2020 19:48:06 +0100 Andrey Konovalov <andreyknvl@google.com> wrote:
> This patchset extends kcov to allow collecting coverage from soft
> interrupts and then uses the new functionality to collect coverage from
> USB code.
>
> This has allowed to find at least one new HID bug [1], which was recently
> fixed by Alan [2].
I might have asked this before, but I don't see this obvious question
addressed in the changelogs so maybe I didn't...
Will this only ever be useful for USB? Or is it anticipated that other
subsystems will use this? If the latter, which ones?
Thanks.
next prev parent reply other threads:[~2020-02-27 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 18:48 Andrey Konovalov
2020-02-26 18:48 ` [PATCH v1 1/3] kcov: cleanup debug messages Andrey Konovalov
2020-02-26 18:48 ` [PATCH v1 2/3] kcov: collect coverage from interrupts Andrey Konovalov
2020-02-26 18:48 ` [PATCH v1 3/3] usb: core: kcov: collect coverage from usb complete callback Andrey Konovalov
2020-02-27 1:41 ` Andrew Morton [this message]
2020-02-27 15:44 ` [PATCH v1 0/3] kcov: collect coverage from usb soft interrupts Andrey Konovalov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200226174141.d1c938e7962a4fc09060eba9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®