Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp3523324pxb; Tue, 12 Jan 2021 17:31:49 -0800 (PST) X-Google-Smtp-Source: ABdhPJy0ChfEX3DiWee5S7lL5widmYYYJEeFj7Ri8bb3l8/MhDJn9+G2uDKn9aNL9yL/bYP+uu8w X-Received: by 2002:a05:6402:1841:: with SMTP id v1mr1583479edy.194.1610501508990; Tue, 12 Jan 2021 17:31:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610501508; cv=none; d=google.com; s=arc-20160816; b=Muzvj6kAPEg7oelbT4MZRxMnm29f2RDpjRRS06noTz5P0CxBVLJmkx0Ht3tZm/w5hm OdJ54G9XKU5AxOTZTl5alvP0nirMIAFu8Dt7ivivF1zBT55M8S1feuuTVbiv2zdx97dR MmbeHmIeIFdG7VTb1Nd7Hf0MTiy6sIDNYUO5lty5GQa+VKjDdD3BUaECMYYlblhbvEuV kr2iqMOezrl6KTbu6bKGxdJ9otC8vGm34ySOLvhoLn9zK0KyFydTUOoDC4IKtJ8MOWkV Iv9o14ESbWEsy5qca+SAVH5cVUsqhvCrN9j73UJLbX99BkiwPBfqS346LZMPJT6PJhZX FYvw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=lI5PuvPTiPf0gmjqGd/hf2wO6dPsnxRECFfzR1WJPLs=; b=flJrddGJteRpJdMhAfXePlN04CRYVVnC/z4maBeqVKzvXiLLNYWL6JKB4YaGpeaY/V JzU3Q5eC7F1i9LaaSbbjTpuSheTghedBGlPcB5TMny6Q8LHVME+oBW8nTDALUkRaABbc UDyEeBgCuFLy/LTrwqqKRBZhOmoVMN/Mjeu1RqsQ2g/Ogw07HQSSpmLhu/FT/tgXCKc7 1tEhrGnVnCO7Mn+16NH/ukj10JA/edxmAza7VWqVjFW1X55jgdWK+q/koY9kXzFyQEN8 pYRPcsCOABya86Rko2/17yO6NiOFskf2/UdYjET8h2jODGFBp0aHU93s2D5RaB4UB6J6 3wVQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=d+wLLjwa; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l23si227538edr.325.2021.01.12.17.31.25; Tue, 12 Jan 2021 17:31:48 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=d+wLLjwa; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404903AbhALKW2 (ORCPT + 99 others); Tue, 12 Jan 2021 05:22:28 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:42963 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404190AbhALKW2 (ORCPT ); Tue, 12 Jan 2021 05:22:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1610446861; 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=lI5PuvPTiPf0gmjqGd/hf2wO6dPsnxRECFfzR1WJPLs=; b=d+wLLjwaKCCpIgTY83REThYySYmchS6C4KBbDgaREWPij5C6YpgyAWeTJIPAeAslVB3/qr oTANctNDsAU0OPm6Qyb5T13XJ7IgouXGBjzKs5pOWiZtYZ5cjfpDyYyuiMceEed6CDK0+A DDAvQA1vTM60ldYAZ6UWWKrS+TZ/EyU= Received: from mail-ej1-f71.google.com (mail-ej1-f71.google.com [209.85.218.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-483-k-Fp2VGcMleXiuPub8KLJQ-1; Tue, 12 Jan 2021 05:21:00 -0500 X-MC-Unique: k-Fp2VGcMleXiuPub8KLJQ-1 Received: by mail-ej1-f71.google.com with SMTP id ov1so826050ejb.1 for ; Tue, 12 Jan 2021 02:21:00 -0800 (PST) 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=lI5PuvPTiPf0gmjqGd/hf2wO6dPsnxRECFfzR1WJPLs=; b=kYTDbhsF8HDY1BvA7QrBGaArKm6njMI3I5vAe0YfCASn5Ejqmsmbue+4pCydxkK1aj WFvPF+y0TfGnuNQqksrI6WB7manFgeH1yDbpNoww2yhp42ttFLLsFrs2ezRw85VMq0n6 C9t7oxnUKeM2R2WjWANRXh5FkP6ct7fpA6zZ1/l7jJ2HFmRISqLCZsN4awnIn63Cy/N5 3O7qveAg8Nij8YUATD2t+nNKj4CTpTufm9jBdTT00XvMGPas8BL0wfctzBood8T3WA8C r7Zakv6usPq2tGhkddwmlisSkv0gw9GQfvcWqPBz4OMF2x30A7cZzOo8jesSAbyyoBuO 4rfQ== X-Gm-Message-State: AOAM532ovUa/HY/jtrHcd8YfamZslJ0nFAvrbQGNmNQOkWZVHGQmi1CC gJ4q4j3kRHCJSJH73kLxygrIUE+wCujMoMHygDpyqrsvKu34bGDPEepFW7HlBogo/FKXBnVcV2U lJcIp/EnaoLdH8vX6oOqTXi// X-Received: by 2002:a17:906:707:: with SMTP id y7mr1527491ejb.212.1610446858831; Tue, 12 Jan 2021 02:20:58 -0800 (PST) X-Received: by 2002:a17:906:707:: with SMTP id y7mr1527483ejb.212.1610446858615; Tue, 12 Jan 2021 02:20:58 -0800 (PST) Received: from ?IPv6:2001:b07:6468:f312:c8dd:75d4:99ab:290a? ([2001:b07:6468:f312:c8dd:75d4:99ab:290a]) by smtp.gmail.com with ESMTPSA id x4sm1192917edr.40.2021.01.12.02.20.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Jan 2021 02:20:57 -0800 (PST) Subject: Re: [PATCH] kvm: Fixes lack of KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2 enabled check To: Kunkun Jiang , kvm@vger.kernel.org, linux-kernel@vger.kernel.org Cc: wanghaibin.wang@huawei.com, Keqian Zhu References: <20210112092942.2310-1-jiangkunkun@huawei.com> From: Paolo Bonzini Message-ID: <9dd32bc9-a35c-e43f-51f2-c0989cca4e66@redhat.com> Date: Tue, 12 Jan 2021 11:20:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <20210112092942.2310-1-jiangkunkun@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/01/21 10:29, Kunkun Jiang wrote: > The KVM_CLEAR_DIRTY_LOG ioctl lacks the check whether the capability > KVM_CAP_MANUAL_DIRTY_LOG_PROTECT is enabled or not. This may cause > some problems if userspace calls the KVM_CLEAR_DIRTY_LOG ioctl, but > dose't enable this capability. So we'd better to add it. > > Fixes: 2a31b9db15353 ("kvm: introduce manual dirty log reprotect") > Signed-off-by: Kunkun Jiang > --- > virt/kvm/kvm_main.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c > index fa9e3614d30e..8f5633d8a0e8 100644 > --- a/virt/kvm/kvm_main.c > +++ b/virt/kvm/kvm_main.c > @@ -1602,6 +1602,9 @@ static int kvm_clear_dirty_log_protect(struct kvm *kvm, > unsigned long *dirty_bitmap_buffer; > bool flush; > > + if (!kvm->manual_dirty_log_protect) > + return -EPERM; > + > /* Dirty ring tracking is exclusive to dirty log tracking */ > if (kvm->dirty_ring_size) > return -ENXIO; This is not a problem, KVM_CLEAR_DIRTY_LOG can always be used even if KVM_CAP_MANUAL_DIRTY_LOG_PROTECT was not enabled. The meaning is the same: clear the bits without returning them. Paolo