diff options
author | Jakub Kicinski <kuba@kernel.org> | 2025-03-25 01:45:30 +0300 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2025-03-25 20:06:44 +0300 |
commit | 4b702f8b72c7b05daa1b763fdc0840aa78178c3a (patch) | |
tree | 51dec262188c65f5bcd29af24fbeb30f41a5b15d /tools/perf/scripts/python/stackcollapse.py | |
parent | e2f81e8f4d0c3109e1a18620c931fe16bfb235ef (diff) | |
download | linux-4b702f8b72c7b05daa1b763fdc0840aa78178c3a.tar.xz |
net: explain "protection types" for the instance lock
Try to define some terminology for which fields are protected
by which lock and how. Some fields are protected by both rtnl_lock
and instance lock which is hard to talk about without having
a "key phrase" to refer to a particular protection scheme.
"ops protected" fields are defined later in the series, one by one.
Add ASSERT_RTNL() to netdev_ops_assert_locked() for drivers
not other instance protection of ops. Hopefully it's not too
confusion that netdev_lock_ops() does not match the lock which
netdev_ops_assert_locked() will assert, exactly. The noun "ops"
is in a different place in the name, so I think it's acceptable...
Acked-by: Stanislav Fomichev <sdf@fomichev.me>
Link: https://patch.msgid.link/20250324224537.248800-5-kuba@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions