[v6.1] WARNING: lock held when returning to user space in f2fs_write_single_data_page

Hello,

syzbot found the following issue on:

HEAD commit: a343b0dd87b4 Linux 6.1.30
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11fd22ed280000
kernel config: https://syzkaller.appspot.com/x/.config?x=5265a3c898f3cbbb
dashboard link: https://syzkaller.appspot.com/bug?extid=d0ab8746c920a592aeab
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=1469bbc1280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f16b99280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/195d974b1f1c/disk-a343b0dd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea41850547fb/vmlinux-a343b0dd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/13ec9e70ad28/bzImage-a343b0dd.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/5dc0a43a490d/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

F2FS-fs (loop0): Mounted with checkpoint version = 753bd00b
syz-executor137: attempt to access beyond end of device
loop0: rw=2049, sector=77824, nr_sectors = 4096 limit=63271
================================================
WARNING: lock held when returning to user space!
6.1.30-syzkaller #0 Not tainted
------------------------------------------------
syz-executor137/3566 is leaving the kernel with locks still held!
1 lock held by syz-executor137/3566:
#0: ffff888028ef0448 (&sbi->node_write){++++}-{3:3}, at: f2fs_down_read fs/f2fs/f2fs.h:2154 [inline]
#0: ffff888028ef0448 (&sbi->node_write){++++}-{3:3}, at: f2fs_write_single_data_page+0xb72/0x2020 fs/f2fs/data.c:2826


---
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 [email protected].

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

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

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

commit 5079e1c0c879311668b77075de3e701869804adf
git tree: upstream
Author: Chao Yu <[email protected]>
Date: Fri Jun 2 08:36:05 2023 +0000

f2fs: avoid dead loop in f2fs_issue_checkpoint()

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15343fbee80000
Please keep in mind that other backports might be required as well.

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