linux-kernel - Re: [PATCH RESEND] ASoC: tlv320aic32x4: Fix the divide by zero

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:   Mon, 14 Aug 2023 23:06:20 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, Guiting Shen <aarongt.shen@...il.com>
Cc:     perex@...ex.cz, tiwai@...e.com, sboyd@...nel.org,
        mripard@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND] ASoC: tlv320aic32x4: Fix the divide by zero

On Sun, 13 Aug 2023 20:55:20 +0800, Guiting Shen wrote:
> The value of register(NDAC,MDAC,NADC,MADC,BCLKN) maybe zero lead to
> divide by zero in clk_aic32x4_div_recalc_rate().And the rate should be
> divide by 128 if the value was zero in this function according to the
> datasheet.
> 
> Add the macro AIC32X4_DIV_MAX to present the 128 and return 0 if failing
> to read the value of register.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tlv320aic32x4: Fix the divide by zero
      commit: 11e756cc85fac43e2025306ad6aea80114cc7e98

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