Hello,
syzbot found the following issue on:
HEAD commit: 574362648507 Linux 5.15.151
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17002311180000
kernel config:
https://syzkaller.appspot.com/x/.config?x=6c9a42d9e3519ca9
dashboard link:
https://syzkaller.appspot.com/bug?extid=17fb3cb11b4f840e0221
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/19969137526d/disk-57436264.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/a11d2450b188/vmlinux-57436264.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/306ba70d0b2f/bzImage-57436264.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+17fb3c...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3532 at kernel/softirq.c:363 __local_bh_enable_ip+0x1b3/0x1f0
Modules linked in:
CPU: 0 PID: 3532 Comm: syz-executor.4 Not tainted 5.15.151-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:__local_bh_enable_ip+0x1b3/0x1f0 kernel/softirq.c:363
Code: 04 25 28 00 00 00 48 3b 44 24 60 75 4a 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 d0 fe ff ff e8 3f 00 00 00 eb a2 <0f> 0b e9 02 ff ff ff 48 c7 c1 84 c0 e3 8d 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90002f075e0 EFLAGS: 00010046
RAX: 0000000000000000 RBX: 1ffff920005e0ec0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000201 RDI: ffffffff884e9060
RBP: ffffc90002f076a0 R08: dffffc0000000000 R09: ffffed100f46fe02
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000004 R14: ffffc90002f07620 R15: 0000000000000201
FS: 0000555556353480(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f443016bf50 CR3: 000000004984a000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
sock_hash_delete_elem+0x1a0/0x2f0 net/core/sock_map.c:945
bpf_prog_2c29ac5cdc6b1842+0x3a/0x444
bpf_dispatcher_nop_func include/linux/bpf.h:780 [inline]
__bpf_prog_run include/linux/filter.h:625 [inline]
bpf_prog_run include/linux/filter.h:632 [inline]
__bpf_trace_run kernel/trace/bpf_trace.c:1880 [inline]
bpf_trace_run2+0x19e/0x340 kernel/trace/bpf_trace.c:1917
__bpf_trace_kfree+0x6e/0x90 include/trace/events/kmem.h:118
trace_kfree include/trace/events/kmem.h:118 [inline]
kfree+0x22f/0x270 mm/slub.c:4549
put_css_set_locked+0x6e0/0x930 kernel/cgroup/cgroup.c:982
cgroup_migrate_finish+0x1b7/0x380 kernel/cgroup/cgroup.c:2670
cgroup_attach_task+0x5b0/0x860 kernel/cgroup/cgroup.c:2871
__cgroup1_procs_write+0x2ed/0x460 kernel/cgroup/cgroup-v1.c:527
cgroup_file_write+0x2ac/0x670 kernel/cgroup/cgroup.c:3947
kernfs_fop_write_iter+0x3a2/0x4f0 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2148 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1832df4aef
Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 b9 80 02 00 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 0c 81 02 00 48
RSP: 002b:00007ffcc4e70fe0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f1832df4aef
RDX: 0000000000000001 RSI: 00007ffcc4e71030 RDI: 0000000000000003
RBP: 00007ffcc4e715d0 R08: 0000000000000000 R09: 00007ffcc4e70e37
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000001
R13: 00007ffcc4e71030 R14: 00007ffcc4e71590 R15: 00007ffcc4e715d0
</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