Re: [PATCH 5.15 000/123] 5.15.196-rc1 review

[Greg Kroah-Hartman]

On Tue, Oct 28, 2025 at 09:11:58PM +0530, Vijayendra Suman wrote:
> 
> 
> On 28/10/25 12:04 am, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.196 release.
> > There are 123 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.
> > 
> > Responses should be made by Wed, 29 Oct 2025 18:34:15 +0000.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/
> > patch-5.15.196-rc1.gz
> > or in the git tree and branch at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> 
> perf failed to compile with following errors at compilation.
> 
> BUILDSTDERR: tests/perf-record.c: In function 'test__PERF_RECORD':
> BUILDSTDERR: tests/perf-record.c:118:17: error: implicit declaration of
> function 'evlist__cancel_workload'; did you mean 'evlist__start_workload'?
> [-Werror=implicit-function-declaration]
> BUILDSTDERR:   118 |                 evlist__cancel_workload(evlist);
> BUILDSTDERR:       |                 ^~~~~~~~~~~~~~~~~~~~~~~
> BUILDSTDERR:       |                 evlist__start_workload
> 
> 
> There is no definition for evlist__cancel_workload
> 
> Following are references of 'evlist__cancel_workload'
> tools/perf/tests/perf-record.c:118:	evlist__cancel_workload(evlist);
> tools/perf/tests/perf-record.c:130:	evlist__cancel_workload(evlist);
> tools/perf/tests/perf-record.c:142:	evlist__cancel_workload(evlist);
> tools/perf/tests/perf-record.c:155:	evlist__cancel_workload(evlist);
> 
> 
> Commit which need to be reverted.
> b7e5c59f3b09 perf test: Don't leak workload gopipe in PERF_RECORD_*

This is already being reverted in the latest -rc release, does that not
work here for you?

thanks,

greg k-h