[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2n881qPpY9J8MQ0@nanopsycho>
Date: Tue, 8 Nov 2022 07:53:39 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, davem@...emloft.net, pabeni@...hat.com,
edumazet@...gle.com, idosch@...sch.org, bigeasy@...utronix.de,
imagedong@...cent.com, kuniyu@...zon.com, petrm@...dia.com
Subject: Re: [patch net-next 1/2] net: introduce a helper to move notifier
block to different namespace
Tue, Nov 08, 2022 at 05:29:37AM CET, kuba@...nel.org wrote:
>On Mon, 7 Nov 2022 15:52:12 +0100 Jiri Pirko wrote:
>> +void __move_netdevice_notifier_net(struct net *src_net, struct net *dst_net,
>> + struct notifier_block *nb)
>> +{
>> + __unregister_netdevice_notifier_net(src_net, nb);
>> + __register_netdevice_notifier_net(dst_net, nb, true);
>> +}
>
>'static' missing
Yep.
>
>> +void move_netdevice_notifier_net(struct net *src_net, struct net *dst_net,
>> + struct notifier_block *nb)
>> +{
>> + rtnl_lock();
>> + __move_netdevice_notifier_net(src_net, dst_net, nb);
>> + rtnl_unlock();
>> +}
>> +EXPORT_SYMBOL(move_netdevice_notifier_net);
>
>Do we need to export this? Maybe let's wait for a module user?
Ah, right.
Powered by blists - more mailing lists