All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Sitnicki <jakub@cloudflare.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Dudu Lu <phx0fer@gmail.com>,
	 John Fastabend <john.fastabend@gmail.com>,
	Jiayuan Chen <jiayuan.chen@linux.dev>,
	 Network Development <netdev@vger.kernel.org>,
	 bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf v2] bpf, sockmap: annotate the psock teardown data races
Date: Mon, 26 Oct 2026 13:33:12 +0100	[thread overview]
Message-ID: <87v76o63qv.fsf@cloudflare.com> (raw)
In-Reply-To: <CAADnVQLTe611mm0iJEf5gJi2GtW42kxNHH3sUPevD039FvzL7g@mail.gmail.com> (Alexei Starovoitov's message of "Fri, 23 Oct 2026 11:53:59 -0700")

On Fri, Oct 23, 2026 at 11:53 AM -07, Alexei Starovoitov wrote:
> On Fri, Oct 23, 2026 at 11:49 AM Jakub Sitnicki <jakub@cloudflare.com> wrote:
>>
>> >
>> >  static bool sock_map_sk_state_allowed(const struct sock *sk)
>>
>> Code LGTM
>
> Jakub,
> Could you commandeer it ?
> Dudu is clearly a bot and doesn't care.

Ack. Will drive this.

  reply	other threads:[~2026-10-26 12:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 15:56 [PATCH bpf] bpf, sockmap: use READ_ONCE/WRITE_ONCE for saved_data_ready in the verdict path Dudu Lu
2026-10-21 16:10 ` sashiko-bot
2026-10-21 16:37 ` bot+bpf-ci
2026-10-21 16:45 ` Alexei Starovoitov
2026-10-21 20:30 ` Jakub Sitnicki
2026-10-22  3:37 ` Jiayuan Chen
2026-10-22  5:48 ` [PATCH bpf v2] bpf, sockmap: annotate the psock teardown data races Dudu Lu
2026-10-22 15:40   ` Alexei Starovoitov
2026-10-23 18:49     ` Jakub Sitnicki
2026-10-23 18:53       ` Alexei Starovoitov
2026-10-26 12:33         ` Jakub Sitnicki [this message]
2026-10-27  5:10           ` phx
2026-10-27 16:33             ` Jakub Sitnicki
2026-10-27 16:46               ` Alexei Starovoitov
2026-10-27 17:34                 ` Jakub Sitnicki

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=87v76o63qv.fsf@cloudflare.com \
    --to=jakub@cloudflare.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=jiayuan.chen@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=phx0fer@gmail.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.