linux-kernel - Re: [RESEND PATCH] ASoC: fsl_asrc

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: <166427485994.60697.4779578506404492678.b4-ty@kernel.org>
Date:   Tue, 27 Sep 2022 11:34:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     festevam@...il.com, nicoleotsuka@...il.com, lgirdwood@...il.com,
        tiwai@...e.com, perex@...ex.cz, shengjiu.wang@...il.com,
        alsa-devel@...a-project.org, Shengjiu Wang <shengjiu.wang@....com>,
        Xiubo.Lee@...il.com
Cc:     linux-kernel@...r.kernel.org, s.hauer@...gutronix.de,
        linuxppc-dev@...ts.ozlabs.org
Subject: Re: [RESEND PATCH] ASoC: fsl_asrc_dma: fully initialize structs

On Fri, 23 Sep 2022 18:15:47 +0800, Shengjiu Wang wrote:
> From: Sascha Hauer <s.hauer@...gutronix.de>
> 
> The driver uses two statically ininitialized struct dma_slave_config,
> but only one of them is initialized to zero. Initialize config_be to
> zero as well to make sure that no fields are filled with random values.
> Let the compiler do this instead of explicitly calling memset() which
> makes it easier to read.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: fsl_asrc_dma: fully initialize structs
      commit: 1849a1505533501ea39ed0538c2d35eba4704baa

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