Re: get rid of the address_space override in setsockopt v2

From: David Miller
Date: Fri Jul 24 2020 - 18:43:48 EST

From: Christoph Hellwig <hch@xxxxxx>
Date: Thu, 23 Jul 2020 08:08:42 +0200

> setsockopt is the last place in architecture-independ code that still
> uses set_fs to force the uaccess routines to operate on kernel pointers.
> This series adds a new sockptr_t type that can contained either a kernel
> or user pointer, and which has accessors that do the right thing, and
> then uses it for setsockopt, starting by refactoring some low-level
> helpers and moving them over to it before finally doing the main
> setsockopt method.
> Note that apparently the eBPF selftests do not even cover this path, so
> the series has been tested with a testing patch that always copies the
> data first and passes 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, or in
> case of bpfilter straight out do not work with kernel pointers at all.
> Against net-next/master.
> Changes since v1:
> - check that users don't pass in kernel addresses
> - more bpfilter cleanups
> - cosmetic mptcp tweak

Series applied to net-next, I'm build testing and will push this out when
that is done.