netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: jmaloy@redhat.com, netdev@vger.kernel.org, davem@davemloft.net
Cc: kbuild-all@lists.01.org, tipc-discussion@lists.sourceforge.net,
	tung.q.nguyen@dektech.com.au, hoang.h.le@dektech.com.au,
	tuong.t.lien@dektech.com.au, jmaloy@redhat.com,
	maloy@donjonn.com, xinl@redhat.com, ying.xue@windriver.com
Subject: Re: [net-next 2/3] tipc: make node number calculation reproducible
Date: Wed, 25 Nov 2020 11:40:06 +0800	[thread overview]
Message-ID: <202011251135.PgGAOmIF-lkp@intel.com> (raw)
In-Reply-To: <20201124172834.317966-3-jmaloy@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2504 bytes --]

Hi,

I love your patch! Perhaps something to improve:

[auto build test WARNING on net-next/master]

url:    https://github.com/0day-ci/linux/commits/jmaloy-redhat-com/tipc-some-minor-improvements/20201125-013225
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git d5a05e69ac6e4c431c380ced2b534c91f7bc3280
config: i386-randconfig-s002-20201125 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.3-151-g540c2c4b-dirty
        # https://github.com/0day-ci/linux/commit/417ce7b0ea8ed268ee0302eb02ee6eaa55f22f9b
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review jmaloy-redhat-com/tipc-some-minor-improvements/20201125-013225
        git checkout 417ce7b0ea8ed268ee0302eb02ee6eaa55f22f9b
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


"sparse warnings: (new ones prefixed by >>)"
   net/tipc/addr.c: note: in included file (through net/tipc/addr.h):
>> net/tipc/core.h:218:15: sparse: sparse: cast to restricted __be32
>> net/tipc/core.h:218:15: sparse: sparse: cast to restricted __be32
>> net/tipc/core.h:218:15: sparse: sparse: cast to restricted __be32
>> net/tipc/core.h:218:15: sparse: sparse: cast to restricted __be32
>> net/tipc/core.h:218:15: sparse: sparse: cast to restricted __be32
>> net/tipc/core.h:218:15: sparse: sparse: cast to restricted __be32
   net/tipc/core.h:222:27: sparse: sparse: cast to restricted __be32
   net/tipc/core.h:222:27: sparse: sparse: cast to restricted __be32
   net/tipc/core.h:222:27: sparse: sparse: cast to restricted __be32
   net/tipc/core.h:222:27: sparse: sparse: cast to restricted __be32
   net/tipc/core.h:222:27: sparse: sparse: cast to restricted __be32
   net/tipc/core.h:222:27: sparse: sparse: cast to restricted __be32

vim +218 net/tipc/core.h

   213	
   214	static inline u32 hash128to32(char *bytes)
   215	{
   216		u32 res, *tmp = (u32 *)bytes;
   217	
 > 218		res = ntohl(tmp[0] ^ tmp[1] ^ tmp[2] ^ tmp[3]);
   219		if (likely(res))
   220			return res;
   221		res = tmp[0] | tmp[1] | tmp[2] | tmp[3];
   222		return !res ? 0 : ntohl(18140715);
   223	}
   224	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40418 bytes --]

  parent reply	other threads:[~2020-11-25  3:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-24 17:28 [net-next 0/3] tipc: some minor improvements jmaloy
2020-11-24 17:28 ` [net-next 1/3] tipc: refactor tipc_sk_bind() function jmaloy
2020-11-24 17:28 ` [net-next 2/3] tipc: make node number calculation reproducible jmaloy
2020-11-25  0:22   ` Jakub Kicinski
2020-11-25  3:40   ` kernel test robot [this message]
2020-11-24 17:28 ` [net-next 3/3] tipc: update address terminology in code jmaloy

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=202011251135.PgGAOmIF-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=hoang.h.le@dektech.com.au \
    --cc=jmaloy@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=maloy@donjonn.com \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tung.q.nguyen@dektech.com.au \
    --cc=tuong.t.lien@dektech.com.au \
    --cc=xinl@redhat.com \
    --cc=ying.xue@windriver.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;
as well as URLs for NNTP newsgroup(s).