syzbot

 sign-in | mailing list | source | docs
🐞 Open [966] ≡ Subsystems 🐞 Fixed [4556] 🐞 Invalid [10489] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

WARNING: lock held when returning to user space in f2fs_write_single_data_page

Status: upstream: reported C repro on 2023/05/01 17:05
Labels: f2fs (incorrect?)
Reported-by: syzbot+eb6201248f684e99b9f8@syzkaller.appspotmail.com
First crash: 30d, last: 28d

Cause bisection: failed (error log, bisect log)
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [f2fs?] WARNING: lock held when returning to user space in f2fs_write_single_data_page 4 (7) 2023/05/04 13:53
▶ ▼ Last patch testing requests (7)
Created Duration User Patch Repo Result
2023/05/14 05:51 30m chao@kernel.org https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/syzbot log
2023/05/14 03:23 53m chao@kernel.org https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git master report log
2023/05/13 08:54 29m chao@kernel.org https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git dev-test log
2023/05/13 02:22 33m chao@kernel.org https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git dev-test log
2023/05/04 12:08 36m chao@kernel.org https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git dev-test log
2023/05/03 15:29 26m chao@kernel.org https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git dev-test report log
2023/05/02 01:52 28m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 58390c8ce1bd log

Sample crash report:
syz-executor125: attempt to access beyond end of device
loop0: rw=2049, sector=77824, nr_sectors = 2976 limit=63271
syz-executor125: attempt to access beyond end of device
loop0: rw=2049, sector=80800, nr_sectors = 1120 limit=63271
================================================
WARNING: lock held when returning to user space!
6.3.0-syzkaller-12378-gc8c655c34e33 #0 Not tainted
------------------------------------------------
syz-executor125/4993 is leaving the kernel with locks still held!
1 lock held by syz-executor125/4993:
 #0: ffff88807effc448 (&sbi->node_write){++++}-{3:3}, at: f2fs_down_read fs/f2fs/f2fs.h:2087 [inline]
 #0: ffff88807effc448 (&sbi->node_write){++++}-{3:3}, at: f2fs_write_single_data_page+0xa10/0x1d50 fs/f2fs/data.c:2842

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Manager Title
2023/05/02 00:41 upstream c8c655c34e33 62df2017 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING: lock held when returning to user space in f2fs_write_single_data_page
2023/05/01 02:36 upstream 58390c8ce1bd 62df2017 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING: lock held when returning to user space in f2fs_write_single_data_page
2023/04/30 08:06 upstream 1ae78a14516b 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root WARNING: lock held when returning to user space in f2fs_write_single_data_page
2023/04/30 05:32 upstream 1ae78a14516b 62df2017 .config console log report info ci-qemu-upstream-386 WARNING: lock held when returning to user space in f2fs_write_single_data_page
* Struck through repros no longer work on HEAD.