From: syzbot <syzbot+6c746eea496f34b3161d@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [erofs?] KMSAN: uninit-value in z_erofs_lz4_decompress (2)
Date: Thu, 28 Dec 2023 16:33:03 -0800 [thread overview]
Message-ID: <000000000000daedc8060d9b2c8d@google.com> (raw)
In-Reply-To: <tencent_F13E97D036504AC27443760366CC3C433609@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+6c746eea496f34b3161d@syzkaller.appspotmail.com
Tested on:
commit: fbafc3e6 Merge tag 'for_linus' of git://git.kernel.org..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=132559bee80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e0c7078a6b901aa3
dashboard link: https://syzkaller.appspot.com/bug?extid=6c746eea496f34b3161d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=12db5255e80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-12-29 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_F13E97D036504AC27443760366CC3C433609@qq.com>
2023-12-29 0:33 ` syzbot [this message]
[not found] <tencent_8E794F870DC725E80D9E92105DC45DE19907@qq.com>
2023-12-28 15:09 ` [syzbot] [erofs?] KMSAN: uninit-value in z_erofs_lz4_decompress (2) syzbot
[not found] <tencent_5E3C1D3628961837D24ACA7447769967B009@qq.com>
2023-12-28 14:32 ` syzbot
[not found] <20231228055642.2202587-1-lizhi.xu@windriver.com>
2023-12-28 6:17 ` syzbot
[not found] <20231228011133.3820766-1-lizhi.xu@windriver.com>
2023-12-28 3:38 ` syzbot
2023-12-27 12:31 syzbot
2023-12-28 1:11 ` syzbot
2023-12-28 3:36 ` Gao Xiang
2023-12-28 4:23 ` syzbot
2023-12-28 5:56 ` 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=000000000000daedc8060d9b2c8d@google.com \
--to=syzbot+6c746eea496f34b3161d@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--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.