linux-kernel - Re: [PATCH] ASoC: tas2781: add module parameter to tascodec

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: Mon, 05 Feb 2024 16:58:42 +0000
From: Mark Brown <broonie@...nel.org>
To: Shenghao Ding <shenghao-ding@...com>, Kevin Lu <kevin-lu@...com>, 
 Baojun Xu <baojun.xu@...com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Liam Girdwood <lgirdwood@...il.com>, 
 Gergo Koteles <soyer@....hu>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 alsa-devel@...a-project.org, stable@...r.kernel.org
Subject: Re: [PATCH] ASoC: tas2781: add module parameter to tascodec_init()

On Sun, 04 Feb 2024 21:01:17 +0100, Gergo Koteles wrote:
> The tascodec_init() of the snd-soc-tas2781-comlib module is called from
> snd-soc-tas2781-i2c and snd-hda-scodec-tas2781-i2c modules. It calls
> request_firmware_nowait() with parameter THIS_MODULE and a cont/callback
> from the latter modules.
> 
> The latter modules can be removed while their callbacks are running,
> resulting in a general protection failure.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tas2781: add module parameter to tascodec_init()
      commit: 34a1066981a967eab619938e7b35a9be6b4c34e1

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