linux-kernel - Re: [PATCH v2] dmaengine: qcom: bam_dma: Fix BAM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250119054105.rhsathhdqapirszh@thinkpad>
Date: Sun, 19 Jan 2025 11:11:05 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
To: Md Sadre Alam <quic_mdalam@...cinc.com>
Cc: vkoul@...nel.org, robin.murphy@....com, linux-arm-msm@...r.kernel.org,
	dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
	quic_varada@...cinc.com, quic_srichara@...cinc.com
Subject: Re: [PATCH v2] dmaengine: qcom: bam_dma: Fix BAM_RIVISON register
 handling

On Fri, Jan 17, 2025 at 04:43:02PM +0530, Md Sadre Alam wrote:
> This patch resolves a bug from the previous commit where the
> BAM_DESC_CNT_TRSHLD register was conditionally written based on BAM-NDP
> mode. It also fixes an issue where reading the BAM_REVISION register

The 'also' sounds like the patch is fixing 2 issues, but it is just fixing one.

> would hang if num-ees was not zero, which occurs when the SoCs power on
> BAM remotely. The BAM_REVISION register read has been moved to inside if
> condition.
> 
> Cc: stable@...r.kernel.org

The offending commit is just in the -next branch. So CCing stable is pointless.

- Mani

-- 
மணிவண்ணன் சதாசிவம்