In the Linux kernel, the following vulnerability has been resolved:EOL][EOL]ext4: fix warning in ext4_iomap_begin as race between bmap and write[EOL][EOL]We got issue as follows:[EOL]------------[ cut here ]------------[EOL]WARNING: CPU: 3 PID: 9310 at fs/ext4/inode.c:3441 ext4_iomap_begin+0x182/0x5d0[EOL]RIP: 0010:ext4_iomap_begin+0x182/0x5d0[EOL]RSP: 0018:ffff88812460fa08 EFLAGS: 00010293[EOL]RAX: ffff88811f168000 RBX: 0000000000000000 RCX: ffffffff97793c12[EOL]RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003[EOL]RBP: ffff88812c669160 R08: ffff88811f168000 R09: ffffed10258cd20f[EOL]R10: ffff88812c669077 R11: ffffed10258cd20e R12: 0000000000000001[EOL]R13: 00000000000000a4 R14: 000000000000000c R15: ffff88812c6691ee[EOL]FS: 00007fd0d6ff3740(0000) GS:ffff8883af180000(0000) knlGS:0000000000000000[EOL]CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033[EOL]CR2: 00007fd0d6dda290 CR3: 0000000104a62000 CR4: 00000000000006e0[EOL]DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000[EOL]DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400[EOL]Call Trace:[EOL] iomap_apply+0x119/0x570[EOL] iomap_bmap+0x124/0x150[EOL] ext4_bmap+0x14f/0x250[EOL] bmap+0x55/0x80[EOL] do_vfs_ioctl+0x952/0xbd0[EOL] __x64_sys_ioctl+0xc6/0x170[EOL] do_syscall_64+0x33/0x40[EOL] entry_SYSCALL_64_after_hwframe+0x44/0xa9[EOL][EOL]Above issue may happen as follows:[EOL] bmap write[EOL]bmap[EOL] ext4_bmap[EOL] iomap_bmap[EOL] ext4_iomap_begin[EOL] ext4_file_write_iter[EOL]\t\t\t ext4_buffered_write_iter[EOL]\t\t\t generic_perform_write[EOL]\t\t\t\t ext4_da_write_begin[EOL]\t\t\t\t ext4_da_write_inline_data_begin[EOL]\t\t\t\t ext4_prepare_inline_data[EOL]\t\t\t\t ext4_create_inline_data[EOL]\t\t\t\t\t ext4_set_inode_flag(inode,[EOL]\t\t\t\t\t\tEXT4_INODE_INLINE_DATA);[EOL] if (WARN_ON_ONCE(ext4_has_inline_data(inode))) ->trigger bug_on[EOL][EOL]To solved above issue hold inode lock in ext4_bamp. CREATE(Triage):(User=lchen-cn) [CVE-2022-50082 (https://nvd.nist.gov/vuln/detail/CVE-2022-50082)