From: Jens Axboe <axboe@kernel.dk>
To: Robert Femmer <robert@fmmr.tech>, io-uring@vger.kernel.org
Cc: Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
kasan-dev@googlegroups.com, Jann Horn <jannh@google.com>
Subject: Re: [PATCH v4] io_uring: annotate remote tasks for kcoverage
Date: Tue, 30 Jun 2026 17:34:10 -0600 [thread overview]
Message-ID: <91b6999b-9854-46bb-8e2b-c8e260581f4a@kernel.dk> (raw)
In-Reply-To: <20260624090145.1715865-2-robert@fmmr.tech>
On 6/24/26 3:01 AM, Robert Femmer wrote:
> diff --git a/io_uring/io-wq.c b/io_uring/io-wq.c
> index 8cc7b47d3089..173299dfc9c2 100644
> --- a/io_uring/io-wq.c
> +++ b/io_uring/io-wq.c
> @@ -19,6 +19,7 @@
> #include <linux/mmu_context.h>
> #include <linux/sched/sysctl.h>
> #include <uapi/linux/io_uring.h>
> +#include <linux/kcov.h>
>
> #include "io-wq.h"
> #include "slist.h"
> @@ -639,6 +640,7 @@ static void io_worker_handle_work(struct io_wq_acct *acct,
> /* handle a whole dependent link */
> do {
> struct io_wq_work *next_hashed, *linked;
> + struct io_kiocb *req;
> unsigned int work_flags = atomic_read(&work->flags);
> unsigned int hash = __io_wq_is_hashed(work_flags)
> ? __io_get_work_hash(work_flags)
We try to, roughly, keep this in reverse xmas tree order. I've fixed it
up.
> diff --git a/io_uring/sqpoll.c b/io_uring/sqpoll.c
> index 46c12afec73e..aafb640d3b2f 100644
> --- a/io_uring/sqpoll.c
> +++ b/io_uring/sqpoll.c
> @@ -13,6 +13,7 @@
> #include <linux/cpuset.h>
> #include <linux/sched/cputime.h>
> #include <linux/io_uring.h>
> +#include <linux/kcov.h>
>
> #include <uapi/linux/io_uring.h>
>
> @@ -342,10 +343,12 @@ static int io_sq_thread(void *data)
>
> cap_entries = !list_is_singular(&sqd->ctx_list);
> list_for_each_entry(ctx, &sqd->ctx_list, sqd_list) {
> + kcov_remote_start_common(ctx->kcov_handle);
> int ret = __io_sq_thread(ctx, sqd, cap_entries, &ist);
Never code before variable declarations in the scope. I've also fixed
that one up.
Also not sure what branch this was against, because it doesn't apply to
any current one. Guessing something old? I had applied 2 hunks, fwiw.
Please check the result!
--
Jens Axboe
next prev parent reply other threads:[~2026-06-30 23:34 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 [this message]
2026-06-30 23:35 ` Jens Axboe
2026-06-24 14:16 ` [PATCH v3] " Jens Axboe
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=91b6999b-9854-46bb-8e2b-c8e260581f4a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox