Hello,
syzbot found the following issue on:
HEAD commit: fb28aa725e05 Linux 6.1.180
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=138263b9580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=872c04466179833f
dashboard link:
https://syzkaller.appspot.com/bug?extid=2c455222b38ef24a567c
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/d420eb944682/disk-fb28aa72.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/affae450ab23/vmlinux-fb28aa72.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/b9e6919ed519/Image-fb28aa72.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+2c4552...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 7 at net/ceph/messenger_v1.c:912 process_connect net/ceph/messenger_v1.c:911 [inline]
WARNING: CPU: 0 PID: 7 at net/ceph/messenger_v1.c:912 ceph_con_v1_try_read+0x26e4/0x5354 net/ceph/messenger_v1.c:1294
Modules linked in:
CPU: 0 PID: 7 Comm: kworker/0:0 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 : process_connect net/ceph/messenger_v1.c:911 [inline]
pc : ceph_con_v1_try_read+0x26e4/0x5354 net/ceph/messenger_v1.c:1294
lr : process_connect net/ceph/messenger_v1.c:911 [inline]
lr : ceph_con_v1_try_read+0x26e4/0x5354 net/ceph/messenger_v1.c:1294
sp : ffff80001cb17140
x29: ffff80001cb17ad0 x28: 2f018fb87aa4aafe x27: ffff0000de154428
x26: dfff800000000000 x25: f8f8f8f8f8f8f8f8 x24: 0000000000000000
x23: 0000000000000001 x22: ffff0000de1548c0 x21: ffff0000de154440
x20: ffff700003962e6c x19: ffff0000de1548bc x18: 1fffe00033e7277e
x17: ffff80001537d000 x16: ffff8000082dd248 x15: 0000000000000000
x14: 000000000000000d x13: 0000000000ff0100 x12: ffff800017cebef8
x11: ff008000117d9c4c x10: 0000000000000000 x9 : ffff8000117d9c4c
x8 : ffff0000c09a3800 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000010
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000001
Call trace:
process_connect net/ceph/messenger_v1.c:911 [inline]
ceph_con_v1_try_read+0x26e4/0x5354 net/ceph/messenger_v1.c:1294
ceph_con_workfn+0x1b0/0xdcc net/ceph/messenger.c:1505
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: 47056
hardirqs last enabled at (47055): [<ffff8000081ad57c>] __local_bh_enable_ip+0x1f8/0x37c kernel/softirq.c:426
hardirqs last disabled at (47056): [<ffff800011b8c2bc>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (47054): [<ffff80000fe7f9c4>] spin_unlock_bh include/linux/spinlock.h:396 [inline]
softirqs last enabled at (47054): [<ffff80000fe7f9c4>] release_sock+0x16c/0x1bc net/core/sock.c:3531
softirqs last disabled at (47052): [<ffff80000fe7f88c>] spin_lock_bh include/linux/spinlock.h:356 [inline]
softirqs last disabled at (47052): [<ffff80000fe7f88c>] release_sock+0x34/0x1bc net/core/sock.c:3518
---[ end trace 0000000000000000 ]---
libceph: read_partial_message bad hdr crc 552194265 != expected 671088640
libceph: mon0 (1)
127.0.0.1:6789 bad crc/signature
---
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