All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+0be4f339a8218d2a5bb1@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	tytso@mit.edu
Subject: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref
Date: Wed, 10 Sep 2025 17:08:33 -0700	[thread overview]
Message-ID: <68c21301.050a0220.3c6139.0031.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    9dd1835ecda5 Merge tag 'dma-mapping-6.17-2025-09-09' of gi..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17e0f87c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=429771c55b615e85
dashboard link: https://syzkaller.appspot.com/bug?extid=0be4f339a8218d2a5bb1
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=1617c934580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10eba642580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63dc392685dc/disk-9dd1835e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3dfcfb97806e/vmlinux-9dd1835e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ddb10128aeb8/bzImage-9dd1835e.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/39ec3165daa7/mount_0.gz
  fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=16fecb12580000)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0be4f339a8218d2a5bb1@syzkaller.appspotmail.com

EXT4-fs warning (device loop0): ext4_xattr_inode_get:556: inode #11: comm syz.0.17: EA inode hash validation failed
EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2848: Unable to expand inode 15. Delete some EAs or run e2fsck.
------------[ cut here ]------------
EA inode 11 ref_count=-1
WARNING: CPU: 1 PID: 6111 at fs/ext4/xattr.c:1048 ext4_xattr_inode_update_ref+0x44b/0x5d0 fs/ext4/xattr.c:1047
Modules linked in:
CPU: 1 UID: 0 PID: 6111 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:ext4_xattr_inode_update_ref+0x44b/0x5d0 fs/ext4/xattr.c:1047
Code: 78 40 4c 89 f8 48 c1 e8 03 80 3c 18 00 74 08 4c 89 ff e8 e8 05 a2 ff 49 8b 37 48 c7 c7 20 6d 1f 8b 4c 89 ea e8 06 9b 07 ff 90 <0f> 0b 90 90 48 bb 00 00 00 00 00 fc ff df 4c 8b 74 24 20 4c 8b 6c
RSP: 0018:ffffc90003fef2e0 EFLAGS: 00010246
RAX: c3a43c61d4524a00 RBX: dffffc0000000000 RCX: ffff888056a79dc0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003fef3d0 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed1017124863 R12: ffffc90003fef340
R13: ffffffffffffffff R14: 00000000ffffffff R15: ffff888042eaee10
FS:  0000555558b13500(0000) GS:ffff8881269bf000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f92c9cf3000 CR3: 0000000056d94000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1076 [inline]
 ext4_xattr_inode_dec_ref_all+0x867/0xda0 fs/ext4/xattr.c:1218
 ext4_xattr_delete_inode+0xa4c/0xc10 fs/ext4/xattr.c:2942
 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:474
 __ext4_fill_super fs/ext4/super.c:5609 [inline]
 ext4_fill_super+0x57fa/0x60b0 fs/ext4/super.c:5728
 get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1692
 vfs_get_tree+0x8f/0x2b0 fs/super.c:1815
 do_new_mount+0x2a2/0x9e0 fs/namespace.c:3808
 do_mount fs/namespace.c:4136 [inline]
 __do_sys_mount fs/namespace.c:4347 [inline]
 __se_sys_mount+0x317/0x410 fs/namespace.c:4324
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f07d069034a
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:00007ffeedf2c668 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffeedf2c6f0 RCX: 00007f07d069034a
RDX: 0000200000000180 RSI: 00002000000001c0 RDI: 00007ffeedf2c6b0
RBP: 0000200000000180 R08: 00007ffeedf2c6f0 R09: 000000000080078b
R10: 000000000080078b R11: 0000000000000246 R12: 00002000000001c0
R13: 00007ffeedf2c6b0 R14: 0000000000000473 R15: 0000200000000680
 </TASK>


---
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

             reply	other threads:[~2025-09-11  0:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11  0:08 syzbot [this message]
2025-09-18  1:03 ` Forwarded: WARNING in ext4_xattr_inode_update_ref syzbot
2025-09-18  4:05 ` syzbot
2025-09-18  4:49 ` syzbot
2025-09-19 23:22 ` syzbot
2025-09-24 19:28 ` syzbot
     [not found] <CAHxJ8O_F5ssDpCPi48eHRY=q29odqrjnOxfvdoOd5xppdhht7A@mail.gmail.com>
2025-09-18  1:28 ` [syzbot] [ext4?] " syzbot
     [not found] <CADfthj0NZ7duGqudQRUfmE=J69+hBkb+gWKQMVrJ18hDsMUGpw@mail.gmail.com>
2025-09-18  4:20 ` syzbot
     [not found] <CADfthj3f-mmvvm3tAWLUmtZGTKw46+eqxZhPekLA_eKLgOUG2g@mail.gmail.com>
2025-09-18  5:19 ` syzbot
     [not found] <CAHxJ8O9EHnwSkBNOmBOEg3GvDxcnqsQ5cURd+uG8G2EvUcXYfg@mail.gmail.com>
2025-09-19 23:56 ` syzbot
     [not found] <CAHxJ8O_w8ewga16ORMaoM8MZj_pbh02ZRV1T_z1B6i8Q=9AE6g@mail.gmail.com>
2025-09-24 19:56 ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=68c21301.050a0220.3c6139.0031.GAE@google.com \
    --to=syzbot+0be4f339a8218d2a5bb1@syzkaller.appspotmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.