linux-kernel - Re: [PATCH 5.15 00/87] 5.15.164-rc1 review

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: <2024072645-delighted-barbecue-154f@gregkh>
Date: Fri, 26 Jul 2024 08:33:00 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
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, f.fainelli@...il.com,
	sudipm.mukherjee@...il.com, srw@...dewatkins.net, rwarsow@....de,
	conor@...nel.org, allen.lkml@...il.com, broonie@...nel.org,
	Anders Roxell <anders.roxell@...aro.org>,
	Arnd Bergmann <arnd@...db.de>,
	Dan Carpenter <dan.carpenter@...aro.org>
Subject: Re: [PATCH 5.15 00/87] 5.15.164-rc1 review

On Thu, Jul 25, 2024 at 10:18:49PM +0530, Naresh Kamboju wrote:
> On Thu, 25 Jul 2024 at 20:22, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.15.164 release.
> > There are 87 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 Sat, 27 Jul 2024 14:27:16 +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.164-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
> 
> The following build errors noticed while building arm configs with toolchains
> gcc-12 and clang-18 on stable-rc linux-5.15.y
> 
> First seen on today builds 25-July-2024.
> 
>   GOOD: b84034c8f228 ("Linux 5.15.163-rc2")
>   BAD:  1d0703aa8114 ("Linux 5.15.164-rc1")
> 
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> 
> Build log:
> -------
> from drivers/net/wireless/ralink/rt2x00/rt2800lib.c:25:
> drivers/net/wireless/ralink/rt2x00/rt2800lib.c: In function
> 'rt2800_txpower_to_dev':
> include/linux/build_bug.h:78:41: error: static assertion failed:
> "clamp() low limit (char)(-7) greater than high limit (char)(15)"
>    78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
>       |                                         ^~~~~~~~~~~~~~
> include/linux/build_bug.h:77:34: note: in expansion of macro '__static_assert'
>    77 | #define static_assert(expr, ...) __static_assert(expr,
> ##__VA_ARGS__, #expr)
>       |                                  ^~~~~~~~~~~~~~~
> include/linux/minmax.h:66:17: note: in expansion of macro 'static_assert'
>    66 |
> static_assert(__builtin_choose_expr(__is_constexpr((lo) > (hi)),
>  \
>       |                 ^~~~~~~~~~~~~
> include/linux/minmax.h:76:17: note: in expansion of macro '__clamp_once'
>    76 |                 __clamp_once(val, lo, hi, __UNIQUE_ID(__val),
>          \
>       |                 ^~~~~~~~~~~~
> include/linux/minmax.h:180:36: note: in expansion of macro '__careful_clamp'
>   180 | #define clamp_t(type, val, lo, hi)
> __careful_clamp((type)(val), (type)(lo), (type)(hi))
>       |                                    ^~~~~~~~~~~~~~~
> drivers/net/wireless/ralink/rt2x00/rt2800lib.c:3993:24: note: in
> expansion of macro 'clamp_t'
>  3993 |                 return clamp_t(char, txpower, MIN_A_TXPOWER,
> MAX_A_TXPOWER);
>       |                        ^~~~~~~
> 

Thanks, I've added a commit that should resolve this now.  I'll push out
a -rc2 in a bit.

greg k-h