syzbot

 sign-in | mailing list | source | docs
🐞 Open [202]
🐞 Fixed [0]
🐞 Invalid [0]
⬇ Missing Backports [3]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

general protection fault in lmLogSync

Status: upstream: reported C repro on 2025/06/21 09:37
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+fd016b483ce9e23a110b@syzkaller.appspotmail.com
First crash: 26d, last: 2d09h
▶ ▼ Bug presence (1)
Date Name Commit Repro Result
2025/06/27 upstream (ToT) 67a993863163 C [report] general protection fault in lmLogSync
▶ ▼ Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream general protection fault in lmLogSync (2) jfs 24 C error 6768 now 1021d 0/29 upstream: reported C repro on 2022/09/29 20:40
linux-6.1 BUG: unable to handle kernel paging request in lmLogSync origin:upstream 24 C 918 57m 856d 0/3 upstream: reported C repro on 2023/03/14 01:30
linux-5.15 BUG: unable to handle kernel paging request in lmLogSync missing-backport origin:upstream 24 C error 474 2d08h 856d 0/3 upstream: reported C repro on 2023/03/14 00:56
upstream general protection fault in lmLogSync jfs 2 1 1196d 1184d 0/29 auto-closed as invalid on 2022/08/06 08:08

Sample crash report:
general protection fault, probably for non-canonical address 0xdffffc0000000008: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]
CPU: 0 PID: 112 Comm: jfsCommit Not tainted 6.6.96-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:write_special_inodes fs/jfs/jfs_logmgr.c:207 [inline]
RIP: 0010:lmLogSync+0xfc/0x9c0 fs/jfs/jfs_logmgr.c:935
Code: bf 84 fe 4d 8d 7e d8 4c 89 f8 48 c1 e8 03 80 3c 18 00 74 08 4c 89 ff e8 12 6e dd fe 4d 8b 3f 49 83 c7 40 4c 89 f8 48 c1 e8 03 <80> 3c 18 00 74 08 4c 89 ff e8 f6 6d dd fe 49 8b 3f e8 3e 8f b3 fe
RSP: 0018:ffffc90002d47c40 EFLAGS: 00010202
RAX: 0000000000000008 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: ffff888018fcda00 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90002d47d48 R08: 0000000000000003 R09: 0000000000000000
R10: ffffc90002d47ca0 R11: fffff520005a8f98 R12: ffff88801fb7a800
R13: dffffc0000000000 R14: ffff888032301038 R15: 0000000000000040
FS:  0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffa59f7cb8 CR3: 0000000023a52000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 jfs_syncpt+0x7b/0x90 fs/jfs/jfs_logmgr.c:1041
 txEnd+0x2e5/0x520 fs/jfs/jfs_txnmgr.c:549
 txLazyCommit fs/jfs/jfs_txnmgr.c:2684 [inline]
 jfs_lazycommit+0x5a6/0xa60 fs/jfs/jfs_txnmgr.c:2732
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:write_special_inodes fs/jfs/jfs_logmgr.c:207 [inline]
RIP: 0010:lmLogSync+0xfc/0x9c0 fs/jfs/jfs_logmgr.c:935
Code: bf 84 fe 4d 8d 7e d8 4c 89 f8 48 c1 e8 03 80 3c 18 00 74 08 4c 89 ff e8 12 6e dd fe 4d 8b 3f 49 83 c7 40 4c 89 f8 48 c1 e8 03 <80> 3c 18 00 74 08 4c 89 ff e8 f6 6d dd fe 49 8b 3f e8 3e 8f b3 fe
RSP: 0018:ffffc90002d47c40 EFLAGS: 00010202
RAX: 0000000000000008 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: ffff888018fcda00 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90002d47d48 R08: 0000000000000003 R09: 0000000000000000
R10: ffffc90002d47ca0 R11: fffff520005a8f98 R12: ffff88801fb7a800
R13: dffffc0000000000 R14: ffff888032301038 R15: 0000000000000040
FS:  0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c007a4b000 CR3: 000000002c59c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	bf 84 fe 4d 8d       	mov    $0x8d4dfe84,%edi
   5:	7e d8                	jle    0xffffffdf
   7:	4c 89 f8             	mov    %r15,%rax
   a:	48 c1 e8 03          	shr    $0x3,%rax
   e:	80 3c 18 00          	cmpb   $0x0,(%rax,%rbx,1)
  12:	74 08                	je     0x1c
  14:	4c 89 ff             	mov    %r15,%rdi
  17:	e8 12 6e dd fe       	call   0xfedd6e2e
  1c:	4d 8b 3f             	mov    (%r15),%r15
  1f:	49 83 c7 40          	add    $0x40,%r15
  23:	4c 89 f8             	mov    %r15,%rax
  26:	48 c1 e8 03          	shr    $0x3,%rax
* 2a:	80 3c 18 00          	cmpb   $0x0,(%rax,%rbx,1) <-- trapping instruction
  2e:	74 08                	je     0x38
  30:	4c 89 ff             	mov    %r15,%rdi
  33:	e8 f6 6d dd fe       	call   0xfedd6e2e
  38:	49 8b 3f             	mov    (%r15),%rdi
  3b:	e8 3e 8f b3 fe       	call   0xfeb38f7e

Crashes (16):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/08 11:00 linux-6.6.y a5df3a702b2c 4f67c4ae .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/07/08 10:24 linux-6.6.y a5df3a702b2c 4f67c4ae .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/07/06 08:16 linux-6.6.y 3f5b4c104b7d 4f67c4ae .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/06/23 07:51 linux-6.6.y 6282921b6825 d6cdfb8a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/06/22 14:08 linux-6.6.y 6282921b6825 d6cdfb8a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/06/22 02:58 linux-6.6.y 6282921b6825 d6cdfb8a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan KASAN: slab-use-after-free Write in lmLogSync
2025/07/15 05:22 linux-6.6.y 9247f4e6573a 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/07/15 05:09 linux-6.6.y 9247f4e6573a 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/07/05 12:13 linux-6.6.y 3f5b4c104b7d 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/07/04 02:13 linux-6.6.y 3f5b4c104b7d 76ad128c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/07/01 21:48 linux-6.6.y 3f5b4c104b7d 091a06cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/06/29 21:37 linux-6.6.y 3f5b4c104b7d fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/06/28 00:17 linux-6.6.y 3f5b4c104b7d fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/06/23 04:46 linux-6.6.y 6282921b6825 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/06/22 11:38 linux-6.6.y 6282921b6825 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan general protection fault in lmLogSync
2025/06/21 09:36 linux-6.6.y 6282921b6825 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan general protection fault in lmLogSync
* Struck through repros no longer work on HEAD.