| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <68ef030a.050a0220.91a22.022a.GAE@google.com> Date: Tue, 14 Oct 2025 19:12:26 -0700 From: syzbot <syzbot+6b156e132970e550194c@...kaller.appspotmail.com> To: agruenba@...hat.com, gfs2@...ts.linux.dev, linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com Subject: [syzbot] [gfs2?] general protection fault in gfs2_log_is_empty Hello, syzbot found the following issue on: HEAD commit: 52ba76324a9d Add linux-next specific files for 20251013 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=1750bb34580000 kernel config: https://syzkaller.appspot.com/x/.config?x=99cb6b007a8889ef dashboard link: https://syzkaller.appspot.com/bug?extid=6b156e132970e550194c compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=132af304580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12cd7892580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/1729256319ee/disk-52ba7632.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/a3152cfcba7c/vmlinux-52ba7632.xz kernel image: https://storage.googleapis.com/syzbot-assets/4065a3b3d959/bzImage-52ba7632.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/e665a3c68fcf/mount_0.gz fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=13085dcd980000) IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+6b156e132970e550194c@...kaller.appspotmail.com Oops: general protection fault, probably for non-canonical address 0xdffffc0000000011: 0000 [#1] SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000088-0x000000000000008f] CPU: 0 UID: 0 PID: 5825 Comm: kworker/0:3 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025 Workqueue: events gfs2_withdraw_func RIP: 0010:gfs2_log_is_empty+0x73/0xd0 fs/gfs2/log.c:430 Code: f0 09 00 00 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 cd f9 28 fe 41 be 8c 00 00 00 4c 03 33 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 38 84 c0 75 34 41 8b 1e 89 ef 89 de e8 c8 51 c3 fd 39 RSP: 0018:ffffc9000407f8d8 EFLAGS: 00010207 RAX: 0000000000000011 RBX: ffff88806848c9f0 RCX: ffffffff83fcf3b0 RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff88806848cd70 RBP: 0000000000001000 R08: ffff88806848cd73 R09: 1ffff1100d0919ae R10: dffffc0000000000 R11: ffffed100d0919af R12: 1ffff9200080ff24 R13: 1ffff1100d091800 R14: 000000000000008c R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff888125d08000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff340164000 CR3: 000000007a948000 CR4: 00000000003526f0 Call Trace: <TASK> do_withdraw+0x15f/0x320 fs/gfs2/util.c:139 gfs2_withdraw_func+0x2f3/0x430 fs/gfs2/util.c:-1 process_one_work kernel/workqueue.c:3263 [inline] process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427 kthread+0x711/0x8a0 kernel/kthread.c:463 ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:gfs2_log_is_empty+0x73/0xd0 fs/gfs2/log.c:430 Code: f0 09 00 00 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 cd f9 28 fe 41 be 8c 00 00 00 4c 03 33 4c 89 f0 48 c1 e8 03 <42> 0f b6 04 38 84 c0 75 34 41 8b 1e 89 ef 89 de e8 c8 51 c3 fd 39 RSP: 0018:ffffc9000407f8d8 EFLAGS: 00010207 RAX: 0000000000000011 RBX: ffff88806848c9f0 RCX: ffffffff83fcf3b0 RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff88806848cd70 RBP: 0000000000001000 R08: ffff88806848cd73 R09: 1ffff1100d0919ae R10: dffffc0000000000 R11: ffffed100d0919af R12: 1ffff9200080ff24 R13: 1ffff1100d091800 R14: 000000000000008c R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff888125d08000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff340164000 CR3: 0000000029b98000 CR4: 00000000003526f0 ---------------- Code disassembly (best guess): 0: f0 09 00 lock or %eax,(%rax) 3: 00 48 89 add %cl,-0x77(%rax) 6: d8 48 c1 fmuls -0x3f(%rax) 9: e8 03 42 80 3c call 0x3c804211 e: 38 00 cmp %al,(%rax) 10: 74 08 je 0x1a 12: 48 89 df mov %rbx,%rdi 15: e8 cd f9 28 fe call 0xfe28f9e7 1a: 41 be 8c 00 00 00 mov $0x8c,%r14d 20: 4c 03 33 add (%rbx),%r14 23: 4c 89 f0 mov %r14,%rax 26: 48 c1 e8 03 shr $0x3,%rax * 2a: 42 0f b6 04 38 movzbl (%rax,%r15,1),%eax <-- trapping instruction 2f: 84 c0 test %al,%al 31: 75 34 jne 0x67 33: 41 8b 1e mov (%r14),%ebx 36: 89 ef mov %ebp,%edi 38: 89 de mov %ebx,%esi 3a: e8 c8 51 c3 fd call 0xfdc35207 3f: 39 .byte 0x39 --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@...glegroups.com. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
Powered by blists - more mailing lists