[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2yuK8kccunmEiYd@nanopsycho>
Date: Thu, 10 Nov 2022 08:54:19 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Eric Dumazet <edumazet@...gle.com>,
Ido Schimmel <idosch@...sch.org>, netdev@...r.kernel.org,
davem@...emloft.net, pabeni@...hat.com, bigeasy@...utronix.de,
imagedong@...cent.com, kuniyu@...zon.com, petrm@...dia.com
Subject: Re: [patch net-next v2 3/3] net: devlink: add WARN_ON to check
return value of unregister_netdevice_notifier_net() call
Wed, Nov 09, 2022 at 10:45:36PM CET, kuba@...nel.org wrote:
>On Wed, 9 Nov 2022 08:26:10 -0800 Eric Dumazet wrote:
>> > On Tue, Nov 08, 2022 at 02:22:08PM +0100, Jiri Pirko wrote:
>> > > From: Jiri Pirko <jiri@...dia.com>
>> > >
>> > > As the return value is not 0 only in case there is no such notifier
>> > > block registered, add a WARN_ON() to yell about it.
>> > >
>> > > Suggested-by: Ido Schimmel <idosch@...sch.org>
>> > > Signed-off-by: Jiri Pirko <jiri@...dia.com>
>> >
>> > Reviewed-by: Ido Schimmel <idosch@...dia.com>
>>
>> Please consider WARN_ON_ONCE(), or DEBUG_NET_WARN_ON_ONCE()
>
>Do you have any general guidance on when to pick WARN() vs WARN_ONCE()?
>Or should we always prefer _ONCE() going forward?
Good question. If so, it should be documented or spotted by checkpatch.
>
>Let me take the first 2 in, to lower the syzbot volume.
Powered by blists - more mailing lists