public inbox for [email protected]
 help / color / mirror / Atom feed
From: lizetao <[email protected]>
To: Bui Quang Minh <[email protected]>
Cc: Jens Axboe <[email protected]>,
	Pavel Begunkov <[email protected]>,
	"[email protected]" <[email protected]>,
	"[email protected]"
	<[email protected]>,
	"[email protected]" <[email protected]>
Subject: RE: [PATCH] io_uring/sqpoll: annotate data race for access in debug check
Date: Wed, 8 Jan 2025 16:24:19 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Hi,

> -----Original Message-----
> From: Bui Quang Minh <[email protected]>
> Sent: Wednesday, January 8, 2025 11:11 PM
> To: [email protected]
> Cc: Bui Quang Minh <[email protected]>; Jens Axboe
> <[email protected]>; Pavel Begunkov <[email protected]>; io-
> [email protected];
> [email protected]
> Subject: [PATCH] io_uring/sqpoll: annotate data race for access in debug check
> 
> sqd->thread must only be access while holding sqd->lock. In
> io_sq_thread_stop, the sqd->thread access to wake up the sq thread is placed
> while holding sqd->lock, but the access in debug check is not. As this access if
> for debug check only, we can safely ignore the data race here. So we annotate
> this access with data_race to silence KCSAN.
> 
> Reported-by: [email protected]
> Signed-off-by: Bui Quang Minh <[email protected]>
> ---
>  io_uring/sqpoll.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/io_uring/sqpoll.c b/io_uring/sqpoll.c index
> 9e5bd79fd2b5..2088c56dbaa0 100644
> --- a/io_uring/sqpoll.c
> +++ b/io_uring/sqpoll.c
> @@ -57,7 +57,7 @@ void io_sq_thread_park(struct io_sq_data *sqd)
> 
>  void io_sq_thread_stop(struct io_sq_data *sqd)  {
> -	WARN_ON_ONCE(sqd->thread == current);
> +	WARN_ON_ONCE(data_race(sqd->thread) == current);
>  	WARN_ON_ONCE(test_bit(IO_SQ_THREAD_SHOULD_STOP, &sqd-
> >state));
> 
>  	set_bit(IO_SQ_THREAD_SHOULD_STOP, &sqd->state);
> --
> 2.43.0
> 

The modification of this patch itself is fine, but there are two other things I need to confirm.
1、Does the io_uring_cancel_generic() require the same modification?
2、It is not holding sqd->lock in io_req_normal_work_add(), is it safe?

Thanks.
Reviewed-by: Li Zetao<[email protected]>

---
Li Zetao

  reply	other threads:[~2025-01-08 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 15:10 [PATCH] io_uring/sqpoll: annotate data race for access in debug check Bui Quang Minh
2025-01-08 16:24 ` lizetao [this message]
2025-01-08 16:42   ` Bui Quang Minh

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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