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 AB74AC4167B for ; Sun, 10 Dec 2023 06:40:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231528AbjLJGkT (ORCPT ); Sun, 10 Dec 2023 01:40:19 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37648 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231549AbjLJGkQ (ORCPT ); Sun, 10 Dec 2023 01:40:16 -0500 Received: from mail-oa1-f69.google.com (mail-oa1-f69.google.com [209.85.160.69]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 93FF811F for ; Sat, 9 Dec 2023 22:40:21 -0800 (PST) Received: by mail-oa1-f69.google.com with SMTP id 586e51a60fabf-1fb2132b0edso6430267fac.2 for ; Sat, 09 Dec 2023 22:40:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702190421; x=1702795221; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=xFFwRy2N/0G7JtfDFizFJ6sDME0Agg87dHPC6Ukv4hA=; b=SfQ40carWVjYQxX75Mhobwl+koA5nR71YeeLx6DRXbGORmX3J1f5kSeteFfq0r1/Jq uUnxj5vuyH44Sqi74NIgTRHILsYFqvpDzhyo2TYWKj0GdU3n6PizSz4XrpP2Dand8O03 /+zh1d7vg/5l/+zc2HANlUfw8JehuBh2dPFxYoTE2FGxnc05ndhTBsSP24CzGAEPX1gd JQTMF84gJQflvPoklqOTKUqubNEb38fHAQP6/pVlNKZjuMT2+rnllU3ql5x5AGHsvUBJ Lg+QtTfO/U+SyjH5mCQq1ixAxZ7XDLUlqyeY+Le7mvPiQq9Y8Zg6mXsduk2JXKuIosKE fa3Q== X-Gm-Message-State: AOJu0YySzAbdcUwf6CLF47tPti0F4u5jucizSY+iDkOPgRy2P8lmWfFg iqxmxCCqazssRagfRHuOzILLT4yRbq5Ua4RvPtRmJkQRs8hp X-Google-Smtp-Source: AGHT+IGCIyoxMIK1pCg+Sf7WO5ZlCiJNt87mIJLCEcZMeArss0IgicVboiTl5pslJEOrUZg0to1SjbN+qQuRVEqyia8ytryejc1/ MIME-Version: 1.0 X-Received: by 2002:a05:6871:5214:b0:1fa:f432:231 with SMTP id ht20-20020a056871521400b001faf4320231mr3318822oac.3.1702190421024; Sat, 09 Dec 2023 22:40:21 -0800 (PST) Date: Sat, 09 Dec 2023 22:40:20 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000062a4cc060c2217de@google.com> Subject: [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in diNewExt From: syzbot To: jfs-discussion@lists.sourceforge.net, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, shaggy@kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: bee0e7762ad2 Merge tag 'for-linus-iommufd' of git://git.ke.. git tree: upstream console+strace: https://syzkaller.appspot.com/x/log.txt?x=1088351ce80000 kernel config: https://syzkaller.appspot.com/x/.config?x=b45dfd882e46ec91 dashboard link: https://syzkaller.appspot.com/bug?extid=553d90297e6d2f50dbc7 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=122acc3ce80000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=110a49b4e80000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/af357ba4767f/disk-bee0e776.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/ae4d50206171/vmlinux-bee0e776.xz kernel image: https://storage.googleapis.com/syzbot-assets/e12203376a9f/bzImage-bee0e776.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/d8974c833f6f/mount_0.gz Bisection is inconclusive: the issue happens on the oldest tested release. bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=133caf54e80000 final oops: https://syzkaller.appspot.com/x/report.txt?x=10bcaf54e80000 console output: https://syzkaller.appspot.com/x/log.txt?x=173caf54e80000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+553d90297e6d2f50dbc7@syzkaller.appspotmail.com loop0: detected capacity change from 0 to 32768 ================================================================================ UBSAN: array-index-out-of-bounds in fs/jfs/jfs_imap.c:2360:2 index -878706688 is out of range for type 'struct iagctl[128]' CPU: 1 PID: 5065 Comm: syz-executor282 Not tainted 6.7.0-rc4-syzkaller-00009-gbee0e7762ad2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:217 [inline] __ubsan_handle_out_of_bounds+0x11c/0x150 lib/ubsan.c:348 diNewExt+0x3cf3/0x4000 fs/jfs/jfs_imap.c:2360 diAllocExt fs/jfs/jfs_imap.c:1949 [inline] diAllocAG+0xbe8/0x1e50 fs/jfs/jfs_imap.c:1666 diAlloc+0x1d3/0x1760 fs/jfs/jfs_imap.c:1587 ialloc+0x8f/0x900 fs/jfs/jfs_inode.c:56 jfs_mkdir+0x1c5/0xb90 fs/jfs/namei.c:225 vfs_mkdir+0x2f1/0x4b0 fs/namei.c:4106 do_mkdirat+0x264/0x3a0 fs/namei.c:4129 __do_sys_mkdir fs/namei.c:4149 [inline] __se_sys_mkdir fs/namei.c:4147 [inline] __x64_sys_mkdir+0x6e/0x80 fs/namei.c:4147 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x45/0x110 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x63/0x6b RIP: 0033:0x7fcb7e6a0b57 Code: ff ff 77 07 31 c0 c3 0f 1f 40 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 b8 53 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffd83023038 EFLAGS: 00000286 ORIG_RAX: 0000000000000053 RAX: ffffffffffffffda RBX: 00000000ffffffff RCX: 00007fcb7e6a0b57 RDX: 00000000000a1020 RSI: 00000000000001ff RDI: 0000000020000140 RBP: 0000000020000140 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000286 R12: 00007ffd830230d0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 ================================================================================ --- 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. For information about bisection process see: https://goo.gl/tpsmEJ#bisection If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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