[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230810143313.016929c5@kernel.org>
Date: Thu, 10 Aug 2023 14:33:13 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Martin KaFai Lau <martin.lau@...ux.dev>
Cc: davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
daniel@...earbox.net, andrii@...nel.org, ast@...nel.org,
netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: pull-request: bpf-next 2023-08-09
On Thu, 10 Aug 2023 14:26:01 -0700 Martin KaFai Lau wrote:
> On 8/10/23 2:19 PM, Jakub Kicinski wrote:
> > On Wed, 9 Aug 2023 22:51:23 -0700 Martin KaFai Lau wrote:
> >> bpf: fix bpf_dynptr_slice() to stop return an ERR_PTR.
> >
> > This one looks like solid bpf material TBH, any reason it's here?
>
> There is an earlier bpf_dynptr_check_off_len() call which should have caught
> that already, so ERR_PTR case should not happen.
> https://lore.kernel.org/bpf/e0e8bf3b-70af-3827-2fa3-30f3d48bcf46@linux.dev/
That kind of info needs to be in the commit message :(
Powered by blists - more mailing lists