linux-kernel - Re: [PATCH v2] spi: stm32: fix pointer-to-pointer variables usage

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: <175140814365.710092.16438205627985189965.b4-ty@kernel.org>
Date: Tue, 01 Jul 2025 23:15:43 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, Antonio Quartulli <antonio@...delbit.com>
Cc: linux-stm32@...md-mailman.stormreply.com, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 Clément Le Goffic <clement.legoffic@...s.st.com>, 
 Alexandre Torgue <alexandre.torgue@...s.st.com>, 
 Maxime Coquelin <mcoquelin.stm32@...il.com>, 
 Alain Volmat <alain.volmat@...s.st.com>
Subject: Re: [PATCH v2] spi: stm32: fix pointer-to-pointer variables usage

On Mon, 30 Jun 2025 10:12:53 +0200, Antonio Quartulli wrote:
> In stm32_spi_prepare_rx_dma_mdma_chaining() both rx_dma_desc
> and rx_mdma_desc are passed as pointer-to-pointer arguments.
> 
> The goal is to pass back to the caller the value returned
> by dmaengine_prep_slave_sg(), when it is not NULL.
> 
> However, these variables are wrongly handled as simple pointers
> during later assignments and checks.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: stm32: fix pointer-to-pointer variables usage
      commit: c4f2c05ab02952c9a56067aeb700ded95b183570

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark