From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Cc: stable-commits@vger.kernel.org, Takashi Iwai <tiwai@suse.de>
Subject: Re: Patch "ASoC: topology: disable size checks for bytes_ext controls if needed" has been added to the 4.9-stable tree
Date: Mon, 26 Oct 2020 10:01:09 -0500 [thread overview]
Message-ID: <e1aae5d8-3820-9126-d1a9-225f093dfde7@linux.intel.com> (raw)
In-Reply-To: <20201026121123.GA2474358@kroah.com>
On 10/26/20 7:11 AM, Greg KH wrote:
> On Mon, Oct 26, 2020 at 01:53:46AM -0400, Sasha Levin wrote:
>> This is a note to let you know that I've just added the patch titled
>>
>> ASoC: topology: disable size checks for bytes_ext controls if needed
>>
>> to the 4.9-stable tree which can be found at:
>> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>> asoc-topology-disable-size-checks-for-bytes_ext-cont.patch
>> and it can be found in the queue-4.9 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>>
>
> This breaks the build, so I'm dropping it from everywhere it had
> problems.
>
> Also, why 5.4.y and not 4.19.y, but 4.14.y and 4.9.y?
Ah yes, there's a missed dependency on
fbd3eb7f66c5b ('ALSA: control: Add verification for kctl accesses')
I thought all of this was 20 years old but that commit added the option
SND_CTL_VALIDATION which exposed the problem with this topology patch.
Given the date (January 2020), I don't think it makes sense before 5.6?
I don't think this could have compiled prior to 5.6, I e.g. checked on
4.14.202 and the define SNDRV_CTL_ELEM_ACCESS_SKIP_CHECK was not defined
either.
git grep SNDRV_CTL_ELEM_ACCESS_SKIP_CHECK
sound/soc/soc-topology.c: k->access |=
SNDRV_CTL_ELEM_ACCESS_SKIP_CHECK;
Summary: I suggested this patch be dropped for all versions that don't
contain fbd3eb7f66c5b. Takashi, do you concur?
Thanks for spotting this.
-Pierre
next prev parent reply other threads:[~2020-10-26 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201026055347.0F79E20882@mail.kernel.org>
2020-10-26 12:11 ` Patch "ASoC: topology: disable size checks for bytes_ext controls if needed" has been added to the 4.9-stable tree Greg KH
2020-10-26 15:01 ` Pierre-Louis Bossart [this message]
2020-10-26 15:22 ` Takashi Iwai
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=e1aae5d8-3820-9126-d1a9-225f093dfde7@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.