Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp74314ybl; Fri, 9 Aug 2019 02:44:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqxY+V2H5KdqVHNIjmhFMw1jNIeW3YO5F90XXm3ZadMbkeWl+tPc7IwW/ObHYI2GDNcN7W5N X-Received: by 2002:a17:902:547:: with SMTP id 65mr8331064plf.131.1565343848829; Fri, 09 Aug 2019 02:44:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565343848; cv=none; d=google.com; s=arc-20160816; b=e8nqnshmTnyRTuDr6TTGEYrTKSwyIZMPFToaXFFdXMztHtaxnm84zwQWVD47SXLH+j qnLKG7l8ut8hdRuBZlxiuINuM+ZCZ/Rr5XhOrzgvB1/BvkAjPkbZyc4XLegiJuZioIg5 dyJVwxQv4Vrf1hK2RB1Lr8bQL7epK2smGwwDx61caTSecq2/lFuiwTWenyBNl1U2R9D+ fEhyd+HQYa4l1or9/yw53+WNk+EgMCt/cjTCWex84Z+zEHSzi22nUT2CIQrt+TOXRzyI geGOC3XGilgAdYQ0lcxTMyZO3Q5Q95kkL0hsNw+9janpAzTJQl3UcZ6SsrKhGVxMlAk2 x+5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=aptc2LF/zzqfCq3WoHKiATpIya7Ph+iVegpzlEO9b8E=; b=kqGQQ++2gSOqt5MxwwIZ+YNQvjueIeIjUIGCDqR85Sf9NxezDwXDQCZXK2ukf0gH0y znOJkD8h50wm1ODVXYrh4I6S7uE+snq1NwyxEYV2OYt58tdMcmvVmIRo8WTdWS8uAS4S OlbnsBYvTuiJPOR0qrMLwwwOyAgUKr/t3EDp/1hHtgbWNhnHicCVTXa9dobPr3iwEhCq cnr2hb5bt7j3QSnMKkCPArJVuAJbKkU3ifUS3rE7NDe+zMUqeEFis9N6deKw57TbrMY3 PbB4mBhZwpIEx4je6+mTep2n5bkZwwvp9HSJJr+s0jN0oVivXTPQwpksYg4fbm7dYw+2 gEUQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j7si62464068pfi.10.2019.08.09.02.43.53; Fri, 09 Aug 2019 02:44:08 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2406128AbfHIJ2J (ORCPT + 99 others); Fri, 9 Aug 2019 05:28:09 -0400 Received: from foss.arm.com ([217.140.110.172]:44118 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726233AbfHIJ2J (ORCPT ); Fri, 9 Aug 2019 05:28:09 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id D4D7415A2; Fri, 9 Aug 2019 02:28:07 -0700 (PDT) Received: from arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id EA7C43F575; Fri, 9 Aug 2019 02:28:02 -0700 (PDT) Date: Fri, 9 Aug 2019 10:28:00 +0100 From: Dave Martin To: Catalin Marinas Cc: Kees Cook , Mark Rutland , kvm@vger.kernel.org, Christian Koenig , Szabolcs Nagy , Will Deacon , dri-devel@lists.freedesktop.org, Kostya Serebryany , Khalid Aziz , Lee Smith , "open list:KERNEL SELFTEST FRAMEWORK" , Vincenzo Frascino , Will Deacon , Jacob Bramley , Leon Romanovsky , linux-rdma@vger.kernel.org, amd-gfx@lists.freedesktop.org, Christoph Hellwig , Jason Gunthorpe , Dmitry Vyukov , Evgeniy Stepanov , linux-media@vger.kernel.org, Ruben Ayrapetyan , Andrey Konovalov , Kevin Brodsky , Alex Williamson , Mauro Carvalho Chehab , Linux ARM , Linux Memory Management List , Greg Kroah-Hartman , Felix Kuehling , Dave Hansen , LKML , Jens Wiklander , Ramana Radhakrishnan , Alexander Deucher , Andrew Morton , enh , Robin Murphy , Yishai Hadas , Luc Van Oostenryck Subject: Re: [PATCH v19 00/15] arm64: untag user pointers passed to the kernel Message-ID: <20190809092758.GK10425@arm.com> References: <20190724140212.qzvbcx5j2gi5lcoj@willie-the-truck> <20190724142059.GC21234@fuggles.cambridge.arm.com> <20190806171335.4dzjex5asoertaob@willie-the-truck> <201908081410.C16D2BD@keescook> <20190808153300.09d3eb80772515f0ea062833@linux-foundation.org> <201908081608.A4F6711@keescook> <20190809090016.GA23083@arrakis.emea.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190809090016.GA23083@arrakis.emea.arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 09, 2019 at 10:00:17AM +0100, Catalin Marinas wrote: > On Thu, Aug 08, 2019 at 04:09:04PM -0700, Kees Cook wrote: > > On Thu, Aug 08, 2019 at 03:33:00PM -0700, Andrew Morton wrote: > > > On Thu, 8 Aug 2019 14:12:19 -0700 Kees Cook wrote: > > > > > > > > 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. :) > > > > > > I'll grab everything that has not yet appeared in linux-next. If more > > > of these patches appear in linux-next I'll drop those as well. > > > > > > The review discussion against " [PATCH v19 02/15] arm64: Introduce > > > prctl() options to control the tagged user addresses ABI" has petered > > > out inconclusively. prctl() vs arch_prctl(). > > > > I've always disliked arch_prctl() existing at all. Given that tagging is > > likely to be a multi-architectural feature, it seems like the controls > > should live in prctl() to me. > > It took a bit of grep'ing to figure out what Dave H meant by > arch_prctl(). It's an x86-specific syscall which we do not have on arm64 > (and possibly any other architecture). Actually, we don't have any arm64 > specific syscalls, only the generic unistd.h, hence the confusion. For > other arm64-specific prctls like SVE we used the generic sys_prctl() and > I can see x86 not being consistent either (PR_MPX_ENABLE_MANAGEMENT). > > In general I disagree with adding any arm64-specific syscalls but in > this instance it can't even be justified. I'd rather see some clean-up > similar to arch_ptrace/ptrace_request than introducing new syscall > numbers (but as I suggested in my reply to Dave, that's for another > patch series). I had a go at refactoring this a while ago, but it fell by the wayside. I can try to resurrect it if it's still considered worthwhile. Cheers ---Dave