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] [day] [month] [year] [list]
Message-Id: <173316064213.537992.6375063758006475146.b4-ty@kernel.org>
Date: Mon, 02 Dec 2024 23:00:42 +0530
From: Vinod Koul <vkoul@...nel.org>
To: dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Viresh Kumar <vireshk@...nel.org>, stable@...r.kernel.org, 
 Ferry Toth <fntoth@...il.com>
Subject: Re: [PATCH v5 1/1] dmaengine: dw: Select only supported masters
 for ACPI devices


On Mon, 04 Nov 2024 11:50:50 +0200, Andy Shevchenko wrote:
> The recently submitted fix-commit revealed a problem in the iDMA 32-bit
> platform code. Even though the controller supported only a single master
> the dw_dma_acpi_filter() method hard-coded two master interfaces with IDs
> 0 and 1. As a result the sanity check implemented in the commit
> b336268dde75 ("dmaengine: dw: Add peripheral bus width verification")
> got incorrect interface data width and thus prevented the client drivers
> from configuring the DMA-channel with the EINVAL error returned. E.g.,
> the next error was printed for the PXA2xx SPI controller driver trying
> to configure the requested channels:
> 
> [...]

Applied, thanks!

[1/1] dmaengine: dw: Select only supported masters for ACPI devices
      commit: f0e870a0e9c5521f2952ea9f3ea9d3d122631a89

Best regards,
-- 
~Vinod



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ