mbox series

[6.8,regression,fix,0/2] ASoC: Intel: Boards: Fix NULL pointer deref in BYT/CHT boards

Message ID 20240210134400.24913-1-hdegoede@redhat.com (mailing list archive)
Headers show
Series ASoC: Intel: Boards: Fix NULL pointer deref in BYT/CHT boards | expand

Message

Hans de Goede Feb. 10, 2024, 1:43 p.m. UTC
Hi All,

While testing 6.8 on a Bay Trail device with a ALC5640 codec
I noticed a regression in 6.8 which causes a NULL pointer deref
in probe().

All BYT/CHT Intel machine drivers are affected. Patch 1/2 of
this series fixes all of them.

Patch 2/2 adds some small cleanups to cht_bsw_rt5645.c for
issues which I noticed while working on 1/2.

Regards,

Hans



Hans de Goede (2):
  ASoC: Intel: Boards: Fix NULL pointer deref in BYT/CHT boards
  ASoC: Intel: cht_bsw_rt5645: Cleanup codec_name handling

 sound/soc/intel/boards/bytcht_cx2072x.c | 3 ++-
 sound/soc/intel/boards/bytcht_da7213.c  | 3 ++-
 sound/soc/intel/boards/bytcht_es8316.c  | 3 ++-
 sound/soc/intel/boards/bytcr_rt5640.c   | 3 ++-
 sound/soc/intel/boards/bytcr_rt5651.c   | 3 ++-
 sound/soc/intel/boards/bytcr_wm5102.c   | 3 ++-
 sound/soc/intel/boards/cht_bsw_rt5645.c | 7 +++----
 sound/soc/intel/boards/cht_bsw_rt5672.c | 3 ++-
 8 files changed, 17 insertions(+), 11 deletions(-)

Comments

Mark Brown Feb. 12, 2024, 1:55 a.m. UTC | #1
On Sat, 10 Feb 2024 14:43:58 +0100, Hans de Goede wrote:
> While testing 6.8 on a Bay Trail device with a ALC5640 codec
> I noticed a regression in 6.8 which causes a NULL pointer deref
> in probe().
> 
> All BYT/CHT Intel machine drivers are affected. Patch 1/2 of
> this series fixes all of them.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: Intel: Boards: Fix NULL pointer deref in BYT/CHT boards
      commit: 7d99a70b65951108d82e1618c67abe69c3ed7720
[2/2] ASoC: Intel: cht_bsw_rt5645: Cleanup codec_name handling
      commit: 930375d34de67e129566caca008de0bbc54a4646

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