summaryrefslogtreecommitdiff
path: root/net/xfrm/xfrm_algo.c
diff options
context:
space:
mode:
authorVictor Nogueira <victor@mojatatu.com>2024-02-08 01:29:02 +0300
committerJakub Kicinski <kuba@kernel.org>2024-02-09 23:57:25 +0300
commitaae09a6c7783e28d1bcafee85e172fe411923b22 (patch)
tree6f5f4b177f1489774db9741a668a67a9d14238e8 /net/xfrm/xfrm_algo.c
parent6a12401b65a5ba57cfe1361c9a3e054ffde68611 (diff)
downloadlinux-aae09a6c7783e28d1bcafee85e172fe411923b22.tar.xz
net/sched: act_mirred: Don't zero blockid when net device is being deleted
While testing tdc with parallel tests for mirred to block we caught an intermittent bug. The blockid was being zeroed out when a net device was deleted and, thus, giving us an incorrect blockid value whenever we tried to dump the mirred action. Since we don't increment the block refcount in the control path (and only use the ID), we don't need to zero the blockid field whenever a net device is going down. Fixes: 42f39036cda8 ("net/sched: act_mirred: Allow mirred to block") Signed-off-by: Victor Nogueira <victor@mojatatu.com> Reviewed-by: Simon Horman <horms@kernel.org> Reviewed-by: Eric Dumazet <edumazet@google.com> Acked-by: Jamal Hadi Salim <jhs@mojatatu.com> Link: https://lore.kernel.org/r/20240207222902.1469398-1-victor@mojatatu.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/xfrm/xfrm_algo.c')
0 files changed, 0 insertions, 0 deletions