public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Edward Adam Davis <eadavis@qq.com>,
	syzbot+f8e9a371388aa62ecab4@syzkaller.appspotmail.com
Cc: asml.silence@gmail.com, io-uring@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] io_uring: fix uninit-value in io_sendrecv_fail
Date: Sat, 16 Mar 2024 07:11:20 -0600	[thread overview]
Message-ID: <6eb8bb77-7440-427b-bbc5-d1ac5d6533d8@kernel.dk> (raw)
In-Reply-To: <tencent_6C22CC2079326CC82FB96CD89458E9F6EF0A@qq.com>

On 3/16/24 6:42 AM, Edward Adam Davis wrote:
> diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
> index cd9a137ad6ce..3db59fd6f676 100644
> --- a/io_uring/io_uring.c
> +++ b/io_uring/io_uring.c
> @@ -1066,6 +1066,7 @@ static void io_preinit_req(struct io_kiocb *req, struct io_ring_ctx *ctx)
>  	/* not necessary, but safer to zero */
>  	memset(&req->cqe, 0, sizeof(req->cqe));
>  	memset(&req->big_cqe, 0, sizeof(req->big_cqe));
> +	memset(&req->cmd, 0, sizeof(req->cmd));
>  }
>  
>  static void io_flush_cached_locked_reqs(struct io_ring_ctx *ctx,

This will just silence the syzbot report, as the memory is initialized
upfront. But it's not the real fix, as ->done_io could still be recycled
from a previous issue.

-- 
Jens Axboe


      reply	other threads:[~2024-03-16 13:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 22:28 [syzbot] [io-uring?] KMSAN: uninit-value in io_sendrecv_fail syzbot
2024-03-15 22:38 ` Jens Axboe
2024-03-16  7:41   ` syzbot
2024-03-16 13:13   ` Jens Axboe
2024-03-16 13:37     ` syzbot
2024-03-16 14:42       ` Jens Axboe
2024-03-16 15:20         ` syzbot
2024-03-16 15:28       ` Pavel Begunkov
2024-03-16 15:46         ` Jens Axboe
2024-03-16 16:01   ` Jens Axboe
2024-03-16 16:29     ` syzbot
2024-03-16 16:36       ` Jens Axboe
2024-03-16 17:18         ` syzbot
2024-03-16  3:48 ` Edward Adam Davis
2024-03-16 10:26   ` syzbot
2024-03-16 12:42 ` [PATCH] io_uring: fix " Edward Adam Davis
2024-03-16 13:11   ` 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=6eb8bb77-7440-427b-bbc5-d1ac5d6533d8@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=eadavis@qq.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+f8e9a371388aa62ecab4@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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