netdev - Re: [net-next] ipv6: sr: switch to GFP_ATOMIC flag to allocate memory during seg6local LWT setup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <174614824249.3123530.9494554975799967680.git-patchwork-notify@kernel.org>
Date: Fri, 02 May 2025 01:10:42 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Andrea Mayer <andrea.mayer@...roma2.it>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com, dsahern@...nel.org, horms@...nel.org, kuniyu@...zon.com,
 linux-kernel@...r.kernel.org, netdev@...r.kernel.org, bpf@...r.kernel.org,
 stefano.salsano@...roma2.it, paolo.lungaroni@...roma2.it,
 ahabdels.dev@...il.com
Subject: Re: [net-next] ipv6: sr: switch to GFP_ATOMIC flag to allocate memory
 during seg6local LWT setup

Hello:

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

On Tue, 29 Apr 2025 15:24:53 +0200 you wrote:
> Recent updates to the locking mechanism that protects IPv6 routing tables
> [1] have affected the SRv6 networking subsystem. Such changes cause
> problems with some SRv6 Endpoints behaviors, like End.B6.Encaps and also
> impact SRv6 counters.
> 
> Starting from commit 169fd62799e8 ("ipv6: Get rid of RTNL for SIOCADDRT and
> RTM_NEWROUTE."), the inet6_rtm_newroute() function no longer needs to
> acquire the RTNL lock for creating and configuring IPv6 routes and set up
> lwtunnels.
> The RTNL lock can be avoided because the ip6_route_add() function
> finishes setting up a new route in a section protected by RCU.
> This makes sure that no dev/nexthops can disappear during the operation.
> Because of this, the steps for setting up lwtunnels - i.e., calling
> lwtunnel_build_state() - are now done in a RCU lock section and not
> under the RTNL lock anymore.
> 
> [...]

Here is the summary with links:
  - [net-next] ipv6: sr: switch to GFP_ATOMIC flag to allocate memory during seg6local LWT setup
    https://git.kernel.org/netdev/net-next/c/14a0087e7236

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html