From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 38BDFC32756 for ; Thu, 8 Aug 2019 21:12:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0B2D02184E for ; Thu, 8 Aug 2019 21:12:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="ACf43qcD" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725535AbfHHVMX (ORCPT ); Thu, 8 Aug 2019 17:12:23 -0400 Received: from mail-pg1-f194.google.com ([209.85.215.194]:46059 "EHLO mail-pg1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390427AbfHHVMW (ORCPT ); Thu, 8 Aug 2019 17:12:22 -0400 Received: by mail-pg1-f194.google.com with SMTP id o13so44676684pgp.12 for ; Thu, 08 Aug 2019 14:12:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=ylddyGuuUpJhKUvK1ev1Q44hiLLmL8PwyC4MRMb3mUE=; b=ACf43qcDjfXfx13Z+1Gsw1UZV/Uosrf1yEiF0Agjii4NCq0aSJm4NT0QzSwLCl7Dc5 gq+wLSnVQcR3qxZ0fm9hvoSL16jb4cCF5OkMFfCEBQn0MQdPfLlk2tDzdSCLPp3vIQBd UxRwIr8unIchMakLD/5qyLX3unblGeVjDLQfg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=ylddyGuuUpJhKUvK1ev1Q44hiLLmL8PwyC4MRMb3mUE=; b=F7hM2b8vM3kUcTmW94c7Ee/uWaXlsFNYrsZYhFbFFVaginARcMc3CyFKMmxeDvdRR6 H4+VD0G6Ba/efHlzK2N6a7J3b6tGYIImdG2zYMd9x0EFoTNsFYfsJl0yNk4h8fJ4+QlE TsTY2oxn0mbCECc8BllZ40Zm1r+28qt0H8gRi2QAq4xxaKFOoOTpeXG3gMKB2jFv8ylZ ubtS0Nf82oY95qm/I35OEpRNnwhJEdYrSVyTIa7KLvb9bivM1m/L1wx12WJsT5Mb+XwI 8SsuodwPhXeVa12+4GSBHbSfwyohACC6uFIZaVGT6xeHR508xcgcgm8fx7i61aNbHYs4 UMrw== X-Gm-Message-State: APjAAAVQrWgrncraKxdZ/1A3SNcbD9jy+7Z3sXmJ09OOkc2TO4gRSi7z hxfiyuJ0aTbJy457c4Ff2PCA/Q== X-Google-Smtp-Source: APXvYqy0pdWoHPkerneL5407ilt1ySmaIIJNjNXYxB0G6sGkOR++FLPJzal2z8CcZbjPxvclbtt+OA== X-Received: by 2002:a62:1750:: with SMTP id 77mr17827956pfx.172.1565298741745; Thu, 08 Aug 2019 14:12:21 -0700 (PDT) Received: from www.outflux.net (smtp.outflux.net. [198.145.64.163]) by smtp.gmail.com with ESMTPSA id q19sm101457867pfc.62.2019.08.08.14.12.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 08 Aug 2019 14:12:20 -0700 (PDT) Date: Thu, 8 Aug 2019 14:12:19 -0700 From: Kees Cook To: Andrey Konovalov Cc: Will Deacon , Andrew Morton , Will Deacon , Vincenzo Frascino , Catalin Marinas , Mark Rutland , kvm@vger.kernel.org, Szabolcs Nagy , dri-devel@lists.freedesktop.org, Kostya Serebryany , Khalid Aziz , "open list:KERNEL SELFTEST FRAMEWORK" , Felix Kuehling , Jacob Bramley , Leon Romanovsky , linux-rdma@vger.kernel.org, amd-gfx@lists.freedesktop.org, Christoph Hellwig , Jason Gunthorpe , Linux ARM , Dave Martin , Evgeniy Stepanov , linux-media@vger.kernel.org, Kevin Brodsky , Ruben Ayrapetyan , Ramana Radhakrishnan , Alex Williamson , Mauro Carvalho Chehab , Dmitry Vyukov , Linux Memory Management List , Greg Kroah-Hartman , Yishai Hadas , LKML , Jens Wiklander , Lee Smith , Alexander Deucher , enh , Robin Murphy , Christian Koenig , Luc Van Oostenryck Subject: Re: [PATCH v19 00/15] arm64: untag user pointers passed to the kernel Message-ID: <201908081410.C16D2BD@keescook> References: <20190724140212.qzvbcx5j2gi5lcoj@willie-the-truck> <20190724142059.GC21234@fuggles.cambridge.arm.com> <20190806171335.4dzjex5asoertaob@willie-the-truck> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kselftest-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kselftest@vger.kernel.org On Wed, Aug 07, 2019 at 07:17:35PM +0200, Andrey Konovalov wrote: > On Tue, Aug 6, 2019 at 7:13 PM Will Deacon wrote: > > > > On Wed, Jul 24, 2019 at 03:20:59PM +0100, Will Deacon wrote: > > > On Wed, Jul 24, 2019 at 04:16:49PM +0200, Andrey Konovalov wrote: > > > > On Wed, Jul 24, 2019 at 4:02 PM Will Deacon wrote: > > > > > On Tue, Jul 23, 2019 at 08:03:29PM +0200, Andrey Konovalov wrote: > > > > > > Should this go through the mm or the arm tree? > > > > > > > > > > I would certainly prefer to take at least the arm64 bits via the arm64 tree > > > > > (i.e. patches 1, 2 and 15). We also need a Documentation patch describing > > > > > the new ABI. > > > > > > > > Sounds good! Should I post those patches together with the > > > > Documentation patches from Vincenzo as a separate patchset? > > > > > > Yes, please (although as you say below, we need a new version of those > > > patches from Vincenzo to address the feedback on v5). The other thing I > > > should say is that I'd be happy to queue the other patches in the series > > > too, but some of them are missing acks from the relevant maintainers (e.g. > > > the mm/ and fs/ changes). > > > > Ok, I've queued patches 1, 2, and 15 on a stable branch here: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=for-next/tbi > > > > which should find its way into -next shortly via our for-next/core branch. > > If you want to make changes, please send additional patches on top. > > > > This is targetting 5.4, but I will drop it before the merge window if > > we don't have both of the following in place: > > > > * Updated ABI documentation with Acks from Catalin and Kevin > > Catalin has posted a new version today. > > > * The other patches in the series either Acked (so I can pick them up) > > or queued via some other tree(s) for 5.4. > > So we have the following patches in this series: > > 1. arm64: untag user pointers in access_ok and __uaccess_mask_ptr > 2. arm64: Introduce prctl() options to control the tagged user addresses ABI > 3. lib: untag user pointers in strn*_user > 4. mm: untag user pointers passed to memory syscalls > 5. mm: untag user pointers in mm/gup.c > 6. mm: untag user pointers in get_vaddr_frames > 7. fs/namespace: untag user pointers in copy_mount_options > 8. userfaultfd: untag user pointers > 9. drm/amdgpu: untag user pointers > 10. drm/radeon: untag user pointers in radeon_gem_userptr_ioctl > 11. IB/mlx4: untag user pointers in mlx4_get_umem_mr > 12. media/v4l2-core: untag user pointers in videobuf_dma_contig_user_get > 13. tee/shm: untag user pointers in tee_shm_register > 14. vfio/type1: untag user pointers in vaddr_get_pfn > 15. selftests, arm64: add a selftest for passing tagged pointers to kernel > > 1, 2 and 15 have been picked by Will. > > 11 has been picked up by Jason. > > 9, 10, 12, 13 and 14 have acks from their subsystem maintainers. > > 3 touches generic lib code, I'm not sure if there's a dedicated > maintainer for that. Andrew tends to pick up lib/ patches. > The ones that are left are the mm ones: 4, 5, 6, 7 and 8. > > Andrew, could you take a look and give your Acked-by or pick them up directly? Given the subsystem Acks, it seems like 3-10 and 12 could all just go via Andrew? I hope he agrees. :) -- Kees Cook