[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2yt5SDkCPTeAoez@nanopsycho>
Date: Thu, 10 Nov 2022 08:53:09 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Eric Dumazet <edumazet@...gle.com>
Cc: Ido Schimmel <idosch@...sch.org>, netdev@...r.kernel.org,
davem@...emloft.net, kuba@...nel.org, 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 05:26:10PM CET, edumazet@...gle.com wrote:
>On Wed, Nov 9, 2022 at 3:49 AM Ido Schimmel <idosch@...sch.org> 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()
Well, in this case, I think that plain WARN_ON is fine as this happens
only during driver cleanup which is not expected to happen very often
(or not at all) in real world scenarios.
Powered by blists - more mailing lists