From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io1-f77.google.com (mail-io1-f77.google.com [209.85.166.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D2D532BAF7 for ; Thu, 30 Oct 2025 22:34:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.77 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761863673; cv=none; b=bIKEbxXFpnpGtsddfDDOqQkzhNEfL24HKpDhkIYBXLv/ZSuxrOKml4tBPmXqTb69mE3u4TTlkE2OYk/B716ctH0OU1qnDPLK3kmGYPQ4IvnKcUWlfhbR4dH3NiSWV9PDFJgBHEkhkprk2ocuO9s8HlxC66qmAmUPOxhFk96kpcc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761863673; c=relaxed/simple; bh=PDG+4R0bR+zUy5rnRXrobvWRNhVRznZikV2XejgbQgQ=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=TIR6fpw7cum9scGvwrY6IxthwhZE4MyoBb7zgVkB4ZD1epYBuMzthe8Hv6fW3VXVx8OnWR47i8SY1cVwlHVYN0PavPRYiKWwGT2b9yaEVBXIS1pTwxHeNBHvE5CERSFkP1sVlKNTHdh5ZV6IZm4K1VfVrHbpg3jrYkJXTayorLk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.166.77 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-io1-f77.google.com with SMTP id ca18e2360f4ac-93e8db8badeso186473539f.3 for ; Thu, 30 Oct 2025 15:34:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761863671; x=1762468471; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=NIZ0Uu9MMshqp8xzh1+njbzcONq0p2voF8lI6LDP9wQ=; b=qehuggLcWvWlI0UyPVD4zScVeDYrpsc2UmnLet6YLOU2gxXbREUAKtnkMRkYZW0mc8 jJW84wPTDAw1jQJSgfbU1KkU1LR77+W3aliCYeiKHq3ta0BU1DwW2mue3aehbkgUvwn3 U0/v8ZrM3LSCOPgtA9i29af15m2PgnL329GeObixkMpOjU9UCEv5LX7H/eGkBDTFLCXD 3Uimff7Ha8oIw6Y62Lqsa9HrO7GlwvhkNaAqKBCYy3YNYYSk2ckAAUPdATTxJYTMtFrl ghTZ5i1cDHAznL+oyniYsI4pucHtUtIHQlua8cXWPAe+ndCzcJqX96VLotD45bRsNJeB CICQ== X-Forwarded-Encrypted: i=1; AJvYcCVC9S3ceBRl9YfoWJHRLxUuo2yAqUTG08v7MfsZjEx+0I+jWptVJsz1iyuUfa6+b/n+NUrGWB4PfnFau1Q=@vger.kernel.org X-Gm-Message-State: AOJu0YxCz2pI8NJ7E0qeL0gTJjmmGQD6hnS3jfBtWh+jVh2LoiCr2YJQ yMYcq5e/Qhsc31MFV7VBO4+GxIfb41WQnY3a+Up6KjG44YAE3qt1emWxFiTGh9owvuTSUix+nUO ZF12jRThkajYUyLTu1nMwrenpgmuVT2xqHHn73MvQV/4CO4MGr9e70O0em4M= X-Google-Smtp-Source: AGHT+IH8rbugZWseHZZude7SAZ+heAK7OUOj2rQDiXnDpnCyUA5qZGMVwJZAbrfFjmu+Ri0uTlGgSp3G2WYaQNW18sOVlKyezB3A Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1447:b0:430:b59b:5f2b with SMTP id e9e14a558f8ab-4330d1bec10mr20376375ab.16.1761863671070; Thu, 30 Oct 2025 15:34:31 -0700 (PDT) Date: Thu, 30 Oct 2025 15:34:31 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6903e7f7.050a0220.3344a1.044c.GAE@google.com> Subject: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2) From: syzbot To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, tytso@mit.edu Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: e53642b87a4f Merge tag 'v6.18-rc3-smb-server-fixes' of git.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=150aa32f980000 kernel config: https://syzkaller.appspot.com/x/.config?x=929790bc044e87d7 dashboard link: https://syzkaller.appspot.com/bug?extid=76916a45d2294b551fd9 compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101f5f34580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=121dbe7c580000 Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-e53642b8.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/bb13d82854da/vmlinux-e53642b8.xz kernel image: https://storage.googleapis.com/syzbot-assets/f3a72d29f243/bzImage-e53642b8.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/fb4c6b817064/mount_0.gz fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=16191fe2580000) IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+76916a45d2294b551fd9@syzkaller.appspotmail.com EXT4-fs warning (device loop0): ext4_xattr_inode_get:546: inode #11: comm syz.0.17: ea_inode file size=0 entry size=6 EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2853: Unable to expand inode 15. Delete some EAs or run e2fsck. ------------[ cut here ]------------ EA inode 11 i_nlink=2 WARNING: CPU: 0 PID: 5496 at fs/ext4/xattr.c:1058 ext4_xattr_inode_update_ref+0x51a/0x5b0 fs/ext4/xattr.c:1056 Modules linked in: CPU: 0 UID: 0 PID: 5496 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:ext4_xattr_inode_update_ref+0x51a/0x5b0 fs/ext4/xattr.c:1056 Code: 48 b8 00 00 00 00 00 fc ff df 41 0f b6 04 06 84 c0 0f 85 80 00 00 00 41 8b 17 48 c7 c7 80 1f 80 8b 4c 89 e6 e8 a7 1b f8 fe 90 <0f> 0b 90 90 4c 8b 6c 24 28 e9 59 fe ff ff e8 f3 0b bd 08 44 89 f9 RSP: 0018:ffffc90002847240 EFLAGS: 00010246 RAX: 96417f00249f1400 RBX: 0000000000000001 RCX: ffff88801f648000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002 RBP: ffffc90002847330 R08: ffff88801fe24293 R09: 1ffff11003fc4852 R10: dffffc0000000000 R11: ffffed1003fc4853 R12: 000000000000000b R13: ffff8880121df630 R14: 1ffff1100243beb4 R15: ffff8880121df5a0 FS: 000055557b2d3500(0000) GS:ffff88808d733000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fd0e033d000 CR3: 000000004bac3000 CR4: 0000000000352ef0 Call Trace: ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1081 [inline] ext4_xattr_inode_dec_ref_all+0x867/0xda0 fs/ext4/xattr.c:1223 ext4_xattr_delete_inode+0xa4c/0xc10 fs/ext4/xattr.c:2947 ext4_evict_inode+0xac9/0xee0 fs/ext4/inode.c:271 evict+0x504/0x9c0 fs/inode.c:810 ext4_orphan_cleanup+0xc20/0x1460 fs/ext4/orphan.c:470 __ext4_fill_super fs/ext4/super.c:5617 [inline] ext4_fill_super+0x5920/0x61e0 fs/ext4/super.c:5736 get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1691 vfs_get_tree+0x92/0x2b0 fs/super.c:1751 fc_mount fs/namespace.c:1208 [inline] do_new_mount_fc fs/namespace.c:3651 [inline] do_new_mount+0x302/0xa10 fs/namespace.c:3727 do_mount fs/namespace.c:4050 [inline] __do_sys_mount fs/namespace.c:4238 [inline] __se_sys_mount+0x313/0x410 fs/namespace.c:4215 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f9e5239076a Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffd45601928 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007ffd456019b0 RCX: 00007f9e5239076a RDX: 0000200000000180 RSI: 00002000000001c0 RDI: 00007ffd45601970 RBP: 0000200000000180 R08: 00007ffd456019b0 R09: 0000000000800700 R10: 0000000000800700 R11: 0000000000000246 R12: 00002000000001c0 R13: 00007ffd45601970 R14: 000000000000046c R15: 0000200000000680 --- 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 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