linux-kernel - Re: [PATCH] spi: fix finalize message on error return

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: <170627973371.36139.11882822858180324422.b4-ty@kernel.org>
Date: Fri, 26 Jan 2024 14:35:33 +0000
From: Mark Brown <broonie@...nel.org>
To: David Lechner <dlechner@...libre.com>
Cc: David Jander <david@...tonic.nl>, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: fix finalize message on error return

On Thu, 25 Jan 2024 14:53:09 -0600, David Lechner wrote:
> In __spi_pump_transfer_message(), the message was not finalized in the
> first error return as it is in the other error return paths. Not
> finalizing the message could cause anything waiting on the message to
> complete to hang forever.
> 
> This adds the missing call to spi_finalize_current_message().
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: fix finalize message on error return
      commit: 8c2ae772fe08e33f3d7a83849e85539320701abd

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