From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753151AbcGTDGa (ORCPT ); Tue, 19 Jul 2016 23:06:30 -0400 Received: from mga04.intel.com ([192.55.52.120]:1603 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751444AbcGTDG2 (ORCPT ); Tue, 19 Jul 2016 23:06:28 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,392,1464678000"; d="scan'208";a="736970336" Date: Wed, 20 Jul 2016 11:06:19 +0800 From: Fengguang Wu To: David Miller 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 Message-ID: <20160720030619.GA26466@wfg-t540p.sh.intel.com> References: <201607200149.0W6994tY%fengguang.wu@intel.com> <20160719.195253.2126109938824378508.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20160719.195253.2126109938824378508.davem@davemloft.net> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 19, 2016 at 07:52:53PM -0700, David Miller wrote: >From: Dexuan Cui >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