linux-kernel - Re: [PATCH] spi: spi-altera-dfl: Fix an error handling path

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 for Android: free password hash cracker in your pocket

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

Message-Id: <165459881400.302078.16808587662616763292.b4-ty@kernel.org>
Date:   Tue, 07 Jun 2022 11:46:54 +0100
From:   Mark Brown <broonie@...nel.org>
To:     christophe.jaillet@...adoo.fr, matthew.gerlach@...ux.intel.com
Cc:     kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: spi-altera-dfl: Fix an error handling path

On Sun, 29 May 2022 08:31:53 +0200, Christophe JAILLET wrote:
> The spi_alloc_master() call is not undone in all error handling paths.
> Moreover, there is no .remove function to release the allocated memory.
> 
> In order to fix both this issues, switch to devm_spi_alloc_master().
> 
> This allows further simplification of the probe.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-altera-dfl: Fix an error handling path
      commit: 8e3ca32f46994e74b7f43c57731150b2aedb2630

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