From: Jens Axboe <axboe@kernel.dk>
To: Colin Ian King <coking@nvidia.com>,
Keith Busch <kbusch@kernel.org>,
io-uring@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] io_uring: Fix incorrect ordering of assinments of sqe and opcode
Date: Wed, 22 Oct 2025 07:46:12 -0600 [thread overview]
Message-ID: <e5f234a2-ef18-4a54-8436-f23f7490c9e4@kernel.dk> (raw)
In-Reply-To: <20251022134431.8220-1-coking@nvidia.com>
On 10/22/25 7:44 AM, Colin Ian King wrote:
> Currently opcode is being assigned to a dereferenced pointer sqe before
> sqe is being assigned. It appears the order of these two assignments cs
> the wrong way around. Fix this by swapping the order of the assignments.
Fix for this has already been folded in.
--
Jens Axboe
prev parent reply other threads:[~2025-10-22 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 13:44 [PATCH][next] io_uring: Fix incorrect ordering of assinments of sqe and opcode Colin Ian King
2025-10-22 13:46 ` 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:
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=e5f234a2-ef18-4a54-8436-f23f7490c9e4@kernel.dk \
--to=axboe@kernel.dk \
--cc=coking@nvidia.com \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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