From: David Ahern <dsahern@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net-next] ipv6: move IFA_F_PERMANENT percpu allocation in process scope
Date: Thu, 26 Mar 2026 11:26:21 -0600 [thread overview]
Message-ID: <d972e1e2-7090-47bd-988a-1ea854cbfb42@kernel.org> (raw)
In-Reply-To: <8c8bfe2e1a324e501f0e15fef404a77443fd8caf.1774365668.git.pabeni@redhat.com>
On 3/24/26 9:22 AM, Paolo Abeni wrote:
> Observed at boot time:
>
> CPU: 43 UID: 0 PID: 3595 Comm: (t-daemon) Not tainted 6.12.0 #1
6.12 ???
> IFA_F_PERMANENT addresses require the allocation of a bunch of percpu
> pointers, currently in atomic scope.
>
> Similar to commit 51454ea42c1a ("ipv6: fix locking issues with loops
> over idev->addr_list"), move fixup_permanent_addr() outside the
> &idev->lock scope, and do the allocations with GFP_KERNEL. With such
> change fixup_permanent_addr() is invoked with the BH enabled, and the
> ifp lock acquired there needs the BH variant.
>
> Note that we don't need to acquire a reference to the permanent
> addresses before releasing the mentioned write lock, because
> addrconf_permanent_addr() runs under RTNL and ifa removal always happens
> under RTNL, too.
>
> Also the PERMANENT flag is constant in the relevant scope, as it can be
> cleared only by inet6_addr_modify() under the RTNL lock.
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
> explicitly targeting net-next as this is IMHO an improvement more than a
> bug fix
> ---
> net/ipv6/addrconf.c | 32 ++++++++++++++++++++------------
> 1 file changed, 20 insertions(+), 12 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2026-03-26 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 15:22 [PATCH net-next] ipv6: move IFA_F_PERMANENT percpu allocation in process scope Paolo Abeni
2026-03-26 17:26 ` David Ahern [this message]
2026-03-27 1:35 ` Jakub Kicinski
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=d972e1e2-7090-47bd-988a-1ea854cbfb42@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--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