Hello,
syzbot found the following issue on:
HEAD commit: 347385861c50 Linux 6.1.84
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=108b4805180000
kernel config:
https://syzkaller.appspot.com/x/.config?x=40dfd13b04bfc094
dashboard link:
https://syzkaller.appspot.com/bug?extid=6c7d6e3a6d55e4d34f42
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=10169103180000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=1668fde3180000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/584c64d6360b/disk-34738586.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/ebe1b8334610/vmlinux-34738586.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/e3d485b54a02/bzImage-34738586.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+6c7d6e...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3589 at net/core/sock_map.c:1638 sock_map_close+0x29b/0x2d0
Modules linked in:
CPU: 1 PID: 3589 Comm: syz-executor106 Not tainted 6.1.84-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:sock_map_close+0x29b/0x2d0 net/core/sock_map.c:1638
Code: 89 df e8 f8 c3 49 f9 48 8b 1b 48 89 d8 48 c1 e8 03 42 80 3c 30 00 74 08 48 89 df e8 df c3 49 f9 4c 8b 33 eb 8b e8 45 4d f2 f8 <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 2f 4d f2 f8
RSP: 0018:ffffc90003bffc90 EFLAGS: 00010293
RAX: ffffffff889839ab RBX: ffffffff920e0780 RCX: ffff888078fdd940
RDX: 0000000000000000 RSI: ffffffff8aebeec0 RDI: ffffffff8b3d2d20
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff2093058
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888073172800
R13: 1ffff1100df15d83 R14: ffffffff88983710 R15: ffffffff8898373c
FS: 0000555556db8380(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa346d3804d CR3: 0000000021b9c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
unix_release+0x7e/0xc0 net/unix/af_unix.c:1038
__sock_release net/socket.c:654 [inline]
sock_close+0xcd/0x230 net/socket.c:1400
__fput+0x3b7/0x890 fs/file_table.c:320
task_work_run+0x246/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xde/0x100 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fa346cee6a0
Code: ff f7 d8 64 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 80 3d 01 8a 07 00 00 74 17 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c
RSP: 002b:00007fff576ac388 EFLAGS: 00000202 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00007fa346cee6a0
RDX: 0000000000000010 RSI: 0000000020000f40 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000056db9610 R09: 0000000056db9610
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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