From: Jens Axboe <[email protected]>
To: [email protected], [email protected], [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH 5.19] io_uring: fix provided buffer import
Date: Thu, 30 Jun 2022 08:56:41 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 30 Jun 2022 06:20:06 -0700, Dylan Yudaken wrote:
> io_import_iovec uses the s pointer, but this was changed immediately
> after the iovec was re-imported and so it was imported into the wrong
> place.
>
> Change the ordering.
>
>
> [...]
Applied, thanks!
[1/1] io_uring: fix provided buffer import
commit: ee10e6851a687c58f516dc924034cb62c7a01e14
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-30 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 13:20 [PATCH 5.19] io_uring: fix provided buffer import Dylan Yudaken
2022-06-30 14:56 ` 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=165660100106.535585.6996984430706147142.b4-ty@kernel.dk \
[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