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 57575C43217 for ; Thu, 1 Dec 2022 12:49:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231153AbiLAMts (ORCPT ); Thu, 1 Dec 2022 07:49:48 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33264 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230208AbiLAMtm (ORCPT ); Thu, 1 Dec 2022 07:49:42 -0500 Received: from mail-io1-f69.google.com (mail-io1-f69.google.com [209.85.166.69]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 183AC92081 for ; Thu, 1 Dec 2022 04:49:41 -0800 (PST) Received: by mail-io1-f69.google.com with SMTP id c20-20020a5d9754000000b006dbd4e6a5abso1456508ioo.17 for ; Thu, 01 Dec 2022 04:49:41 -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=8IHSWu8cpROGIek2vroiLGwTRbK0xKUT/twwPlglJnA=; b=vKrwoteYvt1mcWt0ZpY4em8o1HWI7r93IQEJ+QEUn+sPuJJqar9HfISMPG04hKLoO/ od3NzF3i8tPLo28PBDULvjAmY3MgZ+6djRD1fdC/iagx7OSzwoHOYEWGglpUUUCkaPeY odjMEA/dUNeAHW6BCgtciVBszg5+6WS1u0JehduZvTcIYqgyzkmY8JfHMD2DPKGqTAM0 2deR8F17FaBj3ErQl6oeK4XdBH7nRwLMK8Wl+DW0KBZ5cWDfuTRE3TxJ0/FLevCPq+BD E0EEZBNZVPUHbAKOwFTOR4ksqxMzdrU5KA5zGA+frakCH7USJmd56qrWxid+kZ5jyrLB xxIg== X-Gm-Message-State: ANoB5pl2z1y3M2r04iZeggNcLgcrjU44ty5dPZqxxu1LK0n32Ta2DytK 1RPT0axhYlKYP+7uXMHBCBCdR5Aw7G7VANTPkSiQCC3Bes77 X-Google-Smtp-Source: AA0mqf6JbipCj5IoGcHzLZjfU923ilDwvC/rACUt+vw2J+y1KJ4Qt1F874qk1U3uBoLQWzZJVSQxa8hkRFn26Ld1oDoahWmOIOSG MIME-Version: 1.0 X-Received: by 2002:a05:6638:346:b0:388:9146:8361 with SMTP id x6-20020a056638034600b0038891468361mr17144222jap.19.1669898980456; Thu, 01 Dec 2022 04:49:40 -0800 (PST) Date: Thu, 01 Dec 2022 04:49:40 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000008a836b05eec3a7e9@google.com> Subject: [syzbot] WARNING in hfsplus_cat_read_inode From: syzbot To: damien.lemoal@opensource.wdc.com, jlayton@kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, willy@infradead.org 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: cdb931b58ff5 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=1672f7fd880000 kernel config: https://syzkaller.appspot.com/x/.config?x=ec7118319bfb771e dashboard link: https://syzkaller.appspot.com/bug?extid=e2787430e752a92b8750 compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=120b96a7880000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=116da6bd880000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/07e4eae17e60/disk-cdb931b5.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/fc4815dd00c0/vmlinux-cdb931b5.xz kernel image: https://storage.googleapis.com/syzbot-assets/0f46b40f30e1/Image-cdb931b5.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/3082309c63cc/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+e2787430e752a92b8750@syzkaller.appspotmail.com loop0: detected capacity change from 0 to 1024 ------------[ cut here ]------------ WARNING: CPU: 0 PID: 3073 at fs/hfsplus/inode.c:534 hfsplus_cat_read_inode+0x32c/0x338 fs/hfsplus/inode.c:534 Modules linked in: CPU: 0 PID: 3073 Comm: syz-executor278 Not tainted 6.1.0-rc7-syzkaller-33054-gcdb931b58ff5 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022 pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : hfsplus_cat_read_inode+0x32c/0x338 fs/hfsplus/inode.c:534 lr : hfsplus_cat_read_inode+0x32c/0x338 fs/hfsplus/inode.c:534 sp : ffff80000ff23640 x29: ffff80000ff23850 x28: ffff0000c23a0000 x27: 000000000000000b x26: ffff0000c9e92000 x25: 00000000000000ff x24: ffff0000cbd81530 x23: ffff0000c7bffdf0 x22: ffff0000c7bffd30 x21: 0000000000000058 x20: ffff80000ff23880 x19: ffff0000cbd81bb0 x18: 00000000000000c0 x17: ffff80000dda8198 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000000 x13: 0000000000000002 x12: ffff80000d514f80 x11: ff808000088e828c x10: 0000000000000000 x9 : ffff8000088e828c x8 : ffff0000c23a0000 x7 : 0000000000000000 x6 : 0000000000000000 x5 : ffff80000ff235f6 x4 : ffff0001803f7028 x3 : 0000000000000000 x2 : 0000000000000002 x1 : 0000000000000058 x0 : 00000000000000f8 Call trace: hfsplus_cat_read_inode+0x32c/0x338 fs/hfsplus/inode.c:534 hfsplus_iget+0x244/0x2ac fs/hfsplus/super.c:84 hfsplus_fill_super+0x480/0x864 fs/hfsplus/super.c:503 mount_bdev+0x1b8/0x210 fs/super.c:1401 hfsplus_mount+0x44/0x58 fs/hfsplus/super.c:641 legacy_get_tree+0x30/0x74 fs/fs_context.c:610 vfs_get_tree+0x40/0x140 fs/super.c:1531 do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040 path_mount+0x358/0x890 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __arm64_sys_mount+0x2c4/0x3c4 fs/namespace.c:3568 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall arch/arm64/kernel/syscall.c:52 [inline] el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x140 arch/arm64/kernel/syscall.c:197 el0_svc+0x58/0x150 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:584 irq event stamp: 15818 hardirqs last enabled at (15817): [] __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline] hardirqs last enabled at (15817): [] _raw_spin_unlock_irqrestore+0x48/0x8c kernel/locking/spinlock.c:194 hardirqs last disabled at (15818): [] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405 softirqs last enabled at (15354): [] _stext+0x2e4/0x37c softirqs last disabled at (15241): [] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:80 ---[ end trace 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. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches