linux-kernel - [syzbot] [ext4?] WARNING in ext4_xattr_set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <0000000000003ecb1a0615cdb35c@google.com>
Date: Thu, 11 Apr 2024 01:11:19 -0700
From: syzbot <syzbot+4b03894b6ec5753ddf24@...kaller.appspotmail.com>
To: adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org, 
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com, tytso@....edu
Subject: [syzbot] [ext4?] WARNING in ext4_xattr_set_entry (2)

Hello,

syzbot found the following issue on:

HEAD commit:    a053fd3ca5d1 Add linux-next specific files for 20240409
git tree:       linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=15b0af03180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=cef4d00cd7fe38ca
dashboard link: https://syzkaller.appspot.com/bug?extid=4b03894b6ec5753ddf24
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=143cd79d180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=152e5d9d180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/16fbf27c5977/disk-a053fd3c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cac2847d6c46/vmlinux-a053fd3c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c4f6c7891071/bzImage-a053fd3c.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/134052cf6b8b/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4b03894b6ec5753ddf24@...kaller.appspotmail.com

process 'syz-executor225' launched '/dev/fd/4/./file1' with NULL argv: empty string added
EXT4-fs warning (device loop0): ext4_xattr_inode_create:1471: refuse to create EA inode when umounting
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5089 at fs/ext4/xattr.c:1472 ext4_xattr_inode_create fs/ext4/xattr.c:1472 [inline]
WARNING: CPU: 1 PID: 5089 at fs/ext4/xattr.c:1472 ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1590 [inline]
WARNING: CPU: 1 PID: 5089 at fs/ext4/xattr.c:1472 ext4_xattr_set_entry+0x162c/0x4330 fs/ext4/xattr.c:1718
Modules linked in:
CPU: 1 PID: 5089 Comm: syz-executor225 Not tainted 6.9.0-rc3-next-20240409-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:ext4_xattr_inode_create fs/ext4/xattr.c:1472 [inline]
RIP: 0010:ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1590 [inline]
RIP: 0010:ext4_xattr_set_entry+0x162c/0x4330 fs/ext4/xattr.c:1718
Code: 00 00 e8 57 50 2a ff eb 30 e8 50 50 2a ff 4c 89 ff 48 c7 c6 e9 5d b7 8d ba bf 05 00 00 48 c7 c1 00 aa df 8b e8 75 12 fc ff 90 <0f> 0b 90 49 c7 c4 ea ff ff ff 4c 8b 7c 24 70 48 8b 44 24 40 42 80
RSP: 0018:ffffc9000337efa0 EFLAGS: 00010246
RAX: aa755dc17bf17f00 RBX: 0000000000000000 RCX: aa755dc17bf17f00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc9000337f230 R08: ffffffff8176bb7c R09: 1ffff9200066fd6c
R10: dffffc0000000000 R11: fffff5200066fd6d R12: ffff88807a280cd8
R13: dffffc0000000000 R14: ffffc9000337f150 R15: ffff888060b68000
FS:  0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000005fdeb8 CR3: 0000000060608000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ext4_xattr_block_set+0x6a2/0x3480 fs/ext4/xattr.c:1968
 ext4_xattr_move_to_block fs/ext4/xattr.c:2654 [inline]
 ext4_xattr_make_inode_space fs/ext4/xattr.c:2729 [inline]
 ext4_expand_extra_isize_ea+0x12d7/0x1cf0 fs/ext4/xattr.c:2821
 __ext4_expand_extra_isize+0x2fb/0x3e0 fs/ext4/inode.c:5789
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5832 [inline]
 __ext4_mark_inode_dirty+0x524/0x880 fs/ext4/inode.c:5910
 ext4_dirty_inode+0xce/0x110 fs/ext4/inode.c:5942
 __mark_inode_dirty+0x325/0xe20 fs/fs-writeback.c:2486
 mark_inode_dirty_sync include/linux/fs.h:2406 [inline]
 iput+0x1fe/0x930 fs/inode.c:1764
 __dentry_kill+0x20d/0x630 fs/dcache.c:603
 shrink_kill+0xa9/0x2c0 fs/dcache.c:1048
 shrink_dentry_list+0x2c0/0x5b0 fs/dcache.c:1075
 shrink_dcache_parent+0xcb/0x3b0
 do_one_tree+0x23/0xe0 fs/dcache.c:1538
 shrink_dcache_for_umount+0x7d/0x130 fs/dcache.c:1555
 generic_shutdown_super+0x6a/0x2d0 fs/super.c:619
 kill_block_super+0x44/0x90 fs/super.c:1675
 ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7323
 deactivate_locked_super+0xc4/0x130 fs/super.c:472
 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1267
 task_work_run+0x24f/0x310 kernel/task_work.c:180
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xa1b/0x27e0 kernel/exit.c:878
 do_group_exit+0x207/0x2c0 kernel/exit.c:1027
 __do_sys_exit_group kernel/exit.c:1038 [inline]
 __se_sys_exit_group kernel/exit.c:1036 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1036
 do_syscall_64+0xfb/0x240
 entry_SYSCALL_64_after_hwframe+0x72/0x7a
RIP: 0033:0x7f0fe6f95c49
Code: Unable to access opcode bytes at 0x7f0fe6f95c1f.
RSP: 002b:00007ffc0a1edef8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f0fe6f95c49
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007f0fe7012390 R08: ffffffffffffffb8 R09: 00007ffc0a1edfd0
R10: 0000000000000381 R11: 0000000000000246 R12: 00007f0fe7012390
R13: 0000000000000000 R14: 00007f0fe7013100 R15: 00007f0fe6f63f20
 </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@...glegroups.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