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: <172968431380.31331.15335444902728869740.b4-ty@kernel.org>
Date: Wed, 23 Oct 2024 12:51:53 +0100
From: Mark Brown <broonie@...nel.org>
To: perex@...ex.cz, tiwai@...e.com, hayashi.kunihiko@...ionext.com, 
 mhiramat@...nel.org, 
 (학생) 장인규 (컴퓨터공학과) <ingyujang25@...st.ac.kr>
Cc: lgirdwood@...il.com, linux-sound@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoc: uniphier: Handle regmap_write errors in
 aio_iecout_set_enable()

On Tue, 08 Oct 2024 05:20:30 +0000, (학생) 장인규 (컴퓨터공학과) wrote:
> The aio_oport_set_stream_type() function did not previously check the
> return values of regmap_write().
> If these functions fail, it could lead to silent failures when
> configuring the audio playback port, causing improper behavior in audio
> stream output via S/PDIF without any indication of an error.
> 
> This patch modifies aio_oport_set_stream_type() to check the return
> values of regmap_write().
> If regmap_write() fails, the error code is propagated back to the caller
> to ensure proper error handling.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoc: uniphier: Handle regmap_write errors in aio_iecout_set_enable()
      commit: 9b0c65115acdcb6fd6bbeb360c1f4f7b14c9a610

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ