diff options
| author | Alexander Potapenko <glider@google.com> | 2023-01-24 12:32:34 +0100 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2023-01-25 20:11:08 +0100 |
| commit | eadd7deca0ad8a83edb2b894d8326c78e78635d6 (patch) | |
| tree | f3d82662280e14ea01344621901292fd3974c1b8 /fs/btrfs/send.c | |
| parent | 3c538de0f2a74d50aff7278c092f88ae59cee688 (diff) | |
btrfs: zlib: zero-initialize zlib workspace
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
CC: stable@vger.kernel.org # 5.4+
Signed-off-by: Alexander Potapenko <glider@google.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/send.c')
0 files changed, 0 insertions, 0 deletions