From: Simon Horman <horms@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v2 0/2] Fix implicit sign conversions in handshake upcall
Date: Thu, 21 Sep 2023 22:56:27 +0100 [thread overview]
Message-ID: <20230921215627.GT224399@kernel.org> (raw)
In-Reply-To: <169530154802.8905.2645661840284268222.stgit@oracle-102.nfsv4bat.org>
On Thu, Sep 21, 2023 at 09:07:14AM -0400, Chuck Lever wrote:
> An internal static analysis tool noticed some implicit sign
> conversions for some of the arguments in the handshake upcall
> protocol.
>
> ---
...
For series,
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2023-09-21 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 13:07 [PATCH v2 0/2] Fix implicit sign conversions in handshake upcall Chuck Lever
2023-09-21 13:07 ` [PATCH v2 1/2] handshake: Fix sign of socket file descriptor fields Chuck Lever
2023-09-21 13:08 ` [PATCH v2 2/2] handshake: Fix sign of key_serial_t fields Chuck Lever
2023-09-21 21:56 ` Simon Horman [this message]
2023-10-02 19:40 ` [PATCH v2 0/2] Fix implicit sign conversions in handshake upcall patchwork-bot+netdevbpf
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=20230921215627.GT224399@kernel.org \
--to=horms@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.