linux-kernel - Re: [PATCH][next] ASoC: max98388: Fix missing increment of variable slot

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: <172865347434.3898502.5695068809742521783.b4-ty@kernel.org>
Date: Fri, 11 Oct 2024 14:31:14 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Ryan Lee <ryans.lee@...log.com>, 
 linux-sound@...r.kernel.org, Colin Ian King <colin.i.king@...il.com>
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] ASoC: max98388: Fix missing increment of
 variable slot_found

On Thu, 10 Oct 2024 19:20:32 +0100, Colin Ian King wrote:
> The variable slot_found is being initialized to zero and inside
> a for-loop is being checked if it's reached MAX_NUM_CH, however,
> this is currently impossible since slot_found is never changed.
> In a previous loop a similar coding pattern is used and slot_found
> is being incremented. It appears the increment of slot_found is
> missing from the loop, so fix the code by adding in the increment.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: max98388: Fix missing increment of variable slot_found
      commit: ca2803fadfd239abf155ef4a563b22a9507ee4b2

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