[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <373809f0-9fc8-8eeb-ff13-146df11b4ece@applied-asynchrony.com>
Date: Tue, 5 Apr 2022 13:58:57 +0200
From: Holger Hoffstätte <holger@...lied-asynchrony.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org
Cc: stable@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
jonathanh@...dia.com, f.fainelli@...il.com,
sudipm.mukherjee@...il.com, slade@...dewatkins.com,
Valentin Schneider <valentin.schneider@....com>
Subject: Re: [PATCH 5.15 000/913] 5.15.33-rc1 review
(cc'ing Valentin)
On 2022-04-05 09:17, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.33 release.
> There are 913 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
This locks up immediately when trying to use tracepoints, due to:
"sched-tracing-don-t-re-read-p-state-when-emitting-sc.patch" aka
"sched/tracing: Don't re-read p->state when emitting sched_switch event"
Reverting this patch makes things work again, at least for 5.15.x;
don't know about other series.
cheers
Holger
Powered by blists - more mailing lists