Received-SPF: pass (google.com: domain of linux-kernel+bounces-172049-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, 
 Breno Leitao <leitao@debian.org>
Cc: christophe.jaillet@wanadoo.fr, paulmck@kernel.org, 
 io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <20240507170002.2269003-1-leitao@debian.org>
References: <20240507170002.2269003-1-leitao@debian.org>
Subject: Re: [PATCH v3] io_uring/io-wq: Use set_bit() and test_bit() at
 worker->flags
Message-Id: <171510945496.45805.5070549169318056486.b4-ty@kernel.dk>
Date: Tue, 07 May 2024 13:17:34 -0600
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit


On Tue, 07 May 2024 10:00:01 -0700, Breno Leitao wrote:
> Utilize set_bit() and test_bit() on worker->flags within io_uring/io-wq
> to address potential data races.
> 
> The structure io_worker->flags may be accessed through various data
> paths, leading to concurrency issues. When KCSAN is enabled, it reveals
> data races occurring in io_worker_handle_work and
> io_wq_activate_free_worker functions.
> 
> [...]

Applied, thanks!

[1/1] io_uring/io-wq: Use set_bit() and test_bit() at worker->flags
      commit: 8a565304927fbd28c9f028c492b5c1714002cbab

Best regards,
-- 
Jens Axboe