From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 41824C6FD1B for ; Mon, 6 Mar 2023 17:58:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229841AbjCFR6O (ORCPT ); Mon, 6 Mar 2023 12:58:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50226 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229681AbjCFR5q (ORCPT ); Mon, 6 Mar 2023 12:57:46 -0500 Received: from mail-il1-x147.google.com (mail-il1-x147.google.com [IPv6:2607:f8b0:4864:20::147]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1EC093AA8 for ; Mon, 6 Mar 2023 09:57:12 -0800 (PST) Received: by mail-il1-x147.google.com with SMTP id l1-20020a056e021c0100b003180af2a284so5655017ilh.1 for ; Mon, 06 Mar 2023 09:57:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678125344; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ajIgrIXYqaFuV+qkrohkFZm/iyDUjE1JtksoL40Edr8=; b=NEHrnNGpxXupz9Cn3PRig784jqvhYI1zdJTABWwer81wjkFqYK8QRcY9yoQ82Ow/zA to0p2Sfy9RzBR2BK8ooNDFpKjJC6Ge2oy+rJFtr8Ymalnx3QePvDvN5MpMqRG9yKlPqq KC/o+w00VYhn/8KVl/X20Iesgf2WICU8DZLFD1kK2GaeycUHW0mXuGcYxxsZoCSNI332 2DFkTjZW3KvYwZfGNmftzY1tGacIluYCLfrWjpuK4g4Zeu5KRfOPCWHxYPDDlFrICnNO BulV/xlNGZlFaZsmMnnwy/pH165+ALjC2fLw3LeFjRQtFo3TLoRYJHLfu5Gq5N7tA5IG s3Sg== X-Gm-Message-State: AO0yUKUjXc7FrXDIXT05gqfgKQ/QfehwrD9HEZ71zsjvK80hEpj7HeWG E8kzwKvxYjYqLgbOYVOzKuKelv6TQYAUIg+gPnd9+lbnTmHw X-Google-Smtp-Source: AK7set/tVa2eFCnqZ7AxHXgrzSAqK70ywkfBJxDJ8r95AB8bn4c3lbG50ffdVmngxkFuRceyPo8k0mDKIlSb1o2k0s6VoHeOtt+a MIME-Version: 1.0 X-Received: by 2002:a02:952e:0:b0:3c4:e84b:2a3a with SMTP id y43-20020a02952e000000b003c4e84b2a3amr5913375jah.4.1678125344581; Mon, 06 Mar 2023 09:55:44 -0800 (PST) Date: Mon, 06 Mar 2023 09:55:44 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000000d710705f63f014c@google.com> Subject: [syzbot] [nilfs?] KMSAN: uninit-value in nilfs_add_checksums_on_logs From: syzbot To: glider@google.com, konishi.ryusuke@gmail.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 54b4a7d3d6c6 kmsan: add memsetXX tests git tree: https://github.com/google/kmsan.git master console output: https://syzkaller.appspot.com/x/log.txt?x=143f81e4c80000 kernel config: https://syzkaller.appspot.com/x/.config?x=46c642641b9ef616 dashboard link: https://syzkaller.appspot.com/bug?extid=048585f3f4227bb2b49b 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/b2a457fb4580/disk-54b4a7d3.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/1acddc397ddb/vmlinux-54b4a7d3.xz kernel image: https://storage.googleapis.com/syzbot-assets/eceee3367163/bzImage-54b4a7d3.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+048585f3f4227bb2b49b@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 crc32_le_base+0x446/0xd80 lib/crc32.c:197 crc32_body lib/crc32.c:110 [inline] crc32_le_generic lib/crc32.c:179 [inline] crc32_le_base+0x446/0xd80 lib/crc32.c:197 nilfs_segbuf_fill_in_segsum_crc fs/nilfs2/segbuf.c:182 [inline] nilfs_add_checksums_on_logs+0x2ce/0xe30 fs/nilfs2/segbuf.c:320 nilfs_segctor_do_construct+0xa553/0xe900 fs/nilfs2/segment.c:2076 nilfs_segctor_construct+0x1eb/0xe30 fs/nilfs2/segment.c:2379 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline] nilfs_segctor_thread+0xc76/0x1240 fs/nilfs2/segment.c:2570 kthread+0x31f/0x430 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 Uninit was stored to memory at: nilfs_write_dat_node_binfo+0x12c/0x280 fs/nilfs2/segment.c:658 nilfs_segctor_assign fs/nilfs2/segment.c:1629 [inline] nilfs_segctor_do_construct+0x753c/0xe900 fs/nilfs2/segment.c:2056 nilfs_segctor_construct+0x1eb/0xe30 fs/nilfs2/segment.c:2379 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline] nilfs_segctor_thread+0xc76/0x1240 fs/nilfs2/segment.c:2570 kthread+0x31f/0x430 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 Local variable binfo.i.i created at: nilfs_segctor_update_payload_blocknr fs/nilfs2/segment.c:1562 [inline] nilfs_segctor_assign fs/nilfs2/segment.c:1629 [inline] nilfs_segctor_do_construct+0x6ac9/0xe900 fs/nilfs2/segment.c:2056 nilfs_segctor_construct+0x1eb/0xe30 fs/nilfs2/segment.c:2379 CPU: 1 PID: 28393 Comm: segctord Not tainted 6.2.0-syzkaller-81157-g54b4a7d3d6c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/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.