From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+d199b52665b6c3069b94@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING: ODEBUG bug in __sk_destruct (3)
Date: Sat, 9 Aug 2025 10:53:15 +0800 [thread overview]
Message-ID: <20250809025317.4045-1-hdanton@sina.com> (raw)
In-Reply-To: <6895de6e.050a0220.7f033.005d.GAE@google.com>
> Date: Fri, 08 Aug 2025 04:24:30 -0700 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 7abc678e3084 Merge tag 'pmdomain-v6.16-rc2' of git://git.k..
> git tree: bpf
> console output: https://syzkaller.appspot.com/x/log.txt?x=11b0a4f0580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=12b5044868deb866
> dashboard link: https://syzkaller.appspot.com/bug?extid=d199b52665b6c3069b94
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14a20f22580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12af2f22580000
#syz test upstream master
--- x/net/kcm/kcmsock.c
+++ y/net/kcm/kcmsock.c
@@ -717,6 +717,8 @@ static void kcm_tx_work(struct work_stru
lock_sock(sk);
+ if (kcm->tx_stopped)
+ goto out;
/* Primarily for SOCK_DGRAM sockets, also handle asynchronous tx
* aborts
*/
--
next prev parent reply other threads:[~2025-08-09 2:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 11:24 syzbot
2025-08-08 13:56 ` Hillf Danton
2025-08-08 14:32 ` syzbot
2025-08-09 2:53 ` Hillf Danton [this message]
2025-08-09 3:18 ` syzbot
2025-08-09 4:36 ` Hillf Danton
2025-08-09 5:11 ` syzbot
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=20250809025317.4045-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+d199b52665b6c3069b94@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®