linux-kernel - Re: [PATCH -next] spi: Fix missing unlock on error in sp7021_spi_master_transfer

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]

Date:   Fri, 28 Jan 2022 15:59:10 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Yang Yingliang <yangyingliang@...wei.com>,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     p.zabel@...gutronix.de, lhjeff911@...il.com
Subject: Re: [PATCH -next] spi: Fix missing unlock on error in sp7021_spi_master_transfer_one()

On Thu, 27 Jan 2022 19:58:15 +0800, Yang Yingliang wrote:
> Add the missing unlock before return from sp7021_spi_master_transfer_one()
> in the error handling case.
> 
> 

Applied to

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

Thanks!

[1/1] spi: Fix missing unlock on error in sp7021_spi_master_transfer_one()
      commit: 20dc69ca1023b7e4c4af3c3495aa5a91e1a9be39

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