Date:   Tue, 24 Jan 2023 17:59:21 +0100
From:   David Sterba <dsterba@suse.cz>
To:     Alexander Potapenko <glider@google.com>
Cc:     clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
        linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
        ebiggers@kernel.org,
        syzbot+14d9e7602ebdf7ec0a60@syzkaller.appspotmail.com
Subject: Re: [PATCH] btrfs: zlib: zero-initialize zlib workspace
Message-ID: <20230124165921.GT11562@twin.jikos.cz>
Reply-To: dsterba@suse.cz
References: <20230124113234.2070729-1-glider@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230124113234.2070729-1-glider@google.com>
User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12)
Precedence: bulk

On Tue, Jan 24, 2023 at 12:32:34PM +0100, Alexander Potapenko wrote:
> KMSAN reports uses of uninitialized memory in zlib's longest_match()
> called on memory originating from zlib_alloc_workspace().
> This issue is known by zlib maintainers and is claimed to be harmless,
> but to be on the safe side we'd better initialize the memory.
> 
> Link: https://zlib.net/zlib_faq.html#faq36
> Reported-by: syzbot+14d9e7602ebdf7ec0a60@syzkaller.appspotmail.com
> Signed-off-by: Alexander Potapenko <glider@google.com>

Added to misc-next, thanks.