[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANn89i+0at_D0HXr0mEt1AbANKWRkcE9uFq51JoC==BQ+W1=wA@mail.gmail.com>
Date: Sat, 29 Nov 2025 00:35:28 -0800
From: Eric Dumazet <edumazet@...gle.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Fushuai Wang <fushuai.wang@...ux.dev>, davem@...emloft.net, pabeni@...hat.com,
horms@...nel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
wangfushuai@...du.com
Subject: Re: [PATCH] rtnl: Add guard support
On Fri, Nov 28, 2025 at 7:45 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Fri, 28 Nov 2025 16:34:55 +0800 Fushuai Wang wrote:
> > Introduce guard support to simplify the usage of the
> > lock about rtnl.
>
> We don't accept APIs without a user.
>
> Also in this case please read:
> https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#using-device-managed-and-cleanup-h-constructs
Another argument is that we are working hard to _remove_ RTNL these days.
This is a multi-years huge effort.
Adding such helpers are spreading a wrong signal : "Look how it is
easy to add more RTNL sections in the kernel"
Powered by blists - more mailing lists