public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH 1/1] io_uring: annotate offset timeout races
Date: Fri, 19 May 2023 19:57:26 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <>

On Fri, 19 May 2023 15:21:16 +0100, Pavel Begunkov wrote:
> It's racy to read ->cached_cq_tail without taking proper measures
> (usually grabbing ->completion_lock) as timeout requests with CQE
> offsets do, however they have never had a good semantics for from
> when they start counting. Annotate racy reads with data_race().

Applied, thanks!

[1/1] io_uring: annotate offset timeout races
      commit: 5498bf28d8f2bd63a46ad40f4427518615fb793f

Best regards,
Jens Axboe

      reply	other threads:[~2023-05-20  1:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 14:21 [PATCH 1/1] io_uring: annotate offset timeout races Pavel Begunkov
2023-05-20  1:57 ` 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:

* 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] \

* 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