From: "Michał Górny" <mgorny@gentoo.org>
To: stable@vger.kernel.org
Subject: Re: 5.10 backport request: ASoC: Intel: sof_rt5682: shrink platform_id names below 20 characters
Date: Fri, 29 Aug 2025 09:09:33 +0200 [thread overview]
Message-ID: <55a3d4952c689938775a17df7eeec447e17e9f42.camel@gentoo.org> (raw)
In-Reply-To: <53696f9e03ff0aa2d8ef3903293e49723df967d1.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
Hello,
On Fri, 2025-08-29 at 08:03 +0200, Michał Górny wrote:
> Hello,
>
> I would like to request backporting the following patch to 5.10 series:
>
> 590cfb082837cc6c0c595adf1711330197c86a58
> ASoC: Intel: sof_rt5682: shrink platform_id names below 20 characters
>
> The patch seems to be already present in 5.15 and newer branches, and
> its lack seems to be causing out-of-bounds read. I've hit it in the
> wild while trying to install 5.10.241 on i686:
>
> sh /var/tmp/portage/sys-kernel/gentoo-kernel-5.10.241/work/linux-5.10/scripts/depmod.sh depmod 5.10.241-gentoo-dist
> depmod: FATAL: Module index: bad character '�'=0x80 - only 7-bit ASCII is supported:
> platform:jsl_rt5682_max98360ax�
>
I'm sorry, I should've waited for my test results first. Looks like
this patch alone is insufficient. Looking at 5.15 stable branch, I see
that we probably need:
ASoC: Intel: bxt_da7219_max98357a: shrink platform_id below 20 characters
ASoC: Intel: sof_rt5682: shrink platform_id names below 20 characters
ASoC: Intel: glk_rt5682_max98357a: shrink platform_id below 20 characters
ASoC: Intel: kbl_da7219_max98357a: shrink platform_id below 20 characters
ASoC: Intel: sof_da7219_max98373: shrink platform_id below 20 characters
ASoC: Intel: sof_da7219_mx98360a: fail to initialize soundcard
ASoC: Intel: Fix platform ID matching
Unless I'm mistaken, the firt series are part of the merge commit
98c69fcc9f5902b0c340acdbbfa365464efc52d2. The followup fixes are:
0f32d9eb38c13c32895b5bf695eac639cee02d6c
f4eeaed04e861b95f1f2c911263f2fcaa959c078
I didn't find anything else that seemed obviously elevant, but I didn't
dug deep. With these backports, I can build 5.10.241 fine -- but I
don't have any hardware to test these drivers.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2025-08-29 7:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 6:03 5.10 backport request: ASoC: Intel: sof_rt5682: shrink platform_id names below 20 characters Michał Górny
2025-08-29 7:09 ` Michał Górny [this message]
2025-08-29 13:55 ` Greg KH
2025-08-31 18:25 ` Michał Górny
2025-09-01 5:34 ` Greg KH
2025-09-01 9:54 ` [PATCH linux-5.10.y 1/5] ASoC: Intel: bxt_da7219_max98357a: shrink platform_id " Michał Górny
2025-09-01 9:54 ` [PATCH linux-5.10.y 2/5] ASoC: Intel: sof_rt5682: shrink platform_id names " Michał Górny
2025-09-01 9:54 ` [PATCH linux-5.10.y 3/5] ASoC: Intel: glk_rt5682_max98357a: shrink platform_id " Michał Górny
2025-09-01 9:54 ` [PATCH linux-5.10.y 4/5] ASoC: Intel: sof_da7219_max98373: " Michał Górny
2025-09-01 9:54 ` [PATCH linux-5.10.y 5/5] ASoC: Intel: sof_da7219_mx98360a: fail to initialize soundcard Michał Górny
2025-09-01 13:25 ` [PATCH linux-5.10.y 1/5] ASoC: Intel: bxt_da7219_max98357a: shrink platform_id below 20 characters Greg KH
2025-09-01 13:55 ` Michał Górny
2025-09-01 13:59 ` Greg KH
2025-09-01 14:10 ` [PATCH v2 " Michał Górny
2025-09-01 14:10 ` [PATCH v2 linux-5.10.y 2/5] ASoC: Intel: sof_rt5682: shrink platform_id names " Michał Górny
2025-09-01 14:10 ` [PATCH v2 linux-5.10.y 3/5] ASoC: Intel: glk_rt5682_max98357a: shrink platform_id " Michał Górny
2025-09-01 14:10 ` [PATCH v2 linux-5.10.y 4/5] ASoC: Intel: sof_da7219_max98373: " Michał Górny
2025-09-01 14:10 ` [PATCH v2 linux-5.10.y 5/5] ASoC: Intel: sof_da7219_mx98360a: fail to initialize soundcard Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55a3d4952c689938775a17df7eeec447e17e9f42.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).