lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025090811-pendant-calm-09c5@gregkh>
Date: Mon, 8 Sep 2025 11:09:06 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
	linux-kernel@...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, sudipm.mukherjee@...il.com,
	srw@...dewatkins.net, rwarsow@....de, conor@...nel.org,
	hargar@...rosoft.com, broonie@...nel.org, achill@...ill.org
Subject: Re: [PATCH 6.1 000/104] 6.1.151-rc1 review

On Sun, Sep 07, 2025 at 08:00:39PM -0700, Florian Fainelli wrote:
> 
> 
> On 9/7/2025 12:57 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.151 release.
> > There are 104 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 Tue, 09 Sep 2025 19:55:53 +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/v6.x/stable-review/patch-6.1.151-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-6.1.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> 
> perf fails to build with:
> 
> util/bpf-utils.c: In function 'get_bpf_prog_info_linear':
> util/bpf-utils.c:129:26: error: '__MAX_BPF_PROG_TYPE' undeclared (first use
> in this function); did you mean 'MAX_BPF_LINK_TYPE'?
>   129 |         if (info.type >= __MAX_BPF_PROG_TYPE)
>       |                          ^~~~~~~~~~~~~~~~~~~
>       |                          MAX_BPF_LINK_TYPE
> util/bpf-utils.c:129:26: note: each undeclared identifier is reported only
> once for each function it appears in
> 
> which is due to  05c6ce9491f1851d63c40e918ed5cf7902fd43d3 ("perf bpf-utils:
> Harden get_bpf_prog_info_linear")
> 
> Looks like we need caf8f28e036c4ba1e823355da6c0c01c39e70ab9 ("bpf: Add BPF
> token support to BPF_PROG_LOAD command") which adds the definition for
> __MAX_BPF_PROG_TYPE, unfortunately there is a lot going on there that this
> won't apply cleanly.

Ick.  I'll just drop the perf patch, thanks for noticing this.  And I'll
drop the patch after this one for both 6.1.y and 6.6.y.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ