[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20171003.160500.1804100102889469834.davem@davemloft.net>
Date: Tue, 03 Oct 2017 16:05:00 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: ast@...com
Cc: daniel@...earbox.net, kafai@...com, netdev@...r.kernel.org,
kernel-team@...com
Subject: Re: [PATCH net] bpf: fix bpf_tail_call() x64 JIT
From: Alexei Starovoitov <ast@...com>
Date: Tue, 3 Oct 2017 15:37:20 -0700
> - bpf prog_array just like all other types of bpf array accepts 32-bit index.
> Clarify that in the comment.
> - fix x64 JIT of bpf_tail_call which was incorrectly loading 8 instead of 4 bytes
> - tighten corresponding check in the interpreter to stay consistent
>
> The JIT bug can be triggered after introduction of BPF_F_NUMA_NODE flag
> in commit 96eabe7a40aa in 4.14. Before that the map_flags would stay zero and
> though JIT code is wrong it will check bounds correctly.
> Hence two fixes tags. All other JITs don't have this problem.
>
> Signed-off-by: Alexei Starovoitov <ast@...nel.org>
> Fixes: 96eabe7a40aa ("bpf: Allow selecting numa node during map creation")
> Fixes: b52f00e6a715 ("x86: bpf_jit: implement bpf_tail_call() helper")
> Acked-by: Daniel Borkmann <daniel@...earbox.net>
> Acked-by: Martin KaFai Lau <kafai@...com>
> ---
> Backport to stable would be nice, but not strictly necessary.
Applied and queued up for -stable, thanks.
Powered by blists - more mailing lists