* Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data [not found] <tencent_B483AC64585766776E66C9B36FA36A496905@qq.com> @ 2023-12-15 3:40 ` syzbot 0 siblings, 0 replies; 5+ messages in thread From: syzbot @ 2023-12-15 3:40 UTC (permalink / raw) To: eadavis, linux-kernel, syzkaller-bugs Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: kernel BUG in ext4_do_writepages ------------[ cut here ]------------ kernel BUG at fs/ext4/inode.c:2587! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 1 PID: 10 Comm: kworker/u4:0 Not tainted 6.4.0-rc3-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 Workqueue: writeback wb_workfn (flush-7:0) RIP: 0010:ext4_do_writepages+0x27a1/0x34a0 fs/ext4/inode.c:2587 Code: fc ff df 44 89 64 24 18 48 c1 ea 03 80 3c 02 00 0f 84 bc ed ff ff 48 8b 7c 24 08 e8 19 aa a8 ff e9 ad ed ff ff e8 bf 2f 55 ff <0f> 0b e8 b8 2f 55 ff 48 8b 84 24 b0 00 00 00 48 8d 78 40 48 b8 00 RSP: 0018:ffffc900000f73e8 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff8880684f6e50 RCX: 0000000000000000 RDX: ffff888016649dc0 RSI: ffffffff82306c91 RDI: 0000000000000007 RBP: ffffc900000f75f0 R08: 0000000000000007 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001 R13: ffff88807e006678 R14: ffff8880684f70b0 R15: 7fffffffffffffff FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f07671c7650 CR3: 000000002a381000 CR4: 0000000000350ee0 Call Trace: <TASK> ext4_writepages+0x30b/0x780 fs/ext4/inode.c:2792 do_writepages+0x1b4/0x690 mm/page-writeback.c:2551 __writeback_single_inode+0x158/0xe70 fs/fs-writeback.c:1603 writeback_sb_inodes+0x599/0x1010 fs/fs-writeback.c:1894 wb_writeback+0x2ca/0xa90 fs/fs-writeback.c:2068 wb_do_writeback fs/fs-writeback.c:2211 [inline] wb_workfn+0x29c/0xfd0 fs/fs-writeback.c:2251 process_one_work+0x9f9/0x15f0 kernel/workqueue.c:2405 worker_thread+0x687/0x1110 kernel/workqueue.c:2552 kthread+0x33a/0x430 kernel/kthread.c:379 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:ext4_do_writepages+0x27a1/0x34a0 fs/ext4/inode.c:2587 Code: fc ff df 44 89 64 24 18 48 c1 ea 03 80 3c 02 00 0f 84 bc ed ff ff 48 8b 7c 24 08 e8 19 aa a8 ff e9 ad ed ff ff e8 bf 2f 55 ff <0f> 0b e8 b8 2f 55 ff 48 8b 84 24 b0 00 00 00 48 8d 78 40 48 b8 00 RSP: 0018:ffffc900000f73e8 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff8880684f6e50 RCX: 0000000000000000 RDX: ffff888016649dc0 RSI: ffffffff82306c91 RDI: 0000000000000007 RBP: ffffc900000f75f0 R08: 0000000000000007 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001 R13: ffff88807e006678 R14: ffff8880684f70b0 R15: 7fffffffffffffff FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f07671c7650 CR3: 0000000029b19000 CR4: 0000000000350ee0 Tested on: commit: 44c026a7 Linux 6.4-rc3 git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git console output: https://syzkaller.appspot.com/x/log.txt?x=135a5e3ee80000 kernel config: https://syzkaller.appspot.com/x/.config?x=e2045748b9f1055b dashboard link: https://syzkaller.appspot.com/bug?extid=f4582777a19ec422b517 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 patch: https://syzkaller.appspot.com/x/patch.diff?x=100bda1ee80000 ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <tencent_2D190DCF9D0DA225C98D87922ADDA1DD8607@qq.com>]
* Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data [not found] <tencent_2D190DCF9D0DA225C98D87922ADDA1DD8607@qq.com> @ 2023-12-13 11:56 ` syzbot 0 siblings, 0 replies; 5+ messages in thread From: syzbot @ 2023-12-13 11:56 UTC (permalink / raw) To: eadavis, linux-kernel, syzkaller-bugs Hello, syzbot has tested the proposed patch but the reproducer is still triggering an issue: kernel BUG in ext4_do_writepages ------------[ cut here ]------------ kernel BUG at fs/ext4/inode.c:2587! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 0 PID: 10 Comm: kworker/u4:0 Not tainted 6.4.0-rc3-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023 Workqueue: writeback wb_workfn (flush-7:0) RIP: 0010:ext4_do_writepages+0x27a1/0x34a0 fs/ext4/inode.c:2587 Code: fc ff df 44 89 64 24 18 48 c1 ea 03 80 3c 02 00 0f 84 bc ed ff ff 48 8b 7c 24 08 e8 49 aa a8 ff e9 ad ed ff ff e8 ef 2f 55 ff <0f> 0b e8 e8 2f 55 ff 48 8b 84 24 b0 00 00 00 48 8d 78 40 48 b8 00 RSP: 0018:ffffc900000f73e8 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff88807592bc50 RCX: 0000000000000000 RDX: ffff888016a41dc0 RSI: ffffffff82306c61 RDI: 0000000000000007 RBP: ffffc900000f75f0 R08: 0000000000000007 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000001 R13: ffff88802aede678 R14: ffff88807592beb0 R15: 7fffffffffffffff FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000561e569a2950 CR3: 000000002a00e000 CR4: 0000000000350ef0 Call Trace: <TASK> ext4_writepages+0x30b/0x780 fs/ext4/inode.c:2792 do_writepages+0x1b4/0x690 mm/page-writeback.c:2551 __writeback_single_inode+0x158/0xe70 fs/fs-writeback.c:1603 writeback_sb_inodes+0x599/0x1010 fs/fs-writeback.c:1894 wb_writeback+0x2ca/0xa90 fs/fs-writeback.c:2068 wb_do_writeback fs/fs-writeback.c:2211 [inline] wb_workfn+0x29c/0xfd0 fs/fs-writeback.c:2251 process_one_work+0x9f9/0x15f0 kernel/workqueue.c:2405 worker_thread+0x687/0x1110 kernel/workqueue.c:2552 kthread+0x33a/0x430 kernel/kthread.c:379 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:ext4_do_writepages+0x27a1/0x34a0 fs/ext4/inode.c:2587 Code: fc ff df 44 89 64 24 18 48 c1 ea 03 80 3c 02 00 0f 84 bc ed ff ff 48 8b 7c 24 08 e8 49 aa a8 ff e9 ad ed ff ff e8 ef 2f 55 ff <0f> 0b e8 e8 2f 55 ff 48 8b 84 24 b0 00 00 00 48 8d 78 40 48 b8 00 RSP: 0018:ffffc900000f73e8 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff88807592bc50 RCX: 0000000000000000 RDX: ffff888016a41dc0 RSI: ffffffff82306c61 RDI: 0000000000000007 RBP: ffffc900000f75f0 R08: 0000000000000007 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000001 R13: ffff88802aede678 R14: ffff88807592beb0 R15: 7fffffffffffffff FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f629e29e378 CR3: 000000000c772000 CR4: 0000000000350ef0 Tested on: commit: 44c026a7 Linux 6.4-rc3 git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git console output: https://syzkaller.appspot.com/x/log.txt?x=12c7b6fae80000 kernel config: https://syzkaller.appspot.com/x/.config?x=e2045748b9f1055b dashboard link: https://syzkaller.appspot.com/bug?extid=f4582777a19ec422b517 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 patch: https://syzkaller.appspot.com/x/patch.diff?x=133a9fbce80000 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [syzbot] [ext4?] kernel BUG in ext4_write_inline_data @ 2023-03-17 3:16 syzbot 2023-05-22 20:07 ` syzbot 2023-12-15 3:26 ` syzbot 0 siblings, 2 replies; 5+ messages in thread From: syzbot @ 2023-03-17 3:16 UTC (permalink / raw) To: adilger.kernel, linux-ext4, linux-fsdevel, linux-kernel, syzkaller-bugs, tytso Hello, syzbot found the following issue on: HEAD commit: 134231664868 Merge tag 'staging-6.3-rc2' of git://git.kern.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10ec9f7ac80000 kernel config: https://syzkaller.appspot.com/x/.config?x=8aef547e348b1ab8 dashboard link: https://syzkaller.appspot.com/bug?extid=f4582777a19ec422b517 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 userspace arch: i386 Unfortunately, I don't have any reproducer for this issue yet. IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+f4582777a19ec422b517@syzkaller.appspotmail.com ------------[ cut here ]------------ kernel BUG at fs/ext4/inline.c:225! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 2 PID: 24186 Comm: syz-executor.2 Not tainted 6.3.0-rc1-syzkaller-00274-g134231664868 #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 RIP: 0010:ext4_write_inline_data+0x344/0x3e0 fs/ext4/inline.c:225 Code: 5f e9 b0 16 5b ff e8 ab 16 5b ff 45 8d 64 2c c4 41 bd 3c 00 00 00 41 29 ed e9 e8 fe ff ff e8 93 16 5b ff 0f 0b e8 8c 16 5b ff <0f> 0b e8 a5 5c ac ff e9 fe fd ff ff 4c 89 ff e8 98 5c ac ff e9 99 RSP: 0018:ffffc900035673c0 EFLAGS: 00010216 RAX: 000000000001158c RBX: ffff88801cbb02b0 RCX: ffffc900031ea000 RDX: 0000000000040000 RSI: ffffffff8228bf04 RDI: 0000000000000006 RBP: 0000000000000048 R08: 0000000000000006 R09: 0000000000000051 R10: 0000000000000048 R11: 0000000000000000 R12: 0000000000000009 R13: 0000000000000051 R14: ffffc90003567460 R15: ffff88801cbb0872 FS: 0000000000000000(0000) GS:ffff88802cb00000(0063) knlGS:00000000f7f53b40 CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 CR2: 0000000020030018 CR3: 00000000487e6000 CR4: 0000000000150ee0 Call Trace: <TASK> ext4_write_inline_data_end+0x2a3/0x12f0 fs/ext4/inline.c:766 ext4_da_write_end+0x396/0x9c0 fs/ext4/inode.c:3149 generic_perform_write+0x316/0x570 mm/filemap.c:3937 ext4_buffered_write_iter+0x15b/0x460 fs/ext4/file.c:289 ext4_file_write_iter+0xbe0/0x1740 fs/ext4/file.c:710 call_write_iter include/linux/fs.h:1851 [inline] do_iter_readv_writev+0x20b/0x3b0 fs/read_write.c:735 do_iter_write+0x182/0x700 fs/read_write.c:861 vfs_iter_write+0x74/0xa0 fs/read_write.c:902 iter_file_splice_write+0x743/0xc80 fs/splice.c:778 do_splice_from fs/splice.c:856 [inline] direct_splice_actor+0x114/0x180 fs/splice.c:1022 splice_direct_to_actor+0x335/0x8a0 fs/splice.c:977 do_splice_direct+0x1ab/0x280 fs/splice.c:1065 do_sendfile+0xb19/0x12c0 fs/read_write.c:1255 __do_compat_sys_sendfile fs/read_write.c:1344 [inline] __se_compat_sys_sendfile fs/read_write.c:1327 [inline] __ia32_compat_sys_sendfile+0x1e1/0x220 fs/read_write.c:1327 do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline] __do_fast_syscall_32+0x65/0xf0 arch/x86/entry/common.c:178 do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:203 entry_SYSENTER_compat_after_hwframe+0x70/0x82 RIP: 0023:0xf7f58579 Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00 RSP: 002b:00000000f7f535cc EFLAGS: 00000296 ORIG_RAX: 00000000000000bb RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 0000000000000005 RDX: 0000000000000000 RSI: 0000000080000041 RDI: 0000000000000000 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000296 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:ext4_write_inline_data+0x344/0x3e0 fs/ext4/inline.c:225 Code: 5f e9 b0 16 5b ff e8 ab 16 5b ff 45 8d 64 2c c4 41 bd 3c 00 00 00 41 29 ed e9 e8 fe ff ff e8 93 16 5b ff 0f 0b e8 8c 16 5b ff <0f> 0b e8 a5 5c ac ff e9 fe fd ff ff 4c 89 ff e8 98 5c ac ff e9 99 RSP: 0018:ffffc900035673c0 EFLAGS: 00010216 RAX: 000000000001158c RBX: ffff88801cbb02b0 RCX: ffffc900031ea000 RDX: 0000000000040000 RSI: ffffffff8228bf04 RDI: 0000000000000006 RBP: 0000000000000048 R08: 0000000000000006 R09: 0000000000000051 R10: 0000000000000048 R11: 0000000000000000 R12: 0000000000000009 R13: 0000000000000051 R14: ffffc90003567460 R15: ffff88801cbb0872 FS: 0000000000000000(0000) GS:ffff88802cb00000(0063) knlGS:00000000f7f53b40 CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 CR2: 0000000020030018 CR3: 00000000487e6000 CR4: 0000000000150ee0 ---------------- Code disassembly (best guess), 2 bytes skipped: 0: 10 06 adc %al,(%rsi) 2: 03 74 b4 01 add 0x1(%rsp,%rsi,4),%esi 6: 10 07 adc %al,(%rdi) 8: 03 74 b0 01 add 0x1(%rax,%rsi,4),%esi c: 10 08 adc %cl,(%rax) e: 03 74 d8 01 add 0x1(%rax,%rbx,8),%esi 1e: 00 51 52 add %dl,0x52(%rcx) 21: 55 push %rbp 22: 89 e5 mov %esp,%ebp 24: 0f 34 sysenter 26: cd 80 int $0x80 * 28: 5d pop %rbp <-- trapping instruction 29: 5a pop %rdx 2a: 59 pop %rcx 2b: c3 retq 2c: 90 nop 2d: 90 nop 2e: 90 nop 2f: 90 nop 30: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi 37: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi --- 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. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data 2023-03-17 3:16 syzbot @ 2023-05-22 20:07 ` syzbot 2023-12-15 3:26 ` syzbot 1 sibling, 0 replies; 5+ messages in thread From: syzbot @ 2023-05-22 20:07 UTC (permalink / raw) To: adilger.kernel, linux-ext4, linux-fsdevel, linux-kernel, syzkaller-bugs, tytso syzbot has found a reproducer for the following issue on: HEAD commit: 44c026a73be8 Linux 6.4-rc3 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1028b7a1280000 kernel config: https://syzkaller.appspot.com/x/.config?x=f389ffdf4e9ba3f0 dashboard link: https://syzkaller.appspot.com/bug?extid=f4582777a19ec422b517 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=162a1a8e280000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12eb0691280000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/8c94fba58ffe/disk-44c026a7.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/fc04d8a50461/vmlinux-44c026a7.xz kernel image: https://storage.googleapis.com/syzbot-assets/4d861756bf1a/bzImage-44c026a7.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/f43e36084b2b/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+f4582777a19ec422b517@syzkaller.appspotmail.com ------------[ cut here ]------------ kernel BUG at fs/ext4/inline.c:235! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 1 PID: 5070 Comm: syz-executor189 Not tainted 6.4.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023 RIP: 0010:ext4_write_inline_data+0x344/0x3e0 fs/ext4/inline.c:235 Code: 5f e9 80 76 59 ff e8 7b 76 59 ff 45 8d 64 2c c4 41 bd 3c 00 00 00 41 29 ed e9 e8 fe ff ff e8 63 76 59 ff 0f 0b e8 5c 76 59 ff <0f> 0b e8 25 40 ac ff e9 fe fd ff ff 4c 89 ff e8 18 40 ac ff e9 99 RSP: 0018:ffffc90003e7f950 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff88807497c8b0 RCX: 0000000000000000 RDX: ffff888020bb1dc0 RSI: ffffffff822acc74 RDI: 0000000000000006 RBP: 0000000000000054 R08: 0000000000000006 R09: 0000000000000060 R10: 0000000000000054 R11: 0000000000000000 R12: 000000000000000c R13: 0000000000000060 R14: ffffc90003e7f9e8 R15: ffff88807497ce6a FS: 00007f4e59eb8700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f4e59e71000 CR3: 000000002bdc2000 CR4: 0000000000350ee0 Call Trace: <TASK> ext4_write_inline_data_end+0x2b3/0xd20 fs/ext4/inline.c:775 ext4_da_write_end+0x3d0/0xad0 fs/ext4/inode.c:2985 generic_perform_write+0x316/0x570 mm/filemap.c:3934 ext4_buffered_write_iter+0x15b/0x460 fs/ext4/file.c:289 ext4_file_write_iter+0xbe0/0x1740 fs/ext4/file.c:710 call_write_iter include/linux/fs.h:1868 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x945/0xd50 fs/read_write.c:584 ksys_write+0x12b/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f4e62256399 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f4e59eb82f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 000000000000003a RCX: 00007f4e62256399 RDX: 000000000000000c RSI: 00000000200002c0 RDI: 0000000000000004 RBP: 00007f4e622d37a8 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f4e622d37a0 R13: 00007f4e622a08f8 R14: 0000000020001200 R15: 0030656c69662f2e </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:ext4_write_inline_data+0x344/0x3e0 fs/ext4/inline.c:235 Code: 5f e9 80 76 59 ff e8 7b 76 59 ff 45 8d 64 2c c4 41 bd 3c 00 00 00 41 29 ed e9 e8 fe ff ff e8 63 76 59 ff 0f 0b e8 5c 76 59 ff <0f> 0b e8 25 40 ac ff e9 fe fd ff ff 4c 89 ff e8 18 40 ac ff e9 99 RSP: 0018:ffffc90003e7f950 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff88807497c8b0 RCX: 0000000000000000 RDX: ffff888020bb1dc0 RSI: ffffffff822acc74 RDI: 0000000000000006 RBP: 0000000000000054 R08: 0000000000000006 R09: 0000000000000060 R10: 0000000000000054 R11: 0000000000000000 R12: 000000000000000c R13: 0000000000000060 R14: ffffc90003e7f9e8 R15: ffff88807497ce6a FS: 00007f4e59eb8700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000555a6837b238 CR3: 000000002bdc2000 CR4: 0000000000350ee0 --- 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. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data 2023-03-17 3:16 syzbot 2023-05-22 20:07 ` syzbot @ 2023-12-15 3:26 ` syzbot 1 sibling, 0 replies; 5+ messages in thread From: syzbot @ 2023-12-15 3:26 UTC (permalink / raw) To: linux-kernel For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org. *** Subject: [ext4?] kernel BUG in ext4_write_inline_data Author: eadavis@qq.com please test kernel BUG in ext4_write_inline_data #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 44c026a73be8 diff --git a/fs/ext4/inline.c b/fs/ext4/inline.c index 9a84a5f9fef4..e0d261ffe623 100644 --- a/fs/ext4/inline.c +++ b/fs/ext4/inline.c @@ -169,6 +169,7 @@ int ext4_find_inline_data_nolock(struct inode *inode) (void *)ext4_raw_inode(&is.iloc)); EXT4_I(inode)->i_inline_size = EXT4_MIN_INLINE_DATA_SIZE + le32_to_cpu(is.s.here->e_value_size); + printk("iis: %d, in: %p, %s\n", EXT4_I(inode)->i_inline_size, inode, __func__); } out: brelse(is.iloc.bh); @@ -232,7 +233,9 @@ static void ext4_write_inline_data(struct inode *inode, struct ext4_iloc *iloc, return; BUG_ON(!EXT4_I(inode)->i_inline_off); - BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); + printk("pos: %d, len: %d, in: %p, iis: %d, %s\n", pos, len, inode, EXT4_I(inode)->i_inline_size, __func__); + if (EXT4_I(inode)->i_inline_size > 0) + BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); raw_inode = ext4_raw_inode(iloc); buffer += pos; @@ -314,6 +317,7 @@ static int ext4_create_inline_data(handle_t *handle, EXT4_I(inode)->i_inline_off = (u16)((void *)is.s.here - (void *)ext4_raw_inode(&is.iloc)); EXT4_I(inode)->i_inline_size = len + EXT4_MIN_INLINE_DATA_SIZE; + printk("len: %d, in: %p, iis: %d, %s\n", len, inode, EXT4_I(inode)->i_inline_size, __func__); ext4_clear_inode_flag(inode, EXT4_INODE_EXTENTS); ext4_set_inode_flag(inode, EXT4_INODE_INLINE_DATA); get_bh(is.iloc.bh); @@ -381,6 +385,7 @@ static int ext4_update_inline_data(handle_t *handle, struct inode *inode, (void *)ext4_raw_inode(&is.iloc)); EXT4_I(inode)->i_inline_size = EXT4_MIN_INLINE_DATA_SIZE + le32_to_cpu(is.s.here->e_value_size); + printk("iis: %d, in:%p, %s\n", EXT4_I(inode)->i_inline_size, inode, __func__); ext4_set_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA); get_bh(is.iloc.bh); error = ext4_mark_iloc_dirty(handle, inode, &is.iloc); @@ -469,6 +474,7 @@ static int ext4_destroy_inline_data_nolock(handle_t *handle, EXT4_I(inode)->i_inline_off = 0; EXT4_I(inode)->i_inline_size = 0; + printk("iis: %d, in: %p, %s\n", EXT4_I(inode)->i_inline_size, inode, __func__); ext4_clear_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA); out: brelse(is.iloc.bh); @@ -1979,6 +1985,7 @@ int ext4_inline_data_truncate(struct inode *inode, int *has_inline) EXT4_I(inode)->i_inline_size = i_size < EXT4_MIN_INLINE_DATA_SIZE ? EXT4_MIN_INLINE_DATA_SIZE : i_size; + printk("isize: %d, in: %p, iis: %d, %s\n", i_size, inode, EXT4_I(inode)->i_inline_size, __func__); } out_error: ^ permalink raw reply related [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-12-15 3:40 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <tencent_B483AC64585766776E66C9B36FA36A496905@qq.com>
2023-12-15 3:40 ` [syzbot] [ext4?] kernel BUG in ext4_write_inline_data syzbot
[not found] <tencent_2D190DCF9D0DA225C98D87922ADDA1DD8607@qq.com>
2023-12-13 11:56 ` syzbot
2023-03-17 3:16 syzbot
2023-05-22 20:07 ` syzbot
2023-12-15 3:26 ` syzbot
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).