[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221109134536.447890fb@kernel.org>
Date: Wed, 9 Nov 2022 13:45:36 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Eric Dumazet <edumazet@...gle.com>
Cc: Ido Schimmel <idosch@...sch.org>, Jiri Pirko <jiri@...nulli.us>,
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
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?
Let me take the first 2 in, to lower the syzbot volume.
Powered by blists - more mailing lists