From: Fengguang Wu <lkp@intel.com>
To: David Miller <davem@davemloft.net>
Cc: decui@microsoft.com, mkubecek@suse.cz, olaf@aepfle.de,
gregkh@linuxfoundation.org, jasowang@redhat.com,
dave.scott@docker.com, linux-kernel@vger.kernel.org,
joe@perches.com, rolf.neugebauer@docker.com, kbuild-all@01.org,
netdev@vger.kernel.org, apw@canonical.com,
devel@linuxdriverproject.org, vkuznets@redhat.com,
kys@microsoft.com, cavery@redhat.com, haiyangz@microsoft.com
Subject: Re: [kbuild-all] [PATCH v17 net-next 1/1] hv_sock: introduce Hyper-V Sockets
Date: Wed, 20 Jul 2016 11:06:19 +0800 [thread overview]
Message-ID: <20160720030619.GA26466@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20160719.195253.2126109938824378508.davem@davemloft.net>
On Tue, Jul 19, 2016 at 07:52:53PM -0700, David Miller wrote:
>From: Dexuan Cui <decui@microsoft.com>
>Date: Wed, 20 Jul 2016 01:48:18 +0000
>
>>> From: kbuild test robot [mailto:lkp@intel.com]
>>> Sent: Wednesday, July 20, 2016 1:10
>>>
>>> Hi,
>>>
>>> [auto build test WARNING on net-next/master]
>>>
>>> url: https://github.com/0day-ci/linux/commits/Dexuan-Cui/introduce-
>>> Hyper-V-VM-Sockets-hv_sock/20160715-223433
>>> config: x86_64-randconfig-a0-07191719 (attached as .config)
>>> compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
>>> reproduce:
>>> # save the attached .config to linux build tree
>>> make ARCH=x86_64
>>>
>>> All warnings (new ones prefixed by >>):
>>>
>>> net/hv_sock/af_hvsock.c: In function 'hvsock_open_connection':
>>> net/hv_sock/af_hvsock.c:693: warning: 'hvsk' may be used uninitialized in
>>> this function
>>> net/hv_sock/af_hvsock.c:693: warning: 'new_hvsk' may be used
>>> uninitialized in this function
>>> net/hv_sock/af_hvsock.c:697: warning: 'new_sk' may be used uninitialized
>>> in this function
>>> net/hv_sock/af_hvsock.c: In function 'hvsock_sendmsg_wait':
>>> net/hv_sock/af_hvsock.c:1053: warning: 'ret' may be used uninitialized in
>>> this function
>>> >> net/hv_sock/af_hvsock.o: warning: objtool: hvsock_on_channel_cb()+0x1d:
>>> function has unreachable instruction
>>
>> These warnings are all false alarms.
>
>But you still have to quiet them.
Agreed.
However the last warning
objtool: hvsock_on_channel_cb()+0x1d: function has unreachable instruction
is my fault -- it turns out to be a problem with old gcc-4.4 and
gcc-4.6 which we enabled 2 days ago. I just disabled reporting this
odd warning because it complaints on ~10000 functions all over the
place, which can only be sanely fixed in the toolchain.
Thanks,
Fengguang
next prev parent reply other threads:[~2016-07-20 3:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 14:32 Dexuan Cui
2016-07-19 17:10 ` kbuild test robot
2016-07-20 1:48 ` Dexuan Cui
2016-07-20 1:52 ` [kbuild-all] " Fengguang Wu
2016-07-20 2:52 ` David Miller
2016-07-20 3:06 ` Fengguang Wu [this message]
2016-07-20 4:05 ` Dexuan Cui
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=20160720030619.GA26466@wfg-t540p.sh.intel.com \
--to=lkp@intel.com \
--cc=apw@canonical.com \
--cc=cavery@redhat.com \
--cc=dave.scott@docker.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=joe@perches.com \
--cc=kbuild-all@01.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=rolf.neugebauer@docker.com \
--cc=vkuznets@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
all inboxes | Powered by JetHome®