syzbot


WARNING: lock held when returning

Status: closed as invalid on 2024/09/05 01:27
Subsystems: f2fs
[Documentation on labels]
Reported-by: syzbot+16c06d2c27b585e352f8@syzkaller.appspotmail.com
First crash: 30d, last: 30d
Cause bisection: introduced by (bisect log) :
commit 7566a155c666dd23b413a002a50cd9ae7b95f053
Author: Chao Yu <chao@kernel.org>
Date: Tue Jun 25 03:13:49 2024 +0000

  f2fs: atomic: fix to not allow GC to pollute atomic_file

Crash: WARNING: lock held when returning to user space in f2fs_commit_atomic_write (log)
Repro: C syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [f2fs?] WARNING: lock held when returning 1 (2) 2024/09/05 01:27
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/08/27 18:19 33m retest repro linux-next OK log

Sample crash report:
F2FS-fs (loop0): Mounted with checkpoint version = 48b305e5
syz-executor161: attempt to access beyond end of device
loop0: rw=2049, sector=45096, nr_sectors = 8 limit=40427
================================================
WARNING: lock held when returning

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/08/13 00:19 linux-next 9e6869691724 7b0f4b46 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root WARNING: lock held when returning
* Struck through repros no longer work on HEAD.