mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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,
	hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 5.10 000/270] 5.10.238-rc1 review
Date: Wed, 4 Jun 2025 11:29:47 -0700	[thread overview]
Message-ID: <630fc4c2-dacb-45c8-9cca-0b843365b212@gmail.com> (raw)
In-Reply-To: <2025060412-cursor-navigate-126d@gregkh>

On 6/4/25 01:06, Greg Kroah-Hartman wrote:
> On Tue, Jun 03, 2025 at 09:00:58AM -0700, Florian Fainelli wrote:
>> On 6/3/25 00:58, Greg Kroah-Hartman wrote:
>>> On Mon, Jun 02, 2025 at 09:50:24AM -0700, Florian Fainelli wrote:
>>>> On 6/2/25 09:49, Florian Fainelli wrote:
>>>>> On 6/2/25 06:44, Greg Kroah-Hartman wrote:
>>>>>> This is the start of the stable review cycle for the 5.10.238 release.
>>>>>> There are 270 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, 04 Jun 2025 13:42:20 +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.10.238-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.10.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>
>>>>>
>>>>> Similar build warning as reported for 5.4, due to the same commit:
>>>>>
>>>>> commit b47e6abc7dc5772ecb45383d9956f9fcb7fdf33c
>>>>> Author: Jeongjun Park <aha310510@gmail.com>
>>>>> Date:   Tue Apr 22 20:30:25 2025 +0900
>>>>>
>>>>>        tracing: Fix oob write in trace_seq_to_buffer()
>>>>>
>>>>>        commit f5178c41bb43444a6008150fe6094497135d07cb upstream.
>>>>>
>>>>> In file included from ./include/linux/kernel.h:15,
>>>>>                     from ./include/asm-generic/bug.h:20,
>>>>>                     from ./arch/arm/include/asm/bug.h:60,
>>>>>                     from ./include/linux/bug.h:5,
>>>>>                     from ./include/linux/mmdebug.h:5,
>>>>>                     from ./include/linux/mm.h:9,
>>>>>                     from ./include/linux/ring_buffer.h:5,
>>>>>                     from kernel/trace/trace.c:15:
>>>>> kernel/trace/trace.c: In function 'tracing_splice_read_pipe':
>>>>> ./include/linux/minmax.h:20:35: warning: comparison of distinct pointer
>>>>> types lacks a cast
>>>>>       20 |         (!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
>>>>>          |                                   ^~
>>>>> ./include/linux/minmax.h:26:18: note: in expansion of macro '__typecheck'
>>>>>       26 |                 (__typecheck(x, y) && __no_side_effects(x, y))
>>>>>          |                  ^~~~~~~~~~~
>>>>> ./include/linux/minmax.h:36:31: note: in expansion of macro '__safe_cmp'
>>>>>       36 |         __builtin_choose_expr(__safe_cmp(x, y), \
>>>>>          |                               ^~~~~~~~~~
>>>>> ./include/linux/minmax.h:45:25: note: in expansion of macro '__careful_cmp'
>>>>>       45 | #define min(x, y)       __careful_cmp(x, y, <)
>>>>>          |                         ^~~~~~~~~~~~~
>>>>> kernel/trace/trace.c:6688:43: note: in expansion of macro 'min'
>>>>>     6688 | min((size_t)trace_seq_used(&iter->seq),
>>>>>          |                                           ^~~
>>>>>
>>>>
>>>> And also this one:
>>>>
>>>> commit e0a3a33cecd3ce2fde1de4ff0e223dc1db484a8d
>>>> Author: Eric Dumazet <edumazet@google.com>
>>>> Date:   Wed Mar 5 13:05:50 2025 +0000
>>>>
>>>>       tcp: bring back NUMA dispersion in inet_ehash_locks_alloc()
>>>>
>>>>       [ Upstream commit f8ece40786c9342249aa0a1b55e148ee23b2a746 ]
>>>>
>>>>
>>>> on ARM64:
>>>>
>>>> In file included from ./include/linux/kernel.h:15,
>>>>                    from ./include/linux/list.h:9,
>>>>                    from ./include/linux/module.h:12,
>>>>                    from net/ipv4/inet_hashtables.c:12:
>>>> net/ipv4/inet_hashtables.c: In function 'inet_ehash_locks_alloc':
>>>> ./include/linux/minmax.h:20:35: warning: comparison of distinct pointer
>>>> types lacks a cast
>>>>      20 |         (!!(sizeof((typeof(x) *)1 == (typeof(y) *)1)))
>>>>         |                                   ^~
>>>> ./include/linux/minmax.h:26:18: note: in expansion of macro '__typecheck'
>>>>      26 |                 (__typecheck(x, y) && __no_side_effects(x, y))
>>>>         |                  ^~~~~~~~~~~
>>>> ./include/linux/minmax.h:36:31: note: in expansion of macro '__safe_cmp'
>>>>      36 |         __builtin_choose_expr(__safe_cmp(x, y), \
>>>>         |                               ^~~~~~~~~~
>>>> ./include/linux/minmax.h:52:25: note: in expansion of macro '__careful_cmp'
>>>>      52 | #define max(x, y)       __careful_cmp(x, y, >)
>>>>         |                         ^~~~~~~~~~~~~
>>>> net/ipv4/inet_hashtables.c:946:19: note: in expansion of macro 'max'
>>>>     946 |         nblocks = max(nblocks, num_online_nodes() * PAGE_SIZE /
>>>> locksz);
>>>>         |                   ^~~
>>>>
>>>
>>> For both of these, I'll just let them be as they are ok, it's just the
>>> mess of our min/max macro unwinding causes these issues.
>>>
>>> Unless they really bother someone, and in that case, a patch to add the
>>> correct type to the backport to make the noise go away would be greatly
>>> appreciated.
>>
>> Yeah that's a reasonable resolution, I will try to track down the missing
>> patches for minmax.h so we are warning free for the stable kernels.
> 
> I tried in the past, it's non-trivial.  What would be easier is to just
> properly cast the variables in the places where this warning is showing
> up to get rid of that warning.  We've done that in some backports in the
> past as well.
> 
> good luck!

I see now that in 5.4.295-rc1 you have backported:

commit 36d6c6cd65043d553126b934bf1fcb79dcb58499
Author: Pan Taixi <pantaixi@huaweicloud.com>
Date:   Mon May 26 09:37:31 2025 +0800

     tracing: Fix compilation warning on arm32

     commit 2fbdb6d8e03b70668c0876e635506540ae92ab05 upstream.


which takes care of resolving the warning, thanks!
-- 
Florian

  reply	other threads:[~2025-06-04 18:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02 13:44 Greg Kroah-Hartman
2025-06-02 13:47 ` [PATCH 5.10 151/270] arm64/mm: Check PUD_TYPE_TABLE in pud_bad() Greg Kroah-Hartman
2025-06-02 16:49 ` [PATCH 5.10 000/270] 5.10.238-rc1 review Florian Fainelli
2025-06-02 16:50   ` Florian Fainelli
2025-06-03  7:58     ` Greg Kroah-Hartman
2025-06-03 16:00       ` Florian Fainelli
2025-06-04  8:06         ` Greg Kroah-Hartman
2025-06-04 18:29           ` Florian Fainelli [this message]
2025-06-02 20:37 ` Pavel Machek
2025-06-03  5:48 ` Naresh Kamboju
2025-06-03  7:57   ` Greg Kroah-Hartman
2025-06-03  9:45 ` Mark Brown
2025-06-03 10:06   ` Greg Kroah-Hartman
2025-06-03 10:46     ` Mark Brown
2025-06-04  8:09       ` Greg Kroah-Hartman
2025-06-04  9:40 ` Jon Hunter

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=630fc4c2-dacb-45c8-9cca-0b843365b212@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@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

all inboxes | Powered by JetHome®