[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4f443bc-665c-379b-b73c-a6ca1ce5d701@fb.com>
Date: Mon, 7 Mar 2022 09:07:43 -0800
From: Yonghong Song <yhs@...com>
To: Shung-Hsi Yu <shung-hsi.yu@...e.com>, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>, netdev@...r.kernel.org
Subject: Re: [PATCH bpf-next] bpf: determine buf_info inside
check_buffer_access()
On 3/6/22 9:29 PM, Shung-Hsi Yu wrote:
> Instead of determining buf_info string in the caller of
> check_buffer_access(), we can determine whether the register type is read-only
> through type_is_rdonly_mem() helper inside check_buffer_access() and construct
> buf_info, making the code slightly cleaner.
>
> Signed-off-by: Shung-Hsi Yu <shung-hsi.yu@...e.com>
LGTM. Thanks.
Acked-by: Yonghong Song <yhs@...com>
Powered by blists - more mailing lists