linux-kernel - Re: [PATCH 0/2] Fixes for Tegra audio

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: <172449441067.846858.2296683917418072165.b4-ty@kernel.org>
Date: Sat, 24 Aug 2024 11:13:30 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, Sameer Pujar <spujar@...dia.com>
Cc: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 thierry.reding@...il.com, jonathanh@...dia.com, mkumard@...dia.com, 
 rituc@...dia.com, jbrunet@...libre.com, linux-kernel@...r.kernel.org, 
 linux-tegra@...r.kernel.org, robelin@...dia.com
Subject: Re: [PATCH 0/2] Fixes for Tegra audio

On Fri, 23 Aug 2024 14:43:40 +0000, Sameer Pujar wrote:
> This is a small series which fixes two bugs which were discovered
> on NVIDIA Jetson AGX Orin platform.
> 
> The first patch in the series fixes a KASAN UAF bug discovered
> during suspend/resume testing. This is a core DAPM fix.
> 
> The second patch fixes CBB error and this is Tegra in AHUB driver.
> This error happens when Tegra audio drivers were built as part of
> kernel image.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dapm: Fix UAF for snd_soc_pcm_runtime object
      commit: b4a90b543d9f62d3ac34ec1ab97fc5334b048565
[2/2] ASoC: tegra: Fix CBB error during probe()
      commit: 6781b962d97bc52715a8db8cc17278cc3c23ebe8

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