Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
	song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
	emil@etsalapatis.com, ihor.solodrai@linux.dev, shuah@kernel.org,
	edumazet@kernel.org, kuniyu@google.com, pabeni@redhat.com,
	willemb@google.com, john.fastabend@gmail.com,
	jiayuan.chen@linux.dev, davem@davemloft.net, kuba@kernel.org,
	horms@kernel.org, bpf@vger.kernel.org, netdev@vger.kernel.org,
	kernel-team@cloudflare.com
Subject: Re: [PATCH bpf-next 0/2] Fix psock update-side data races on sk->sk_prot and progs
Date: Sat, 31 Oct 2026 21:20:04 +0000	[thread overview]
Message-ID: <179348160430.2237852.4848010976171902619.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261030-bpf-next-v1-0-035eabf8eae7@cloudflare.com>

Hello:

This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 30 Oct 2026 13:01:52 +0100 you wrote:
> Follow up to the thread at [1]. See individual patches for details.
> 
> [1] https://lore.kernel.org/bpf/20261022054811.35008-1-phx0fer@gmail.com/
> 
> Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
> ---
> Jakub Sitnicki (2):
>       selftests/bpf: Cover concurrent sockmap update and delete
>       bpf, sockmap: Fix psock update-side data races on sk->sk_prot and progs
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] selftests/bpf: Cover concurrent sockmap update and delete
    (no matching commit)
  - [bpf-next,2/2] bpf, sockmap: Fix psock update-side data races on sk->sk_prot and progs
    https://git.kernel.org/bpf/bpf/c/bcd07fd1673b

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-10-31 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 12:01 [PATCH bpf-next 0/2] Fix psock update-side data races on sk->sk_prot and progs Jakub Sitnicki
2026-10-30 12:01 ` [PATCH bpf-next 1/2] selftests/bpf: Cover concurrent sockmap update and delete Jakub Sitnicki
2026-10-30 12:01 ` [PATCH bpf-next 2/2] bpf, sockmap: Fix psock update-side data races on sk->sk_prot and progs Jakub Sitnicki
2026-10-30 12:45   ` bot+bpf-ci
2026-10-31 20:52 ` [PATCH bpf-next 0/2] " Alexei Starovoitov
2026-10-31 21:20 ` 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=179348160430.2237852.4848010976171902619.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eddyz87@gmail.com \
    --cc=edumazet@kernel.org \
    --cc=emil@etsalapatis.com \
    --cc=horms@kernel.org \
    --cc=ihor.solodrai@linux.dev \
    --cc=jakub@cloudflare.com \
    --cc=jiayuan.chen@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@cloudflare.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=willemb@google.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