[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z_6Y5iWvbDr9dmjK@mini-arch>
Date: Tue, 15 Apr 2025 10:35:34 -0700
From: Stanislav Fomichev <stfomichev@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
syzbot+de1c7d68a10e3f123bdd@...kaller.appspotmail.com,
sdf@...ichev.me, kuniyu@...zon.com
Subject: Re: [PATCH net] net: don't try to ops lock uninitialized devs
On 04/15, Jakub Kicinski wrote:
> We need to be careful when operating on dev while in rtnl_create_link().
> Some devices (vxlan) initialize netdev_ops in ->newlink, so later on.
> Avoid using netdev_lock_ops(), the device isn't registered so we
> cannot legally call its ops or generate any notifications for it.
>
> netdev_ops_assert_locked_or_invisible() is safe to use, it checks
> registration status first.
>
> Reported-by: syzbot+de1c7d68a10e3f123bdd@...kaller.appspotmail.com
> Fixes: 04efcee6ef8d ("net: hold instance lock during NETDEV_CHANGE")
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
Acked-by: Stanislav Fomichev <sdf@...ichev.me>
Powered by blists - more mailing lists