From: Jens Axboe <axboe@kernel.dk>
To: Jann Horn <jannh@google.com>, robert@fmmr.tech
Cc: io-uring@vger.kernel.org, Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
kasan-dev@googlegroups.com
Subject: Re: [PATCH v3] io_uring: annotate remote tasks for kcoverage
Date: Wed, 24 Jun 2026 08:16:14 -0600 [thread overview]
Message-ID: <15170077-5975-46d4-b2f4-6cf47ee8151f@kernel.dk> (raw)
In-Reply-To: <CAG48ez02Sio8ZENVK3gUWM+8j6NgG9LxtnDV=v+FSqsqs_KfnA@mail.gmail.com>
On 6/23/26 10:37 AM, Jann Horn wrote:
> On Tue, May 26, 2026 at 6:49 PM Robert Femmer <robert@fmmr.tech> wrote:
>> Fuzzers use coverage information to guide generation of test cases
>> towards new or interesting code paths. Syzkaller, specifically, makes
>> use kcoverage (CONFIG_KCOV). Coverage information is not collected for
>> kernel tasks unless annotated by kcov_remote_start and kcov_remote_stop.
>> This patch annotates io-uring's work queue and sqpoll tasks.
>
> I think this is a useful change overall.
Agree, mostly waiting on Andrey and Robert to hash out the details and
we can get this landed for 7.3. On vacation the next weeks, not much
going on on my end, work wise.
--
Jens Axboe
prev parent reply other threads:[~2026-06-24 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 15:39 [PATCH] io_uring: annotate remote tasks for kcoverage Robert Femmer
2026-05-20 17:36 ` Andrey Konovalov
2026-05-20 20:43 ` [PATCH v2] " Robert Femmer
2026-05-22 16:23 ` Andrey Konovalov
2026-05-26 16:49 ` [PATCH v3] " Robert Femmer
2026-06-23 16:37 ` Jann Horn
2026-06-23 16:46 ` Jann Horn
2026-06-24 9:01 ` [PATCH v4] " Robert Femmer
2026-06-30 13:41 ` Andrey Konovalov
2026-06-30 23:34 ` Jens Axboe
2026-06-30 23:35 ` Jens Axboe
2026-06-24 14:16 ` Jens Axboe [this message]
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=15170077-5975-46d4-b2f4-6cf47ee8151f@kernel.dk \
--to=axboe@kernel.dk \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=io-uring@vger.kernel.org \
--cc=jannh@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=robert@fmmr.tech \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.