All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH net-next] openvswitch: Introduce per-cpu upcall dispatch
Date: Thu, 01 Jul 2021 00:29:03 +0800	[thread overview]
Message-ID: <202107010029.GOx2Kvsm-lkp@intel.com> (raw)
In-Reply-To: <20210630095350.817785-1-mark.d.gray@redhat.com>

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

Hi Mark,

Thank you for the patch! Perhaps something to improve:

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

url:    https://github.com/0day-ci/linux/commits/Mark-Gray/openvswitch-Introduce-per-cpu-upcall-dispatch/20210630-175435
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git b6df00789e2831fff7a2c65aa7164b2a4dcbe599
config: sh-randconfig-s032-20210630 (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.3-341-g8af24329-dirty
        # https://github.com/0day-ci/linux/commit/24234cf5ef3fdbb1cad04189ba6459292f84180e
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Mark-Gray/openvswitch-Introduce-per-cpu-upcall-dispatch/20210630-175435
        git checkout 24234cf5ef3fdbb1cad04189ba6459292f84180e
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=sh 

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/openvswitch/datapath.c:169:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void const * @@     got struct dp_nlsk_pids [noderef] __rcu *upcall_portids @@
   net/openvswitch/datapath.c:169:17: sparse:     expected void const *
   net/openvswitch/datapath.c:169:17: sparse:     got struct dp_nlsk_pids [noderef] __rcu *upcall_portids

vim +169 net/openvswitch/datapath.c

   160	
   161	static void destroy_dp_rcu(struct rcu_head *rcu)
   162	{
   163		struct datapath *dp = container_of(rcu, struct datapath, rcu);
   164	
   165		ovs_flow_tbl_destroy(&dp->table);
   166		free_percpu(dp->stats_percpu);
   167		kfree(dp->ports);
   168		ovs_meters_exit(dp);
 > 169		kfree(dp->upcall_portids);
   170		kfree(dp);
   171	}
   172	

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

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

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Mark Gray <mark.d.gray@redhat.com>,
	dev@openvswitch.org, netdev@vger.kernel.org
Cc: kbuild-all@lists.01.org, fbl@sysclose.org,
	dan.carpenter@oracle.com, pravin.ovn@gmail.com,
	Mark Gray <mark.d.gray@redhat.com>
Subject: Re: [PATCH net-next] openvswitch: Introduce per-cpu upcall dispatch
Date: Thu, 1 Jul 2021 00:29:03 +0800	[thread overview]
Message-ID: <202107010029.GOx2Kvsm-lkp@intel.com> (raw)
In-Reply-To: <20210630095350.817785-1-mark.d.gray@redhat.com>

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

Hi Mark,

Thank you for the patch! Perhaps something to improve:

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

url:    https://github.com/0day-ci/linux/commits/Mark-Gray/openvswitch-Introduce-per-cpu-upcall-dispatch/20210630-175435
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git b6df00789e2831fff7a2c65aa7164b2a4dcbe599
config: sh-randconfig-s032-20210630 (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.3-341-g8af24329-dirty
        # https://github.com/0day-ci/linux/commit/24234cf5ef3fdbb1cad04189ba6459292f84180e
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Mark-Gray/openvswitch-Introduce-per-cpu-upcall-dispatch/20210630-175435
        git checkout 24234cf5ef3fdbb1cad04189ba6459292f84180e
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=sh 

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/openvswitch/datapath.c:169:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void const * @@     got struct dp_nlsk_pids [noderef] __rcu *upcall_portids @@
   net/openvswitch/datapath.c:169:17: sparse:     expected void const *
   net/openvswitch/datapath.c:169:17: sparse:     got struct dp_nlsk_pids [noderef] __rcu *upcall_portids

vim +169 net/openvswitch/datapath.c

   160	
   161	static void destroy_dp_rcu(struct rcu_head *rcu)
   162	{
   163		struct datapath *dp = container_of(rcu, struct datapath, rcu);
   164	
   165		ovs_flow_tbl_destroy(&dp->table);
   166		free_percpu(dp->stats_percpu);
   167		kfree(dp->ports);
   168		ovs_meters_exit(dp);
 > 169		kfree(dp->upcall_portids);
   170		kfree(dp);
   171	}
   172	

---
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: 22072 bytes --]

  reply	other threads:[~2021-06-30 16:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  9:53 [PATCH net-next] openvswitch: Introduce per-cpu upcall dispatch Mark Gray
2021-06-30 16:29 ` kernel test robot [this message]
2021-06-30 16:29   ` kernel test robot
2021-07-01 20:59 ` Flavio Leitner
2021-07-05 23:54 ` Flavio Leitner
2021-07-08 14:40 ` Flavio Leitner
2021-07-12 18:07   ` [ovs-dev] " Flavio Leitner
2021-07-15  4:45 ` Pravin Shelar
2021-07-15 11:55   ` Mark Gray

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=202107010029.GOx2Kvsm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.