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=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no 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 B10FCC433DB for ; Mon, 8 Feb 2021 23:38:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 82D5164E7C for ; Mon, 8 Feb 2021 23:38:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231263AbhBHXhq (ORCPT ); Mon, 8 Feb 2021 18:37:46 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47624 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229822AbhBHXh3 (ORCPT ); Mon, 8 Feb 2021 18:37:29 -0500 Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8EE3BC061788 for ; Mon, 8 Feb 2021 15:36:49 -0800 (PST) Received: by mail-ed1-x530.google.com with SMTP id df22so21328257edb.1 for ; Mon, 08 Feb 2021 15:36:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eGGcKAyTzmY7XmHqKjg37Fb2afx54tMCqzIlqIxaU7M=; b=E5dDhWELy3490cipw2qXqX2bxpHoPiVzQRaR2X4dSFiRqOjLee56yC4S848SYQ7DHE TdW2iX6wSAayi8M7TQ5MMi4LhfUPROW4AZ6ZZOqjJFTYTE5q5E4sV/GibnBSH8lySu0y Uyvf6SQAxXS7uRrtKj3agOmXXQYr2c5xv+HgO5WxwAvRmw/+0NiQSSyWhVntPGknaeyA 2q042JtRZZZYrxE5qrQYldeSgOlG0x2U0IaHs3AwcLCd7L5nOVh3ATxC4Zkpls71QW8X iF7cHXO4b5hDGaLJSd8+KCt2uoywgyj2XpoqdNsGqaqAxuWIKViVqb100OOjUtUyje0Z k2DQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eGGcKAyTzmY7XmHqKjg37Fb2afx54tMCqzIlqIxaU7M=; b=uXKO/yospdqmEfPpCbLiForvAhpSIX2HZVAetxQEgybqtQGj8IF+VpxmJ1ZTskwgWB LHe0rMCcjC6BQ4XEq53VeJKBQNYX1RKyctVTOltuoZsrY0a5DEmsq60Bp4cjptfzS+P9 3Ly3iB5HR2i6vRX4WlSue0D5+u5RQUYDtc0/cjoJ4UypWNPfwX8V21utoKYS8jIP+P/7 1kjhCYL4ZjQ7m6f9LyWC3xv8rJdBpk4Qpbz95tzQEBamNeOMOv6RRMSlzFztbz7DG92i 44qOPNqqualHkk6Y8CdZDu7fnQ9V47z6FTDGRX2cONuSOC09MWQH8TdV0AhVNNU9WEzS V9HA== X-Gm-Message-State: AOAM531/h9MYs0po4BRJboGReFQgkrHsPNzGq7qfKYL8iDu3p7YQtEVq LC7sKnRmp6ZvdOX3zrM36WptlW1ql8DygnX8GdDYnQ== X-Google-Smtp-Source: ABdhPJy9ZjJZRXDvIzBmNSGdGKMoO79oPi5SonIYHgHcEcFwYmkhh/wOyEJYChGVMiInUvinect2p135EQFvnomUZL4= X-Received: by 2002:aa7:cd87:: with SMTP id x7mr20441251edv.210.1612827408336; Mon, 08 Feb 2021 15:36:48 -0800 (PST) MIME-Version: 1.0 References: <20210130002438.1872527-1-ben.widawsky@intel.com> <20210130002438.1872527-9-ben.widawsky@intel.com> <202102081406.CDE33FB8@keescook> In-Reply-To: <202102081406.CDE33FB8@keescook> From: Dan Williams Date: Mon, 8 Feb 2021 15:36:35 -0800 Message-ID: Subject: Re: [PATCH 08/14] taint: add taint for direct hardware access To: Kees Cook Cc: Jonathan Corbet , linux-cxl@vger.kernel.org, Ben Widawsky , Linux ACPI , Linux Kernel Mailing List , linux-nvdimm , Linux PCI , Bjorn Helgaas , Chris Browy , Ira Weiny , Jon Masters , Jonathan Cameron , Rafael Wysocki , Randy Dunlap , Vishal Verma , daniel.lll@alibaba-inc.com, "John Groves (jgroves)" , "Kelley, Sean V" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 8, 2021 at 2:09 PM Kees Cook wrote: > > On Mon, Feb 08, 2021 at 02:00:33PM -0800, Dan Williams wrote: > > [ add Jon Corbet as I'd expect him to be Cc'd on anything that > > generically touches Documentation/ like this, and add Kees as the last > > person who added a taint (tag you're it) ] > > > > Jon, Kees, are either of you willing to ack this concept? > > > > Top-posting to add more context for the below: > > > > This taint is proposed because it has implications for > > CONFIG_LOCK_DOWN_KERNEL among other things. These CXL devices > > implement memory like DDR would, but unlike DDR there are > > administrative / configuration commands that demand kernel > > coordination before they can be sent. The posture taken with this > > taint is "guilty until proven innocent" for commands that have yet to > > be explicitly allowed by the driver. This is different than NVME for > > example where an errant vendor-defined command could destroy data on > > the device, but there is no wider threat to system integrity. The > > taint allows a pressure release valve for any and all commands to be > > sent, but flagged with WARN_TAINT_ONCE if the driver has not > > explicitly enabled it on an allowed list of known-good / kernel > > coordinated commands. > > > > On Fri, Jan 29, 2021 at 4:25 PM Ben Widawsky wrote: > > > > > > For drivers that moderate access to the underlying hardware it is > > > sometimes desirable to allow userspace to bypass restrictions. Once > > > userspace has done this, the driver can no longer guarantee the sanctity > > > of either the OS or the hardware. When in this state, it is helpful for > > > kernel developers to be made aware (via this taint flag) of this fact > > > for subsequent bug reports. > > > > > > Example usage: > > > - Hardware xyzzy accepts 2 commands, waldo and fred. > > > - The xyzzy driver provides an interface for using waldo, but not fred. > > > - quux is convinced they really need the fred command. > > > - xyzzy driver allows quux to frob hardware to initiate fred. > > > - kernel gets tainted. > > > - turns out fred command is borked, and scribbles over memory. > > > - developers laugh while closing quux's subsequent bug report. > > But a taint flag only lasts for the current boot. If this is a drive, it > could still be compromised after reboot. It sounds like this taint is > really only for ephemeral things? "vendor shenanigans" is a pretty giant > scope ... > That is true. This is more about preventing an ecosystem / cottage industry of tooling built around bypassing the kernel. So the kernel complains loudly and hopefully prevents vendor tooling from propagating and instead directs that development effort back to the native tooling. However for the rare "I know what I'm doing" cases, this tainted kernel bypass lets some experimentation and debug happen, but the kernel is transparent that when the capability ships in production it needs to be a native implementation. So it's less, "the system integrity is compromised" and more like "you're bypassing the development process that ensures sanity for CXL implementations that may take down a system if implemented incorrectly". For example, NVME reset is a non-invent, CXL reset can be like surprise removing DDR DIMM. Should this be more tightly scoped to CXL? I had hoped to use this in other places in LIBNVDIMM, but I'm ok to lose some generality for the specific concerns that make CXL devices different than other PCI endpoints.