linux-kernel - Re: [PATCH] mmc: core: Only set maximum DMA segment size if DMA is supported

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: 
 <173145199424.701548.5612261824540957185.git-patchwork-notify@kernel.org>
Date: Tue, 12 Nov 2024 22:53:14 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Guenter Roeck <linux@...ck-us.net>
Cc: linux-riscv@...ts.infradead.org, ulf.hansson@...aro.org,
 paul.walmsley@...ive.com, samuel.holland@...ive.com,
 linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org, hch@....de,
 robin.murphy@....com
Subject: Re: [PATCH] mmc: core: Only set maximum DMA segment size if DMA is
 supported

Hello:

This patch was applied to riscv/linux.git (fixes)
by Ulf Hansson <ulf.hansson@...aro.org>:

On Tue, 24 Sep 2024 14:01:23 -0700 you wrote:
> Since upstream commit 334304ac2bac ("dma-mapping: don't return errors
> from dma_set_max_seg_size") calling dma_set_max_seg_size() on a device
> not supporting DMA results in a warning traceback. This is seen when
> booting the sifive_u machine from SD. The underlying SPI controller
> (sifive,spi0 compatible) explicitly sets dma_mask to NULL.
> 
> Avoid the backtrace by only calling dma_set_max_seg_size() if DMA is
> supported.
> 
> [...]

Here is the summary with links:
  - mmc: core: Only set maximum DMA segment size if DMA is supported
    https://git.kernel.org/riscv/c/c26339faed11

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html