Linux-EROFS Archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: syzbot <syzbot+88ad8b0517a9d3bb9dc8@syzkaller.appspotmail.com>,
	linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, xiang@kernel.org
Subject: Re: [syzbot] [erofs?] KMSAN: uninit-value in z_erofs_lz4_decompress (3)
Date: Tue, 19 Mar 2024 18:34:23 +0800	[thread overview]
Message-ID: <fad8f767-7870-486c-b8af-1f260b6bdb65@linux.alibaba.com> (raw)
In-Reply-To: <0000000000007e031e061400c64d@google.com>

#syz dup KMSAN: uninit-value in z_erofs_lz4_decompress (2)

On 2024/3/19 18:17, syzbot wrote:
> Hello,
> 
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
> 
> Reported-and-tested-by: syzbot+88ad8b0517a9d3bb9dc8@syzkaller.appspotmail.com
> 
> Tested on:
> 
> commit:         b3603fcb Merge tag 'dlm-6.9' of git://git.kernel.org/p..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=14395479180000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=c0f689e0798c5101
> dashboard link: https://syzkaller.appspot.com/bug?extid=88ad8b0517a9d3bb9dc8
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> 
> Note: no patches were applied.
> Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2024-03-19 10:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 11:04 [syzbot] [erofs?] KMSAN: uninit-value in z_erofs_lz4_decompress (3) syzbot
2024-02-01 16:17 ` Gao Xiang
2024-02-01 16:57   ` syzbot
2024-02-20  6:50     ` Gao Xiang
2024-02-20  7:22       ` syzbot
2024-02-20  7:47         ` Gao Xiang
2024-03-19  9:31         ` Gao Xiang
2024-03-19 10:17           ` syzbot
2024-03-19 10:34             ` Gao Xiang [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=fad8f767-7870-486c-b8af-1f260b6bdb65@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+88ad8b0517a9d3bb9dc8@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=xiang@kernel.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).