public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: john.fastabend@gmail.com, jakub@cloudflare.com,
	martin.lau@linux.dev, wangyufen@huawei.com, kuni1840@gmail.com,
	bpf@vger.kernel.org,
	syzbot+b0842d38af58376d1fdc@syzkaller.appspotmail.com
Subject: Re: [PATCH v2 bpf] sockmap: Fix sk_psock_drop() race vs sock_map_{unhash,close,destroy}().
Date: Fri, 24 Apr 2026 03:40:10 +0000	[thread overview]
Message-ID: <177700201030.900079.374070181715062663.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260420194846.1089595-1-kuniyu@google.com>

Hello:

This patch was applied to bpf/bpf.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Mon, 20 Apr 2026 19:48:41 +0000 you wrote:
> syzbot reported a splat in sock_map_destroy() [0], where psock was
> NULL even though sk->sk_prot still pointed to tcp_bpf_prots[][].
> 
> The stack trace shows how badly the path was excercised, see
> inet_release() calls tcp_close(), not sock_map_close() yet, but
> finally reaching sock_map_destroy().
> 
> [...]

Here is the summary with links:
  - [v2,bpf] sockmap: Fix sk_psock_drop() race vs sock_map_{unhash,close,destroy}().
    https://git.kernel.org/bpf/bpf/c/6451d58a3556

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-04-24  3:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 19:48 [PATCH v2 bpf] sockmap: Fix sk_psock_drop() race vs sock_map_{unhash,close,destroy}() Kuniyuki Iwashima
2026-04-21  1:13 ` sashiko-bot
2026-04-21  3:21   ` Jiayuan Chen
2026-04-23 21:17     ` Martin KaFai Lau
2026-04-23 23:02       ` Kuniyuki Iwashima
2026-04-21  9:26 ` Jiayuan Chen
2026-04-24  3:40 ` 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=177700201030.900079.374070181715062663.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=jakub@cloudflare.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=martin.lau@linux.dev \
    --cc=syzbot+b0842d38af58376d1fdc@syzkaller.appspotmail.com \
    --cc=wangyufen@huawei.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