[v5.15] WARNING in ext4_set_page_dirty

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d9b4a0c83a2d Linux 5.15.98
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12165dbcc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=2f8d9515b973b23b
dashboard link: https://syzkaller.appspot.com/bug?extid=02f21431b65c214aa1d6
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/037cabbd3313/disk-d9b4a0c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9967e551eb34/vmlinux-d9b4a0c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a050c7a4fd99/bzImage-d9b4a0c8.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+02f214...@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 15527 at fs/ext4/inode.c:3614 ext4_set_page_dirty+0x2aa/0x340
Modules linked in:
CPU: 0 PID: 15527 Comm: syz-executor.1 Not tainted 5.15.98-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:ext4_set_page_dirty+0x2aa/0x340 fs/ext4/inode.c:3614
Code: 5d 41 5e 41 5f 5d e9 75 76 c7 ff e8 30 e0 62 ff 48 ff cb e9 c6 fd ff ff e8 23 e0 62 ff 49 ff cd e9 21 fe ff ff e8 16 e0 62 ff <0f> 0b eb cb e8 0d e0 62 ff 48 ff cb e9 93 fe ff ff e8 00 e0 62 ff
RSP: 0018:ffffc9000aa7fa98 EFLAGS: 00010246
RAX: ffffffff821d747a RBX: 00fff00000000055 RCX: 0000000000040000
RDX: ffffc90003e47000 RSI: 000000000003ffff RDI: 0000000000040000
RBP: 0000000000000000 R08: ffffffff821d743f R09: fffff940005833b9
R10: 0000000000000000 R11: dffffc0000000001 R12: 00fff00000000055
R13: dffffc0000000000 R14: ffffea0002c19dc0 R15: ffffea0002c19dc8
FS: 00007fb48767d700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3fa0a03db0 CR3: 00000000777c5000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000006
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
set_page_dirty_lock+0xbd/0xe0 mm/page-writeback.c:2634
unpin_user_pages_dirty_lock+0x2b4/0x4c0 mm/gup.c:365
process_vm_rw_single_vec mm/process_vm_access.c:126 [inline]
process_vm_rw_core mm/process_vm_access.c:215 [inline]
process_vm_rw+0x94a/0xcc0 mm/process_vm_access.c:283
__do_sys_process_vm_writev mm/process_vm_access.c:303 [inline]
__se_sys_process_vm_writev mm/process_vm_access.c:298 [inline]
__x64_sys_process_vm_writev+0xdc/0xf0 mm/process_vm_access.c:298
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fb48910b0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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:00007fb48767d168 EFLAGS: 00000246 ORIG_RAX: 0000000000000137
RAX: ffffffffffffffda RBX: 00007fb48922af80 RCX: 00007fb48910b0f9
RDX: 0000000000000070 RSI: 0000000020c22000 RDI: 00000000000004d5
RBP: 00007fb489166ae9 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000020c22fa0 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd220f5d6f R14: 00007fb48767d300 R15: 0000000000022000
</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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: d214f240b0f6 Linux 5.15.100
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14ab52dac80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5c5a36ceb954515

dashboard link: https://syzkaller.appspot.com/bug?extid=02f21431b65c214aa1d6
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1215d60ac80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16bf047cc80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4e12037285d4/disk-d214f240.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/929d982226d5/vmlinux-d214f240.xz
kernel image: https://storage.googleapis.com/syzbot-assets/59140c032c99/bzImage-d214f240.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+02f214...@syzkaller.appspotmail.com

------------[ cut here ]------------

WARNING: CPU: 0 PID: 3602 at fs/ext4/inode.c:3614 ext4_set_page_dirty+0x2aa/0x340
Modules linked in:
CPU: 0 PID: 3602 Comm: syz-executor171 Not tainted 5.15.100-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:ext4_set_page_dirty+0x2aa/0x340 fs/ext4/inode.c:3614

Code: 5d 41 5e 41 5f 5d e9 15 4e c7 ff e8 f0 4e 62 ff 48 ff cb e9 c6 fd ff ff e8 e3 4e 62 ff 49 ff cd e9 21 fe ff ff e8 d6 4e 62 ff <0f> 0b eb cb e8 cd 4e 62 ff 48 ff cb e9 93 fe ff ff e8 c0 4e 62 ff
RSP: 0018:ffffc90002c3fa98 EFLAGS: 00010293
RAX: ffffffff821e2baa RBX: 00fff00000000035 RCX: ffff888023f99d00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff821e2b6f R09: fffff9400037d179
R10: 0000000000000000 R11: dffffc0000000001 R12: 00fff00000000035
R13: dffffc0000000000 R14: ffffea0001be8bc0 R15: ffffea0001be8bc8
FS: 00007f947836f700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00005610b498a038 CR3: 0000000018751000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Call Trace:
<TASK>
set_page_dirty_lock+0xbd/0xe0 mm/page-writeback.c:2634
unpin_user_pages_dirty_lock+0x2b4/0x4c0 mm/gup.c:365
process_vm_rw_single_vec mm/process_vm_access.c:126 [inline]
process_vm_rw_core mm/process_vm_access.c:215 [inline]
process_vm_rw+0x94a/0xcc0 mm/process_vm_access.c:283
__do_sys_process_vm_writev mm/process_vm_access.c:303 [inline]
__se_sys_process_vm_writev mm/process_vm_access.c:298 [inline]
__x64_sys_process_vm_writev+0xdc/0xf0 mm/process_vm_access.c:298
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb

RIP: 0033:0x7f94783df1f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 41 15 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:00007f947836f308 EFLAGS: 00000246 ORIG_RAX: 0000000000000137
RAX: ffffffffffffffda RBX: 00007f94784684f8 RCX: 00007f94783df1f9
RDX: 0000000000000001 RSI: 0000000020c22000 RDI: 0000000000000e12
RBP: 00007f94784684f0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000020c22fa0 R11: 0000000000000246 R12: 00007f9478435074
R13: 00007ffcbf192a4f R14: 00007f947836f400 R15: 0000000000022000
</TASK>

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit e41c81d0d30e1a6ebf408feaf561f80cac4457dc
git tree: upstream
Author: Matthew Wilcox (Oracle) <wi...@infradead.org>
Date: Sat Feb 12 22:43:16 2022 +0000

mm/truncate: Replace page_mapped() call in invalidate_inode_page()

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16112108680000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5592cc4916e1c2f
dashboard link: https://syzkaller.appspot.com/bug?extid=02f21431b65c214aa1d6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e0c205c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=119865cec80000


Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection