diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-10-20 14:17:16 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-10-20 14:17:17 -0700 |
| commit | 06d870fe6c022b6c65f660fa502c2f7067749b23 (patch) | |
| tree | 5c561cede48cd2cb79ba1cb4816ba1206724a6a3 /rust/kernel/alloc/kvec/errors.rs | |
| parent | 15b7a86a8888dc6a8fd19e181757e32389de9064 (diff) | |
| parent | b5dc3fde8b92286a0cb06bf08e2ec0141cf867bb (diff) | |
| download | linux-06d870fe6c022b6c65f660fa502c2f7067749b23.tar.gz linux-06d870fe6c022b6c65f660fa502c2f7067749b23.zip | |
Merge branch 'ipv6-fix-suspicious-rcu-usage-in-route-hardware-flags-notification'
Ido Schimmel says:
====================
ipv6: Fix suspicious RCU usage in route hardware flags notification
fib6_info_hw_flags_set() is called by drivers to update the hardware
flags of an IPv6 route and to emit a notification when
fib_notify_on_flag_change is set. Drivers call it from process context
without RTNL or RCU, so when the route uses a nexthop object, building
the notification triggers suspicious RCU usage splats.
Patch #1 fixes the problem by holding RCU while building the
notification.
Patch #2 adds IPv4 and IPv6 test cases for routes that use nexthop
objects. Without patch #1, the IPv6 one triggers the splats.
====================
Link: https://patch.msgid.link/20261019140337.2886875-1-idosch@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'rust/kernel/alloc/kvec/errors.rs')
0 files changed, 0 insertions, 0 deletions