Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp2104325pxp; Mon, 7 Mar 2022 08:29:06 -0800 (PST) X-Google-Smtp-Source: ABdhPJzQP1CjlXJT+EZKwcN53CiisfGvnQk9zmhRHFZ/abKblX42dxeUpC8B5AxD7LoTkpJDTB2o X-Received: by 2002:a17:907:6d86:b0:6da:86b9:ac3 with SMTP id sb6-20020a1709076d8600b006da86b90ac3mr9923185ejc.532.1646670545823; Mon, 07 Mar 2022 08:29:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646670545; cv=none; d=google.com; s=arc-20160816; b=aD38ns0F6zUF2pJTNsXMaejJnLxCnAdL1D5qN2SI9adbGahk3UxBy5GPrkTyUe58+s kWirWDg44HU4eZ2LaEEaWuqAzmFl2YLiwi09uJBlMgv2a5kBHeElxKuLdFG+psfo3Jzi iLNDetO4+aJj5q7C5Og7t0kJTUERgoTKW4aYjEUsCA1lC8JD9QGiOQZHUVNOwT6elSLV CIEEBXyaKc4Crb6r3nd7DBSsAcgCLHT9Tndgf1cb5X5xjLBVS8vhKT2Ch/W7Bgf3ngWK s8ypirMX5n/nlF+I/x7F9rwwd0BInB7RBDHsQxGqizgRSijRpYePmxkGETZNCVPPkhCe CW+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=HwtiP2PdA6+r3sc42cDbQcqvFIOWSZq0r0yI/YMvgEc=; b=noCfhG//IhP0YoQe8Wa2FNv3zOmfXhqzpSqrEIK3iB5GQZTRgQRi3qYlK7GwRCLHDA M+OLx9RM5kKq+oK5xNVt858KLmBDTY2KVS5V+JmDNLlvrM6AclT9Ey6kpIfYe5wU8zEQ pU7R1tp8wZReN6pVKODaP6kKr/848bT6DS/CdIfuLRwXLpPgoDV5nQDHRhYnRU4ep0i5 yEBKh0KqPTifjudCUYPPPgk/7UWaGFfgQunPFICmK4ptPAU0F58Frm9bI2XfMe/ruU8I gMOZRCfwypLRXD5Yww8tqdtKh63ak6/6Q6Py+Bw4C2Na9bBXLYT7KP0bwLijTPSAdn/1 h5CQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=P7U0s8PZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hs1-20020a1709073e8100b006da68ea5bc3si11448570ejc.692.2022.03.07.08.28.41; Mon, 07 Mar 2022 08:29:05 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=P7U0s8PZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242353AbiCGNrT (ORCPT + 99 others); Mon, 7 Mar 2022 08:47:19 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45656 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242344AbiCGNrR (ORCPT ); Mon, 7 Mar 2022 08:47:17 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 796E58C7D0; Mon, 7 Mar 2022 05:46:22 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 2D048B81240; Mon, 7 Mar 2022 13:46:21 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8768BC340E9; Mon, 7 Mar 2022 13:46:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1646660779; bh=lS/OPCoHfVOEsXyzTtf0B3Ua3GfsuGvGlHz7Xory8S4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=P7U0s8PZ98rV142USqp5u6HkvXsUGgwidIdoY3fNfGQ8VjyBfWQWPX8d0+jCDWMin tTod77LhMhL5BNjtLdDsZIIfTQW4tLrENCsiIgFeClpAzXZZzVs1PnekE4UeYY5Ggv hWs92B6NyHq4VtHClvf/GVl22alXmOP+yB58BwbIiqrlVEHE7Yf7fBBeX5flcNQ9bz tfB5wva4blFQHOOKEB+rixyYXzTk8/j9Tpxoh8NscjvTKW+Na/sUdPsvx6Mas0tJd2 gv2ZuFx474+4yDhci/z86WN85FRlBHUUeUGJSZseUftpJYNQGyGO10AHEvbFelAglU Je9mOFVRYQHHQ== Date: Mon, 7 Mar 2022 15:45:38 +0200 From: Jarkko Sakkinen To: GUO Zihua Cc: linux-integrity@vger.kernel.org, wangweiyang2@huawei.com, xiujianfeng@huawei.com, weiyongjun1@huawei.com, peterhuewe@gmx.de, jgg@ziepe.ca, linux-kernel@vger.kernel.org Subject: Re: [PATCH] tpm: Fix memory leak in tpmm_chip_alloc Message-ID: References: <20220307104827.40843-1-guozihua@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220307104827.40843-1-guozihua@huawei.com> X-Spam-Status: No, score=-7.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 07, 2022 at 06:48:27PM +0800, GUO Zihua wrote: > Fix a memory leak in tpmm_chip_alloc. devm_add_action_or_reset would > call put_device on error, while tpm->devs is left untouched. Call > put_device on tpm->devs as well if devm_add_action_or_reset returns an > error. > > Fixes: fdc915f7f719 ("tpm: expose spaces via a device link /dev/tpmrm") > Signed-off-by: GUO Zihua > --- > drivers/char/tpm/tpm-chip.c | 13 +++++++++---- > 1 file changed, 9 insertions(+), 4 deletions(-) > > diff --git a/drivers/char/tpm/tpm-chip.c b/drivers/char/tpm/tpm-chip.c > index b009e7479b70..0a92334e8c40 100644 > --- a/drivers/char/tpm/tpm-chip.c > +++ b/drivers/char/tpm/tpm-chip.c > @@ -308,6 +308,12 @@ static int tpm_class_shutdown(struct device *dev) > return 0; > } > > +static void tpm_chip_free(struct tpm_chip *chip) > +{ > + put_device(&chip->devs); > + put_device(&chip->dev); > +} > + > /** > * tpm_chip_alloc() - allocate a new struct tpm_chip instance > * @pdev: device to which the chip is associated > @@ -396,8 +402,7 @@ struct tpm_chip *tpm_chip_alloc(struct device *pdev, > return chip; > > out: > - put_device(&chip->devs); > - put_device(&chip->dev); > + tpm_chip_free(chip); > return ERR_PTR(rc); > } > EXPORT_SYMBOL_GPL(tpm_chip_alloc); > @@ -420,8 +425,8 @@ struct tpm_chip *tpmm_chip_alloc(struct device *pdev, > return chip; > > rc = devm_add_action_or_reset(pdev, > - (void (*)(void *)) put_device, > - &chip->dev); > + (void (*)(void *)) tpm_chip_free, > + chip); > if (rc) > return ERR_PTR(rc); > > -- > 2.17.1 > Please test against the latest in git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git and share your results. BR, Jarkko