[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250410195440.3ba7ba0f@kernel.org>
Date: Thu, 10 Apr 2025 19:54:40 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Antonio Quartulli <antonio@...nvpn.net>
Cc: netdev@...r.kernel.org, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Donald Hunter <donald.hunter@...il.com>, Shuah Khan
<shuah@...nel.org>, sd@...asysnail.net, ryazanov.s.a@...il.com, Andrew Lunn
<andrew+netdev@...n.ch>, Simon Horman <horms@...nel.org>,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org, Xiao Liang
<shaw.leon@...il.com>, steffen.klassert@...unet.com,
antony.antony@...unet.com
Subject: Re: [PATCH net-next v25 01/23] net: introduce OpenVPN Data Channel
Offload (ovpn)
On Mon, 07 Apr 2025 21:46:09 +0200 Antonio Quartulli wrote:
> +static int ovpn_netdev_notifier_call(struct notifier_block *nb,
> + unsigned long state, void *ptr)
> +{
> + struct net_device *dev = netdev_notifier_info_to_dev(ptr);
> +
> + if (!ovpn_dev_is_valid(dev))
> + return NOTIFY_DONE;
> +
> + switch (state) {
> + case NETDEV_REGISTER:
> + /* add device to internal list for later destruction upon
> + * unregistration
> + */
> + break;
> + case NETDEV_UNREGISTER:
> + /* can be delivered multiple times, so check registered flag,
> + * then destroy the interface
> + */
> + break;
> + case NETDEV_POST_INIT:
> + case NETDEV_GOING_DOWN:
> + case NETDEV_DOWN:
> + case NETDEV_UP:
> + case NETDEV_PRE_UP:
> + default:
> + return NOTIFY_DONE;
> + }
Why are you using a notifier to get events for your own device?
> + return NOTIFY_OK;
> +}
> +MODULE_DESCRIPTION("OpenVPN data channel offload (ovpn)");
> +MODULE_AUTHOR("(C) 2020-2025 OpenVPN, Inc.");
Companies can't author code, only people. Note that MODULE_AUTHOR()
is optional.
Powered by blists - more mailing lists