[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210706154416.v63cvb6ylr5cnyxo@kafai-mbp.dhcp.thefacebook.com>
Date: Tue, 6 Jul 2021 08:44:16 -0700
From: Martin KaFai Lau <kafai@...com>
To: David Laight <David.Laight@...LAB.COM>
CC: "bpf@...r.kernel.org" <bpf@...r.kernel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Eric Dumazet <edumazet@...gle.com>,
"kernel-team@...com" <kernel-team@...com>,
Neal Cardwell <ncardwell@...gle.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Yonghong Song <yhs@...com>, Yuchung Cheng <ycheng@...gle.com>
Subject: Re: [PATCH v2 bpf-next 0/8] bpf: Allow bpf tcp iter to do
bpf_(get|set)sockopt
On Fri, Jul 02, 2021 at 10:50:43AM +0000, David Laight wrote:
> From: Martin KaFai Lau
> > Sent: 01 July 2021 21:06
> >
> > This set is to allow bpf tcp iter to call bpf_(get|set)sockopt.
>
> How does that work at all?
>
> IIRC only setsockopt() was converted so that it is callable
> with a kernel buffer.
> The corresponding change wasn't done to getsockopt().
It calls _bpf_getsockopt which does not depend on sys_getsockopt.
Powered by blists - more mailing lists