linux-kernel - Re: linux-next: Tree for Jul 4 (kernel/bpf/stream.c)

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: <d5136da0-51f9-4359-a283-9075b4992bfb@infradead.org>
Date: Fri, 4 Jul 2025 21:52:58 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Kumar Kartikeya Dwivedi <memxor@...il.com>, bot@...nelci.org,
 kernelci@...ts.linux.dev
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
 Linux Next Mailing List <linux-next@...r.kernel.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, bpf@...r.kernel.org
Subject: Re: linux-next: Tree for Jul 4 (kernel/bpf/stream.c)



On 7/4/25 9:44 PM, Kumar Kartikeya Dwivedi wrote:
> On Sat, 5 Jul 2025 at 01:38, Randy Dunlap <rdunlap@...radead.org> wrote:
>>
>>
>>
>> On 7/4/25 4:35 PM, Randy Dunlap wrote:
>>>
>>>
>>> On 7/4/25 3:51 AM, Stephen Rothwell wrote:
>>>> Hi all,
>>>>
>>>> Changes since 20250703:
>>>>
>>>
>>> on i386:
>>>
>>> kernel/bpf/stream.c: In function 'dump_stack_cb':
>>> kernel/bpf/stream.c:501:53: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>>>   501 |                                                     (void *)ip, line, file, num);
>>>       |                                                     ^
>>> ../kernel/bpf/stream.c:505:64: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>>>   505 |         ctxp->err = bpf_stream_stage_printk(ctxp->ss, "%pS\n", (void *)ip);
>>>       |
>>>
>>>
>>
>> Also reported (earlier) here:
>>
>>   https://lore.kernel.org/linux-next/CACo-S-16Ry4Gn33k4zygRKwjE116h1t--DSqJpQfodeVb0ssGA@mail.gmail.com/T/#u
>>
> 
> Thanks, I will share a fix soon. Could the bot also Cc the author of
> the commit using git blame?

I added the email address for the bot. We'll see if it can read email.

-- 
~Randy