From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>,
Dylan Yudaken <[email protected]>,
Pavel Begunkov <[email protected]>
Cc: io-uring Mailing List <[email protected]>,
Facebook Kernel Team <[email protected]>
Subject: Re: [PATCH liburing] fix io_uring_recvmsg_cmsg_nexthdr logic
Date: Mon, 18 Jul 2022 07:42:04 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 7/18/22 7:41 AM, Ammar Faizi wrote:
> On 7/18/22 8:34 PM, Dylan Yudaken wrote:
>> io_uring_recvmsg_cmsg_nexthdr was using the payload to delineate the end
>> of the cmsg list, but really it needs to use whatever was returned by the
>> kernel.
>>
>> Reported-by: Jens Axboe <[email protected]>
>> Fixes: 874406f ("add multishot recvmsg API")
>> Signed-off-by: Dylan Yudaken <[email protected]>
>
> The Fixes tag must be at least 12 chars.
It was fixed up while applying.
--
Jens Axboe
next prev parent reply other threads:[~2022-07-18 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 13:34 [PATCH liburing] fix io_uring_recvmsg_cmsg_nexthdr logic Dylan Yudaken
2022-07-18 13:41 ` Ammar Faizi
2022-07-18 13:42 ` Jens Axboe [this message]
2022-07-18 13:41 ` Jens Axboe
2022-07-18 13:41 ` Jens Axboe
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 \
[email protected] \
[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