[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c9d2f2d4-7d8c-4acb-9960-805a3c6d83e0@redhat.com>
Date: Tue, 25 Nov 2025 15:17:52 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Dmitry Skorodumov <skorodumov.dmitry@...wei.com>, netdev@...r.kernel.org,
Jakub Kicinski <kuba@...nel.org>, Xiao Liang <shaw.leon@...il.com>,
Kuniyuki Iwashima <kuniyu@...gle.com>, Stanislav Fomichev <sdf@...ichev.me>,
Etienne Champetier <champetier.etienne@...il.com>,
linux-kernel@...r.kernel.org
Cc: andrey.bokhanko@...wei.com, edumazet@...gle.com,
Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH net-next 06/12] ipvlan: Take addr_lock in ipvlan_open()
On 11/20/25 6:49 PM, Dmitry Skorodumov wrote:
> It was forgotten to lock addrs in ipvlan_open().
>
> Seems that code was initially written in assumption
> that any address change occurs under rtnl_lock(). But
> it's not true for the ipv6 case. So, we have to
> take addr_lock in ipvlan_open().
>
> Signed-off-by: Dmitry Skorodumov <skorodumov.dmitry@...wei.com>
... same here. This looks like 'net' material and need a fixes tag.
/P
Powered by blists - more mailing lists