BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
	cong.wang@bytedance.com, bonan.ruan@u.nus.edu,
	yonghong.song@linux.dev, john.fastabend@gmail.com,
	jakub@cloudflare.com
Subject: Re: [Patch bpf] sock_map: fix a NULL pointer dereference in sock_map_link_update_prog()
Date: Tue, 29 Oct 2024 02:00:30 +0000	[thread overview]
Message-ID: <173016723076.241400.15764382647149470728.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241026185522.338562-1-xiyou.wangcong@gmail.com>

Hello:

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

On Sat, 26 Oct 2024 11:55:22 -0700 you wrote:
> From: Cong Wang <cong.wang@bytedance.com>
> 
> The following race condition could trigger a NULL pointer dereference:
> 
> sock_map_link_detach():		sock_map_link_update_prog():
>    mutex_lock(&sockmap_mutex);
>    ...
>    sockmap_link->map = NULL;
>    mutex_unlock(&sockmap_mutex);
>    				   mutex_lock(&sockmap_mutex);
> 				   ...
> 				   sock_map_prog_link_lookup(sockmap_link->map);
> 				   mutex_unlock(&sockmap_mutex);
>    <continue>
> 
> [...]

Here is the summary with links:
  - [bpf] sock_map: fix a NULL pointer dereference in sock_map_link_update_prog()
    https://git.kernel.org/bpf/bpf/c/740be3b9a6d7

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



      parent reply	other threads:[~2024-10-29  2:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26 18:55 [Patch bpf] sock_map: fix a NULL pointer dereference in sock_map_link_update_prog() Cong Wang
2024-10-28  5:58 ` Yonghong Song
2024-10-29  1:57   ` Martin KaFai Lau
2024-10-29  2:00 ` 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=173016723076.241400.15764382647149470728.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bonan.ruan@u.nus.edu \
    --cc=bpf@vger.kernel.org \
    --cc=cong.wang@bytedance.com \
    --cc=jakub@cloudflare.com \
    --cc=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    --cc=yonghong.song@linux.dev \
    /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