[syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (4)

* [syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (4)
@ 2024-04-01 21:52 syzbot
  2024-04-03  9:39 ` Herbert Xu
  2024-05-09  7:22 ` [syzbot] [btrfs] " syzbot
  0 siblings, 2 replies; 3+ messages in thread
From: syzbot @ 2024-04-01 21:52 UTC (permalink / raw)
  To: davem, herbert, linux-crypto, linux-kernel, syzkaller-bugs

Hello,

syzbot found the following issue on:

HEAD commit:    8d025e2092e2 Merge tag 'erofs-for-6.9-rc2-fixes' of git://..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1385be41180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e2599baf258ef795
dashboard link: https://syzkaller.appspot.com/bug?extid=549710bad9c798e25b15
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5ccde1a19e22/disk-8d025e20.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/45420817e7d9/vmlinux-8d025e20.xz
kernel image: https://storage.googleapis.com/syzbot-assets/354bdafd8c8f/bzImage-8d025e20.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+549710bad9c798e25b15@syzkaller.appspotmail.com

=====================================================
BUG: KMSAN: uninit-value in crc32_body lib/crc32.c:110 [inline]
BUG: KMSAN: uninit-value in crc32_le_generic lib/crc32.c:179 [inline]
BUG: KMSAN: uninit-value in __crc32c_le_base+0x43c/0xd80 lib/crc32.c:201
 crc32_body lib/crc32.c:110 [inline]
 crc32_le_generic lib/crc32.c:179 [inline]
 __crc32c_le_base+0x43c/0xd80 lib/crc32.c:201
 chksum_update+0x5b/0xd0 crypto/crc32c_generic.c:88
 crypto_shash_update+0x79/0xa0 crypto/shash.c:70
 csum_tree_block+0x35f/0x5d0 fs/btrfs/disk-io.c:96
 btree_csum_one_bio+0x4d5/0xeb0 fs/btrfs/disk-io.c:294
 btrfs_bio_csum fs/btrfs/bio.c:538 [inline]
 btrfs_submit_chunk fs/btrfs/bio.c:741 [inline]
 btrfs_submit_bio+0x1eb6/0x2930 fs/btrfs/bio.c:770
 write_one_eb+0x13fa/0x1570 fs/btrfs/extent_io.c:1750
 submit_eb_page fs/btrfs/extent_io.c:1909 [inline]
 btree_write_cache_pages+0x1d2a/0x29a0 fs/btrfs/extent_io.c:1959
 btree_writepages+0x84/0x270 fs/btrfs/disk-io.c:516
 do_writepages+0x427/0xc30 mm/page-writeback.c:2612
 filemap_fdatawrite_wbc+0x1d8/0x270 mm/filemap.c:397
 __filemap_fdatawrite_range mm/filemap.c:430 [inline]
 filemap_fdatawrite_range+0xe1/0x110 mm/filemap.c:448
 btrfs_write_marked_extents+0x2e7/0x620 fs/btrfs/transaction.c:1154
 btrfs_sync_log+0x9fd/0x3830 fs/btrfs/tree-log.c:2969
 btrfs_sync_file+0x144c/0x1c60 fs/btrfs/file.c:1968
 vfs_fsync_range+0x20d/0x270 fs/sync.c:188
 generic_write_sync include/linux/fs.h:2793 [inline]
 btrfs_do_write_iter+0x1c5f/0x2270 fs/btrfs/file.c:1695
 btrfs_file_write_iter+0x38/0x50 fs/btrfs/file.c:1705
 call_write_iter include/linux/fs.h:2108 [inline]
 new_sync_write fs/read_write.c:497 [inline]
 vfs_write+0xb63/0x1520 fs/read_write.c:590
 ksys_write+0x20f/0x4c0 fs/read_write.c:643
 __do_sys_write fs/read_write.c:655 [inline]
 __se_sys_write fs/read_write.c:652 [inline]
 __x64_sys_write+0x93/0xe0 fs/read_write.c:652
 do_syscall_64+0xd5/0x1f0
 entry_SYSCALL_64_after_hwframe+0x6d/0x75

Uninit was created at:
 __alloc_pages+0x9d6/0xe70 mm/page_alloc.c:4598
 __alloc_pages_bulk+0x19e/0x21e0 mm/page_alloc.c:4523
 alloc_pages_bulk_array include/linux/gfp.h:202 [inline]
 btrfs_alloc_page_array+0x9e/0x460 fs/btrfs/extent_io.c:689
 alloc_eb_folio_array fs/btrfs/extent_io.c:724 [inline]
 alloc_extent_buffer+0xa68/0x4180 fs/btrfs/extent_io.c:3859
 btrfs_find_create_tree_block+0x46/0x60 fs/btrfs/disk-io.c:610
 btrfs_init_new_buffer fs/btrfs/extent-tree.c:5063 [inline]
 btrfs_alloc_tree_block+0x35c/0x17c0 fs/btrfs/extent-tree.c:5178
 btrfs_alloc_log_tree_node fs/btrfs/disk-io.c:960 [inline]
 btrfs_add_log_tree+0x1b7/0x7a0 fs/btrfs/disk-io.c:1008
 start_log_trans fs/btrfs/tree-log.c:208 [inline]
 btrfs_log_inode_parent+0x9b6/0x1dd0 fs/btrfs/tree-log.c:7066
 btrfs_log_dentry_safe+0x9a/0x100 fs/btrfs/tree-log.c:7171
 btrfs_sync_file+0x126c/0x1c60 fs/btrfs/file.c:1933
 vfs_fsync_range+0x20d/0x270 fs/sync.c:188
 generic_write_sync include/linux/fs.h:2793 [inline]
 btrfs_do_write_iter+0x1c5f/0x2270 fs/btrfs/file.c:1695
 btrfs_file_write_iter+0x38/0x50 fs/btrfs/file.c:1705
 call_write_iter include/linux/fs.h:2108 [inline]
 new_sync_write fs/read_write.c:497 [inline]
 vfs_write+0xb63/0x1520 fs/read_write.c:590
 ksys_write+0x20f/0x4c0 fs/read_write.c:643
 __do_sys_write fs/read_write.c:655 [inline]
 __se_sys_write fs/read_write.c:652 [inline]
 __x64_sys_write+0x93/0xe0 fs/read_write.c:652
 do_syscall_64+0xd5/0x1f0
 entry_SYSCALL_64_after_hwframe+0x6d/0x75

CPU: 1 PID: 5344 Comm: syz-executor.4 Not tainted 6.9.0-rc1-syzkaller-00061-g8d025e2092e2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
=====================================================

---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

^ permalink raw reply	[flat|nested] 3+ messages in thread