syzbot

 sign-in | mailing list | source | docs
🐞 Open [710]
🐞 Fixed [52]
🐞 Invalid [537]
⬇ Missing Backports [56]
Kernel Health Bugs/Month Bug Lifetimes Fuzzing Crashes
💬 Send us feedback

general protection fault in jfs_flush_journal

Status: upstream: reported C repro on 2023/03/16 22:18
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+c708d902646b38b761e8@syzkaller.appspotmail.com
First crash: 578d, last: 8d01h
▶ ▼ Bug presence (1)
Date Name Commit Repro Result
2024/09/19 upstream (ToT) 176000734ee2 C [report] BUG: unable to handle kernel paging request in jfs_flush_journal
▶ ▼ Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream general protection fault in jfs_flush_journal jfs C inconclusive 907 3d05h 743d 0/28 upstream: reported C repro on 2022/10/02 18:56
linux-6.1 general protection fault in jfs_flush_journal origin:upstream C 83 22d 574d 0/3 upstream: reported C repro on 2023/03/20 13:13
▶ ▼ Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/10/07 05:13 12m retest repro linux-5.15.y report log

Sample crash report:
loop1: detected capacity change from 0 to 32768
read_mapping_page failed!
diRead: diIAGRead returned -5
Unable to handle kernel paging request at virtual address dfff800000000006
Mem abort info:
  ESR = 0x0000000096000006
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x06: level 2 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000006
  CM = 0, WnR = 0
[dfff800000000006] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4098 Comm: syz-executor186 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : write_special_inodes fs/jfs/jfs_logmgr.c:208 [inline]
pc : jfs_flush_journal+0x6ac/0xd94 fs/jfs/jfs_logmgr.c:1581
lr : write_special_inodes fs/jfs/jfs_logmgr.c:207 [inline]
lr : jfs_flush_journal+0x688/0xd94 fs/jfs/jfs_logmgr.c:1581
sp : ffff80001fee76e0
x29: ffff80001fee77d0 x28: dfff800000000000 x27: dfff800000000000
x26: 1fffe000193ab435 x25: 1fffe000193ab400 x24: 0000000000000000
x23: ffff0000c9d5a1b8 x22: 0000000000000030 x21: ffff0000c085f038
x20: ffff0000c9d5a1a8 x19: ffff0000c9d5a000 x18: 0000000000000001
x17: 0000000000000000 x16: ffff80000824ecc0 x15: 00000000ffffffff
x14: 1ffff0000295806a x13: dfff800000000000 x12: 0000000000000003
x11: 0000000000000000 x10: 0000000000000000 x9 : cc40be3277aa7800
x8 : 0000000000000006 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000008 x3 : 0000000000000010
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
 write_special_inodes fs/jfs/jfs_logmgr.c:208 [inline]
 jfs_flush_journal+0x6ac/0xd94 fs/jfs/jfs_logmgr.c:1581
 jfs_umount+0xf8/0x338 fs/jfs/jfs_umount.c:58
 jfs_fill_super+0x744/0xa08 fs/jfs/super.c:605
 mount_bdev+0x274/0x370 fs/super.c:1398
 jfs_do_mount+0x44/0x58 fs/jfs/super.c:675
 legacy_get_tree+0xd4/0x16c fs/fs_context.c:611
 vfs_get_tree+0x90/0x274 fs/super.c:1528
 do_new_mount+0x278/0x8fc fs/namespace.c:3005
 path_mount+0x594/0x101c fs/namespace.c:3335
 do_mount fs/namespace.c:3348 [inline]
 __do_sys_mount fs/namespace.c:3556 [inline]
 __se_sys_mount fs/namespace.c:3533 [inline]
 __arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3533
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 97bf707e f94002c8 9100c116 d343fec8 (387c6908) 
---[ end trace a93384b6ef4c53c0 ]---
----------------
Code disassembly (best guess):
   0:	97bf707e 	bl	0xfffffffffefdc1f8
   4:	f94002c8 	ldr	x8, [x22]
   8:	9100c116 	add	x22, x8, #0x30
   c:	d343fec8 	lsr	x8, x22, #3
* 10:	387c6908 	ldrb	w8, [x8, x28] <-- trapping instruction

Crashes (26):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/09/18 17:13 linux-5.15.y 3a5928702e71 c673ca06 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2024/06/27 17:08 linux-5.15.y 4878aadf2d15 6ef39602 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan general protection fault in jfs_flush_journal
2024/04/08 12:48 linux-5.15.y 9465fef4ae35 53df08b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan general protection fault in jfs_flush_journal
2023/08/30 23:23 linux-5.15.y 9e43368a3393 84803932 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan general protection fault in jfs_flush_journal
2023/07/14 07:12 linux-5.15.y d54cfc420586 d624500f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan general protection fault in jfs_flush_journal
2023/06/18 09:56 linux-5.15.y 471e639e59d1 f3921d4d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan general protection fault in jfs_flush_journal
2023/03/16 22:18 linux-5.15.y 2ddbd0f967b3 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan general protection fault in jfs_flush_journal
2024/05/01 03:13 linux-5.15.y b925f60c6ee7 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2024/04/16 03:37 linux-5.15.y fa3df276cd36 0d592ce4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2024/04/03 03:53 linux-5.15.y 9465fef4ae35 7925100d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2024/03/30 11:06 linux-5.15.y 9465fef4ae35 6baf5069 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2024/03/29 04:47 linux-5.15.y 9465fef4ae35 c52bcb23 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2024/02/19 14:54 linux-5.15.y 6139f2a02fe0 3af7dd65 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/12/03 08:16 linux-5.15.y 9b91d36ba301 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/08/24 05:15 linux-5.15.y f6f7927ac664 4d7ae7ab .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/07/17 13:52 linux-5.15.y d54cfc420586 20f8b3c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/07/07 05:34 linux-5.15.y d54cfc420586 22ae5830 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/07/06 01:06 linux-5.15.y d54cfc420586 ba5dba36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/06/29 14:02 linux-5.15.y 4af60700a60c 134ddc02 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/06/19 17:52 linux-5.15.y 471e639e59d1 d521bc56 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/06/18 10:05 linux-5.15.y 471e639e59d1 f3921d4d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/06/15 15:30 linux-5.15.y 471e639e59d1 90d4044e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/06/02 00:42 linux-5.15.y 0ab06468cbd1 a4ae4f42 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/05/31 21:38 linux-5.15.y 0ab06468cbd1 babc4389 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/05/02 23:19 linux-5.15.y 8a7f2a5c5aa1 48e0a81d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
2023/04/09 06:26 linux-5.15.y d86dfc4d95cd 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in jfs_flush_journal
* Struck through repros no longer work on HEAD.