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 854A2CD13D8 for ; Mon, 18 Sep 2023 18:15:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229558AbjIRSPM (ORCPT ); Mon, 18 Sep 2023 14:15:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48662 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229454AbjIRSPK (ORCPT ); Mon, 18 Sep 2023 14:15:10 -0400 Received: from mail-oi1-f205.google.com (mail-oi1-f205.google.com [209.85.167.205]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CF653FD for ; Mon, 18 Sep 2023 11:15:03 -0700 (PDT) Received: by mail-oi1-f205.google.com with SMTP id 5614622812f47-3a9f2f6d356so7755660b6e.2 for ; Mon, 18 Sep 2023 11:15:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695060903; x=1695665703; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=/Pj2gflzChdTjSILey0wOqNwEyneT96tigxwfb0NNcI=; b=Ux0a/IN+YLHI1J3pjIq7upI22WvROoXQEnAm1MkHCiebBdP7h1nO4kCUNcHFCDFnk/ 9X/5AFvEF55kxxkuJu3yBhE/uP53CEtE8TizlMhoDSsnbCHISRvnWxaA5xcU8gBnz4Sn zMvcinfdD6s5CHtgnwzoragYHTPkFkkSn8b0h4CAydPYRXWm2iDIea27HylS/FKM7oYv a17SGbaIMJfkRhbOl6LvAAWGcuN+z5QOaG7SHeO8bYKVWLkMQr6t2DaJHhr5pZN/S5/5 Sp4em3/1BTgAeqOn+Ww6/Dbsiu93B3I1H49zal9FEvbNlN5fJCtdHJMxKVInVIVf4kGp 0vWA== X-Gm-Message-State: AOJu0YzW1PEmJq+ymwSToMFoqdwGm1ejMsAdynBtievLk/asOBQtYBgE 0C2lcSBtW0IqPQqOa6/Aiw9FHSVI4VTZ/EdR3uMCmhFkpTj6 X-Google-Smtp-Source: AGHT+IH/KlrUDvkFgo9hFBpByYArzSmPKdxJWL6YyFOfonnFx5CNvuIiVHkGgxAVgWkj2bXY1b+CLP8xf3F5PvfGjymwPk5ETPHG MIME-Version: 1.0 X-Received: by 2002:a05:6808:13c6:b0:3a8:42ec:53b with SMTP id d6-20020a05680813c600b003a842ec053bmr4399697oiw.3.1695060903158; Mon, 18 Sep 2023 11:15:03 -0700 (PDT) Date: Mon, 18 Sep 2023 11:15:03 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000001752e0605a61fd8@google.com> Subject: [syzbot] [jfs?] UBSAN: shift-out-of-bounds in dbAlloc (2) 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: aed8aee11130 Merge tag 'pmdomain-v6.6-rc1' of git://git.ke.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14eb20c4680000 kernel config: https://syzkaller.appspot.com/x/.config?x=f4894cf58531f dashboard link: https://syzkaller.appspot.com/bug?extid=debee9ab7ae2b34b0307 compiler: gcc (Debian 12.2.0-14) 12.2.0, 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/1e8c59eb8bd1/disk-aed8aee1.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/edab4b80fc33/vmlinux-aed8aee1.xz kernel image: https://storage.googleapis.com/syzbot-assets/0b280af46d8f/bzImage-aed8aee1.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+debee9ab7ae2b34b0307@syzkaller.appspotmail.com loop3: detected capacity change from 0 to 32768 ================================================================================ UBSAN: shift-out-of-bounds in fs/jfs/jfs_dmap.c:799:12 shift exponent -16777216 is negative CPU: 1 PID: 16087 Comm: syz-executor.3 Not tainted 6.6.0-rc1-syzkaller-00072-gaed8aee11130 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x125/0x1b0 lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:217 [inline] __ubsan_handle_shift_out_of_bounds+0x27a/0x600 lib/ubsan.c:387 dbAlloc.cold+0x33/0x38 fs/jfs/jfs_dmap.c:799 diNewExt+0x736/0x1a70 fs/jfs/jfs_imap.c:2252 diAllocExt fs/jfs/jfs_imap.c:1946 [inline] diAllocAG+0x1707/0x2330 fs/jfs/jfs_imap.c:1663 diAlloc+0x893/0x1a00 fs/jfs/jfs_imap.c:1584 ialloc+0x8e/0xa70 fs/jfs/jfs_inode.c:56 jfs_mkdir+0x240/0xb00 fs/jfs/namei.c:225 vfs_mkdir+0x532/0x7e0 fs/namei.c:4120 do_mkdirat+0x2a9/0x330 fs/namei.c:4143 __do_sys_mkdirat fs/namei.c:4158 [inline] __se_sys_mkdirat fs/namei.c:4156 [inline] __x64_sys_mkdirat+0x115/0x170 fs/namei.c:4156 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fe9b047b5e7 Code: 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 02 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fe9b124eee8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe9b047b5e7 RDX: 00000000000001ff RSI: 00000000200016c0 RDI: 00000000ffffff9c RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00000000200016c0 R13: 00007fe9b124ef40 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. If the bug is already fixed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite 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