Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hyunwoo Kim <imv4bel@gmail.com>
Cc: edumazet@kernel.org, ncardwell@google.com, kuniyu@google.com,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, martin.lau@linux.dev, john.fastabend@gmail.com,
	weiwan@google.com, sd@queasysnail.net, jiayuan.chen@linux.dev,
	netdev@vger.kernel.org
Subject: Re: [PATCH net v5 0/2] inet: fix lockless ehash walk races
Date: Tue, 03 Nov 2026 14:40:06 +0000	[thread overview]
Message-ID: <179371680630.1177966.16879360910200844454.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261029214219.1035176-1-imv4bel@gmail.com>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 30 Oct 2026 06:42:15 +0900 you wrote:
> Fix two issues in lockless ehash walks. Reject unhashed sockets after
> taking a reference in established lookups, and restore the acquire/release
> ordering around refcount publication and acquisition.
> 
> Changes in v5:
> - 2/2: add acquire ordering to bpf_sk_assign() for BTF socket pointers
>   (Kuniyuki)
> - v4: https://lore.kernel.org/r/20261026003804.61923-1-imv4bel@gmail.com
> 
> [...]

Here is the summary with links:
  - [net,v5,1/2] inet: reject unhashed sockets during established lookups
    https://git.kernel.org/netdev/net/c/4e2b3ef19e0e
  - [net,v5,2/2] net: restore refcount ordering for lockless socket access
    https://git.kernel.org/netdev/net/c/5b5d8f351dd9

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-11-03 14:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 21:42 [PATCH net v5 0/2] inet: fix lockless ehash walk races Hyunwoo Kim
2026-10-29 21:42 ` [PATCH net v5 1/2] inet: reject unhashed sockets during established lookups Hyunwoo Kim
2026-11-02 22:06   ` netdev-bot+sashiko
2026-10-29 21:42 ` [PATCH net v5 2/2] net: restore refcount ordering for lockless socket access Hyunwoo Kim
2026-10-29 21:55   ` Kuniyuki Iwashima
2026-11-02 22:06   ` netdev-bot+sashiko
2026-11-03  7:47     ` Hyunwoo Kim
2026-11-03 14:30     ` Paolo Abeni
2026-11-03 14:49   ` Eric Dumazet
2026-11-03 14: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=179371680630.1177966.16879360910200844454.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=imv4bel@gmail.com \
    --cc=jiayuan.chen@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=martin.lau@linux.dev \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=weiwan@google.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