net: document NETDEV_UNREGISTER unlocked rationale

The lock-state table marks UNREGISTER as unlocked without saying
why. Add a short note that many handlers release the lowers via
dev_close().

Signed-off-by: Stanislav Fomichev <sdf@fomichev.me>
Link: https://patch.msgid.link/20260702224150.3730033-7-sdf@fomichev.me
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
This commit is contained in:
Stanislav Fomichev 2026-07-02 15:41:50 -07:00 committed by Paolo Abeni
parent f540caaaca
commit 538d89fd91

View File

@ -427,6 +427,11 @@ running under the lock:
The following notifiers are running without the lock:
* ``NETDEV_UNREGISTER``
Many SW devices (uppers) catch their lower's ``NETDEV_UNREGISTER``
events and may interact with them via ``dev_*()`` handlers, which take
the instance lock. Until we convert these devices to ``netif_*()`` variants,
``NETDEV_UNREGISTER`` stays unlocked.
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.