[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <155c581f-1a3e-4d6c-82b9-0ff7855dcaab@kili.mountain>
Date: Tue, 14 Mar 2023 17:22:28 +0300
From: Dan Carpenter <error27@...il.com>
To: Dongliang Mu <dzm91@...t.edu.cn>
Cc: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Hans de Goede <hdegoede@...hat.com>,
Mark Gross <markgross@...nel.org>,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH linux-next v2 1/3] platform/x86/intel/tpmi: Fix double
free in tpmi_create_device()
On Thu, Mar 09, 2023 at 12:01:05PM +0800, Dongliang Mu wrote:
> The previous commit 6a192c0cbf38 ("platform/x86/intel/tpmi: Fix
> double free reported by Smatch") incorrectly handle the deallocation of
> res variable. As shown in the comment, intel_vsec_add_aux handles all
> the deallocation of res and feature_vsec_dev. Therefore, kfree(res) can
> still cause double free if intel_vsec_add_aux returns error.
>
> Fix this by adjusting the error handling part in tpmi_create_device,
> following the function intel_vsec_add_dev.
>
> Fixes: 6a192c0cbf38 ("platform/x86/intel/tpmi: Fix double free reported by Smatch")
> Signed-off-by: Dongliang Mu <dzm91@...t.edu.cn>
> ---
Yeah. These patches are right. The earlier fix still has a double
free. Devres stuff is confusing...
Reviewed-by: Dan Carpenter <error27@...il.com>
regards,
dan carpenter
Powered by blists - more mailing lists