From: Jared Holzman <jholzman@nvidia.com>
To: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>
Cc: Uday Shankar <ushankar@purestorage.com>,
Caleb Sander Mateos <csander@purestorage.com>,
Guy Eisenberg <geisenberg@nvidia.com>,
Yoav Cohen <yoav@nvidia.com>, Omri Levi <omril@nvidia.com>,
Ofer Oshri <ofer@nvidia.com>
Subject: Re: [PATCH V2 0/2] ublk: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd
Date: Mon, 28 Apr 2025 16:31:19 +0300 [thread overview]
Message-ID: <76bdc68b-04b9-4e47-b184-702a281456a5@nvidia.com> (raw)
In-Reply-To: <174554599841.1088672.7136612395116492771.b4-ty@kernel.dk>
On 25/04/2025 4:53, Jens Axboe wrote:
>
> On Fri, 25 Apr 2025 09:37:38 +0800, Ming Lei wrote:
>> The 2 patches try to fix race between between io_uring_cmd_complete_in_task
>> and ublk_cancel_cmd.
>>
>> Thanks,
>> Ming
>>
>> V2:
>> - improve comment and commit log
>> - remove useless memory barrier(Caleb Sander Mateos)
>> - add tested-by fixes tag
>>
>> [...]
>
> Applied, thanks!
>
> [1/2] ublk: call ublk_dispatch_req() for handling UBLK_U_IO_NEED_GET_DATA
> commit: d6aa0c178bf81f30ae4a780b2bca653daa2eb633
> [2/2] ublk: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd
> commit: f40139fde5278d81af3227444fd6e76a76b9506d
>
> Best regards,
Confirmed that this version also fixes the issue for us.
Thanks,
Jared
prev parent reply other threads:[~2025-04-28 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 1:37 [PATCH V2 0/2] ublk: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd Ming Lei
2025-04-25 1:37 ` [PATCH V2 1/2] ublk: call ublk_dispatch_req() for handling UBLK_U_IO_NEED_GET_DATA Ming Lei
2025-04-25 1:37 ` [PATCH V2 2/2] ublk: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd Ming Lei
2025-05-14 1:50 ` Shinichiro Kawasaki
2025-05-18 19:12 ` Jared Holzman
2025-05-18 23:54 ` Shinichiro Kawasaki
2025-05-19 2:45 ` Ming Lei
2025-04-25 1:53 ` [PATCH V2 0/2] " Jens Axboe
2025-04-28 13:31 ` Jared Holzman [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=76bdc68b-04b9-4e47-b184-702a281456a5@nvidia.com \
--to=jholzman@nvidia.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=geisenberg@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=ofer@nvidia.com \
--cc=omril@nvidia.com \
--cc=ushankar@purestorage.com \
--cc=yoav@nvidia.com \
/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