Bug 217159

Summary:	WARN in ext4_handle_inode_extension: i_size_read(inode) < EXT4_I(inode)->i_disksize
Product:	File System	Reporter:	Zhihao Cheng (chengzhihao1)
Component:	ext4	Assignee:	fs_ext4 (fs_ext4)
Status:	NEW ---
Severity:	normal	CC:	tytso
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	6.3.0-rc1	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	disk b.c

Description Zhihao Cheng 2023-03-08 02:55:35 UTC

CONFIG_EXT4_FS=y

1. download corrupted ext4 image disk(nonzero i_size for EXT4_BOOT_LOADER_INO)
2. gcc -o bb b.c
3. ./bb
[   16.966779] ------------[ cut here ]------------
[   16.967594] WARNING: CPU: 0 PID: 2580 at fs/ext4/file.c:319 ext4_file_write_iter+0xbc7/0xd10
[   16.968996] Modules linked in:
[   16.969521] CPU: 0 PID: 2580 Comm: bb Not tainted 6.3.0-rc1-00004-g703695902cfa #1109
[   16.970806] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraprojec4
[   16.973047] RIP: 0010:ext4_file_write_iter+0xbc7/0xd10
[   16.973813] Code: 56 0f e5 0c 01 48 83 05 76 12 e5 0c 01 e9 f1 fd ff ff 48 83 05 a9 14 e5 0c 01 49 89 c7 e9 01 fb ff ff 48 83c
[   16.975571] RSP: 0018:ffffc9000189fde0 EFLAGS: 00010202
[   16.976073] RAX: 0000000000006464 RBX: 0000000000000000 RCX: 00000000038b8000
[   16.976753] RDX: 00000000038b6000 RSI: ffff8881738c60f0 RDI: 0000000000030f70
[   16.977444] RBP: ffffc9000189fe70 R08: ffff8881738c60b8 R09: ffff8881738c60b8
[   16.978130] R10: 0000000000000307 R11: 0000000000000400 R12: ffff88817a9c61a0
[   16.978796] R13: 000000000000000a R14: ffffc9000189fe98 R15: 0000000000000400
[   16.979483] FS:  00007f3de0f00440(0000) GS:ffff88842fc00000(0000) knlGS:0000000000000000
[   16.980251] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   16.980787] CR2: 00007f3de08ffe70 CR3: 000000017576a000 CR4: 00000000000006f0
[   16.981491] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   16.982179] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   16.982851] Call Trace:
[   16.983110]  <TASK>
[   16.983327]  ? __ext4_ioctl+0x1375/0x2700
[   16.983711]  vfs_write+0x3b1/0x5c0
[   16.984059]  ksys_write+0x77/0x160
[   16.984395]  __x64_sys_write+0x22/0x30
[   16.984754]  do_syscall_64+0x39/0x80
[   16.985120]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
[   16.985611] RIP: 0033:0x7f3de0900130
[   16.985972] Code: 73 01 c3 48 8b 0d 58 ed 2c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d b9 45 2d 00 00 75 10 b84
[   16.987744] RSP: 002b:00007ffe63ff5e98 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
[   16.988482] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f3de0900130
[   16.989181] RDX: 0000000000000400 RSI: 00000000012e1400 RDI: 0000000000000003
[   16.989874] RBP: 00007ffe63ff5eb0 R08: 0000000000000000 R09: 0000000000000450
[   16.990569] R10: 0000000000000003 R11: 0000000000000246 R12: 0000000000400570
[   16.991266] R13: 00007ffe63ff5f90 R14: 0000000000000000 R15: 0000000000000000
[   16.991948]  </TASK>
[   16.992174] ---[ end trace 0000000000000000 ]---

Comment 1 Zhihao Cheng 2023-03-08 02:57:12 UTC

Created attachment 303897 [details]
disk

Comment 2 Zhihao Cheng 2023-03-08 02:57:23 UTC

Created attachment 303898 [details]
b.c

Comment 3 Theodore Tso 2023-03-08 04:19:31 UTC

I guess if you edit the subject line, bugzilla won't be able to thread the reply.   It could use the in-reply-to header, but apparently.... it doesn't.

Reply and fix here: https://lore.kernel.org/all/20230308041252.GC860405@mit.edu/