summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-07-21 12:25:10 -0700
committerJakub Kicinski <kuba@kernel.org>2026-07-21 12:25:45 -0700
commitf14a8561f3c548bec4ff2f3b5507978dd77a50b0 (patch)
tree2e2dc81dc78d01d7c51bd707819ab838358a1b8e /tools/perf/scripts/python/task-analyzer.py
parentf2596ce59b151b4bac31f355ea82bed22b57d502 (diff)
parentaa22336b76b732d2c890f9de3419e05873711027 (diff)
Merge branch 'align-ipv4-teardown-with-ipv6-and-fix-driver-regressions'
Yuyang Huang says: ==================== align IPv4 teardown with IPv6 and fix driver regressions This series aligns the IPv4 address teardown sequence with IPv6 by clearing dev->ip_ptr early in inetdev_destroy() before freeing the multicast list and individual IP addresses. This prevents RCU readers from accessing a partially destroyed in_device structure. However, clearing dev->ip_ptr early causes __in_dev_get_rtnl() to return NULL during the notifier loop in inetdev_destroy(). This causes regressions in some drivers (prestera and mac80211) that use this lookup helper in their inetaddr notifier callbacks. To prevent regressions and maintain bisectability, this series first fixes the affected drivers (Patch 1 and 2) before applying the core IPv4 change (Patch 3). An audit was performed on all other registered inetaddr and inet6addr notifier listeners, and no other drivers were found to be affected. ==================== Link: https://patch.msgid.link/20260711005405.2861680-1-yuyanghuang@google.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions