linux-kernel - Re: [PATCH] ASoC: amd: ps: fix for acp

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]

Date:   Tue, 30 May 2023 17:32:34 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc:     alsa-devel@...a-project.org, pierre-louis.bossart@...ux.intel.com,
        Basavaraj.Hiregoudar@....com, Sunil-kumar.Dommati@....com,
        Mastan.Katragadda@....com, Arungopal.kondaveeti@....com,
        mario.limonciello@....com, Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Syed Saba Kareem <Syed.SabaKareem@....com>,
        Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: amd: ps: fix for acp_lock access in pdm driver

On Thu, 25 May 2023 16:59:55 +0530, Vijendar Mukunda wrote:
> Sending the mutex address(acp_lock) as platform
> data during ACP PDM platform driver register sequence,
> its creating copy of the platform data.
> Referencing this platform data in ACP PDM driver results
> incorrect reference to the common lock usage.
> 
> Instead of directly passing the lock address as platform
> data, retrieve it from parent driver data structure
> and use the same lock reference in ACP PDM driver.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: amd: ps: fix for acp_lock access in pdm driver
      commit: b6b5c6426efe27cbd954409a50604d99c79bd42b

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