From: patchwork-bot+netdevbpf@kernel.org
To: Mahanta Jambigi <mjambigi@linux.ibm.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, alibuda@linux.alibaba.com,
dust.li@linux.alibaba.com, sidraya@linux.ibm.com,
hidayath@linux.ibm.com, pasic@linux.ibm.com, horms@kernel.org,
tonylu@linux.alibaba.com, guwen@linux.alibaba.com,
netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH net] net/smc: hash socket only after full initialisation in smc_sk_init()
Date: Tue, 18 Aug 2026 10:10:08 +0000 [thread overview]
Message-ID: <178704780864.2000568.4734388817870408144.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813074315.554926-1-mjambigi@linux.ibm.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 13 Aug 2026 09:43:15 +0200 you wrote:
> smc_sk_init() calls sk->sk_prot->hash(sk) before several fields are
> fully initialised: clcsock_release_lock, the saved clcsk_* callbacks,
> use_fallback/fallback_rsn, and conn.close_work. Once hash() returns the
> socket is visible to concurrent hash walkers, which can then observe
> uninitialised state.
>
> Move hash(sk) to the end of smc_sk_init() so the socket is published
> only after it is fully constructed.
>
> [...]
Here is the summary with links:
- [net] net/smc: hash socket only after full initialisation in smc_sk_init()
https://git.kernel.org/netdev/net/c/8acf691d8017
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-18 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 7:43 [PATCH net] net/smc: hash socket only after full initialisation in smc_sk_init() Mahanta Jambigi
2026-08-14 7:43 ` sashiko-bot
2026-08-14 11:04 ` Mahanta Jambigi
2026-08-18 10:10 ` 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=178704780864.2000568.4734388817870408144.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=hidayath@linux.ibm.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.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