linux-kernel - Re: [PATCH] regulator: tps6594-regulator: Fix random kernel crash

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:   Tue, 05 Sep 2023 22:42:01 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Esteban Blanc <eblanc@...libre.com>,
        Jerome Neanne <jneanne@...libre.com>
Cc:     linux-kernel@...r.kernel.org, u-kumar1@...com, jpanis@...libre.com,
        khilman@...libre.com, s.sharma@...com, aseketeli@...libre.com
Subject: Re: [PATCH] regulator: tps6594-regulator: Fix random kernel crash

On Tue, 05 Sep 2023 16:07:34 +0200, Jerome Neanne wrote:
> Random kernel crash detected in TI CICD when regulator driver is added.
> This is root caused to irq index increment being done twice causing
> irq_data being allocated outside of the range.
> 
> - Rework tps6594_request_reg_irqs with correct index increment
> - Adjust irq_data kmalloc size to the exact size needed for the device
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: tps6594-regulator: Fix random kernel crash
      commit: ca0e36e3e39a4e8b5a4b647dff8c5938ca6ccbec

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