Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp5441304ybv; Tue, 11 Feb 2020 16:02:49 -0800 (PST) X-Google-Smtp-Source: APXvYqzBRQ9YWhxUOZJGKaKNFxRFxaBcJq+KLO9g8Fx2nggRajYyalvxegGXh+TkOZ8ekMNpx1w+ X-Received: by 2002:a9d:4f17:: with SMTP id d23mr7363959otl.170.1581465769785; Tue, 11 Feb 2020 16:02:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581465769; cv=none; d=google.com; s=arc-20160816; b=sI4mtelu9m8eSSLpOuf7a0/cvhTQT5CDjExLu408Rm9musrJbvNs2N154prfEfBi6G uJMiRmSwo6I7ZBx2XQ2RCIA+FTb2q+sg6NWXx4pNBZsC91tKL2j22a3cMU2MagoFEjIp CVmd9lSLng/NOOBxWEZHQckhQgkvwyxXQmZEaVnfagK7xUq+8bcZBFv/1jDIxO8flcJ8 BqiEp8pOoQ/QF4oOhKMbDJx+y6JVplCU1k2xFIE2yAZtdoTJYgv9f1FOEmlSV0Z4+yuZ bFn9vC30R8DuPobZbaPNLiLVk3iblDwNtVPIJBKuvlxDWPsYgXYGOG1a9RZFZiB2iDia b50w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=sBKZH8E44E4utEFngPpXSV+XcyxhS56f0qlgmHLQDO4=; b=akTS1nQjIgt2kWcrN7UlQl54nOrASB79wjEdGVydiJr8JaA8nlT9fnQbeHD3kihUMD cQU292P6erlsgk1CLbQvE/V8zRnTLRXADsaTPuUqX1WAMad1DK2PIBnJ1SI/Zt4m+JzL g6DQsQ1VD519svNQ799j9blSUPPYUnBggiU108Bj28/B0YRwM6MQhVoPqz2842qtd8Dj ySezB4h9SFby7SbkwUoH2aK1ch1Qc/BJKV2I4tP3VggQjuY8uinIEDtDuogIszgjBNRk +WN644CKrly4OBIphq/aNvZoQrSCxmfNtm+gCjIM0T6H5bRsyxLDhbE2mYnBKgc6Gjt1 2+8Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=peRaHaSj; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c67si2280075oib.276.2020.02.11.16.02.33; Tue, 11 Feb 2020 16:02:49 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=default header.b=peRaHaSj; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728018AbgBLACa (ORCPT + 99 others); Tue, 11 Feb 2020 19:02:30 -0500 Received: from mail.kernel.org ([198.145.29.99]:32846 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727956AbgBLACa (ORCPT ); Tue, 11 Feb 2020 19:02:30 -0500 Received: from [192.168.1.112] (c-24-9-64-241.hsd1.co.comcast.net [24.9.64.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 93D0C20724; Wed, 12 Feb 2020 00:02:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1581465749; bh=VXj1a+npI+7ydAyG+Owt//6Nop6TGqj0xGSkiZ+iHYA=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=peRaHaSjJBWu0RxNWsbg2RkLC4l6xVY/UNgyg4oYdntqHFeDLMDpCQq3ZzzKuUrOA zeKtNvUu0+uN19gu6qqY1w2j4lz2W0GQnIGL18vKQttilbW3vUx2lHkkkV77SlzbVT RktuuaFjkVVQ6c/0oY+eZo3VzmOB0u5pYTbjNi84= Subject: Re: [PATCH v3 7/7] selftests/exec: Add READ_IMPLIES_EXEC tests To: Kees Cook Cc: Ingo Molnar , Hector Marco-Gisbert , Catalin Marinas , Will Deacon , Jason Gunthorpe , Jann Horn , Russell King , x86@kernel.org, kernel-hardening@lists.openwall.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, shuah References: <20200210193049.64362-1-keescook@chromium.org> <20200210193049.64362-8-keescook@chromium.org> <4f8a5036-dc2a-90ad-5fc8-69560a5dd78e@kernel.org> <202002111124.0A334167@keescook> <202002111549.CF18B7B3B@keescook> From: shuah Message-ID: <36e45314-b672-b211-72c5-eef1d48984c0@kernel.org> Date: Tue, 11 Feb 2020 17:02:27 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <202002111549.CF18B7B3B@keescook> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/11/20 4:54 PM, Kees Cook wrote: > On Tue, Feb 11, 2020 at 02:06:53PM -0700, shuah wrote: >> On 2/11/20 12:25 PM, Kees Cook wrote: >>> On Tue, Feb 11, 2020 at 11:11:21AM -0700, shuah wrote: >>>> On 2/10/20 12:30 PM, Kees Cook wrote: >>>>> In order to check the matrix of possible states for handling >>>>> READ_IMPLIES_EXEC across native, compat, and the state of PT_GNU_STACK, >>>>> add tests for these execution conditions. >>>>> >>>>> Signed-off-by: Kees Cook >>>> >>>> No issues for this to go through tip. >>>> >>>> A few problems to fix first. This fails to compile when 32-bit libraries >>>> aren't installed. It should fail the 32-bit part and run other checks. >>> >>> Do you mean the Makefile should detect the missing compat build deps and >>> avoid building them? Testing compat is pretty important to this test, so >>> it seems like missing the build deps causing the build to fail is the >>> correct action here. This is likely true for the x86/ selftests too. >>> >>> What would you like this to do? >>> >> >> selftests/x86 does this already and runs the dependency check in >> x86/Makefile. >> >> >> check_cc.sh:# check_cc.sh - Helper to test userspace compilation support >> Makefile:CAN_BUILD_I386 := $(shell ./check_cc.sh $(CC) >> trivial_32bit_program.c -m32) >> Makefile:CAN_BUILD_X86_64 := $(shell ./check_cc.sh $(CC) >> trivial_64bit_program.c) >> Makefile:CAN_BUILD_WITH_NOPIE := $(shell ./check_cc.sh $(CC) >> trivial_program.c -no-pie) >> >> Take a look and see if you can leverage this. > > I did before, and it can certainly be done, but their stuff is somewhat > specific to x86_64/ia32. I'm looking at supporting _all_ compat for any > 64-bit architecture. I can certainly write some similar build tooling, > but the question I have for you is one of coverage: > > If a builder is 64-bit, it needs to be able to produce 32-bit compat > binaries for testing, otherwise the test is incomplete. (i.e. the tests > will only be able to test native behavior and not compat). This doesn't > seem like an "XFAIL" situation to me, and it doesn't seem right to > silently pass. It seems like the build should explicitly fail because > the needed prerequisites are missing. Do you instead want me to just > have it skip building the compat binaries if it can't build them? > Can we do the following: Build and run tests thatc an be built. Skip build and warn that test coverage is incomplete for compat with a strong recommendation on installing 32-bit libraries with some instructions on how to if applicable. thanks, -- Shuah