lwt: disable BH too in run_lwt_bpf()
Subsystems (3)
PATCH v2 1/2 lwt: disable BH too in run_lwt_bpf()
From: Dongdong Wang <[email protected]>
The per-cpu bpf_redirect_info is shared among all skb_do_redirect() and BPF redirect helpers. Callers on RX path are all in BH context, disabling preemption is not sufficient to prevent BH interruption.
In production, we observed strange packet drops because of the race condition between LWT xmit and TC ingress, and we verified this issue is fixed after we disable BH.
Although this bug was technically introduced from the beginning, that is commit 3a0af8fd61f9 ("bpf: BPF for lightweight tunnel infrastructure"), at that time call_rcu() had to be call_rcu_bh() to match the RCU context. So this patch may not work well before RCU flavor consolidation has been completed around v5.0.
Update the comments above the code too, as call_rcu() is now BH friendly.
--- net/core/lwt_bpf.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
net/core/lwt_bpf.c +4 -4
@@ -39,12 +39,11 @@ static int run_lwt_bpf(struct sk_buff *skb, struct bpf_lwt_prog *lwt, {int ret; -/* Preempt disable is needed to protect per-cpu redirect_info between -* BPF prog and skb_do_redirect(). The call_rcu in bpf_prog_put() and -* access to maps strictly require a rcu_read_lock() for protection, -* mixing with BH RCU lock doesn't work. +/* Preempt disable and BH disable are needed to protect per-cpu +* redirect_info between BPF prog and skb_do_redirect(). */ preempt_disable (); +local_bh_disable ();bpf_compute_data_pointers (skb); ret =bpf_prog_run_save_cb (lwt->prog, skb);
@@ -78,6 +77,7 @@ static int run_lwt_bpf(struct sk_buff *skb, struct bpf_lwt_prog *lwt,break ; } +local_bh_enable ();preempt_enable ();return ret;
Signature · 1 line
2.25.1
PATCH v2 2/2 lwt_bpf: replace preempt_disable() with migrate_disable()
From: Cong Wang <[email protected]>
migrate_disable() is just a wrapper for preempt_disable() in non-RT kernel. It is safe to replace it, and RT kernel will benefit.
Note that it is introduced since Feb 2020.
--- net/core/lwt_bpf.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
net/core/lwt_bpf.c +3 -3
@@ -39,10 +39,10 @@ static int run_lwt_bpf(struct sk_buff *skb, struct bpf_lwt_prog *lwt, {int ret; -/* Preempt disable and BH disable are needed to protect per-cpu +/* Migration disable and BH disable are needed to protect per-cpu * redirect_info between BPF prog and skb_do_redirect(). */ -preempt_disable (); +migrate_disable ();local_bh_disable ();bpf_compute_data_pointers (skb); ret =bpf_prog_run_save_cb (lwt->prog, skb);
@@ -78,7 +78,7 @@ static int run_lwt_bpf(struct sk_buff *skb, struct bpf_lwt_prog *lwt, }local_bh_enable (); -preempt_enable (); +migrate_enable ();return ret; }
Signature · 1 line
2.25.1
This series was applied to bpf/bpf.git (refs/heads/master):
Hello:
This series was applied to bpf/bpf.git (refs/heads/master):
Quoted 11 lines · On Fri, 4 Dec 2020 23:59:45 -0800 you wrote:
From: Dongdong Wang <[email protected]>
The per-cpu
bpf_redirect_infois shared among allskb_do_redirect()and BPF redirect helpers. Callers on RX path are all in BH context, disabling preemption is not sufficient to prevent BH interruption.In production, we observed strange packet drops because of the race condition between LWT xmit and TC ingress, and we verified this issue is fixed after we disable BH.
[...]
Here is the summary with links:
- [net,v2,1/2] lwt: disable BH too in run_lwt_bpf()
https://git.kernel.org/bpf/bpf/c/d9054a1ff585 - [net,v2,2/2] lwt_bpf: replace preempt_disable() with migrate_disable() https://git.kernel.org/bpf/bpf/c/e3366884b383
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html