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=-13.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 0479EC4332F for ; Tue, 14 Sep 2021 12:04:22 +0000 (UTC) Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A740861107 for ; Tue, 14 Sep 2021 12:04:21 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org A740861107 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.linux-foundation.org Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 7380C40363; Tue, 14 Sep 2021 12:04:21 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NKp50FO4jwdN; Tue, 14 Sep 2021 12:04:20 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [140.211.9.56]) by smtp2.osuosl.org (Postfix) with ESMTPS id ABC804035F; Tue, 14 Sep 2021 12:04:19 +0000 (UTC) Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id 7C858C0011; Tue, 14 Sep 2021 12:04:19 +0000 (UTC) Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 73481C000D for ; Tue, 14 Sep 2021 12:04:18 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 5FE2640363 for ; Tue, 14 Sep 2021 12:04:18 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TjnoOmloVYP3 for ; Tue, 14 Sep 2021 12:04:17 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by smtp2.osuosl.org (Postfix) with ESMTPS id 6A3F24035F for ; Tue, 14 Sep 2021 12:04:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1631621056; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=PmmJi9goLsRt1V5iBGWfVlcuwuFQZzQtEgv6TzZiJac=; b=aGBFXbsctt/2axNt5k2kM9Fs6WayMHhqAP3xU4/PO8fP783MvKzh3EqUt0Pd8BpGv4TFYP 8qba0OXUq8UPouzTXVFXUPxSY8JxZ10eyUBhSMEvzZQOeImsfjR084DXLPU/xYqxc184JZ C2exkxQU5MhVDv8enwcDjEyqtIxQzPU= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-98-QX5FAN2eMZaPnZq_ArW39w-1; Tue, 14 Sep 2021 08:04:13 -0400 X-MC-Unique: QX5FAN2eMZaPnZq_ArW39w-1 Received: by mail-wr1-f69.google.com with SMTP id m18-20020adfe952000000b0015b0aa32fd6so3867530wrn.12 for ; Tue, 14 Sep 2021 05:04:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=PmmJi9goLsRt1V5iBGWfVlcuwuFQZzQtEgv6TzZiJac=; b=ctepL3XrgN7X/jl3efd0Pc/U4r3vqFtFK1oKZqqnpltWjBDMmJ0zvt87E+h5dfhSq5 Kk1fg9Tii9h4x8nPjdHvB/LjvZt1tsKCzpRkcmV0w5V62+O7V9f/TTTMFJmBc0DhmvAS 2bHJBsO1k5TmaPAC04XlXnDcv4o+hQ4ZgLWuoGX8/r7Ghn5FOcQeH6XD6ZYYeyYD6U4j kC+4Cd2kE7ItmTAf9FbIk71FOg40wRwWFkLfTqZuGGk/zDGy7m2aXs4yxAzrOwV26R3I QG+Oz2Qmhvp9yWBSR6EZvaWtb9Rhfc5iQCxNSlMBj8Tv9epKA+Y5I0qIhcz9W9VnnQyF Zw5Q== X-Gm-Message-State: AOAM532BMvYU/CCGswRAfw1VQvvJ9S5eEy5MuzeyM36fkcONBRARvzxK yJwA5rOD26e+MMxZV0IEYatr+Et3ZlQJn+3uB6VtvCj2hORYWKIc/qlipLfhc9hzxcA+Zi7GshS Dq3uY1AdYXtzC8AbMH7u1UNx5jdzkPUBj+JyRiMKrug== X-Received: by 2002:a05:6000:181:: with SMTP id p1mr18975955wrx.247.1631621051824; Tue, 14 Sep 2021 05:04:11 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwJwZsYm/MFLb7iUE900cvEQZTx5sTohcENBhz8d6nMsHTUdYbyDMk8uJ6xtpfdkjVUVzeLkA== X-Received: by 2002:a05:6000:181:: with SMTP id p1mr18975921wrx.247.1631621051608; Tue, 14 Sep 2021 05:04:11 -0700 (PDT) Received: from redhat.com ([2.55.151.134]) by smtp.gmail.com with ESMTPSA id l3sm931243wms.4.2021.09.14.05.04.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Sep 2021 05:04:11 -0700 (PDT) Date: Tue, 14 Sep 2021 08:04:07 -0400 From: "Michael S. Tsirkin" To: David Hildenbrand Subject: Re: [PATCH v4 3/3] virtio-mem: disallow mapping virtio-mem memory via /dev/mem Message-ID: <20210914080213-mutt-send-email-mst@kernel.org> References: <20210902160919.25683-1-david@redhat.com> <20210902160919.25683-4-david@redhat.com> <20210903025630-mutt-send-email-mst@kernel.org> <20210914075046-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 In-Reply-To: Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mst@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Disposition: inline Cc: Arnd Bergmann , Greg Kroah-Hartman , "Rafael J. Wysocki" , linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-mm@kvack.org, Andy Shevchenko , Hanjun Guo , Andrew Morton , Dan Williams X-BeenThere: virtualization@lists.linux-foundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Linux virtualization List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: virtualization-bounces@lists.linux-foundation.org Sender: "Virtualization" On Tue, Sep 14, 2021 at 01:57:25PM +0200, David Hildenbrand wrote: > On 14.09.21 13:52, Michael S. Tsirkin wrote: > > On Tue, Sep 14, 2021 at 11:45:25AM +0200, David Hildenbrand wrote: > > > On 03.09.21 09:02, Michael S. Tsirkin wrote: > > > > On Thu, Sep 02, 2021 at 06:09:19PM +0200, David Hildenbrand wrote: > > > > > We don't want user space to be able to map virtio-mem device memory > > > > > directly (e.g., via /dev/mem) in order to have guarantees that in a sane > > > > > setup we'll never accidentially access unplugged memory within the > > > > > device-managed region of a virtio-mem device, just as required by the > > > > > virtio-spec. > > > > > > > > > > As soon as the virtio-mem driver is loaded, the device region is visible > > > > > in /proc/iomem via the parent device region. From that point on user space > > > > > is aware of the device region and we want to disallow mapping anything > > > > > inside that region (where we will dynamically (un)plug memory) until > > > > > the driver has been unloaded cleanly and e.g., another driver might take > > > > > over. > > > > > > > > > > By creating our parent IORESOURCE_SYSTEM_RAM resource with > > > > > IORESOURCE_EXCLUSIVE, we will disallow any /dev/mem access to our > > > > > device region until the driver was unloaded cleanly and removed the > > > > > parent region. This will work even though only some memory blocks are > > > > > actually currently added to Linux and appear as busy in the resource tree. > > > > > > > > > > So access to the region from user space is only possible > > > > > a) if we don't load the virtio-mem driver. > > > > > b) after unloading the virtio-mem driver cleanly. > > > > > > > > > > Don't build virtio-mem if access to /dev/mem cannot be restricticted -- > > > > > if we have CONFIG_DEVMEM=y but CONFIG_STRICT_DEVMEM is not set. > > > > > > > > > > Reviewed-by: Dan Williams > > > > > Signed-off-by: David Hildenbrand > > > > > > > > > > > > > --- > > > > > drivers/virtio/Kconfig | 1 + > > > > > drivers/virtio/virtio_mem.c | 4 +++- > > > > > 2 files changed, 4 insertions(+), 1 deletion(-) > > > > > > > > > > diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig > > > > > index ce1b3f6ec325..ff80cd03f1d1 100644 > > > > > --- a/drivers/virtio/Kconfig > > > > > +++ b/drivers/virtio/Kconfig > > > > > @@ -101,6 +101,7 @@ config VIRTIO_MEM > > > > > depends on MEMORY_HOTPLUG_SPARSE > > > > > depends on MEMORY_HOTREMOVE > > > > > depends on CONTIG_ALLOC > > > > > + depends on !DEVMEM || STRICT_DEVMEM > > > > > help > > > > > This driver provides access to virtio-mem paravirtualized memory > > > > > devices, allowing to hotplug and hotunplug memory. > > > > > > > > It would be nicer if there was a symbol in the MEMORY_ namespace > > > > we can depend on exported by mm and depending on !DEVMEM || > > > > STRICT_DEVMEM. > > > > > > > > E.g. > > > > > > > > config MEMORY_EXCLUSIVE > > > > def_bool y > > > > depends on !DEVMEM || STRICT_DEVMEM > > > > > > > > and then in virtio > > > > depends on MEMORY_EXCLUSIVE > > > > > > > > > > > > > > Yes, but I'm not able to come up with an expressive name. MEMORY_EXCLUSIVE > > > can be highly misleading ... > > > > > > I mean ... it enables IORESOURCE_EXCLUSIVE ... but ok ... > > MEMORY_EXCLUSIVE_KERNEL_MAP ? > > It enables IORESOURCE_EXCLUSIVE for IORESOURCE_SYSTEM_RAM ... and notably > not for IORESOURCE_MEM. > > MEMORY_EXCLUSIVE_SYSTEM_RAM ? OK. > > > > > > > > > the virtio change itself is ok though: > > > > > > > > Acked-by: Michael S. Tsirkin > > > > > > Thanks! > > > > > > > > > -- > > > Thanks, > > > > > > David / dhildenb > > > > > -- > Thanks, > > David / dhildenb _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization