Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1229755pxk; Fri, 25 Sep 2020 09:18:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzFihQL5geLajini4Ey6I568zD0sPv4Rn6zsKFz4OQlnAyHMH/mSbntYB5aAavd9cLDAM/w X-Received: by 2002:a17:906:5509:: with SMTP id r9mr3593061ejp.12.1601050720815; Fri, 25 Sep 2020 09:18:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601050720; cv=none; d=google.com; s=arc-20160816; b=qG3k0Vzbe1SquN/dAhd6nJgcMG9PA5S4fpwLl3tF9XJ/vT2hbIB4yhs9tEDrwg15xp eAjEbhsMQhtpFZ7EdaxcEIX/d3c2OzatkZRA6wf04nWMII0e4e3TRhTdJKobGhloq0M/ 3HOJtpkTh/6YyHki+XmRf3NVxN3dQDCd/Ze0UuUnJG6TfTFX2dkR67T6E8rQf8e9EmYo CkmspGqQPuKXoDvZSRPLrsmPNMsMW378WCHpI2ACqxT9xxZnMEni0a880vy982ICPEdi O69DH6TnhDNKIk+oHgZrgAdkcCPquhngMWL5fldKkiYGlni9rRj9bZ49EBnt2kb67tvt VVDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:message-id:in-reply-to :date:references:organization:subject:cc:to:from; bh=YweaTWLi9ig4meK6SfWYT1+6qouMJ3jq6mdMR85m4Ds=; b=AIbYfzLhnEOlyXNDHJZ5d/FMreofpNu9gD+7DLR1TYLPexasiqxq2pGOBrYkP64APv P0UH8fvgURhtOImDTIINaWYa69P2wo/2E22mVxio8B8OMNvEAujlglGGxyUoxPiBUwDk QxSOmz0DeTIh4yAEPzJNinMHWMkkp3H9T/a4X35sMOHw7hdAk2JZVWLL6eoynoAEPy3I vGKh0tdg3jQhZXGJCJYe5WgoCX2AX2N6ETWVpe35gxsN2LGtmoI8+AXQQilQWqTXtBrj 6E6dVevllv06bqw57luRKvyMLsHcnMZB0iyDg47Q6aNSU4B9x8Dle8kdR9B33+vLmcfo KMrg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u6si2586343ejf.115.2020.09.25.09.18.17; Fri, 25 Sep 2020 09:18:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729021AbgIYQQA (ORCPT + 99 others); Fri, 25 Sep 2020 12:16:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42124 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727402AbgIYQP7 (ORCPT ); Fri, 25 Sep 2020 12:15:59 -0400 Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e3e3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A9498C0613CE; Fri, 25 Sep 2020 09:15:59 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: krisman) with ESMTPSA id 9F94829D78D From: Gabriel Krisman Bertazi To: Thomas Gleixner Cc: Kees Cook , luto@kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, willy@infradead.org, linux-kselftest@vger.kernel.org, shuah@kernel.org, kernel@collabora.com Subject: Re: [PATCH v6 1/9] kernel: Support TIF_SYSCALL_INTERCEPT flag Organization: Collabora References: <20200904203147.2908430-1-krisman@collabora.com> <20200904203147.2908430-2-krisman@collabora.com> <202009221243.6BC5635E@keescook> <874kno6yct.fsf@collabora.com> <202009231349.4A25EAF@keescook> <87o8luuvze.fsf@nanos.tec.linutronix.de> Date: Fri, 25 Sep 2020 12:15:54 -0400 In-Reply-To: <87o8luuvze.fsf@nanos.tec.linutronix.de> (Thomas Gleixner's message of "Fri, 25 Sep 2020 10:00:21 +0200") Message-ID: <87k0whsuh1.fsf@collabora.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thomas Gleixner writes: > On Wed, Sep 23 2020 at 13:49, Kees Cook wrote: >> On Wed, Sep 23, 2020 at 04:18:26PM -0400, Gabriel Krisman Bertazi wrote: >>> Kees Cook writes: >>> Yes, we can, and I'm happy to follow up with that as part of my TIF >>> clean up work, but can we not block the current patchset to be merged >>> waiting for that, as this already grew a lot from the original feature >>> submission? >> >> In that case, I'd say just add the new TIF flag. The consolidation can >> come later. > > No. This is exactly the wrong order. Cleanup and consolidation have > precedence over features. I'm tired of 'we'll do that later' songs, > simply because in the very end I'm going to be the idiot who mops up the > resulting mess. > No problem. I will follow up with a patchset consolidating those flags into this syscall_intercept interface I proposed. I assume there is no immediate concerns with the consolidation approach itself. -- Gabriel Krisman Bertazi