netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislav Fomichev <stfomichev@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Stanislav Fomichev <sdf@fomichev.me>,
	netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com
Subject: Re: [PATCH net v4 07/11] docs: net: document netdev notifier expectations
Date: Mon, 31 Mar 2025 14:49:27 -0700	[thread overview]
Message-ID: <Z-sN51vNmepkwPc8@mini-arch> (raw)
In-Reply-To: <20250331135825.32acfce7@kernel.org>

On 03/31, Jakub Kicinski wrote:
> On Mon, 31 Mar 2025 08:05:59 -0700 Stanislav Fomichev wrote:
> > +The following notifiers are running without the lock (so the ops-locked
> > +devices need to manually grab the lock if needed):
> 
> Not sure about the text in the parenthesis, "the devices" don't "grab
> the lock". I mean - drivers don't generally register for notifications
> about their own devices. It's whoever registered the notifier that needs
> to make sure they take appropriate locks. I think we're fine without
> that sentence.

Good point, I was mostly referring to dev_ vs netif_ calls for managing
lower devices, will drop the sentence.

> > +* ``NETDEV_UNREGISTER``
> > +
> > +There are no clear expectations for the remaining notifiers. Notifiers not on
> > +the list may run with or without the instance lock, potentially even invoking
> > +the same notifier type with and without the lock from different code paths.
> > +The goal is to eventually ensure that all (or most, with a few documented
> > +exceptions) notifiers run under the instance lock.
> 
> Should we add a sentence here along the lines of "Please extend this
> documentation whenever you make explicit assumption about lock being
> held from a notifier." or is that obvious?

Yes, that was the assumption, but let's explicitly state that, shouldn't
hurt.

  reply	other threads:[~2025-03-31 21:49 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
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 [this message]
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=Z-sN51vNmepkwPc8@mini-arch \
    --to=stfomichev@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).