From: Chuck Lever III <chuck.lever@oracle.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Chuck Lever <cel@kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
"kernel-tls-handshake@lists.linux.dev"
<kernel-tls-handshake@lists.linux.dev>
Subject: Re: [PATCH v1 0/2] Fix implicit sign conversions in handshake upcall
Date: Thu, 21 Sep 2023 13:02:07 +0000 [thread overview]
Message-ID: <E8AA8416-0914-494D-B463-D3F8AE5F087E@oracle.com> (raw)
In-Reply-To: <b5db3535a15b7e1bf89724d934fb880d292913cd.camel@redhat.com>
> On Sep 21, 2023, at 4:59 AM, Paolo Abeni <pabeni@redhat.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
prev parent reply other threads:[~2023-09-21 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 19:49 [PATCH v1 0/2] Fix implicit sign conversions in handshake upcall Chuck Lever
2023-09-19 19:49 ` [PATCH v1 1/2] handshake: Fix sign of socket file descriptor fields Chuck Lever
2023-09-19 19:50 ` [PATCH v1 2/2] handshake: Fix sign of key_serial_t fields Chuck Lever
2023-09-21 8:59 ` [PATCH v1 0/2] Fix implicit sign conversions in handshake upcall Paolo Abeni
2023-09-21 13:02 ` Chuck Lever III [this message]
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=E8AA8416-0914-494D-B463-D3F8AE5F087E@oracle.com \
--to=chuck.lever@oracle.com \
--cc=cel@kernel.org \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).