From: patchwork-bot+bluetooth@kernel.org
To: Tamas Koczka <poprdi@google.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, theflow@google.com,
nogikh@google.com, dvyukov@google.com
Subject: Re: [PATCH v2] Bluetooth: Collect kcov coverage from hci_rx_work
Date: Thu, 14 Jul 2022 20:00:13 +0000 [thread overview]
Message-ID: <165782881350.24437.8150730211077461222.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220714104814.1296858-1-poprdi@google.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 14 Jul 2022 10:48:14 +0000 you wrote:
> Annotate hci_rx_work() with kcov_remote_start() and kcov_remote_stop()
> calls, so remote KCOV coverage is collected while processing the rx_q
> queue which is the main incoming Bluetooth packet queue.
>
> Coverage is associated with the thread which created the packet skb.
>
> The collected extra coverage helps kernel fuzzing efforts in finding
> vulnerabilities.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: Collect kcov coverage from hci_rx_work
https://git.kernel.org/bluetooth/bluetooth-next/c/b28a31ebc74f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-07-14 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 10:48 [PATCH v2] Bluetooth: Collect kcov coverage from hci_rx_work Tamas Koczka
2022-07-14 20:00 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-07 10:40 Tamas Koczka
2022-06-07 11:44 ` Tamás Koczka
2022-06-14 13:34 ` Tamás Koczka
2022-06-22 10:20 ` Aleksandr Nogikh
2022-06-23 9:18 ` Dmitry Vyukov
2022-07-04 12:52 ` Tamás Koczka
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=165782881350.24437.8150730211077461222.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=pabeni@redhat.com \
--cc=poprdi@google.com \
--cc=theflow@google.com \
/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;
as well as URLs for NNTP newsgroup(s).