From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
hagar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 5.4 000/461] 5.4.285-rc2 review
Date: Fri, 8 Nov 2024 08:50:49 +0100 [thread overview]
Message-ID: <2024110817-ozone-tanning-0df8@gregkh> (raw)
In-Reply-To: <05671820-dee5-4b31-b585-5e1f034e65f6@gmail.com>
On Thu, Nov 07, 2024 at 08:39:39AM -0800, Florian Fainelli wrote:
>
>
> On 11/6/2024 10:47 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.4.285 release.
> > There are 461 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, 09 Nov 2024 06:32:59 +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.4.285-rc2.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.4.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> On ARCH_BRCMSTB using 32-bit and 64-bit ARM kernels, build tested on
> BMIPS_GENERIC:
>
> Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
>
> There are however new build warnings, on 32-bit:
>
> In file included from ./include/linux/mm.h:29,
> from ./include/linux/pagemap.h:8,
> from ./include/linux/buffer_head.h:14,
> from fs/udf/udfdecl.h:12,
> from fs/udf/inode.c:32:
> fs/udf/inode.c: In function 'udf_current_aext':
> ./include/linux/overflow.h:61:22: warning: comparison of distinct pointer
> types lacks a cast
> 61 | (void) (&__a == __d); \
> | ^~
> fs/udf/inode.c:2202:21: note: in expansion of macro 'check_add_overflow'
> 2202 | if (check_add_overflow(sizeof(struct allocExtDesc),
> | ^~~~~~~~~~~~~~~~~~
>
>
> On 64-bit:
>
> fs/udf/inode.c: In function 'udf_current_aext':
> ./include/linux/overflow.h:60:15: warning: comparison of distinct pointer
> types lacks a cast
> (void) (&__a == &__b); \
> ^~
> fs/udf/inode.c:2202:7: note: in expansion of macro 'check_add_overflow'
> if (check_add_overflow(sizeof(struct allocExtDesc),
> ^~~~~~~~~~~~~~~~~~
> ./include/linux/overflow.h:61:15: warning: comparison of distinct pointer
> types lacks a cast
> (void) (&__a == __d); \
> ^~
> fs/udf/inode.c:2202:7: note: in expansion of macro 'check_add_overflow'
> if (check_add_overflow(sizeof(struct allocExtDesc),
> ^~~~~~~~~~~~~~~~~~
>
> In file included from ./include/linux/mm.h:29,
> from ./include/linux/pagemap.h:8,
> from ./include/linux/buffer_head.h:14,
> from fs/udf/udfdecl.h:12,
> from fs/udf/super.c:41:
> fs/udf/super.c: In function 'udf_fill_partdesc_info':
> ./include/linux/overflow.h:60:15: warning: comparison of distinct pointer
> types lacks a cast
> (void) (&__a == &__b); \
> ^~
> fs/udf/super.c:1162:7: note: in expansion of macro 'check_add_overflow'
> if (check_add_overflow(map->s_partition_len,
> ^~~~~~~~~~~~~~~~~~
Yes, this is due to commit d219d2a9a92e ("overflow: Allow mixed type
arguments") not being backported to 5.4 and 5.10.y trees. If people
want to see these warnings removed, perhaps someone can provide a
working backport of this commit :)
thanks,
greg k-h
next prev parent reply other threads:[~2024-11-08 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 6:47 [PATCH 5.4 000/461] 5.4.285-rc2 review Greg Kroah-Hartman
2024-11-07 13:42 ` Jon Hunter
2024-11-07 16:39 ` Florian Fainelli
2024-11-08 7:50 ` Greg Kroah-Hartman [this message]
2024-11-08 14:55 ` Muhammad Usama Anjum
2024-11-09 1:27 ` Naresh Kamboju
2024-11-09 16:02 ` Harshit Mogalapalli
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=2024110817-ozone-tanning-0df8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hagar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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