netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: kbuild-all@lists.01.org, netfilter-devel@vger.kernel.org,
	davem@davemloft.net, netdev@vger.kernel.org,
	jakub.kicinski@netronome.com, jiri@resnulli.us,
	saeedm@mellanox.com, vishal@chelsio.com, vladbu@mellanox.com,
	ecree@solarflare.com
Subject: Re: [PATCH net-next,v5 3/4] net: flow_offload: mangle action at byte level
Date: Tue, 15 Oct 2019 16:48:47 +0800	[thread overview]
Message-ID: <201910151628.aXIOUKNY%lkp@intel.com> (raw)
In-Reply-To: <20191014221051.8084-4-pablo@netfilter.org>

Hi Pablo,

I love your patch! Perhaps something to improve:

[auto build test WARNING on net-next/master]
[cannot apply to v5.4-rc3 next-20191014]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Pablo-Neira-Ayuso/flow_offload-update-mangle-action-representation/20191015-061232
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.1-rc1-43-g0ccb3b4-dirty
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

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


sparse warnings: (new ones prefixed by >>)

   net/sched/cls_api.c:200:22: sparse: sparse: incorrect type in assignment (different base types) @@    expected restricted __be16 [usertype] protocol @@    got icted __be16 [usertype] protocol @@
   net/sched/cls_api.c:200:22: sparse:    expected restricted __be16 [usertype] protocol
   net/sched/cls_api.c:200:22: sparse:    got unsigned int [usertype] protocol
   net/sched/cls_api.c:1587:16: sparse: sparse: incompatible types in comparison expression (different address spaces):
   net/sched/cls_api.c:1587:16: sparse:    struct tcf_proto *
   net/sched/cls_api.c:1587:16: sparse:    struct tcf_proto [noderef] <asn:4> *
   net/sched/cls_api.c:1680:20: sparse: sparse: incompatible types in comparison expression (different address spaces):
   net/sched/cls_api.c:1680:20: sparse:    struct tcf_proto [noderef] <asn:4> *
   net/sched/cls_api.c:1680:20: sparse:    struct tcf_proto *
   net/sched/cls_api.c:1643:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
   net/sched/cls_api.c:1643:25: sparse:    struct tcf_proto [noderef] <asn:4> *
   net/sched/cls_api.c:1643:25: sparse:    struct tcf_proto *
   net/sched/cls_api.c:1662:16: sparse: sparse: incompatible types in comparison expression (different address spaces):
   net/sched/cls_api.c:1662:16: sparse:    struct tcf_proto *
   net/sched/cls_api.c:1662:16: sparse:    struct tcf_proto [noderef] <asn:4> *
   net/sched/cls_api.c:1727:25: sparse: sparse: restricted __be16 degrades to integer
   net/sched/cls_api.c:2372:50: sparse: sparse: restricted __be16 degrades to integer
>> net/sched/cls_api.c:3396:27: sparse: sparse: symbol 'tc_proto_udp_hdr' was not declared. Should it be static?
>> net/sched/cls_api.c:3499:27: sparse: sparse: cast to restricted __be32
>> net/sched/cls_api.c:3499:27: sparse: sparse: cast to restricted __be32
>> net/sched/cls_api.c:3499:27: sparse: sparse: cast to restricted __be32
>> net/sched/cls_api.c:3499:27: sparse: sparse: cast to restricted __be32
>> net/sched/cls_api.c:3499:27: sparse: sparse: cast to restricted __be32
>> net/sched/cls_api.c:3499:27: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3533:33: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3533:33: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3533:33: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3533:33: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3533:33: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3533:33: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3543:25: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3543:25: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3543:25: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3543:25: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3543:25: sparse: sparse: cast to restricted __be32
   net/sched/cls_api.c:3543:25: sparse: sparse: cast to restricted __be32

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

  reply	other threads:[~2019-10-15  8:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 22:10 [PATCH net-next,v5 0/4] flow_offload: update mangle action representation Pablo Neira Ayuso
2019-10-14 22:10 ` [PATCH net-next,v5 1/4] net: flow_offload: flip mangle action mask Pablo Neira Ayuso
2019-10-15  6:05   ` Jiri Pirko
2019-10-14 22:10 ` [PATCH net-next,v5 2/4] net: flow_offload: bitwise AND on mangle action value field Pablo Neira Ayuso
2019-10-15  6:12   ` Jiri Pirko
2019-10-14 22:10 ` [PATCH net-next,v5 3/4] net: flow_offload: mangle action at byte level Pablo Neira Ayuso
2019-10-15  8:48   ` kbuild test robot [this message]
2019-10-15  8:48   ` [RFC PATCH] net: flow_offload: tc_proto_udp_hdr[] can be static kbuild test robot
2019-10-16 23:36   ` [PATCH net-next,v5 3/4] net: flow_offload: mangle action at byte level Jakub Kicinski
2019-10-17 16:11     ` Pablo Neira Ayuso
2019-10-17 16:22       ` Pablo Neira Ayuso
2019-10-17 17:59         ` Edward Cree
2019-10-17 18:02           ` David Miller
2019-10-17 17:30       ` Jakub Kicinski
2019-10-17 17:46         ` Pablo Neira Ayuso
2019-10-17 18:01           ` Edward Cree
2019-10-17 18:03             ` David Miller
2019-10-14 22:10 ` [PATCH net-next,v5 4/4] netfilter: nft_payload: packet mangling offload support Pablo Neira Ayuso

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=201910151628.aXIOUKNY%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=ecree@solarflare.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=jiri@resnulli.us \
    --cc=kbuild-all@lists.01.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=saeedm@mellanox.com \
    --cc=vishal@chelsio.com \
    --cc=vladbu@mellanox.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).