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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 838AAECAAA1 for ; Tue, 30 Aug 2022 21:37:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231126AbiH3VhE (ORCPT ); Tue, 30 Aug 2022 17:37:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36388 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230254AbiH3VhD (ORCPT ); Tue, 30 Aug 2022 17:37:03 -0400 Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 60843895E6 for ; Tue, 30 Aug 2022 14:37:02 -0700 (PDT) Received: by mail-pj1-x102b.google.com with SMTP id t11-20020a17090a510b00b001fac77e9d1fso19233250pjh.5 for ; Tue, 30 Aug 2022 14:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc; bh=zP3t1aYxwJPDk5XaVLsNCmAQ5v0NuNcsY2lJm9GovWA=; b=sSBdnFkQOT821zpew9yak7rxkuZeb2MC4Eg/M3h9RsaLbVBKZWY1eG0KF0WBa4hLVO dB4nfwltxmIzCziE1xcAppBM373cXbZojODy5YxqR70mcY1ijLMFLQO7/+hdRo12N5RW mV/695VjyHZBmg1V7KrxpNYChUGpOisqUQjT0CiEVEppX2kmUB4xhztvwHWweMW9uPSN 9XsAYUnoXxgqfPg1WH+vZJt+6Yf8RIz5p8LdpBfClKrkDkszZH+4ezYh3iD01HriOvos 38iu1NJovNQHvTytzm3pMP9YM4tqbrZMogaWEMXGekMhhp1WHqgQtjkD9hvCTDUG6DVi OIdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=zP3t1aYxwJPDk5XaVLsNCmAQ5v0NuNcsY2lJm9GovWA=; b=NCQ8JNLTuZH+6I5Ws1nGkm1MWjkYgvuum18Jg0C9q3o71ubdfSbxJ9286VD7B4XPu/ 9N4qbxes9nVLwLulzszVFxrCdz3jLZSV9tkttMfw8D5//ay97jQ/8/7TTD37YgKkE0S5 RXKoQdOpAfPNC+kiXwIQbp2sw7eZZExVRbeIQFft9F/LsF0QGEc7vphMSGJ1fP2jAMQX +g73CUgH8p4Oo8NtzIQod9M3ARpwY9w0Hv/z7UiBmAmjpjeb0oSeo+Ax3i5EVLPxENyY khAOqx9nQdBmnbUiYDwhaRyoBBW6MvOJTdSrdNnl6tbZEJj2eVkDJzdoENrM1NtHrPb2 8jnA== X-Gm-Message-State: ACgBeo0cJJbPp92x4/ETHvk+5gF8jZNenQLHWPCkTBYdwNZoRSonfYze bIhESyURivO2zH/x04yusj4iZQ== X-Google-Smtp-Source: AA6agR7HymFegM1rQHVDFtk3+q6iFsbn6uobQxibnrsrUL5dEkAGm+VM696UFUWDHP/kya2qGH8WhQ== X-Received: by 2002:a17:90b:1c81:b0:1fb:887c:f82e with SMTP id oo1-20020a17090b1c8100b001fb887cf82emr36240pjb.92.1661895421775; Tue, 30 Aug 2022 14:37:01 -0700 (PDT) Received: from google.com (7.104.168.34.bc.googleusercontent.com. [34.168.104.7]) by smtp.gmail.com with ESMTPSA id b11-20020a170902650b00b00172a567d910sm10059594plk.289.2022.08.30.14.37.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 30 Aug 2022 14:37:01 -0700 (PDT) Date: Tue, 30 Aug 2022 21:36:58 +0000 From: Sean Christopherson To: Miaohe Lin Cc: pbonzini@redhat.com, vkuznets@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] KVM: fix memoryleak in kvm_init() Message-ID: References: <20220823063414.59778-1-linmiaohe@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220823063414.59778-1-linmiaohe@huawei.com> Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Tue, Aug 23, 2022, Miaohe Lin wrote: > When alloc_cpumask_var_node() fails for a certain cpu, there might be some > allocated cpumasks for percpu cpu_kick_mask. We should free these cpumasks > or memoryleak will occur. > > Fixes: baff59ccdc65 ("KVM: Pre-allocate cpumasks for kvm_make_all_cpus_request_except()") > Signed-off-by: Miaohe Lin > --- Pushed to branch `for_paolo/6.1` at: https://github.com/sean-jc/linux.git Unless you hear otherwise, it will make its way to kvm/queue "soon". Note, the commit IDs are not guaranteed to be stable.