linux-kernel - Re: [PATCH] ASoC: wcd9335: Remove RX channel from old list before adding it to a new one

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: <165513647538.514792.3755540877211595484.b4-ty@kernel.org>
Date:   Mon, 13 Jun 2022 17:07:55 +0100
From:   Mark Brown <broonie@...nel.org>
To:     perex@...ex.cz, yassine.oudjana@...il.com, lgirdwood@...il.com,
        srinivas.kandagatla@...aro.org, tiwai@...e.com
Cc:     linux-arm-msm@...r.kernel.org, alsa-devel@...a-project.org,
        y.oudjana@...tonmail.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: wcd9335: Remove RX channel from old list before adding it to a new one

On Mon, 6 Jun 2022 19:22:26 +0400, Yassine Oudjana wrote:
> From: Yassine Oudjana <y.oudjana@...tonmail.com>
> 
> Currently in slim_rx_mux_put, an RX channel gets added to a new list
> even if it is already in one. This can mess up links and make either
> it, the new list head, or both, get linked to the wrong entries.
> This can cause an entry to link to itself which in turn ends up
> making list_for_each_entry in other functions loop infinitely.
> To avoid issues, always remove the RX channel from any list it's in
> before adding it to a new list.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: wcd9335: Remove RX channel from old list before adding it to a new one
      commit: 7263fc6c71c3a88c17a1ce3565b7b6f378d13878

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