linux-kernel - Re: [PATCH 0/2] Improve support for sof_ipc{3|4}_bytes_ext

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: <168487824751.297010.12344595686520411932.b4-ty@kernel.org>
Date:   Tue, 23 May 2023 22:44:07 +0100
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        Daniel Baluta <daniel.baluta@....nxp.com>
Cc:     linux-kernel@...r.kernel.org, pierre-louis.bossart@...ux.intel.com,
        lgirdwood@...il.com, peter.ujfalusi@...ux.intel.com,
        yung-chuan.liao@...ux.intel.com, ranjani.sridharan@...ux.intel.com,
        kai.vehmanen@...ux.intel.com, daniel.baluta@...il.com
Subject: Re: [PATCH 0/2] Improve support for sof_ipc{3|4}_bytes_ext_put

On Wed, 03 May 2023 11:10:47 +0300, Daniel Baluta wrote:
> This patch series provides better handling of cases where sending
> a data blob to FW results in a validation error.
> 
> In this case we restore to the last good known value instead of keeping
> the data that firwmare rejected.
> 
> Paul Olaru (2):
>   ASoC: sof: Improve sof_ipc3_bytes_ext_put function
>   ASoC: sof: Improve sof_ipc4_bytes_ext_put function
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: sof: Improve sof_ipc3_bytes_ext_put function
      commit: 299f6c752f8f7dabb62fe4df62ebd233b58402bd
[2/2] ASoC: sof: Improve sof_ipc4_bytes_ext_put function
      commit: db38d86d0c54e0dbea063e915ce3e1fe394af444

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