Hello,
syzbot found the following issue on:
HEAD commit: dc5c83b7f5f8 Linux 6.1.178
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=126e7746580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=872c04466179833f
dashboard link:
https://syzkaller.appspot.com/bug?extid=0dc33bac91300aa25c34
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/96393e4697a3/disk-dc5c83b7.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/0d4afce44fab/vmlinux-dc5c83b7.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/4787e310d875/Image-dc5c83b7.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+0dc33b...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 24 at net/ceph/messenger_v2.c:2940 populate_in_iter net/ceph/messenger_v2.c:2940 [inline]
WARNING: CPU: 1 PID: 24 at net/ceph/messenger_v2.c:2940 ceph_con_v2_try_read+0x5c10/0x5d80 net/ceph/messenger_v2.c:2970
Modules linked in:
CPU: 1 PID: 24 Comm: kworker/1:1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026
Workqueue: ceph-msgr ceph_con_workfn
pstate: 82400005 (Nzcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : populate_in_iter net/ceph/messenger_v2.c:2940 [inline]
pc : ceph_con_v2_try_read+0x5c10/0x5d80 net/ceph/messenger_v2.c:2970
lr : populate_in_iter net/ceph/messenger_v2.c:2940 [inline]
lr : ceph_con_v2_try_read+0x5c10/0x5d80 net/ceph/messenger_v2.c:2970
sp : ffff80001cc37780
x29: ffff80001cc37ad0 x28: dfff800000000000 x27: ffff80001cc37860
x26: 00000000000000f8 x25: ffff0000db094440 x24: ffff0000db094a10
x23: 0000000000000000 x22: 1fffe0001b6128d8 x21: ffff0000db0946c0
x20: ffff0000db094428 x19: ffff700003986f0c x18: 0000000000000000
x17: ffff80018a0de000 x16: ffff8000082dd244 x15: 0000000000000000
x14: 0000000000000006 x13: 0000000000000000 x12: 0a32762068706563
x11: ff008000117e877c x10: 0000000000000000 x9 : ffff8000117e877c
x8 : ffff0000c0a60000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
x2 : ffff0000db0946d8 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
populate_in_iter net/ceph/messenger_v2.c:2940 [inline]
ceph_con_v2_try_read+0x5c10/0x5d80 net/ceph/messenger_v2.c:2970
ceph_con_workfn+0x16c/0xdcc net/ceph/messenger.c:1503
process_one_work+0x7e4/0x13bc kernel/workqueue.c:2292
worker_thread+0x8cc/0xfe8 kernel/workqueue.c:2439
kthread+0x254/0x2e0 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
irq event stamp: 45680
hardirqs last enabled at (45679): [<ffff8000081ad57c>] __local_bh_enable_ip+0x1f8/0x37c kernel/softirq.c:426
hardirqs last disabled at (45680): [<ffff800011b8c77c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (45678): [<ffff80000fe7fe84>] spin_unlock_bh include/linux/spinlock.h:396 [inline]
softirqs last enabled at (45678): [<ffff80000fe7fe84>] release_sock+0x16c/0x1bc net/core/sock.c:3531
softirqs last disabled at (45676): [<ffff80000fe7fd4c>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (45676): [<ffff80000fe7fd4c>] release_sock+0x34/0x1bc net/core/sock.c:3518
---[ end trace 0000000000000000 ]---
libceph: mon0 (2)
127.0.0.1:6789 read processing error
---
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