From: syzbot <syzbot+01fcd39a0d90cdb0e3df@syzkaller.appspotmail.com>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, xiaopei01@kylinos.cn
Subject: Re: [syzbot] [crypto?] KMSAN: uninit-value in poly1305_blocks
Date: Mon, 20 Oct 2025 21:46:03 -0700 [thread overview]
Message-ID: <68f7100b.a70a0220.3bf6c6.0000.GAE@google.com> (raw)
In-Reply-To: <6556ef55c42ea17d82561b8182d9453b19d66a62.1761016077.git.xiaopei01@kylinos.cn>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+01fcd39a0d90cdb0e3df@syzkaller.appspotmail.com
Tested-by: syzbot+01fcd39a0d90cdb0e3df@syzkaller.appspotmail.com
Tested on:
commit: 6548d364 Merge tag 'cgroup-for-6.18-rc2-fixes' of git:..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1266fde2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bbd3e7f3c2e28265
dashboard link: https://syzkaller.appspot.com/bug?extid=01fcd39a0d90cdb0e3df
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=13b58e7c580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-10-21 4:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 21:07 [syzbot] [crypto?] KMSAN: uninit-value in poly1305_blocks syzbot
2025-10-21 1:54 ` [PATCH] [patch] syz test Pei Xiao
2025-10-21 2:51 ` [syzbot] [crypto?] KMSAN: uninit-value in poly1305_blocks syzbot
2025-10-21 3:08 ` [PATCH] [patch] syz test Pei Xiao
2025-10-21 3:12 ` Herbert Xu
2025-10-21 4:46 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-21 8:35 [PATCH] " Pei Xiao
2025-10-21 8:46 ` Pei Xiao
2025-10-21 9:21 ` [syzbot] [crypto?] KMSAN: uninit-value in poly1305_blocks 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=68f7100b.a70a0220.3bf6c6.0000.GAE@google.com \
--to=syzbot+01fcd39a0d90cdb0e3df@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiaopei01@kylinos.cn \
/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.