On Fri, Mar 9, 2018 at 4:58 PM, Catalin Marinas <catalin.marinas@xxxxxxx> wrote: > On Fri, Mar 09, 2018 at 03:03:09PM +0000, Mark Rutland wrote: >> On Fri, Mar 09, 2018 at 03:02:00PM +0100, Andrey Konovalov wrote: >> > copy_from_user (and a few other similar functions) are used to copy data >> > from user memory into the kernel memory or vice versa. Since a user can >> > provided a tagged pointer to one of the syscalls that use copy_from_user, >> > we need to correctly handle such pointers. >> >> I don't think it makes sense to do this in the low-level uaccess >> primitives, given we're going to have to untag pointers before common >> code can use them, e.g. for comparisons against TASK_SIZE or >> user_addr_max(). >> >> I think we'll end up with subtle bugs unless we consistently untag >> pointers before we get to uaccess primitives. If core code does untag >> pointers, then it's redundant to do so here. There are two different approaches to untagging the user pointers that I see: 1. Untag user pointers right after they are passed to the kernel. While this might be possible for pointers that are passed to syscalls as arguments (Catalin's "hack"), this leaves user pointers, that are embedded into for example structs that are passed to the kernel. Since there's no specification of the interface between user space and the kernel, different kernel parts handle user pointers differently and I don't see an easy way to cover them all. 2. Untag user pointers where they are used in the kernel. Although there's no specification on the interface between the user space and the kernel, the kernel still has to use one of a few specific ways to access user data (copy_from_user, etc.). So the idea here is to add untagging into them. This patchset mostly takes this approach (with the exception of memory subsystem syscalls). If there's a better approach, I'm open to suggestions.
