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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172963894347.334190.2415888818283876880.b4-ty@kernel.org>
Date: Wed, 23 Oct 2024 00:15:43 +0100
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Pierre-Louis Bossart <pierre-louis.bossart@...ux.dev>, 
 linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org, 
 linux-kernel@...r.kernel.org, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: stable@...r.kernel.org, Alexey Klimov <alexey.klimov@...aro.org>, 
 Steev Klimaszewski <steev@...i.org>
Subject: Re: [PATCH v2] ASoC: qcom: sc7280: Fix missing Soundwire runtime
 stream alloc

On Sat, 12 Oct 2024 12:11:08 +0200, Krzysztof Kozlowski wrote:
> Commit 15c7fab0e047 ("ASoC: qcom: Move Soundwire runtime stream alloc to
> soundcards") moved the allocation of Soundwire stream runtime from the
> Qualcomm Soundwire driver to each individual machine sound card driver,
> except that it forgot to update SC7280 card.
> 
> Just like for other Qualcomm sound cards using Soundwire, the card
> driver should allocate and release the runtime.  Otherwise sound
> playback will result in a NULL pointer dereference or other effect of
> uninitialized memory accesses (which was confirmed on SDM845 having
> similar issue).
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: qcom: sc7280: Fix missing Soundwire runtime stream alloc
      commit: db7e59e6a39a4d3d54ca8197c796557e6d480b0d

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