syzbot
WARNING: lock held when returning to user space in f2fs_write_single_data_page
Status:
fixed on 2024/07/27 10:29
Bug presence:
origin:upstream
Labels:
missing-backport
[Documentation on labels]
Reported-by: syzbot+d0ab8746c920a592aeab@syzkaller.appspotmail.com
Fix commit:
f2ba11ba9325
f2fs: avoid dead loop in f2fs_issue_checkpoint()
First crash: 1172d, last: 968d
Fix bisection:
the issue occurs on the latest tested release
(bisect log)
Crash: no output from test machine (
log)
Repro:
C
syz
.config
▶
▼
Bug presence (3)
| Date |
Name |
Commit |
Repro |
Result |
| 2023/08/29 |
linux-6.1.y (ToT) |
024f76bca9d0 |
C
|
[report] no output from test machine
|
| 2023/05/30 |
upstream (ToT) |
afead42fdfca |
C
|
[report] WARNING: lock held when returning to user space in f2fs_write_single_data_page
|
| 2023/08/29 |
upstream (ToT) |
d68b4b6f307d |
C
|
Didn't crash |
▶
▼
Fix bisection attempts (6)
Sample crash report:
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
* Struck through repros no longer work on HEAD.