From: patchwork-bot+netdevbpf@kernel.org
To: Sven Stegemann <sven@stegemann.de>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+e62c9db591c30e174662@syzkaller.appspotmail.com,
syzbot+d199b52665b6c3069b94@syzkaller.appspotmail.com,
syzbot+be6b1fdfeae512726b4e@syzkaller.appspotmail.com
Subject: Re: [PATCH net v2] net: kcm: Fix race condition in kcm_unattach()
Date: Thu, 14 Aug 2025 01:30:11 +0000 [thread overview]
Message-ID: <175513501124.3846704.13838201534984026862.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250812191810.27777-1-sven@stegemann.de>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 12 Aug 2025 21:18:03 +0200 you wrote:
> syzbot found a race condition when kcm_unattach(psock)
> and kcm_release(kcm) are executed at the same time.
>
> kcm_unattach() is missing a check of the flag
> kcm->tx_stopped before calling queue_work().
>
> If the kcm has a reserved psock, kcm_unattach() might get executed
> between cancel_work_sync() and unreserve_psock() in kcm_release(),
> requeuing kcm->tx_work right before kcm gets freed in kcm_done().
>
> [...]
Here is the summary with links:
- [net,v2] net: kcm: Fix race condition in kcm_unattach()
https://git.kernel.org/netdev/net/c/52565a935213
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-14 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 19:18 [PATCH net v2] net: kcm: Fix race condition in kcm_unattach() Sven Stegemann
2025-08-14 1:30 ` patchwork-bot+netdevbpf [this message]
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=175513501124.3846704.13838201534984026862.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sven@stegemann.de \
--cc=syzbot+be6b1fdfeae512726b4e@syzkaller.appspotmail.com \
--cc=syzbot+d199b52665b6c3069b94@syzkaller.appspotmail.com \
--cc=syzbot+e62c9db591c30e174662@syzkaller.appspotmail.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.