All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com
Subject: Re: [PATCH net v4 05/11] netdevsim: add dummy device notifiers
Date: Mon, 31 Mar 2025 13:54:21 -0700	[thread overview]
Message-ID: <20250331135421.018c49db@kernel.org> (raw)
In-Reply-To: <20250331150603.1906635-6-sdf@fomichev.me>

On Mon, 31 Mar 2025 08:05:57 -0700 Stanislav Fomichev wrote:
> +#if IS_ENABLED(CONFIG_DEBUG_NET)
> +int netdev_debug_event(struct notifier_block *nb, unsigned long event,
> +		       void *ptr);
> +#else
> +static inline int netdev_debug_event(struct notifier_block *nb,
> +				     unsigned long event, void *ptr)
> +{
> +	return 0;
> +}
> +#endif

Maybe we can wrap the while notifier setup in

	if (IS_ENABLED(CONFIG_DEBUG_NET)) {

instead? We don't expect more users of the event callback, and it may
be useful to give readers of the netdevsim code a hint that this
callback will only do something when DEBUG_NET=y

>  #endif
> diff --git a/net/core/lock_debug.c b/net/core/lock_debug.c
> index 7ecd28cc1c22..506899164f31 100644
> --- a/net/core/lock_debug.c
> +++ b/net/core/lock_debug.c

> @@ -66,6 +69,7 @@ static int rtnl_net_debug_event(struct notifier_block *nb,
>  
>  	return NOTIFY_DONE;
>  }
> +EXPORT_SYMBOL_GPL(netdev_debug_event);

EXPORT_SYMBOL_NS_GPL(netdev_debug_event, "NETDEV_INTERNAL");

  reply	other threads:[~2025-03-31 20:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31 15:05 [PATCH net v4 00/11] net: hold instance lock during NETDEV_UP/REGISTER Stanislav Fomichev
2025-03-31 15:05 ` [PATCH net v4 01/11] net: switch to netif_disable_lro in inetdev_init Stanislav Fomichev
2025-03-31 20:43   ` Jakub Kicinski
2025-03-31 21:06     ` Stanislav Fomichev
2025-03-31 15:05 ` [PATCH net v4 02/11] net: hold instance lock during NETDEV_REGISTER/UP Stanislav Fomichev
2025-03-31 20:48   ` Jakub Kicinski
2025-03-31 21:13     ` Stanislav Fomichev
2025-03-31 21:27       ` Jakub Kicinski
2025-03-31 15:05 ` [PATCH net v4 03/11] net: use netif_disable_lro in ipv6_add_dev Stanislav Fomichev
2025-03-31 15:05 ` [PATCH net v4 04/11] net: rename rtnl_net_debug to lock_debug Stanislav Fomichev
2025-03-31 20:48   ` Jakub Kicinski
2025-03-31 15:05 ` [PATCH net v4 05/11] netdevsim: add dummy device notifiers Stanislav Fomichev
2025-03-31 20:54   ` Jakub Kicinski [this message]
2025-03-31 21:20     ` Stanislav Fomichev
2025-03-31 15:05 ` [PATCH net v4 06/11] net: dummy: request ops lock Stanislav Fomichev
2025-03-31 15:05 ` [PATCH net v4 07/11] docs: net: document netdev notifier expectations Stanislav Fomichev
2025-03-31 20:58   ` Jakub Kicinski
2025-03-31 21:49     ` Stanislav Fomichev
2025-03-31 15:06 ` [PATCH net v4 08/11] selftests: net: use netdevsim in netns test Stanislav Fomichev
2025-03-31 15:06 ` [PATCH net v4 09/11] net: designate XSK pool pointers in queues as "ops protected" Stanislav Fomichev
2025-03-31 15:06 ` [PATCH net v4 10/11] netdev: add "ops compat locking" helpers Stanislav Fomichev
2025-03-31 15:06 ` [PATCH net v4 11/11] netdev: don't hold rtnl_lock over nl queue info get when possible Stanislav Fomichev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250331135421.018c49db@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.