public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, kuniyu@google.com, netdev@vger.kernel.org,
	eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] net: __lock_sock() can be static
Date: Wed, 25 Feb 2026 01:00:07 +0000	[thread overview]
Message-ID: <177198120778.17446.9183992293157130973.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260223092716.3673939-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 23 Feb 2026 09:27:15 +0000 you wrote:
> After commit 6511882cdd82 ("mptcp: allocate fwd memory separately
> on the rx and tx path") __lock_sock() can be static again.
> 
> Make sure __lock_sock() is not inlined, so that lock_sock_nested()
> no longer needs a stack canary.
> 
> Add a noinline attribute on lock_sock_nested() so that calls
> to lock_sock() from net/core/sock.c are not inlined,
> none of them are fast path to deserve that:
> 
> [...]

Here is the summary with links:
  - [net-next] net: __lock_sock() can be static
    https://git.kernel.org/netdev/net-next/c/2550def53bbf

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-02-25  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23  9:27 [PATCH net-next] net: __lock_sock() can be static Eric Dumazet
2026-02-23 18:41 ` Kuniyuki Iwashima
2026-02-25  1: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=177198120778.17446.9183992293157130973.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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