[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<SJ1PR12MB633943D654272A0612695F1DC0F22@SJ1PR12MB6339.namprd12.prod.outlook.com>
Date: Wed, 29 May 2024 06:53:42 +0000
From: Akhil R <akhilrajeev@...dia.com>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>, Herbert Xu
<herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net>,
Thierry Reding <thierry.reding@...il.com>, Jon Hunter <jonathanh@...dia.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: RE: [PATCH] crypto: tegra - Remove an incorrect iommu_fwspec_free()
call in tegra_se_remove()
> The only iommu function call in this driver is a
> tegra_dev_iommu_get_stream_id() which does not allocate anything and does
> not take any reference.
>
> More-over, what is freed is "se->dev" which has been devm_kzalloc()'ed in the
> probe.
I did not completely understand what is being tried to convey here.
If I understand it right, iommu_fwspec_free() does not do anything
with the "devm_kzalloc"ed variable.
It would probably be a good idea to remove this line from the commit message.
>
> So there is no point in calling iommu_fwspec_free() in the remove function.
>
> Remove this incorrect function call.
>
> Fixes: 0880bb3b00c8 ("crypto: tegra - Add Tegra Security Engine driver")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@...adoo.fr>
Powered by blists - more mailing lists