From: kbuild test robot <lkp@intel.com>
To: Atul Gupta <atul.gupta@chelsio.com>
Cc: kbuild-all@01.org, herbert@gondor.apana.org.au,
davem@davemloft.net, linux-crypto@vger.kernel.org,
netdev@vger.kernel.org, dt@chelsio.com, atul.gupta@chelsio.com
Subject: Re: [crypto 4/4] IPv6 changes for Inline TLS
Date: Fri, 12 Apr 2019 05:59:55 +0800 [thread overview]
Message-ID: <201904120528.DTQt9Vn4%lkp@intel.com> (raw)
In-Reply-To: <20190409152540.11729-1-atul.gupta@chelsio.com>
[-- Attachment #1: Type: text/plain, Size: 3137 bytes --]
Hi Atul,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on crypto/master]
url: https://github.com/0day-ci/linux/commits/Atul-Gupta/Inline-TLS-client-and-v6-support/20190412-034407
base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git master
config: mips-allmodconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=mips
All warnings (new ones prefixed by >>):
In file included from drivers/crypto/chelsio/chtls/chtls_main.c:19:0:
>> include/net/transp_v6.h:52:33: warning: 'struct ipcm6_cookie' declared inside parameter list will not be visible outside of this definition or declaration
struct flowi6 *fl6, struct ipcm6_cookie *ipc6);
^~~~~~~~~~~~
--
drivers/crypto/chelsio/chtls/chtls_cm.c: In function 'chtls_pass_accept_request':
>> drivers/crypto/chelsio/chtls/chtls_cm.c:2272:8: warning: 'eh' may be used uninitialized in this function [-Wmaybe-uninitialized]
ip6h = (struct ipv6hdr *)(eh + 1);
~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/crypto/chelsio/chtls/chtls_cm.c: In function 'chtls_v6_connect':
>> drivers/crypto/chelsio/chtls/chtls_cm.c:1552:12: warning: 'saddr' may be used uninitialized in this function [-Wmaybe-uninitialized]
fl6.saddr = saddr ? *saddr : np->saddr;
~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +52 include/net/transp_v6.h
f145b67f2 Joe Perches 2013-06-02 42
4b261c75a Hannes Frederic Sowa 2014-01-20 43 /* this does all the common and the specific ctl work */
4b261c75a Hannes Frederic Sowa 2014-01-20 44 void ip6_datagram_recv_ctl(struct sock *sk, struct msghdr *msg,
4b261c75a Hannes Frederic Sowa 2014-01-20 45 struct sk_buff *skb);
4b261c75a Hannes Frederic Sowa 2014-01-20 46 void ip6_datagram_recv_common_ctl(struct sock *sk, struct msghdr *msg,
4b261c75a Hannes Frederic Sowa 2014-01-20 47 struct sk_buff *skb);
4b261c75a Hannes Frederic Sowa 2014-01-20 48 void ip6_datagram_recv_specific_ctl(struct sock *sk, struct msghdr *msg,
^1da177e4 Linus Torvalds 2005-04-16 49 struct sk_buff *skb);
^1da177e4 Linus Torvalds 2005-04-16 50
f145b67f2 Joe Perches 2013-06-02 51 int ip6_datagram_send_ctl(struct net *net, struct sock *sk, struct msghdr *msg,
5fdaa88df Willem de Bruijn 2018-07-06 @52 struct flowi6 *fl6, struct ipcm6_cookie *ipc6);
^1da177e4 Linus Torvalds 2005-04-16 53
:::::: The code at line 52 was first introduced by commit
:::::: 5fdaa88dfefa87ee1ea92750e99950dca182ea41 ipv6: fold sockcm_cookie into ipcm6_cookie
:::::: TO: Willem de Bruijn <willemb@google.com>
:::::: CC: David S. Miller <davem@davemloft.net>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 58380 bytes --]
next prev parent reply other threads:[~2019-04-11 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 15:25 [crypto 4/4] IPv6 changes for Inline TLS Atul Gupta
2019-04-11 21:59 ` kbuild test robot [this message]
2019-04-11 23:00 ` Willem de Bruijn
2019-04-12 5:25 ` [RFC PATCH] chtls_rsk_opsv6 can be static kbuild test robot
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=201904120528.DTQt9Vn4%lkp@intel.com \
--to=lkp@intel.com \
--cc=atul.gupta@chelsio.com \
--cc=davem@davemloft.net \
--cc=dt@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@01.org \
--cc=linux-crypto@vger.kernel.org \
--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 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 NNTP newsgroup(s).