[moderation] [bcachefs?] general protection fault in get_work_pool (3)

5 views
Skip to first unread message

syzbot

unread,
Apr 14, 2025, 5:49:31 PM4/14/25
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 2eb959eeecc6 Merge tag 'for-linus-6.15a-rc2-tag' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17259d78580000
kernel config: https://syzkaller.appspot.com/x/.config?x=fb8650d88e9fb80f
dashboard link: https://syzkaller.appspot.com/bug?extid=76ff05d98d70e40c6acc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [kent.ov...@linux.dev linux-b...@vger.kernel.org linux-...@vger.kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/90f3f40b3733/disk-2eb959ee.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e4ce9660a8bb/vmlinux-2eb959ee.xz
kernel image: https://storage.googleapis.com/syzbot-assets/05464811fdfe/bzImage-2eb959ee.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+76ff05...@syzkaller.appspotmail.com

Oops: general protection fault, probably for non-canonical address 0xe003fbfffff80000: 0000 [#1] SMP KASAN PTI
KASAN: maybe wild-memory-access in range [0x001fffffffc00000-0x001fffffffc00007]
CPU: 0 UID: 0 PID: 8209 Comm: syz-executor Not tainted 6.15.0-rc1-syzkaller-00095-g2eb959eeecc6 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:get_work_pool+0xea/0x180 kernel/workqueue.c:887
Code: de e8 7a 7a 38 00 81 fb ff ff ff 7f 75 37 e8 8d 75 38 00 31 c0 eb 25 e8 84 75 38 00 48 81 e3 00 fe ff ff 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 df e8 c7 0c a0 00 48 8b 03 5b 41 5e 5d
RSP: 0018:ffffc90003357960 EFLAGS: 00010206
RAX: 0003fffffff80000 RBX: 001fffffffc00000 RCX: ffff888025785a00
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffff818adef9 R09: 1ffffd1ffff8fb99
R10: dffffc0000000000 R11: fffff91ffff8fb9a R12: ffffe8ffffc7dce0
R13: 1ffffd1ffff8fb9c R14: dffffc0000000000 R15: ffffffff93657020
FS: 000055557f5f6500(0000) GS:ffff888124fc9000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000008000 CR3: 000000001296a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
start_flush_work kernel/workqueue.c:4151 [inline]
__flush_work+0x19a/0xc60 kernel/workqueue.c:4208
rcu_pending_exit+0x4c1/0x7b0 fs/bcachefs/rcu_pending.c:621
bch2_fs_btree_key_cache_exit+0x8d8/0xa00 fs/bcachefs/btree_key_cache.c:783
__bch2_fs_free fs/bcachefs/super.c:576 [inline]
bch2_fs_release+0x220/0x7d0 fs/bcachefs/super.c:631
kobject_cleanup lib/kobject.c:689 [inline]
kobject_release lib/kobject.c:720 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x22f/0x480 lib/kobject.c:737
deactivate_locked_super+0xc4/0x130 fs/super.c:473
cleanup_mnt+0x422/0x4c0 fs/namespace.c:1435
task_work_run+0x251/0x310 kernel/task_work.c:227
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x13f/0x340 kernel/entry/common.c:218
do_syscall_64+0x100/0x230 arch/x86/entry/syscall_64.c:100
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f6f5738e497
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffe740f3438 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f6f5740e51c RCX: 00007f6f5738e497
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffe740f34f0
RBP: 00007ffe740f34f0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffe740f4580
R13: 00007f6f5740e51c R14: 00000000000425ef R15: 00007ffe740f45c0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:get_work_pool+0xea/0x180 kernel/workqueue.c:887
Code: de e8 7a 7a 38 00 81 fb ff ff ff 7f 75 37 e8 8d 75 38 00 31 c0 eb 25 e8 84 75 38 00 48 81 e3 00 fe ff ff 48 89 d8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 df e8 c7 0c a0 00 48 8b 03 5b 41 5e 5d
RSP: 0018:ffffc90003357960 EFLAGS: 00010206
RAX: 0003fffffff80000 RBX: 001fffffffc00000 RCX: ffff888025785a00
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffffff818adef9 R09: 1ffffd1ffff8fb99
R10: dffffc0000000000 R11: fffff91ffff8fb9a R12: ffffe8ffffc7dce0
R13: 1ffffd1ffff8fb9c R14: dffffc0000000000 R15: ffffffff93657020
FS: 000055557f5f6500(0000) GS:ffff888124fc9000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffcd8cf0fe8 CR3: 000000001296a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: de e8 fsubrp %st,%st(0)
2: 7a 7a jp 0x7e
4: 38 00 cmp %al,(%rax)
6: 81 fb ff ff ff 7f cmp $0x7fffffff,%ebx
c: 75 37 jne 0x45
e: e8 8d 75 38 00 call 0x3875a0
13: 31 c0 xor %eax,%eax
15: eb 25 jmp 0x3c
17: e8 84 75 38 00 call 0x3875a0
1c: 48 81 e3 00 fe ff ff and $0xfffffffffffffe00,%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 30 00 cmpb $0x0,(%rax,%r14,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 c7 0c a0 00 call 0xa00d00
39: 48 8b 03 mov (%rbx),%rax
3c: 5b pop %rbx
3d: 41 5e pop %r14
3f: 5d pop %rbp


---
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 syzk...@googlegroups.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 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

syzbot

unread,
Jul 14, 2025, 1:41:16 PM7/14/25
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages