Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Akhil R <akhilrajeev@nvidia.com>
To: <vulab@iscas.ac.cn>
Cc: <akhilrajeev@nvidia.com>, <davem@davemloft.net>,
	<herbert@gondor.apana.org.au>, <jonathanh@nvidia.com>,
	<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>, <stable@vger.kernel.org>,
	<thierry.reding@kernel.org>
Subject: [PATCH] fix: crypto/tegra: tegra_se_host1x_submit: timeout path leaks host1x_job   reference
Date: Fri, 26 Jun 2026 15:07:05 +0000	[thread overview]
Message-ID: <20260626150705.5658-1-akhilrajeev@nvidia.com> (raw)
In-Reply-To: <20260626121453.35043-1-vulab@iscas.ac.cn>

On Fri, 26 Jun 2026 20:14:53 +0800, WenTao Liang wrote:
> When host1x_syncpt_wait returns a timeout error, the function returns ret
>   directly without calling host1x_job_put(job). The job reference acquired
>   by host1x_job_alloc is properly released on all other error paths via the
>   job_put label but is missing on the timeout path.
> 
> Cc: stable@vger.kernel.org
> Fixes: 0880bb3b00c8 ("crypto: tegra - Add Tegra Security Engine driver")
> Signed-off-by: WenTao Liang <vulab@iscas.ac.cn>

This fix is already applied in linux-next as commit 6ea0ce3a19f9
("crypto: tegra - fix refcount leak in tegra_se_host1x_submit()").

https://lore.kernel.org/linux-tegra/aip3_Hqk876NZFHf@gondor.apana.org.au/T/#t

Regards,
Akhil

      reply	other threads:[~2026-06-26 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 12:14 [PATCH] fix: crypto/tegra: tegra_se_host1x_submit: timeout path leaks host1x_job reference WenTao Liang
2026-06-26 15:07 ` Akhil R [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260626150705.5658-1-akhilrajeev@nvidia.com \
    --to=akhilrajeev@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jonathanh@nvidia.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=thierry.reding@kernel.org \
    --cc=vulab@iscas.ac.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox