Thread (50 messages) 50 messages, 9 authors, 2020-07-22

Re: get rid of the address_space override in setsockopt

From: Alexei Starovoitov <hidden>
Date: 2020-07-22 17:09:58
Also in: bpf, bridge, linux-can, linux-crypto, linux-hams, linux-s390, linux-sctp, lkml, lvs-devel, mptcp, netdev, netfilter-devel

On Wed, Jul 22, 2020 at 12:56 AM Christoph Hellwig [off-list ref] wrote:
On Mon, Jul 20, 2020 at 01:47:56PM -0700, Alexei Starovoitov wrote:
quoted
quoted
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.
Right. I've realized that after sending that email two days ago.
Now bpf-next->net-next PR is pending and as soon as it's merged
bpf-next will have all the recent bits.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help