Re: [PATCH bpf-next] lwt_bpf: remove unnecessary rcu_read_lock in run_lwt_bpf

2018-07-31 Thread Daniel Borkmann
On 07/30/2018 03:22 PM, Taehee Yoo wrote: > run_lwt_bpf is called by bpf_{input/output/xmit}. > These functions are already protected by rcu_read_lock. > because lwtunnel_{input/output/xmit} holds rcu_read_lock > and then calls bpf_{input/output/xmit}. > So that rcu_read_lock in the run_lwt_bpf is

Re: [PATCH bpf-next] lwt_bpf: remove unnecessary rcu_read_lock in run_lwt_bpf

2018-07-30 Thread Y Song
On Mon, Jul 30, 2018 at 6:22 AM, Taehee Yoo wrote: > run_lwt_bpf is called by bpf_{input/output/xmit}. > These functions are already protected by rcu_read_lock. > because lwtunnel_{input/output/xmit} holds rcu_read_lock > and then calls bpf_{input/output/xmit}. > So that rcu_read_lock in the run_l

[PATCH bpf-next] lwt_bpf: remove unnecessary rcu_read_lock in run_lwt_bpf

2018-07-30 Thread Taehee Yoo
run_lwt_bpf is called by bpf_{input/output/xmit}. These functions are already protected by rcu_read_lock. because lwtunnel_{input/output/xmit} holds rcu_read_lock and then calls bpf_{input/output/xmit}. So that rcu_read_lock in the run_lwt_bpf is unnecessary. Signed-off-by: Taehee Yoo --- net/co