|
On Mon, Jul 20, 2020 at 01:47:56PM -0700, Alexei Starovoitov wrote:
> > a kernel pointer. This is something that works for most common sockopts
> > (and is something that the ePBF support relies on), but unfortunately
> > in various corner cases we either don't use the passed in length, or in
> > one case actually copy data back from setsockopt, so we unfortunately
> > can't just always do the copy in the highlevel code, which would have
> > been much nicer.
>
> could you rebase on bpf-next tree and we can route it this way then?
> we'll also test the whole thing before applying.
The bpf-next tree is missing all my previous setsockopt cleanups, so
there series won't apply.
|
