================================================
WARNING: lock held when returning to user space!
6.18.0-rc7-next-20251128 #1 Not tainted
------------------------------------------------
syz-executor.7/8033 is leaving the kernel with locks still held!
1 lock held by syz-executor.7/8033:
 #0: ffff888018e615c8 (&sb->s_type->i_mutex_key#27/1){+.+.}-{4:4}, at: start_creating_noperm+0x84/0xd0
loop0: detected capacity change from 0 to 512
EXT4-fs (loop0): corrupt root inode, run e2fsck
EXT4-fs (loop0): mount failed
loop0: detected capacity change from 0 to 512
EXT4-fs error (device loop0): __ext4_fill_super:5553: inode #2: comm syz-executor.0: unexpected EA_INODE flag
EXT4-fs (loop0): get root inode failed
EXT4-fs (loop0): mount failed
loop3: detected capacity change from 0 to 512
EXT4-fs error (device loop3): __ext4_fill_super:5553: inode #2: comm syz-executor.3: unexpected EA_INODE flag
EXT4-fs (loop3): get root inode failed
EXT4-fs (loop3): mount failed
loop0: detected capacity change from 0 to 512
EXT4-fs (loop0): corrupt root inode, run e2fsck
EXT4-fs (loop0): mount failed
loop3: detected capacity change from 0 to 512
EXT4-fs error (device loop3): __ext4_fill_super:5553: inode #2: comm syz-executor.3: unexpected EA_INODE flag
EXT4-fs (loop3): get root inode failed
EXT4-fs (loop3): mount failed
loop0: detected capacity change from 0 to 512
EXT4-fs (loop0): corrupt root inode, run e2fsck
EXT4-fs (loop0): mount failed