public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jiri Slaby <[email protected]>
To: Jens Axboe <[email protected]>, io-uring <[email protected]>
Cc: Pavel Begunkov <[email protected]>
Subject: Re: [PATCH v2] io_uring/net: ensure compat import handlers clear free_iov
Date: Tue, 20 Dec 2022 07:45:09 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 19. 12. 22, 15:36, Jens Axboe wrote:
> If we're not allocating the vectors because the count is below
> UIO_FASTIOV, we still do need to properly clear ->free_iov to prevent
> an erronous free of on-stack data.
> 
> Reported-by: Jiri Slaby <[email protected]>
> Fixes: 4c17a496a7a0 ("io_uring/net: fix cleanup double free free_iov init")
> Cc: [email protected]
> Signed-off-by: Jens Axboe <[email protected]>

Tested-by: Jiri Slaby <[email protected]>


> ---
> 
> v2: let's play it a bit safer and just always clear at the top rather
>      in the individual cases.
> 
> diff --git a/io_uring/net.c b/io_uring/net.c
> index 5229976cb582..f76b688f476e 100644
> --- a/io_uring/net.c
> +++ b/io_uring/net.c
> @@ -494,6 +494,7 @@ static int __io_compat_recvmsg_copy_hdr(struct io_kiocb *req,
>   	if (req->flags & REQ_F_BUFFER_SELECT) {
>   		compat_ssize_t clen;
>   
> +		iomsg->free_iov = NULL;
>   		if (msg.msg_iovlen == 0) {
>   			sr->len = 0;
>   		} else if (msg.msg_iovlen > 1) {
> 

thanks,
-- 
js
suse labs


  reply	other threads:[~2022-12-20  6:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 14:36 [PATCH v2] io_uring/net: ensure compat import handlers clear free_iov Jens Axboe
2022-12-20  6:45 ` Jiri Slaby [this message]
2022-12-20 14:15   ` 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] \
    /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