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=-6.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 D95E8C4741F for ; Fri, 25 Sep 2020 21:05:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8F18E238A0 for ; Fri, 25 Sep 2020 21:05:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="acDjwy5t" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727511AbgIYVF6 (ORCPT ); Fri, 25 Sep 2020 17:05:58 -0400 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:54498 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726309AbgIYVF5 (ORCPT ); Fri, 25 Sep 2020 17:05:57 -0400 Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1601067956; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=KYytt9bssGAEWyPGrn3z2bXHN59vb0kbWX+R/SRNIRg=; b=acDjwy5tLDRZ2zX70/IWMAbCMHQpHjWnnJXDhtgLZCO/9HAJPcHFkrBOJUUtfqMC6T83hf /87SSB+OxiZLqSAEeD5aCPEwQYd+9SsoGAOGQasVKW1ZqlkKVvgmJvnErudjRDcysANrVJ Vnjrw6NS+xEBtZ6S2iduUpMWOVTNQqs= Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-510-QmeEMI95PeyXkK-_qgZFBA-1; Fri, 25 Sep 2020 17:05:52 -0400 X-MC-Unique: QmeEMI95PeyXkK-_qgZFBA-1 Received: by mail-wr1-f71.google.com with SMTP id h4so1567977wrb.4 for ; Fri, 25 Sep 2020 14:05:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=KYytt9bssGAEWyPGrn3z2bXHN59vb0kbWX+R/SRNIRg=; b=fiSf/Kq0GFKlVr0d0Xn7YuKT3TxWjDJW9gcT1Q6hsOXO7faLBgxajH1VifAi1M5nI9 PyCsvDlz2xjpSoBAjZF8Avqpdp081YmbXK6b4p0FX6wgPQXkq4PqQL+inGBc0s8imDT1 /K4e7o4UYPsAORoGfgVl38csH2+aoT7ZZq0Nig2o/vc+iDpY6L8Dh2Du/pnPOUHhLB8h buTwSoaUtaBxphgZt/8lztzRqFTDF6TP4zq3LZZNIucdRRZRSKSvR3Sf7UR34uq3cR87 JIpQvp2ZAJdD7XubPHMYrdtKOJb5jsukplMkf0WVLPsEoTySWkI4kuh0oOAvtfH1ZBl6 a6yg== X-Gm-Message-State: AOAM531uJR1rId2gb5Lt+vfjiz2sdwEZjgXZ88H5Xj1zbInzyhl7ITuA ZIsA9a69hquDK/g8w4slr/q50fa7IyQoPxHhEjPzkVuOhpUlnwak9bKHkM31xHts0poHz0k3CdL f33cFl5NP+ENEzm377BO8IlFi X-Received: by 2002:a05:600c:228e:: with SMTP id 14mr457094wmf.17.1601067950964; Fri, 25 Sep 2020 14:05:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyXVvhHeab8ly63BYQtucuJlTvz3AS/Mr+Hmurwb2UpVZ7QkUFAEARwgGqla0VJ1OcRKIUZ6A== X-Received: by 2002:a05:600c:228e:: with SMTP id 14mr457065wmf.17.1601067950750; Fri, 25 Sep 2020 14:05:50 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:ec9b:111a:97e3:4baf? ([2001:b07:6468:f312:ec9b:111a:97e3:4baf]) by smtp.gmail.com with ESMTPSA id a15sm4540071wrn.3.2020.09.25.14.05.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 25 Sep 2020 14:05:50 -0700 (PDT) Subject: Re: [RFC PATCH 0/3] KVM: Introduce "VM bugged" concept To: Marc Zyngier , Sean Christopherson Cc: Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, James Morse , Julien Thierry , Suzuki K Poulose , linux-arm-kernel@lists.infradead.org, Huacai Chen , Aleksandar Markovic , linux-mips@vger.kernel.org, Paul Mackerras , kvm-ppc@vger.kernel.org, Christian Borntraeger , Janosch Frank , David Hildenbrand , Cornelia Huck , Claudio Imbrenda References: <20200923224530.17735-1-sean.j.christopherson@intel.com> <874knlrf4a.wl-maz@kernel.org> From: Paolo Bonzini Message-ID: <100a603f-193c-5a46-d428-cfc0ce0a8fe4@redhat.com> Date: Fri, 25 Sep 2020 23:05:48 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <874knlrf4a.wl-maz@kernel.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25/09/20 18:32, Marc Zyngier wrote: > I'm quite like the idea. However, I wonder whether preventing the > vcpus from re-entering the guest is enough. When something goes really > wrong, is it safe to allow the userspace process to terminate normally > and free the associated memory? And is it still safe to allow new VMs > to be started? For something that bad, where e.g. you can't rule out future memory corruptions via use-after-free bugs or similar, you're probably entering BUG_ON territory. Paolo