linux-kernel - Re: [PATCH] ASoC: cs48l32: Fix a signedness bug in cs48l32_hw

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: <174947641193.126747.915802797193162530.b4-ty@kernel.org>
Date: Mon, 09 Jun 2025 14:40:11 +0100
From: Mark Brown <broonie@...nel.org>
To: David Rhodes <david.rhodes@...rus.com>, 
 Richard Fitzgerald <rf@...nsource.cirrus.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Stuart Henderson <stuarth@...nsource.cirrus.com>, 
 Piotr Stankiewicz <piotrs@...nsource.cirrus.com>, 
 Qi Zhou <qi.zhou@...rus.com>, linux-sound@...r.kernel.org, 
 patches@...nsource.cirrus.com, linux-kernel@...r.kernel.org, 
 Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
Cc: dan.carpenter@...aro.org, kernel-janitors@...r.kernel.org, 
 error27@...il.com
Subject: Re: [PATCH] ASoC: cs48l32: Fix a signedness bug in
 cs48l32_hw_params()

On Tue, 03 Jun 2025 14:48:13 -0700, Harshit Mogalapalli wrote:
> There is a type promotion that can happen when freq(u32) variable is
> comapared with sclk_target(integer), when sclk_target is a negative
> value it promotes to a large postive integer which might not be a
> problem in this particular case as the condition evaluates to false
> when that happens, but bail out early when sclk_target has negative
> error codes.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs48l32: Fix a signedness bug in cs48l32_hw_params()
      commit: 22188b9df60dde48eaba276da22062aaf8e12dfe

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