From: Jens Axboe <[email protected]>
To: syzbot <[email protected]>,
[email protected], [email protected],
[email protected], [email protected]
Subject: Re: [syzbot] [io-uring?] KMSAN: uninit-value in io_sendrecv_fail
Date: Fri, 15 Mar 2024 16:38:34 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/15/24 4:28 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 8ede842f669b Merge tag 'rust-6.9' of https://github.com/Ru..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=138f0ad6180000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a271c5dca0ff14df
> dashboard link: https://syzkaller.appspot.com/bug?extid=f8e9a371388aa62ecab4
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b4a6fa180000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14a59799180000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/af1cd47b84ef/disk-8ede842f.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/be9297712c37/vmlinux-8ede842f.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/c569fb33468d/bzImage-8ede842f.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: [email protected]
>
> =====================================================
> BUG: KMSAN: uninit-value in io_sendrecv_fail+0x91/0x1e0 io_uring/net.c:1334
> io_sendrecv_fail+0x91/0x1e0 io_uring/net.c:1334
> io_req_defer_failed+0x3bd/0x610 io_uring/io_uring.c:1050
> io_queue_sqe_fallback+0x1e3/0x280 io_uring/io_uring.c:2126
> io_submit_fail_init+0x4e1/0x790 io_uring/io_uring.c:2304
> io_submit_sqes+0x19cd/0x2fb0 io_uring/io_uring.c:2480
> __do_sys_io_uring_enter io_uring/io_uring.c:3656 [inline]
> __se_sys_io_uring_enter+0x409/0x43e0 io_uring/io_uring.c:3591
> __x64_sys_io_uring_enter+0x11b/0x1a0 io_uring/io_uring.c:3591
> do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83
> entry_SYSCALL_64_after_hwframe+0x63/0x6b
This is similar to the issue fixed by:
commit 0a535eddbe0dc1de4386046ab849f08aeb2f8faf
Author: Jens Axboe <[email protected]>
Date: Thu Dec 21 08:49:18 2023 -0700
io_uring/rw: ensure io->bytes_done is always initialized
which I did fix separately for this case, just not in the 6.9 pile. I'll
move it over there to silence this one.
Only side effect of this is that cqe->res may not be -EINVAL, when it
should've been, for an ill formed request that was issued with
ISOQE_ASYNC.
#syz test: git://git.kernel.dk/linux.git io_uring-6.0
--
Jens Axboe
next prev parent reply other threads:[~2024-03-15 22:38 UTC|newest]
Thread overview: 15+ 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 [this message]
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 12:42 ` [PATCH] io_uring: fix " Edward Adam Davis
2024-03-16 13:11 ` 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