From: Vitaly Chikunov <vt@altlinux.org>
To: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Cc: "Thorsten Leemhuis" <regressions@leemhuis.info>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Sasha Levin" <sashal@kernel.org>,
linux-kernel@vger.kernel.org,
"Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Mark Brown" <broonie@kernel.org>,
lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
linux-sound@vger.kernel.org,
"Linux kernel regressions list" <regressions@lists.linux.dev>
Subject: Re: [PATCH AUTOSEL 6.9 17/40] ASoC: topology: Fix route memory corruption
Date: Wed, 14 Aug 2024 03:00:53 +0300 [thread overview]
Message-ID: <20240814000053.posrfbgoic2yzpsk@altlinux.org> (raw)
In-Reply-To: <53ab1511-b79c-4378-b2b5-ea9e19e8f65b@linux.intel.com>
Greg, Amadeusz,
On Tue, Aug 13, 2024 at 04:42:04PM +0200, Amadeusz Sławiński wrote:
> On 8/12/2024 4:11 PM, Greg Kroah-Hartman wrote:
> > On Mon, Aug 12, 2024 at 01:38:42PM +0300, Vitaly Chikunov wrote:
> > > Greg,
> > >
> > > On Mon, Aug 12, 2024 at 12:25:54PM +0200, Greg Kroah-Hartman wrote:
> > > > On Mon, Aug 12, 2024 at 12:01:48PM +0200, Amadeusz Sławiński wrote:
> > > > > I guess that for completeness you need to apply both patches:
> > > > >
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/sound/soc/soc-topology.c?id=97ab304ecd95c0b1703ff8c8c3956dc6e2afe8e1
> > > >
> > > > This is already in the tree.
> > > >
> > > > > was an incorrect fix which was later fixed by:
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/sound/soc/soc-topology.c?id=0298f51652be47b79780833e0b63194e1231fa34
> > > >
> > > > This commit will not apply :(
> > >
> > > It depends upon e0e7bc2cbee9 ("ASoC: topology: Clean up route loading"),
> > > which was in the same patchset that didn't get applied.
> > > https://lore.kernel.org/stable/?q=ASoC%3A+topology%3A+Clean+up+route+loading
> > >
> > > I see, Mark Brown said it's not suitable material for stable kernels
> > > (since it's code cleanup), and Sasha Levin dropped it, and the dependent
> > > commit with real fix.
> >
> > Ok, then someone needs to provide a working backport please...
> >
>
> Should this be cherry-pick of both (they should apply cleanly):
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/sound/soc/soc-topology.c?id=e0e7bc2cbee93778c4ad7d9a792d425ffb5af6f7
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/sound/soc/soc-topology.c?id=0298f51652be47b79780833e0b63194e1231fa34
> or just the second one adjusted to apply for stable trees?
I think having commit with memory corruption fix is more important to
stable kernels than not having the code cleanup commit. So, I would
suggest stable policy to be changed a bit, and minor commits like this
code cleanup, be allowed in stable if they are dependence of bug fixing
commits.
Additionally, these neutral commits just make stable trees become closer
to mainline trees (which allows more bug fix commits to be applied
cleanly).
Thanks,
next prev parent reply other threads:[~2024-08-14 0:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 16:17 [PATCH AUTOSEL 6.9 17/40] ASoC: topology: Fix route memory corruption Vitaly Chikunov
2024-08-05 17:09 ` Pierre-Louis Bossart
2024-08-12 9:53 ` Thorsten Leemhuis
2024-08-12 10:01 ` Amadeusz Sławiński
2024-08-12 10:25 ` Greg Kroah-Hartman
2024-08-12 10:38 ` Vitaly Chikunov
2024-08-12 14:11 ` Greg Kroah-Hartman
2024-08-13 14:42 ` Amadeusz Sławiński
2024-08-14 0:00 ` Vitaly Chikunov [this message]
2024-08-14 10:33 ` Mark Brown
2024-08-14 14:07 ` Amadeusz Sławiński
2024-08-12 10:24 ` Greg Kroah-Hartman
2024-08-14 2:18 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2024-07-09 16:18 [PATCH AUTOSEL 6.9 01/40] workqueue: Refactor worker ID formatting and make wq_worker_comm() use full ID string Sasha Levin
2024-07-09 16:18 ` [PATCH AUTOSEL 6.9 17/40] ASoC: topology: Fix route memory corruption Sasha Levin
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=20240814000053.posrfbgoic2yzpsk@altlinux.org \
--to=vt@altlinux.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
/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