linux-kernel - Re: [PATCH 1/2] ASoC: codecs: wsa881x: handle timeouts in resume path

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: <165660814249.771023.7178878929435843579.b4-ty@kernel.org>
Date:   Thu, 30 Jun 2022 17:55:42 +0100
From:   Mark Brown <broonie@...nel.org>
To:     srinivas.kandagatla@...aro.org
Cc:     perex@...ex.cz, linux-kernel@...r.kernel.org, tiwai@...e.com,
        alsa-devel@...a-project.org, lgirdwood@...il.com,
        pierre-louis.bossart@...ux.intel.com
Subject: Re: [PATCH 1/2] ASoC: codecs: wsa881x: handle timeouts in resume path

On Thu, 30 Jun 2022 14:00:22 +0100, Srinivas Kandagatla wrote:
> Currently we do not check if SoundWire slave initialization timeout
> expired before continuing to access its registers.
> 
> Its possible that the registers are not accessible if timeout is
> expired. Handle this by returning timeout in resume path.
> 
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: codecs: wsa881x: handle timeouts in resume path
      commit: cf6af24b54903f9f70c29b3e5b19cb72cc862d60
[2/2] ASoC: codecs: wsa883x: handle timeouts in resume path
      commit: 0df73e1a9f7b1152ace21b6406138f7487239128

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