[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240207205335.1465818-1-victor@mojatatu.com>
Date: Wed, 7 Feb 2024 17:53:35 -0300
From: Victor Nogueira <victor@...atatu.com>
To: jhs@...atatu.com,
xiyou.wangcong@...il.com,
jiri@...nulli.us,
davem@...emloft.net,
edumazet@...gle.com,
kuba@...nel.org,
pabeni@...hat.com,
netdev@...r.kernel.org
Cc: kernel@...atatu.com,
pctammela@...atatu.com
Subject: [PATCH net] net/sched: act_mirred: Don't zero blockid when netns is going down
While testing tdc with parallel tests for mirred to block we caught an
intermittent bug. The blockid was being zeroed out when a parallel net
namespace was going down and, thus, giving us an incorrect blockid value(0)
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 the net namespace is going down.
Fixes: 42f39036cda8 ("net/sched: act_mirred: Allow mirred to block")
Signed-off-by: Victor Nogueira <victor@...atatu.com>
---
net/sched/act_mirred.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/net/sched/act_mirred.c b/net/sched/act_mirred.c
index 93a96e9d8d90..6f4bb1c8ce7b 100644
--- a/net/sched/act_mirred.c
+++ b/net/sched/act_mirred.c
@@ -533,8 +533,6 @@ static int mirred_device_event(struct notifier_block *unused,
* net_device are already rcu protected.
*/
RCU_INIT_POINTER(m->tcfm_dev, NULL);
- } else if (m->tcfm_blockid) {
- m->tcfm_blockid = 0;
}
spin_unlock_bh(&m->tcf_lock);
}
--
2.34.1
Powered by blists - more mailing lists