[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220124103932.5d22fad2@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Mon, 24 Jan 2022 10:39:32 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Leonard Crestez <cdleonard@...il.com>
Cc: David Ahern <dsahern@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
Philip Paeps <philip@...uble.is>,
Dmitry Safonov <0x7f454c46@...il.com>,
Shuah Khan <shuah@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Herbert Xu <herbert@...dor.apana.org.au>,
Kuniyuki Iwashima <kuniyu@...zon.co.jp>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Yuchung Cheng <ycheng@...gle.com>,
Francesco Ruggeri <fruggeri@...sta.com>,
Mat Martineau <mathew.j.martineau@...ux.intel.com>,
Christoph Paasch <cpaasch@...le.com>,
Ivan Delalande <colona@...sta.com>,
Priyaranjan Jha <priyarjha@...gle.com>, netdev@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 00/20] tcp: Initial support for RFC5925 auth option
On Mon, 24 Jan 2022 14:12:46 +0200 Leonard Crestez wrote:
> This is similar to TCP-MD5 in functionality but it's sufficiently
> different that packet formats and interfaces are incompatible.
> Compared to TCP-MD5 more algorithms are supported and multiple keys
> can be used on the same connection but there is still no negotiation
> mechanism.
>
> [...]
Could you make sure that each individual patch builds cleanly with W=1
C=1? There is a bunch of missing "static" and unused function warnings
in the first few patches. I presume they are made moot by later patches
but with kernel defaulting to Werror now it's a dangerous game to play,
we don't want to break bisection.
Also I spotted this:
include/net/tcp_authopt.h:59: warning: Function parameter or member 'prefixlen' not described in 'tcp_authopt_key_info'
Powered by blists - more mailing lists