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 3EAB1C64ED6 for ; Tue, 28 Feb 2023 14:19:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229649AbjB1OTu (ORCPT ); Tue, 28 Feb 2023 09:19:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46430 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229501AbjB1OTt (ORCPT ); Tue, 28 Feb 2023 09:19:49 -0500 Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 16C1424103 for ; Tue, 28 Feb 2023 06:19:47 -0800 (PST) Received: by mail-io1-f70.google.com with SMTP id c13-20020a0566022d0d00b0074cc4ed52d9so5992750iow.18 for ; Tue, 28 Feb 2023 06:19:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=J6I9nx2s7RTfWTlnagZt92XwoQkoLlEorV5GfVg0HLE=; b=3yIUH6Ym1O9n43BDNesrS7Gn1cNIdemaPXPGbrSA3mWpQi8syxjXkzYWk171S1TP8g BnvxTNRFjNP5udiCv3Tvr2Pgczo/8hoNXzwWwD+OisHJ8F8DGPxo4J0eXM/Jy9vuPkS2 YWqvgH0U3TFdjXNnemLr3KhmKkzaCpHuFWsTrwqZ1ALgOWOvpB9yIcwgMcQShbI9+S5X om6amqvOBro5RRiR6IfXK5n2jVXwzzs9YLMx/LQtKF21rBgdYZHn6TVcFToZBmCra/nU p0N4tyca3wjYqtS+jJXtCLi5TQ1FguggMJHhaAvc/nleEeXueAlLb6LauExw7qqbdLWX tO0w== X-Gm-Message-State: AO0yUKXMb008oaiSG+8mjI6g88e8IfS626Es6b8IL0gBuObEeB1MtJxh Dj4BhCA54IlT9XYQQ6mwAqLQU+gREn/G1mYpC4/Lag3rhRaV X-Google-Smtp-Source: AK7set80BgvGPfY0VZVc50EMjNfjx1r+lpseH5pu22IzNmUTBUhber0fCBuJJHCdpw2t1xFRIPl0wI8XeLnKny7oPSOmITR6cbg3 MIME-Version: 1.0 X-Received: by 2002:a02:6244:0:b0:3ad:65e:e489 with SMTP id d65-20020a026244000000b003ad065ee489mr1374385jac.1.1677593986353; Tue, 28 Feb 2023 06:19:46 -0800 (PST) Date: Tue, 28 Feb 2023 06:19:46 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000a24e7405f5c34912@google.com> Subject: [syzbot] [ntfs3?] UBSAN: shift-out-of-bounds in ntfs_fill_super (2) From: syzbot To: almaz.alexandrovich@paragon-software.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, llvm@lists.linux.dev, nathan@kernel.org, ndesaulniers@google.com, ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com, trix@redhat.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: 2ebd1fbb946d Merge branch 'for-next/core' into for-kernelci git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=17f0d518c80000 kernel config: https://syzkaller.appspot.com/x/.config?x=3519974f3f27816d dashboard link: https://syzkaller.appspot.com/bug?extid=478c1bf0e6bf4a8f3a04 compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=165b7474c80000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c9de8cc80000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/16985cc7a274/disk-2ebd1fbb.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/fd3452567115/vmlinux-2ebd1fbb.xz kernel image: https://storage.googleapis.com/syzbot-assets/c75510922212/Image-2ebd1fbb.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/deffedf88bc5/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+478c1bf0e6bf4a8f3a04@syzkaller.appspotmail.com loop0: detected capacity change from 0 to 4096 ================================================================================ UBSAN: shift-out-of-bounds in fs/ntfs3/super.c:777:25 shift exponent 128 is too large for 32-bit type 'unsigned int' CPU: 0 PID: 5928 Comm: syz-executor258 Not tainted 6.2.0-syzkaller-18300-g2ebd1fbb946d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023 Call trace: dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106 dump_stack+0x1c/0x28 lib/dump_stack.c:113 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_shift_out_of_bounds+0x2f4/0x36c lib/ubsan.c:321 ntfs_init_from_boot fs/ntfs3/super.c:777 [inline] ntfs_fill_super+0x2544/0x3b9c fs/ntfs3/super.c:970 get_tree_bdev+0x360/0x54c fs/super.c:1282 ntfs_fs_get_tree+0x28/0x38 fs/ntfs3/super.c:1408 vfs_get_tree+0x90/0x274 fs/super.c:1489 do_new_mount+0x25c/0x8c8 fs/namespace.c:3145 path_mount+0x590/0xe58 fs/namespace.c:3475 do_mount fs/namespace.c:3488 [inline] __do_sys_mount fs/namespace.c:3697 [inline] __se_sys_mount fs/namespace.c:3674 [inline] __arm64_sys_mount+0x45c/0x594 fs/namespace.c:3674 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x198 arch/arm64/kernel/syscall.c:193 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591 ================================================================================ --- 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. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches