summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2021-11-01 13:26:07 +0000
committerDavid S. Miller <davem@davemloft.net>2021-11-01 13:26:07 +0000
commit1adc58ea2330cd014fde8a254480441e10ee280d (patch)
treebd94424fa9d4bf6788edba77057a6822f3007d14 /tools/perf/scripts/python/stackcollapse.py
parentc6e03dbe0c7cdbe7b259deeae0f193d15ec5002f (diff)
parent1af0a0948e28d83bcfa9d48cd0f992f616c5d62e (diff)
Merge branch 'devlink-locking'
Jakub Kicinski says: ==================== improve ethtool/rtnl vs devlink locking During ethtool netlink development we decided to move some of the commmands to devlink. Since we don't want drivers to implement both devlink and ethtool version of the commands ethtool ioctl falls back to calling devlink. Unfortunately devlink locks must be taken before rtnl_lock. This results in a questionable dev_hold() / rtnl_unlock() / devlink / rtnl_lock() / dev_put() pattern. This method "works" but it working depends on drivers in question not doing much in ethtool_ops->begin / complete, and on the netdev not having needs_free_netdev set. Since commit 437ebfd90a25 ("devlink: Count struct devlink consumers") we can hold a reference on a devlink instance and prevent it from going away (sort of like netdev with dev_hold()). We can use this to create a more natural reference nesting where we get a ref on the devlink instance and make the devlink call entirely outside of the rtnl_lock section. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions