Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp5530086ima; Tue, 5 Feb 2019 13:22:37 -0800 (PST) X-Google-Smtp-Source: AHgI3IatpFuYpohUXnZjl9ogQcCnmaM+dVvbb4D5TfDktJax8BTO4FwQGGw/7Bi01X/yEsb5RJof X-Received: by 2002:a63:d90b:: with SMTP id r11mr6457121pgg.5.1549401757473; Tue, 05 Feb 2019 13:22:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549401757; cv=none; d=google.com; s=arc-20160816; b=kVNvTSKQv8KcU/cFlv+anne4URNC+nuMN1zs9XaH4yyStrR2qeVdI14vrfiRqZDDZL mS1ipD8B00QfRWh1qwN5mYb/0DzLhHWQIJgrC3NmJW6GuWa0FxSkKHLkD3K8S65SwZEV cWhTWbpJuKjhAnJFtoqL3J/ielJeMDSw4UjmD2cRtrr2ImeTiKTW2yvDpwNMBSfXLhOY SJjRj/YJNy36Ec34o+XCzAqiKUQ7gAqh1V7n7xzcbdm19Yci5W4N2IUboj3bnLk/A6y9 3kybWgjxfgj44F+tqwW/XmF8cjmsL64ELWJeWTFYtZCElZCrhMNCyN9qMzvhybGT0TKg zKQg== 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:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=KWmYD0CAyU8FAtZy0mcH4/Kk75elDiWkZogG6yiY1F8=; b=Bx9lOx+YNfbBooO98nRx+QsdX0GFnAELEFCM4173RRY5Aq7qdbifPj7KlKOt5UKsHG GtXfeq4zmfhxhDD4Q5bhm+93EpLR80LfSxF1e+62IZ3Z3OFviK4W98JKwzIGdGx0a1NE jNeONsLn0nHnDNX1HECU+y6aW7mzWFcdWh8NpCVZ/XKKqBJZzN+SOWXn80ejxS4aMqc2 n72TQ7DXQcKKTQulvQvJuYkhxBz9+TbECM1S8L3GMOb2ETGKCdeJswh7EUNzves/sWbg vH9GpnfVfirNfDNywfKbDMRlvThh4d/fwbs+9YUtej5BxHgXr3UPM4HfFO6fd68oug6J 2tvg== 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 q14si4042226pgf.47.2019.02.05.13.22.21; Tue, 05 Feb 2019 13:22:37 -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; 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 S1727489AbfBEVVt (ORCPT + 99 others); Tue, 5 Feb 2019 16:21:49 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:48048 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726062AbfBEVVt (ORCPT ); Tue, 5 Feb 2019 16:21:49 -0500 Received: from akpm3.svl.corp.google.com (unknown [104.133.8.65]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 90126A6FF; Tue, 5 Feb 2019 21:21:48 +0000 (UTC) Date: Tue, 5 Feb 2019 13:21:46 -0800 From: Andrew Morton To: Andy Lutomirski Cc: "Chang S. Bae" , Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Andi Kleen , Markus T Metzger , Ravi Shankar , LKML Subject: Re: [PATCH v5 01/13] taint: Introduce a new taint flag (insecure) Message-Id: <20190205132146.2e61b3df9e7be49e22b7d903@linux-foundation.org> In-Reply-To: References: <20190201205319.15995-1-chang.seok.bae@intel.com> <20190201205319.15995-2-chang.seok.bae@intel.com> X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 1 Feb 2019 18:42:29 -0800 Andy Lutomirski wrote: > On Fri, Feb 1, 2019 at 12:54 PM Chang S. Bae wrote: > > > > For testing (or root-only) purposes, the new flag will serve to tag the > > kernel taint accurately. > > > > When adding a new feature support, patches need to be incrementally > > applied and tested with temporal parameters. Currently, there is no flag > > for this usage. > > I think this should be reviewed by someone like akpm. akpm, for > background, this is part of an x86 patch series. If only part of the > series is applied, the kernel will be blatantly insecure (but still > functional and useful for testing and bisection), and this taint flag > will be set if this kernel is booted. With the whole series applied, > there are no users of the taint flag in the kernel. > > Do you think this is a good idea? What does "temporal parameters" mean? A complete description of this testing process would help. I sounds a bit strange. You mean it assumes that people will partially apply the series to test its functionality? That would be inconvenient. - Can the new and now-unused taint flag be removed again at end-of-series? - It would be a lot more convenient if we had some means of testing after the whole series is applied, on a permanent basis - some debugfs flag, perhaps?