From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+82609b8937a4458106ca@syzkaller.appspotmail.com>,
asml.silence@gmail.com, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [io-uring?] KMSAN: uninit-value in io_req_task_work_add_remote
Date: Thu, 25 Jul 2024 08:46:34 -0600 [thread overview]
Message-ID: <b8783e34-1011-4eae-86cc-9ba2b310863d@kernel.dk> (raw)
In-Reply-To: <000000000000a4fe65061e049a02@google.com>
On 7/24/24 3:03 PM, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-by: syzbot+82609b8937a4458106ca@syzkaller.appspotmail.com
> Tested-by: syzbot+82609b8937a4458106ca@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: c33ffdb7 Merge tag 'phy-for-6.11' of git://git.kernel...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17d29bb5980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=f26f43c6f7db5ad2
> dashboard link: https://syzkaller.appspot.com/bug?extid=82609b8937a4458106ca
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> patch: https://syzkaller.appspot.com/x/patch.diff?x=120b7dad980000
>
> Note: testing is done by a robot and is best-effort only.
#syz test: git://git.kernel.dk/linux io_uring-6.11
--
Jens Axboe
next prev parent reply other threads:[~2024-07-25 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 10:51 [syzbot] [io-uring?] KMSAN: uninit-value in io_req_task_work_add_remote syzbot
2024-07-24 11:13 ` Edward Adam Davis
2024-07-24 11:39 ` syzbot
2024-07-24 12:11 ` Edward Adam Davis
2024-07-24 15:57 ` syzbot
2024-07-24 16:04 ` Jens Axboe
2024-07-24 18:37 ` Jens Axboe
2024-07-24 18:59 ` syzbot
2024-07-24 20:34 ` Jens Axboe
2024-07-24 21:03 ` syzbot
2024-07-24 21:04 ` Jens Axboe
2024-07-25 14:46 ` Jens Axboe [this message]
2024-07-25 17:32 ` syzbot
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=b8783e34-1011-4eae-86cc-9ba2b310863d@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+82609b8937a4458106ca@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.