linux-kernel - Re: [PATCH net-next 05/13] ipvlan: Fix compilation warning about _

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: <4e73c06e-fec9-4760-804a-eeca0d44943d@huawei.com>
Date: Thu, 20 Nov 2025 14:15:07 +0300
From: Dmitry Skorodumov <skorodumov.dmitry@...wei.com>
To: Jakub Kicinski <kuba@...nel.org>, Eric Dumazet <edumazet@...gle.com>
CC: <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<andrey.bokhanko@...wei.com>, Andrew Lunn <andrew+netdev@...n.ch>, "David S.
 Miller" <davem@...emloft.net>, Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next 05/13] ipvlan: Fix compilation warning about
 __be32 -> u32


On 19.11.2025 04:26, Jakub Kicinski wrote:
> On Tue, 18 Nov 2025 04:47:03 -0800 Eric Dumazet wrote:
>> On Tue, Nov 18, 2025 at 2:01 AM Dmitry Skorodumov
>> <skorodumov.dmitry@...wei.com> wrote:
>>> Fixed a compilation warning:
>>>
>>> ipvlan_core.c:56: warning: incorrect type in argument 1
>>> (different base types) expected unsigned int [usertype] a
>>> got restricted __be32 const [usertype] s_addr  
>> This is not a compilation warning, but a sparse related one ?
>>
>> This patch does not belong to this series, this is a bit distracting.
>>
>> Send a standalone patch targeting net tree, with an appropriate Fixes: tag
>>
>> Fixes: 2ad7bf363841 ("ipvlan: Initial check-in of the IPVLAN driver.")
> Not sure we should be sending Linus "fixes" for false positive sparse
> warnings at rc7/final..
>

Not sure how to proceed! Is it op if I send this path as "net-next"?