From: syzbot <syzbot+d199b52665b6c3069b94@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING: ODEBUG bug in __sk_destruct (3)
Date: Fri, 08 Aug 2025 20:18:03 -0700 [thread overview]
Message-ID: <6896bdeb.050a0220.7f033.00a2.GAE@google.com> (raw)
In-Reply-To: <20250809025317.4045-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING: ODEBUG bug in __sk_destruct
------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff8880777a8d68 object type: work_struct hint: kcm_tx_work+0x0/0x1e0 net/kcm/kcmsock.c:-1
WARNING: CPU: 0 PID: 7359 at lib/debugobjects.c:615 debug_print_object+0x16b/0x1e0 lib/debugobjects.c:612
Modules linked in:
CPU: 0 UID: 0 PID: 7359 Comm: syz.0.134 Not tainted 6.16.0-syzkaller-12063-g37816488247d-dirty #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:debug_print_object+0x16b/0x1e0 lib/debugobjects.c:612
Code: 4c 89 ff e8 e7 9b 53 fd 4d 8b 0f 48 c7 c7 20 30 e3 8b 48 8b 34 24 4c 89 ea 89 e9 4d 89 f0 41 54 e8 aa cf b3 fc 48 83 c4 08 90 <0f> 0b 90 90 ff 05 e7 fd d3 0a 48 83 c4 08 5b 41 5c 41 5d 41 5e 41
RSP: 0018:ffffc900035d7b30 EFLAGS: 00010296
RAX: 3388542328802800 RBX: dffffc0000000000 RCX: ffff888026a89e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1bfa1ec R12: ffffffff8aa80950
R13: ffffffff8be331a0 R14: ffff8880777a8d68 R15: ffffffff8b89d380
FS: 00007f2fe43246c0(0000) GS:ffff888125c21000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2fe4323f98 CR3: 0000000033878000 CR4: 00000000003526f0
Call Trace:
<TASK>
__debug_check_no_obj_freed lib/debugobjects.c:1099 [inline]
debug_check_no_obj_freed+0x3a2/0x470 lib/debugobjects.c:1129
slab_free_hook mm/slub.c:2348 [inline]
slab_free mm/slub.c:4680 [inline]
kmem_cache_free+0x113/0x400 mm/slub.c:4782
sk_prot_free net/core/sock.c:2276 [inline]
__sk_destruct+0x4d2/0x660 net/core/sock.c:2373
kcm_release+0x528/0x5c0 net/kcm/kcmsock.c:1738
__sock_release net/socket.c:649 [inline]
sock_close+0xc0/0x240 net/socket.c:1439
__fput+0x44c/0xa70 fs/file_table.c:468
fput_close_sync+0x119/0x200 fs/file_table.c:573
__do_sys_close fs/open.c:1587 [inline]
__se_sys_close fs/open.c:1572 [inline]
__x64_sys_close+0x7f/0x110 fs/open.c:1572
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2fe358e9a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2fe4324038 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 00007f2fe37b6160 RCX: 00007f2fe358e9a9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000006
RBP: 00007f2fe3610d69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f2fe37b6160 R15: 00007ffd637a7ad8
</TASK>
Tested on:
commit: 37816488 Merge tag 'net-6.17-rc1' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11ddd5bc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2ae1da3a7f4a6ba4
dashboard link: https://syzkaller.appspot.com/bug?extid=d199b52665b6c3069b94
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=1652b2f0580000
next prev parent reply other threads:[~2025-08-09 3:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 11:24 [syzbot] [net?] WARNING: ODEBUG bug in __sk_destruct (3) syzbot
2025-08-08 13:56 ` Hillf Danton
2025-08-08 14:32 ` syzbot
2025-08-09 2:53 ` Hillf Danton
2025-08-09 3:18 ` syzbot [this message]
2025-08-09 4:36 ` Hillf Danton
2025-08-09 5:11 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-08-09 7:56 [PATCH net-next] net: kcm: Fix race condition in kcm_unattach() Hillf Danton
2025-08-09 11:08 ` [syzbot] [net?] WARNING: ODEBUG bug in __sk_destruct (3) syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6896bdeb.050a0220.7f033.00a2.GAE@google.com \
--to=syzbot+d199b52665b6c3069b94@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.