All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a6d6b8fffa294705dbd8@syzkaller.appspotmail.com>
To: davem@davemloft.net, glider@google.com,
	herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (3)
Date: Thu, 27 Apr 2023 13:50:49 -0700	[thread overview]
Message-ID: <000000000000f66a3005fa578223@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    81af97bdef5e printk: Export console trace point for kcsan/..
git tree:       https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=178eaf77c80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=60f9227cd7ef4e36
dashboard link: https://syzkaller.appspot.com/bug?extid=a6d6b8fffa294705dbd8
compiler:       Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/959cdbc34509/disk-81af97bd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/21bf12585d87/vmlinux-81af97bd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d46348c365bd/bzImage-81af97bd.xz

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

XFS: attr2 mount option is deprecated.
XFS (loop3): Mounting V5 Filesystem a2f82aab-77f8-4286-afd4-a8f747a74bab
XFS (loop3): Ending clean mount
XFS (loop3): Quotacheck needed: Please wait.
=====================================================
BUG: KMSAN: uninit-value in crc32_body lib/crc32.c:112 [inline]
BUG: KMSAN: uninit-value in crc32_le_generic lib/crc32.c:179 [inline]
BUG: KMSAN: uninit-value in __crc32c_le_base+0x467/0xd80 lib/crc32.c:201
 crc32_body lib/crc32.c:112 [inline]
 crc32_le_generic lib/crc32.c:179 [inline]
 __crc32c_le_base+0x467/0xd80 lib/crc32.c:201
 chksum_update+0x5b/0xd0 crypto/crc32c_generic.c:88
 crypto_shash_update+0x28f/0x400 crypto/shash.c:121
 crc32c+0xd9/0x1a0 lib/libcrc32c.c:47
 xlog_cksum fs/xfs/xfs_log.c:1867 [inline]
 xlog_sync+0xf66/0x11e0 fs/xfs/xfs_log.c:2111
 xlog_state_release_iclog+0x3d0/0x7e0 fs/xfs/xfs_log.c:619
 xlog_force_iclog fs/xfs/xfs_log.c:888 [inline]
 xlog_force_and_check_iclog fs/xfs/xfs_log.c:3172 [inline]
 xfs_log_force+0x9d3/0xf20 fs/xfs/xfs_log.c:3249
 xfs_qm_dqflush+0x11d9/0x17f0 fs/xfs/xfs_dquot.c:1293
 xfs_qm_flush_one+0x148/0x5b0 fs/xfs/xfs_qm.c:1260
 xfs_qm_dquot_walk+0x2be/0x7b0 fs/xfs/xfs_qm.c:87
 xfs_qm_quotacheck+0x4e1/0xb20 fs/xfs/xfs_qm.c:1338
 xfs_qm_mount_quotas+0x3ef/0x890 fs/xfs/xfs_qm.c:1457
 xfs_mountfs+0x2184/0x2410 fs/xfs/xfs_mount.c:959
 xfs_fs_fill_super+0x1fb3/0x22b0 fs/xfs/xfs_super.c:1677
 get_tree_bdev+0x890/0xd10 fs/super.c:1303
 xfs_fs_get_tree+0x34/0x40 fs/xfs/xfs_super.c:1724
 vfs_get_tree+0xa5/0x500 fs/super.c:1510
 do_new_mount+0x69a/0x1580 fs/namespace.c:3042
 path_mount+0x725/0x1ee0 fs/namespace.c:3372
 do_mount fs/namespace.c:3385 [inline]
 __do_sys_mount fs/namespace.c:3594 [inline]
 __se_sys_mount+0x734/0x840 fs/namespace.c:3571
 __ia32_sys_mount+0xe3/0x150 fs/namespace.c:3571
 do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]
 __do_fast_syscall_32+0xa2/0x100 arch/x86/entry/common.c:178
 do_fast_syscall_32+0x37/0x80 arch/x86/entry/common.c:203
 do_SYSENTER_32+0x1f/0x30 arch/x86/entry/common.c:246
 entry_SYSENTER_compat_after_hwframe+0x70/0x82

Uninit was stored to memory at:
 xlog_write_iovec fs/xfs/xfs_log.c:2259 [inline]
 xlog_write_full fs/xfs/xfs_log.c:2294 [inline]
 xlog_write+0x1c3c/0x21a0 fs/xfs/xfs_log.c:2563
 xlog_cil_write_chain fs/xfs/xfs_log_cil.c:973 [inline]
 xlog_cil_push_work+0x30c7/0x4430 fs/xfs/xfs_log_cil.c:1318
 process_one_work+0xb0d/0x1410 kernel/workqueue.c:2390
 worker_thread+0x107e/0x1d60 kernel/workqueue.c:2537
 kthread+0x31f/0x430 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308

Uninit was created at:
 slab_post_alloc_hook+0x12d/0xb60 mm/slab.h:774
 slab_alloc_node mm/slub.c:3452 [inline]
 __kmem_cache_alloc_node+0x518/0x920 mm/slub.c:3491
 __do_kmalloc_node mm/slab_common.c:966 [inline]
 __kmalloc+0x121/0x3c0 mm/slab_common.c:980
 kmalloc include/linux/slab.h:584 [inline]
 xlog_kvmalloc fs/xfs/xfs_log_priv.h:700 [inline]
 xlog_cil_alloc_shadow_bufs fs/xfs/xfs_log_cil.c:338 [inline]
 xlog_cil_commit+0x493/0x4c80 fs/xfs/xfs_log_cil.c:1629
 __xfs_trans_commit+0x78e/0x13d0 fs/xfs/xfs_trans.c:1005
 xfs_trans_roll+0x10a/0x6e0 fs/xfs/xfs_trans.c:1153
 xfs_defer_trans_roll+0x10f/0x590 fs/xfs/libxfs/xfs_defer.c:366
 xfs_defer_finish_noroll+0x49d/0x2d40 fs/xfs/libxfs/xfs_defer.c:551
 __xfs_trans_commit+0x979/0x13d0 fs/xfs/xfs_trans.c:970
 xfs_trans_commit+0x2f/0x40 fs/xfs/xfs_trans.c:1049
 xfs_dquot_disk_alloc+0xd4f/0x11a0 fs/xfs/xfs_dquot.c:384
 xfs_qm_dqread+0x149/0x950 fs/xfs/xfs_dquot.c:665
 xfs_qm_dqget+0x32c/0xb40 fs/xfs/xfs_dquot.c:870
 xfs_qm_quotacheck_dqadjust+0xc4/0x860 fs/xfs/xfs_qm.c:1085
 xfs_qm_dqusage_adjust+0x51b/0x910 fs/xfs/xfs_qm.c:1190
 xfs_iwalk_ag_recs+0x5ca/0xa50 fs/xfs/xfs_iwalk.c:220
 xfs_iwalk_run_callbacks+0x27f/0x590 fs/xfs/xfs_iwalk.c:376
 xfs_iwalk_ag+0xee3/0x1080 fs/xfs/xfs_iwalk.c:482
 xfs_iwalk_ag_work+0x207/0x300 fs/xfs/xfs_iwalk.c:624
 xfs_pwork_work+0x97/0x2b0 fs/xfs/xfs_pwork.c:47
 process_one_work+0xb0d/0x1410 kernel/workqueue.c:2390
 worker_thread+0x107e/0x1d60 kernel/workqueue.c:2537
 kthread+0x31f/0x430 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308

CPU: 1 PID: 5349 Comm: syz-executor.3 Not tainted 6.3.0-syzkaller-g81af97bdef5e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
=====================================================


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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

             reply	other threads:[~2023-04-27 20:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27 20:50 syzbot [this message]
2023-12-13 10:49 ` [syzbot] [crypto?] KMSAN: uninit-value in __crc32c_le_base (3) Alexander Potapenko
2023-12-13 10:50   ` Alexander Potapenko
2023-12-13 21:16   ` Dave Chinner
2023-12-13 21:58     ` Dave Chinner
2023-12-14 14:55       ` Alexander Potapenko
2023-12-14 21:39         ` Dave Chinner
2023-12-15 14:41           ` Alexander Potapenko
2023-12-15 21:59             ` Dave Chinner
2023-12-18 10:22               ` Aleksandr Nogikh
2023-12-19 12:41                 ` Dave Chinner
2023-12-19 13:56                   ` Alexander Potapenko
2023-12-19 23:33                     ` Dave Chinner
2024-03-17 23:21 ` [syzbot] " syzbot
  -- strict thread matches above, loose matches on Subject: below --
2023-12-04 12:56 [syzbot] [crypto?] " xingwei lee

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=000000000000f66a3005fa578223@google.com \
    --to=syzbot+a6d6b8fffa294705dbd8@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=glider@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --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.