netdev - Re: [PATCH v1 0/2] Fix implicit sign conversions in handshake upcall

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] [day] [month] [year] [list]

Message-ID: <E8AA8416-0914-494D-B463-D3F8AE5F087E@oracle.com>
Date: Thu, 21 Sep 2023 13:02:07 +0000
From: Chuck Lever III <chuck.lever@...cle.com>
To: Paolo Abeni <pabeni@...hat.com>
CC: Chuck Lever <cel@...nel.org>,
        "open list:NETWORKING [GENERAL]"
	<netdev@...r.kernel.org>,
        "kernel-tls-handshake@...ts.linux.dev"
	<kernel-tls-handshake@...ts.linux.dev>
Subject: Re: [PATCH v1 0/2] Fix implicit sign conversions in handshake upcall



> On Sep 21, 2023, at 4:59 AM, Paolo Abeni <pabeni@...hat.com> wrote:
> 
> Hi,
> 
> On Tue, 2023-09-19 at 15:49 -0400, Chuck Lever wrote:
>> An internal static analysis tool noticed some implicit sign
>> conversions for some of the arguments in the handshake upcall
>> protocol.
> 
> This does not apply cleanly to -net nor to -net-next, and the lack of
> the target inside the subj is confusing. I guess this is for your devel
> tree???

Series as submitted was based on v6.5 because I wasn't expecting
conflicts. I will rebase on net-next and resubmit.


--
Chuck Lever