[v5.15] inconsistent lock state in x25_kill_by_neigh
16 views
Skip to first unread message
syzbot
Aug 28, 2026, 8:21:25 PMAug 28
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 28c35638ec51 Linux 5.15.219
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17d7ce25580000
kernel config: https://syzkaller.appspot.com/x/.config?x=21845b39f8fc6be8
dashboard link: https://syzkaller.appspot.com/bug?extid=268ee2c437483f50f7aa
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/baa03a1911e6/disk-28c35638.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fc932057f792/vmlinux-28c35638.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d0d901fc7bd/bzImage-28c35638.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+268ee2...@syzkaller.appspotmail.com
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ksoftirqd/1/20 [HC0[0]:SC1[1]:HE1:SE0] takes:
ffff888076882120 (sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1744 [inline]
ffff888076882120 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
{SOFTIRQ-ON-W} state was registered at:
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
lock_sock_nested+0x44/0x100 net/core/sock.c:3258
lock_sock include/net/sock.h:1744 [inline]
x25_bind+0x18a/0x3b0 net/x25/af_x25.c:698
__sys_bind+0x2e9/0x3e0 net/socket.c:1730
__do_sys_bind net/socket.c:1741 [inline]
__se_sys_bind net/socket.c:1739 [inline]
__x64_sys_bind+0x76/0x80 net/socket.c:1739
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
irq event stamp: 409738
hardirqs last enabled at (409738): [<ffffffff814936e6>] __local_bh_enable_ip+0x136/0x1c0 kernel/softirq.c:406
hardirqs last disabled at (409737): [<ffffffff81493687>] __local_bh_enable_ip+0xd7/0x1c0 kernel/softirq.c:383
softirqs last enabled at (409338): [<ffffffff814961c4>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
softirqs last disabled at (409381): [<ffffffff814961c4>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(sk_lock-AF_X25);
<Interrupt>
lock(sk_lock-AF_X25);
*** DEADLOCK ***
1 lock held by ksoftirqd/1/20:
#0: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:313
stack backtrace:
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
valid_state+0x13b/0x1d0 kernel/locking/lockdep.c:3932
mark_lock_irq+0xa9/0x900 kernel/locking/lockdep.c:4135
mark_lock+0x208/0x320 kernel/locking/lockdep.c:4591
mark_usage kernel/locking/lockdep.c:-1 [inline]
__lock_acquire+0xc63/0x7b50 kernel/locking/lockdep.c:4966
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
lock_sock_nested+0x44/0x100 net/core/sock.c:3258
lock_sock include/net/sock.h:1744 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
x25_lapb_receive_frame+0x19d/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5551 [inline]
netif_receive_skb_core+0x149/0x210 net/core/dev.c:5576
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x430 net/core/dev.c:7101
napi_poll net/core/dev.c:7168 [inline]
net_rx_action+0x522/0xa80 net/core/dev.c:7258
handle_softirqs+0x336/0x830 kernel/softirq.c:576
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
smpboot_thread_fn+0x520/0x990 kernel/smpboot.c:164
kthread+0x42e/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
BUG: sleeping function called from invalid context at net/core/sock.c:3260
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 20, name: ksoftirqd/1
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff81493a7d>] softirq_handle_begin kernel/softirq.c:414 [inline]
[<ffffffff81493a7d>] handle_softirqs+0xfd/0x830 kernel/softirq.c:552
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
___might_sleep+0x493/0x610 kernel/sched/core.c:9658
lock_sock_nested+0x5b/0x100 net/core/sock.c:3260
lock_sock include/net/sock.h:1744 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
x25_lapb_receive_frame+0x19d/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5551 [inline]
netif_receive_skb_core+0x149/0x210 net/core/dev.c:5576
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x430 net/core/dev.c:7101
napi_poll net/core/dev.c:7168 [inline]
net_rx_action+0x522/0xa80 net/core/dev.c:7258
handle_softirqs+0x336/0x830 kernel/softirq.c:576
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
smpboot_thread_fn+0x520/0x990 kernel/smpboot.c:164
kthread+0x42e/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
---
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 found the following issue on:
HEAD commit: 28c35638ec51 Linux 5.15.219
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17d7ce25580000
kernel config: https://syzkaller.appspot.com/x/.config?x=21845b39f8fc6be8
dashboard link: https://syzkaller.appspot.com/bug?extid=268ee2c437483f50f7aa
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/baa03a1911e6/disk-28c35638.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fc932057f792/vmlinux-28c35638.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d0d901fc7bd/bzImage-28c35638.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+268ee2...@syzkaller.appspotmail.com
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ksoftirqd/1/20 [HC0[0]:SC1[1]:HE1:SE0] takes:
ffff888076882120 (sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1744 [inline]
ffff888076882120 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
{SOFTIRQ-ON-W} state was registered at:
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
lock_sock_nested+0x44/0x100 net/core/sock.c:3258
lock_sock include/net/sock.h:1744 [inline]
x25_bind+0x18a/0x3b0 net/x25/af_x25.c:698
__sys_bind+0x2e9/0x3e0 net/socket.c:1730
__do_sys_bind net/socket.c:1741 [inline]
__se_sys_bind net/socket.c:1739 [inline]
__x64_sys_bind+0x76/0x80 net/socket.c:1739
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
irq event stamp: 409738
hardirqs last enabled at (409738): [<ffffffff814936e6>] __local_bh_enable_ip+0x136/0x1c0 kernel/softirq.c:406
hardirqs last disabled at (409737): [<ffffffff81493687>] __local_bh_enable_ip+0xd7/0x1c0 kernel/softirq.c:383
softirqs last enabled at (409338): [<ffffffff814961c4>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
softirqs last disabled at (409381): [<ffffffff814961c4>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(sk_lock-AF_X25);
<Interrupt>
lock(sk_lock-AF_X25);
*** DEADLOCK ***
1 lock held by ksoftirqd/1/20:
#0: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:313
stack backtrace:
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
valid_state+0x13b/0x1d0 kernel/locking/lockdep.c:3932
mark_lock_irq+0xa9/0x900 kernel/locking/lockdep.c:4135
mark_lock+0x208/0x320 kernel/locking/lockdep.c:4591
mark_usage kernel/locking/lockdep.c:-1 [inline]
__lock_acquire+0xc63/0x7b50 kernel/locking/lockdep.c:4966
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
lock_sock_nested+0x44/0x100 net/core/sock.c:3258
lock_sock include/net/sock.h:1744 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
x25_lapb_receive_frame+0x19d/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5551 [inline]
netif_receive_skb_core+0x149/0x210 net/core/dev.c:5576
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x430 net/core/dev.c:7101
napi_poll net/core/dev.c:7168 [inline]
net_rx_action+0x522/0xa80 net/core/dev.c:7258
handle_softirqs+0x336/0x830 kernel/softirq.c:576
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
smpboot_thread_fn+0x520/0x990 kernel/smpboot.c:164
kthread+0x42e/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
BUG: sleeping function called from invalid context at net/core/sock.c:3260
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 20, name: ksoftirqd/1
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff81493a7d>] softirq_handle_begin kernel/softirq.c:414 [inline]
[<ffffffff81493a7d>] handle_softirqs+0xfd/0x830 kernel/softirq.c:552
CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
___might_sleep+0x493/0x610 kernel/sched/core.c:9658
lock_sock_nested+0x5b/0x100 net/core/sock.c:3260
lock_sock include/net/sock.h:1744 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
x25_lapb_receive_frame+0x19d/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5551 [inline]
netif_receive_skb_core+0x149/0x210 net/core/dev.c:5576
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x430 net/core/dev.c:7101
napi_poll net/core/dev.c:7168 [inline]
net_rx_action+0x522/0xa80 net/core/dev.c:7258
handle_softirqs+0x336/0x830 kernel/softirq.c:576
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943
smpboot_thread_fn+0x520/0x990 kernel/smpboot.c:164
kthread+0x42e/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
---
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
Aug 28, 2026, 8:46:34 PMAug 28
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d64a499eea6b Linux 6.1.186
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11344c15580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=f4e24b88b1f7abcfbfbd
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/75ba0c7f69a9/disk-d64a499e.raw.xz
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/f589e88693be/vmlinux-d64a499e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/276c04874097/bzImage-d64a499e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ffff888055dae130 (sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1805 [inline]
ffff888055dae130 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1783
{SOFTIRQ-ON-W} state was registered at:
lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
lock_sock_nested+0x44/0x100 net/core/sock.c:3504
lock_sock include/net/sock.h:1805 [inline]
x25_bind+0x1aa/0x3e0 net/x25/af_x25.c:698
__sys_bind+0x2e9/0x3e0 net/socket.c:1811
__do_sys_bind net/socket.c:1822 [inline]
__se_sys_bind net/socket.c:1820 [inline]
__do_sys_bind net/socket.c:1822 [inline]
__x64_sys_bind+0x76/0x80 net/socket.c:1820
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
irq event stamp: 1637710
hardirqs last enabled at (1637710): [<ffffffff814f3bd6>] __local_bh_enable_ip+0x136/0x1c0 kernel/softirq.c:426
hardirqs last disabled at (1637709): [<ffffffff814f3b77>] __local_bh_enable_ip+0xd7/0x1c0 kernel/softirq.c:403
softirqs last enabled at (1637630): [<ffffffff814f6b64>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
softirqs last disabled at (1637635): [<ffffffff814f6b64>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(sk_lock-AF_X25);
<Interrupt>
lock(sk_lock-AF_X25);
*** DEADLOCK ***
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: netif_receive_skb_core+0x30/0x230 net/core/dev.c:5643
stack backtrace:
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
Call Trace:
<TASK>
valid_state+0x13b/0x1d0 kernel/locking/lockdep.c:3974
mark_lock_irq+0xa9/0x900 kernel/locking/lockdep.c:4177
mark_lock+0x208/0x320 kernel/locking/lockdep.c:4633
mark_usage kernel/locking/lockdep.c:-1 [inline]
__lock_acquire+0xce0/0x7c40 kernel/locking/lockdep.c:5017
lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
lock_sock_nested+0x44/0x100 net/core/sock.c:3504
lock_sock include/net/sock.h:1805 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1783
x25_lapb_receive_frame+0x1a3/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5619 [inline]
netif_receive_skb_core+0x166/0x230 net/core/dev.c:5644
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x460 net/core/dev.c:6628
napi_poll net/core/dev.c:6695 [inline]
net_rx_action+0x622/0xbc0 net/core/dev.c:6809
handle_softirqs+0x291/0x910 kernel/softirq.c:596
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
smpboot_thread_fn+0x667/0xa30 kernel/smpboot.c:164
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
BUG: sleeping function called from invalid context at net/core/sock.c:3506
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 21, name: ksoftirqd/1
preempt_count: 100, expected: 0
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff814f3f6d>] softirq_handle_begin kernel/softirq.c:434 [inline]
Preemption disabled at:
[<ffffffff814f3f6d>] handle_softirqs+0xfd/0x910 kernel/softirq.c:572
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
Call Trace:
<TASK>
__might_resched+0x489/0x5f0 kernel/sched/core.c:9970
lock_sock_nested+0x59/0x100 net/core/sock.c:3506
lock_sock include/net/sock.h:1805 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1783
x25_lapb_receive_frame+0x1a3/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5619 [inline]
netif_receive_skb_core+0x166/0x230 net/core/dev.c:5644
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x460 net/core/dev.c:6628
napi_poll net/core/dev.c:6695 [inline]
net_rx_action+0x622/0xbc0 net/core/dev.c:6809
handle_softirqs+0x291/0x910 kernel/softirq.c:596
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
smpboot_thread_fn+0x667/0xa30 kernel/smpboot.c:164
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
syzbot
Aug 29, 2026, 12:35:30 PMAug 29
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: a4a971135a2f Linux 6.6.155
syzbot found the following issue on:
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17f2bd79580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7be9809cedd6b69c
dashboard link: https://syzkaller.appspot.com/bug?extid=628a7c9a2093bde0446b
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6bc048ae6cd8/disk-a4a97113.raw.xz
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/01ff4e23fd69/vmlinux-a4a97113.xz
kernel image: https://storage.googleapis.com/syzbot-assets/00a94362667a/bzImage-a4a97113.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ffff888021cea130 (sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1780 [inline]
ffff888021cea130 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x10d/0x250 net/x25/af_x25.c:1782
{SOFTIRQ-ON-W} state was registered at:
lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
lock_sock_nested+0x48/0x100 net/core/sock.c:3543
lock_sock include/net/sock.h:1780 [inline]
x25_bind+0x20a/0x460 net/x25/af_x25.c:698
__sys_bind+0x2f0/0x3f0 net/socket.c:1856
__do_sys_bind net/socket.c:1867 [inline]
__se_sys_bind net/socket.c:1865 [inline]
__x64_sys_bind+0x7a/0x90 net/socket.c:1865
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
irq event stamp: 898656
hardirqs last enabled at (898656): [<ffffffff8152ccba>] __local_bh_enable_ip+0x13a/0x1c0 kernel/softirq.c:411
hardirqs last disabled at (898655): [<ffffffff8152cc5b>] __local_bh_enable_ip+0xdb/0x1c0 kernel/softirq.c:388
softirqs last enabled at (898436): [<ffffffff8152f928>] run_ksoftirqd+0xa8/0x100 kernel/softirq.c:950
softirqs last disabled at (898441): [<ffffffff8152f928>] run_ksoftirqd+0xa8/0x100 kernel/softirq.c:950
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(sk_lock-AF_X25);
<Interrupt>
lock(sk_lock-AF_X25);
*** DEADLOCK ***
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: netif_receive_skb_core+0x34/0x230 net/core/dev.c:5688
stack backtrace:
CPU: 1 PID: 22 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
Call Trace:
<TASK>
valid_state+0x13b/0x1d0 kernel/locking/lockdep.c:4013
mark_lock_irq+0xad/0x900 kernel/locking/lockdep.c:4216
mark_lock+0x208/0x320 kernel/locking/lockdep.c:4678
mark_usage kernel/locking/lockdep.c:-1 [inline]
__lock_acquire+0xcfc/0x7d80 kernel/locking/lockdep.c:5091
lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
lock_sock_nested+0x48/0x100 net/core/sock.c:3543
lock_sock include/net/sock.h:1780 [inline]
x25_kill_by_neigh+0x10d/0x250 net/x25/af_x25.c:1782
x25_lapb_receive_frame+0x1a7/0xef0 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5664 [inline]
netif_receive_skb_core+0x16a/0x230 net/core/dev.c:5689
lapbeth_napi_poll+0x42/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x460 net/core/dev.c:6668
napi_poll net/core/dev.c:6735 [inline]
net_rx_action+0x65f/0xcc0 net/core/dev.c:6871
handle_softirqs+0x27d/0x820 kernel/softirq.c:578
run_ksoftirqd+0xa8/0x100 kernel/softirq.c:950
smpboot_thread_fn+0x651/0x9f0 kernel/smpboot.c:164
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
BUG: sleeping function called from invalid context at net/core/sock.c:3545
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 22, name: ksoftirqd/1
preempt_count: 100, expected: 0
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff8152cfe1>] softirq_handle_begin kernel/softirq.c:419 [inline]
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff8152cfe1>] handle_softirqs+0x101/0x820 kernel/softirq.c:554
CPU: 1 PID: 22 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
Call Trace:
<TASK>
__might_resched+0x48d/0x5f0 kernel/sched/core.c:10212
lock_sock_nested+0x5d/0x100 net/core/sock.c:3545
lock_sock include/net/sock.h:1780 [inline]
x25_kill_by_neigh+0x10d/0x250 net/x25/af_x25.c:1782
x25_lapb_receive_frame+0x1a7/0xef0 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5664 [inline]
netif_receive_skb_core+0x16a/0x230 net/core/dev.c:5689
lapbeth_napi_poll+0x42/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x460 net/core/dev.c:6668
napi_poll net/core/dev.c:6735 [inline]
net_rx_action+0x65f/0xcc0 net/core/dev.c:6871
handle_softirqs+0x27d/0x820 kernel/softirq.c:578
run_ksoftirqd+0xa8/0x100 kernel/softirq.c:950
smpboot_thread_fn+0x651/0x9f0 kernel/smpboot.c:164
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
syzbot
Aug 29, 2026, 2:02:37 PMAug 29
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: a4a971135a2f Linux 6.6.155
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=129d1d79580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12167d49580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6bc048ae6cd8/disk-a4a97113.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/01ff4e23fd69/vmlinux-a4a97113.xz
kernel image: https://storage.googleapis.com/syzbot-assets/00a94362667a/bzImage-a4a97113.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+628a7c...@syzkaller.appspotmail.com
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ksoftirqd/0/16 [HC0[0]:SC1[1]:HE1:SE0] takes:
ffff88807a9cc130 (sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1780 [inline]
ffff88807a9cc130 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x10d/0x250 net/x25/af_x25.c:1782
hardirqs last enabled at (543908): [<ffffffff8152ccba>] __local_bh_enable_ip+0x13a/0x1c0 kernel/softirq.c:411
hardirqs last disabled at (543907): [<ffffffff8152cc5b>] __local_bh_enable_ip+0xdb/0x1c0 kernel/softirq.c:388
softirqs last enabled at (543758): [<ffffffff8152f928>] run_ksoftirqd+0xa8/0x100 kernel/softirq.c:950
softirqs last disabled at (543763): [<ffffffff8152f928>] run_ksoftirqd+0xa8/0x100 kernel/softirq.c:950
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(sk_lock-AF_X25);
<Interrupt>
lock(sk_lock-AF_X25);
*** DEADLOCK ***
1 lock held by ksoftirqd/0/16:
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 16, name: ksoftirqd/0
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
HEAD commit: a4a971135a2f Linux 6.6.155
git tree: linux-6.6.y
kernel config: https://syzkaller.appspot.com/x/.config?x=7be9809cedd6b69c
dashboard link: https://syzkaller.appspot.com/bug?extid=628a7c9a2093bde0446b
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1347cc15580000
dashboard link: https://syzkaller.appspot.com/bug?extid=628a7c9a2093bde0446b
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12167d49580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6bc048ae6cd8/disk-a4a97113.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/01ff4e23fd69/vmlinux-a4a97113.xz
kernel image: https://storage.googleapis.com/syzbot-assets/00a94362667a/bzImage-a4a97113.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+628a7c...@syzkaller.appspotmail.com
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ffff88807a9cc130 (sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1780 [inline]
ffff88807a9cc130 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x10d/0x250 net/x25/af_x25.c:1782
{SOFTIRQ-ON-W} state was registered at:
lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
lock_sock_nested+0x48/0x100 net/core/sock.c:3543
lock_sock include/net/sock.h:1780 [inline]
x25_bind+0x20a/0x460 net/x25/af_x25.c:698
__sys_bind+0x2f0/0x3f0 net/socket.c:1856
__do_sys_bind net/socket.c:1867 [inline]
__se_sys_bind net/socket.c:1865 [inline]
__x64_sys_bind+0x7a/0x90 net/socket.c:1865
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
irq event stamp: 543908
lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
lock_sock_nested+0x48/0x100 net/core/sock.c:3543
lock_sock include/net/sock.h:1780 [inline]
x25_bind+0x20a/0x460 net/x25/af_x25.c:698
__sys_bind+0x2f0/0x3f0 net/socket.c:1856
__do_sys_bind net/socket.c:1867 [inline]
__se_sys_bind net/socket.c:1865 [inline]
__x64_sys_bind+0x7a/0x90 net/socket.c:1865
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
hardirqs last enabled at (543908): [<ffffffff8152ccba>] __local_bh_enable_ip+0x13a/0x1c0 kernel/softirq.c:411
hardirqs last disabled at (543907): [<ffffffff8152cc5b>] __local_bh_enable_ip+0xdb/0x1c0 kernel/softirq.c:388
softirqs last enabled at (543758): [<ffffffff8152f928>] run_ksoftirqd+0xa8/0x100 kernel/softirq.c:950
softirqs last disabled at (543763): [<ffffffff8152f928>] run_ksoftirqd+0xa8/0x100 kernel/softirq.c:950
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(sk_lock-AF_X25);
<Interrupt>
lock(sk_lock-AF_X25);
*** DEADLOCK ***
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: netif_receive_skb_core+0x34/0x230 net/core/dev.c:5688
stack backtrace:
CPU: 0 PID: 16 Comm: ksoftirqd/0 Not tainted syzkaller #0
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: netif_receive_skb_core+0x34/0x230 net/core/dev.c:5688
stack backtrace:
preempt_count: 100, expected: 0
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff8152cfe1>] softirq_handle_begin kernel/softirq.c:419 [inline]
[<ffffffff8152cfe1>] handle_softirqs+0x101/0x820 kernel/softirq.c:554
CPU: 0 PID: 16 Comm: ksoftirqd/0 Not tainted syzkaller #0
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
Preemption disabled at:
[<ffffffff8152cfe1>] softirq_handle_begin kernel/softirq.c:419 [inline]
[<ffffffff8152cfe1>] handle_softirqs+0x101/0x820 kernel/softirq.c:554
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
__might_resched+0x48d/0x5f0 kernel/sched/core.c:10212
lock_sock_nested+0x5d/0x100 net/core/sock.c:3545
lock_sock include/net/sock.h:1780 [inline]
x25_kill_by_neigh+0x10d/0x250 net/x25/af_x25.c:1782
x25_lapb_receive_frame+0x1a7/0xef0 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5664 [inline]
netif_receive_skb_core+0x16a/0x230 net/core/dev.c:5689
lapbeth_napi_poll+0x42/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x460 net/core/dev.c:6668
napi_poll net/core/dev.c:6735 [inline]
net_rx_action+0x65f/0xcc0 net/core/dev.c:6871
handle_softirqs+0x27d/0x820 kernel/softirq.c:578
run_ksoftirqd+0xa8/0x100 kernel/softirq.c:950
smpboot_thread_fn+0x651/0x9f0 kernel/smpboot.c:164
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
---
If you want syzbot to run the reproducer, reply with:
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
__might_resched+0x48d/0x5f0 kernel/sched/core.c:10212
lock_sock_nested+0x5d/0x100 net/core/sock.c:3545
lock_sock include/net/sock.h:1780 [inline]
x25_kill_by_neigh+0x10d/0x250 net/x25/af_x25.c:1782
x25_lapb_receive_frame+0x1a7/0xef0 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5664 [inline]
netif_receive_skb_core+0x16a/0x230 net/core/dev.c:5689
lapbeth_napi_poll+0x42/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x460 net/core/dev.c:6668
napi_poll net/core/dev.c:6735 [inline]
net_rx_action+0x65f/0xcc0 net/core/dev.c:6871
handle_softirqs+0x27d/0x820 kernel/softirq.c:578
run_ksoftirqd+0xa8/0x100 kernel/softirq.c:950
smpboot_thread_fn+0x651/0x9f0 kernel/smpboot.c:164
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
---
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
syzbot
Aug 30, 2026, 12:48:41 AMAug 30
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 28c35638ec51 Linux 5.15.219
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1768ac15580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15fefd49580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/baa03a1911e6/disk-28c35638.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fc932057f792/vmlinux-28c35638.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d0d901fc7bd/bzImage-28c35638.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+268ee2...@syzkaller.appspotmail.com
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
swapper/1/0 [HC0[0]:SC1[1]:HE1:SE0] takes:
ffff888025820120 (sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1744 [inline]
ffff888025820120 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
hardirqs last enabled at (477942): [<ffffffff814936e6>] __local_bh_enable_ip+0x136/0x1c0 kernel/softirq.c:406
hardirqs last disabled at (477941): [<ffffffff81493687>] __local_bh_enable_ip+0xd7/0x1c0 kernel/softirq.c:383
softirqs last enabled at (477632): [<ffffffff814943fb>] __do_softirq kernel/softirq.c:610 [inline]
softirqs last enabled at (477632): [<ffffffff814943fb>] invoke_softirq kernel/softirq.c:450 [inline]
softirqs last enabled at (477632): [<ffffffff814943fb>] __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
softirqs last disabled at (477651): [<ffffffff814943fb>] __do_softirq kernel/softirq.c:610 [inline]
softirqs last disabled at (477651): [<ffffffff814943fb>] invoke_softirq kernel/softirq.c:450 [inline]
softirqs last disabled at (477651): [<ffffffff814943fb>] __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(sk_lock-AF_X25);
<Interrupt>
lock(sk_lock-AF_X25);
*** DEADLOCK ***
1 lock held by swapper/1/0:
invoke_softirq kernel/softirq.c:450 [inline]
__irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:default_idle+0xb/0x10 arch/x86/kernel/process.c:730
Code: b7 48 89 df e8 56 8f f4 f7 eb ad e8 4f ab f6 ff 00 00 cc cc 00 00 cc cc 00 00 cc cc 00 00 cc 66 90 0f 00 2d b7 25 5c 00 fb f4 <c3> 0f 1f 40 00 41 57 41 56 53 49 be 00 00 00 00 00 fc ff df 65 48
RSP: 0018:ffffc90000d67d48 EFLAGS: 000002c2
RAX: cf38a7824ce27400 RBX: ffff888016e98000 RCX: cf38a7824ce27400
RDX: 0000000000000001 RSI: ffffffff8a2b2be0 RDI: ffffffff8a7a43c0
RBP: ffffc90000d67e80 R08: ffff8880b913b30b R09: 1ffff11017227661
R10: dffffc0000000000 R11: ffffed1017227662 R12: 1ffff920001acfb4
R13: dffffc0000000000 R14: 1ffff11002dd3000 R15: 0000000000000000
default_idle_call+0x81/0xc0 kernel/sched/idle.c:112
cpuidle_idle_call kernel/sched/idle.c:202 [inline]
do_idle+0x3a1/0x650 kernel/sched/idle.c:326
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:424
start_secondary+0x32f/0x430 arch/x86/kernel/smpboot.c:281
secondary_startup_64_no_verify+0xb1/0xbb
CPU: 1 PID: 0 Comm: swapper/1 Not tainted syzkaller #0
invoke_softirq kernel/softirq.c:450 [inline]
__irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:default_idle+0xb/0x10 arch/x86/kernel/process.c:730
Code: b7 48 89 df e8 56 8f f4 f7 eb ad e8 4f ab f6 ff 00 00 cc cc 00 00 cc cc 00 00 cc cc 00 00 cc 66 90 0f 00 2d b7 25 5c 00 fb f4 <c3> 0f 1f 40 00 41 57 41 56 53 49 be 00 00 00 00 00 fc ff df 65 48
RSP: 0018:ffffc90000d67d48 EFLAGS: 000002c2
RAX: cf38a7824ce27400 RBX: ffff888016e98000 RCX: cf38a7824ce27400
RDX: 0000000000000001 RSI: ffffffff8a2b2be0 RDI: ffffffff8a7a43c0
RBP: ffffc90000d67e80 R08: ffff8880b913b30b R09: 1ffff11017227661
R10: dffffc0000000000 R11: ffffed1017227662 R12: 1ffff920001acfb4
R13: dffffc0000000000 R14: 1ffff11002dd3000 R15: 0000000000000000
default_idle_call+0x81/0xc0 kernel/sched/idle.c:112
cpuidle_idle_call kernel/sched/idle.c:202 [inline]
do_idle+0x3a1/0x650 kernel/sched/idle.c:326
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:424
start_secondary+0x32f/0x430 arch/x86/kernel/smpboot.c:281
secondary_startup_64_no_verify+0xb1/0xbb
</TASK>
----------------
Code disassembly (best guess):
0: b7 48 mov $0x48,%bh
2: 89 df mov %ebx,%edi
4: e8 56 8f f4 f7 call 0xf7f48f5f
9: eb ad jmp 0xffffffb8
b: e8 4f ab f6 ff call 0xfff6ab5f
10: 00 00 add %al,(%rax)
12: cc int3
13: cc int3
14: 00 00 add %al,(%rax)
16: cc int3
17: cc int3
18: 00 00 add %al,(%rax)
1a: cc int3
1b: cc int3
1c: 00 00 add %al,(%rax)
1e: cc int3
1f: 66 90 xchg %ax,%ax
21: 0f 00 2d b7 25 5c 00 verw 0x5c25b7(%rip) # 0x5c25df
28: fb sti
29: f4 hlt
* 2a: c3 ret <-- trapping instruction
2b: 0f 1f 40 00 nopl 0x0(%rax)
2f: 41 57 push %r15
31: 41 56 push %r14
33: 53 push %rbx
34: 49 be 00 00 00 00 00 movabs $0xdffffc0000000000,%r14
3b: fc ff df
3e: 65 gs
3f: 48 rex.W
HEAD commit: 28c35638ec51 Linux 5.15.219
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=21845b39f8fc6be8
dashboard link: https://syzkaller.appspot.com/bug?extid=268ee2c437483f50f7aa
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10036e25580000
dashboard link: https://syzkaller.appspot.com/bug?extid=268ee2c437483f50f7aa
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15fefd49580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/baa03a1911e6/disk-28c35638.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fc932057f792/vmlinux-28c35638.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2d0d901fc7bd/bzImage-28c35638.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+268ee2...@syzkaller.appspotmail.com
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ffff888025820120 (sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1744 [inline]
ffff888025820120 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
{SOFTIRQ-ON-W} state was registered at:
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
lock_sock_nested+0x44/0x100 net/core/sock.c:3258
lock_sock include/net/sock.h:1744 [inline]
x25_bind+0x18a/0x3b0 net/x25/af_x25.c:698
__sys_bind+0x2e9/0x3e0 net/socket.c:1730
__do_sys_bind net/socket.c:1741 [inline]
__se_sys_bind net/socket.c:1739 [inline]
__x64_sys_bind+0x76/0x80 net/socket.c:1739
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
irq event stamp: 477942
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
lock_sock_nested+0x44/0x100 net/core/sock.c:3258
lock_sock include/net/sock.h:1744 [inline]
x25_bind+0x18a/0x3b0 net/x25/af_x25.c:698
__sys_bind+0x2e9/0x3e0 net/socket.c:1730
__do_sys_bind net/socket.c:1741 [inline]
__se_sys_bind net/socket.c:1739 [inline]
__x64_sys_bind+0x76/0x80 net/socket.c:1739
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
hardirqs last enabled at (477942): [<ffffffff814936e6>] __local_bh_enable_ip+0x136/0x1c0 kernel/softirq.c:406
hardirqs last disabled at (477941): [<ffffffff81493687>] __local_bh_enable_ip+0xd7/0x1c0 kernel/softirq.c:383
softirqs last enabled at (477632): [<ffffffff814943fb>] __do_softirq kernel/softirq.c:610 [inline]
softirqs last enabled at (477632): [<ffffffff814943fb>] invoke_softirq kernel/softirq.c:450 [inline]
softirqs last enabled at (477632): [<ffffffff814943fb>] __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
softirqs last disabled at (477651): [<ffffffff814943fb>] __do_softirq kernel/softirq.c:610 [inline]
softirqs last disabled at (477651): [<ffffffff814943fb>] invoke_softirq kernel/softirq.c:450 [inline]
softirqs last disabled at (477651): [<ffffffff814943fb>] __irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(sk_lock-AF_X25);
<Interrupt>
lock(sk_lock-AF_X25);
*** DEADLOCK ***
#0: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:313
stack backtrace:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted syzkaller #0
stack backtrace:
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<IRQ>
Call Trace:
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
valid_state+0x13b/0x1d0 kernel/locking/lockdep.c:3932
mark_lock_irq+0xa9/0x900 kernel/locking/lockdep.c:4135
mark_lock+0x208/0x320 kernel/locking/lockdep.c:4591
mark_usage kernel/locking/lockdep.c:-1 [inline]
__lock_acquire+0xc63/0x7b50 kernel/locking/lockdep.c:4966
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
lock_sock_nested+0x44/0x100 net/core/sock.c:3258
lock_sock include/net/sock.h:1744 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
x25_lapb_receive_frame+0x19d/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5551 [inline]
netif_receive_skb_core+0x149/0x210 net/core/dev.c:5576
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x430 net/core/dev.c:7101
napi_poll net/core/dev.c:7168 [inline]
net_rx_action+0x522/0xa80 net/core/dev.c:7258
handle_softirqs+0x336/0x830 kernel/softirq.c:576
__do_softirq kernel/softirq.c:610 [inline]
valid_state+0x13b/0x1d0 kernel/locking/lockdep.c:3932
mark_lock_irq+0xa9/0x900 kernel/locking/lockdep.c:4135
mark_lock+0x208/0x320 kernel/locking/lockdep.c:4591
mark_usage kernel/locking/lockdep.c:-1 [inline]
__lock_acquire+0xc63/0x7b50 kernel/locking/lockdep.c:4966
lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
lock_sock_nested+0x44/0x100 net/core/sock.c:3258
lock_sock include/net/sock.h:1744 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
x25_lapb_receive_frame+0x19d/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5551 [inline]
netif_receive_skb_core+0x149/0x210 net/core/dev.c:5576
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x430 net/core/dev.c:7101
napi_poll net/core/dev.c:7168 [inline]
net_rx_action+0x522/0xa80 net/core/dev.c:7258
handle_softirqs+0x336/0x830 kernel/softirq.c:576
invoke_softirq kernel/softirq.c:450 [inline]
__irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:default_idle+0xb/0x10 arch/x86/kernel/process.c:730
Code: b7 48 89 df e8 56 8f f4 f7 eb ad e8 4f ab f6 ff 00 00 cc cc 00 00 cc cc 00 00 cc cc 00 00 cc 66 90 0f 00 2d b7 25 5c 00 fb f4 <c3> 0f 1f 40 00 41 57 41 56 53 49 be 00 00 00 00 00 fc ff df 65 48
RSP: 0018:ffffc90000d67d48 EFLAGS: 000002c2
RAX: cf38a7824ce27400 RBX: ffff888016e98000 RCX: cf38a7824ce27400
RDX: 0000000000000001 RSI: ffffffff8a2b2be0 RDI: ffffffff8a7a43c0
RBP: ffffc90000d67e80 R08: ffff8880b913b30b R09: 1ffff11017227661
R10: dffffc0000000000 R11: ffffed1017227662 R12: 1ffff920001acfb4
R13: dffffc0000000000 R14: 1ffff11002dd3000 R15: 0000000000000000
default_idle_call+0x81/0xc0 kernel/sched/idle.c:112
cpuidle_idle_call kernel/sched/idle.c:202 [inline]
do_idle+0x3a1/0x650 kernel/sched/idle.c:326
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:424
start_secondary+0x32f/0x430 arch/x86/kernel/smpboot.c:281
secondary_startup_64_no_verify+0xb1/0xbb
</TASK>
BUG: sleeping function called from invalid context at net/core/sock.c:3260
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 0, name: swapper/1
BUG: sleeping function called from invalid context at net/core/sock.c:3260
INFO: lockdep is turned off.
Preemption disabled at:
[<0000000000000000>] 0x0
Preemption disabled at:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<IRQ>
Call Trace:
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
___might_sleep+0x493/0x610 kernel/sched/core.c:9658
lock_sock_nested+0x5b/0x100 net/core/sock.c:3260
lock_sock include/net/sock.h:1744 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
x25_lapb_receive_frame+0x19d/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5551 [inline]
netif_receive_skb_core+0x149/0x210 net/core/dev.c:5576
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x430 net/core/dev.c:7101
napi_poll net/core/dev.c:7168 [inline]
net_rx_action+0x522/0xa80 net/core/dev.c:7258
handle_softirqs+0x336/0x830 kernel/softirq.c:576
__do_softirq kernel/softirq.c:610 [inline]
___might_sleep+0x493/0x610 kernel/sched/core.c:9658
lock_sock_nested+0x5b/0x100 net/core/sock.c:3260
lock_sock include/net/sock.h:1744 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1779
x25_lapb_receive_frame+0x19d/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5551 [inline]
netif_receive_skb_core+0x149/0x210 net/core/dev.c:5576
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x430 net/core/dev.c:7101
napi_poll net/core/dev.c:7168 [inline]
net_rx_action+0x522/0xa80 net/core/dev.c:7258
handle_softirqs+0x336/0x830 kernel/softirq.c:576
invoke_softirq kernel/softirq.c:450 [inline]
__irq_exit_rcu+0x13b/0x230 kernel/softirq.c:659
irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:default_idle+0xb/0x10 arch/x86/kernel/process.c:730
Code: b7 48 89 df e8 56 8f f4 f7 eb ad e8 4f ab f6 ff 00 00 cc cc 00 00 cc cc 00 00 cc cc 00 00 cc 66 90 0f 00 2d b7 25 5c 00 fb f4 <c3> 0f 1f 40 00 41 57 41 56 53 49 be 00 00 00 00 00 fc ff df 65 48
RSP: 0018:ffffc90000d67d48 EFLAGS: 000002c2
RAX: cf38a7824ce27400 RBX: ffff888016e98000 RCX: cf38a7824ce27400
RDX: 0000000000000001 RSI: ffffffff8a2b2be0 RDI: ffffffff8a7a43c0
RBP: ffffc90000d67e80 R08: ffff8880b913b30b R09: 1ffff11017227661
R10: dffffc0000000000 R11: ffffed1017227662 R12: 1ffff920001acfb4
R13: dffffc0000000000 R14: 1ffff11002dd3000 R15: 0000000000000000
default_idle_call+0x81/0xc0 kernel/sched/idle.c:112
cpuidle_idle_call kernel/sched/idle.c:202 [inline]
do_idle+0x3a1/0x650 kernel/sched/idle.c:326
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:424
start_secondary+0x32f/0x430 arch/x86/kernel/smpboot.c:281
secondary_startup_64_no_verify+0xb1/0xbb
</TASK>
----------------
Code disassembly (best guess):
0: b7 48 mov $0x48,%bh
2: 89 df mov %ebx,%edi
4: e8 56 8f f4 f7 call 0xf7f48f5f
9: eb ad jmp 0xffffffb8
b: e8 4f ab f6 ff call 0xfff6ab5f
10: 00 00 add %al,(%rax)
12: cc int3
13: cc int3
14: 00 00 add %al,(%rax)
16: cc int3
17: cc int3
18: 00 00 add %al,(%rax)
1a: cc int3
1b: cc int3
1c: 00 00 add %al,(%rax)
1e: cc int3
1f: 66 90 xchg %ax,%ax
21: 0f 00 2d b7 25 5c 00 verw 0x5c25b7(%rip) # 0x5c25df
28: fb sti
29: f4 hlt
* 2a: c3 ret <-- trapping instruction
2b: 0f 1f 40 00 nopl 0x0(%rax)
2f: 41 57 push %r15
31: 41 56 push %r14
33: 53 push %rbx
34: 49 be 00 00 00 00 00 movabs $0xdffffc0000000000,%r14
3b: fc ff df
3e: 65 gs
3f: 48 rex.W
syzbot
Sep 10, 2026, 8:16:26 PMSep 10
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: cf82dcca9634 Linux 6.1.187
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11b0ac8e580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11f3c601580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/97e1e40b968b/disk-cf82dcca.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cfec27562c15/vmlinux-cf82dcca.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4c7cd066c46d/bzImage-cf82dcca.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f4e24b...@syzkaller.appspotmail.com
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ksoftirqd/1/21 [HC0[0]:SC1[1]:HE1:SE0] takes:
ffff888028cb6130 (sk_lock-AF_X25){+.?.}-{0:0}, at: lock_sock include/net/sock.h:1805 [inline]
ffff888028cb6130 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1783
hardirqs last enabled at (370418): [<ffffffff814f4bd6>] __local_bh_enable_ip+0x136/0x1c0 kernel/softirq.c:426
hardirqs last disabled at (370417): [<ffffffff814f4b77>] __local_bh_enable_ip+0xd7/0x1c0 kernel/softirq.c:403
softirqs last enabled at (370180): [<ffffffff814f7b64>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
softirqs last disabled at (370185): [<ffffffff814f7b64>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(sk_lock-AF_X25);
<Interrupt>
lock(sk_lock-AF_X25);
*** DEADLOCK ***
1 lock held by ksoftirqd/1/21:
#0: ffffffff8cb2dc20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2dc20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2dc20 (rcu_read_lock){....}-{1:2}, at: netif_receive_skb_core+0x30/0x230 net/core/dev.c:5643
[<ffffffff814f4f6d>] softirq_handle_begin kernel/softirq.c:434 [inline]
[<ffffffff814f4f6d>] handle_softirqs+0xfd/0x910 kernel/softirq.c:572
HEAD commit: cf82dcca9634 Linux 6.1.187
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11b0ac8e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=f4e24b88b1f7abcfbfbd
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15b0ac8e580000
dashboard link: https://syzkaller.appspot.com/bug?extid=f4e24b88b1f7abcfbfbd
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11f3c601580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/97e1e40b968b/disk-cf82dcca.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cfec27562c15/vmlinux-cf82dcca.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4c7cd066c46d/bzImage-cf82dcca.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f4e24b...@syzkaller.appspotmail.com
================================
WARNING: inconsistent lock state
syzkaller #0 Not tainted
--------------------------------
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
ksoftirqd/1/21 [HC0[0]:SC1[1]:HE1:SE0] takes:
ffff888028cb6130 (sk_lock-AF_X25){+.?.}-{0:0}, at: x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1783
{SOFTIRQ-ON-W} state was registered at:
lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
lock_sock_nested+0x44/0x100 net/core/sock.c:3504
lock_sock include/net/sock.h:1805 [inline]
x25_bind+0x1aa/0x3e0 net/x25/af_x25.c:698
__sys_bind+0x2e9/0x3e0 net/socket.c:1811
__do_sys_bind net/socket.c:1822 [inline]
__se_sys_bind net/socket.c:1820 [inline]
__x64_sys_bind+0x76/0x80 net/socket.c:1820
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
irq event stamp: 370418
lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5676
lock_sock_nested+0x44/0x100 net/core/sock.c:3504
lock_sock include/net/sock.h:1805 [inline]
x25_bind+0x1aa/0x3e0 net/x25/af_x25.c:698
__sys_bind+0x2e9/0x3e0 net/socket.c:1811
__do_sys_bind net/socket.c:1822 [inline]
__se_sys_bind net/socket.c:1820 [inline]
__x64_sys_bind+0x76/0x80 net/socket.c:1820
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
hardirqs last enabled at (370418): [<ffffffff814f4bd6>] __local_bh_enable_ip+0x136/0x1c0 kernel/softirq.c:426
hardirqs last disabled at (370417): [<ffffffff814f4b77>] __local_bh_enable_ip+0xd7/0x1c0 kernel/softirq.c:403
softirqs last enabled at (370180): [<ffffffff814f7b64>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
softirqs last disabled at (370185): [<ffffffff814f7b64>] run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(sk_lock-AF_X25);
<Interrupt>
lock(sk_lock-AF_X25);
*** DEADLOCK ***
1 lock held by ksoftirqd/1/21:
#0: ffffffff8cb2dc20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2dc20 (rcu_read_lock){....}-{1:2}, at: netif_receive_skb_core+0x30/0x230 net/core/dev.c:5643
[<ffffffff814f4f6d>] handle_softirqs+0xfd/0x910 kernel/softirq.c:572
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
__might_resched+0x489/0x5f0 kernel/sched/core.c:9970
lock_sock_nested+0x59/0x100 net/core/sock.c:3506
lock_sock include/net/sock.h:1805 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1783
x25_lapb_receive_frame+0x1a3/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5619 [inline]
netif_receive_skb_core+0x166/0x230 net/core/dev.c:5644
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x460 net/core/dev.c:6628
napi_poll net/core/dev.c:6695 [inline]
net_rx_action+0x622/0xbc0 net/core/dev.c:6809
handle_softirqs+0x291/0x910 kernel/softirq.c:596
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
smpboot_thread_fn+0x667/0xa30 kernel/smpboot.c:164
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
---
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
__might_resched+0x489/0x5f0 kernel/sched/core.c:9970
lock_sock_nested+0x59/0x100 net/core/sock.c:3506
lock_sock include/net/sock.h:1805 [inline]
x25_kill_by_neigh+0x109/0x250 net/x25/af_x25.c:1783
x25_lapb_receive_frame+0x1a3/0xf20 net/x25/x25_dev.c:138
__netif_receive_skb_one_core net/core/dev.c:5619 [inline]
netif_receive_skb_core+0x166/0x230 net/core/dev.c:5644
lapbeth_napi_poll+0x3e/0x80 drivers/net/wan/lapbether.c:99
__napi_poll+0xbb/0x460 net/core/dev.c:6628
napi_poll net/core/dev.c:6695 [inline]
net_rx_action+0x622/0xbc0 net/core/dev.c:6809
handle_softirqs+0x291/0x910 kernel/softirq.c:596
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
smpboot_thread_fn+0x667/0xa30 kernel/smpboot.c:164
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
---
Reply all
Reply to author
Forward
0 new messages