All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC mptcp-next v2 2/2] mptcp: add bpf_burst set/get params
Date: Sat, 26 Aug 2023 09:21:11 +0800	[thread overview]
Message-ID: <202308260938.lXj4ClGy-lkp@intel.com> (raw)
In-Reply-To: <486891cb494ba4e9eeb02b6e220ca670dbc80866.1692788531.git.geliang.tang@suse.com>

Hi Geliang,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on mptcp/export]
[cannot apply to mptcp/export-net linus/master v6.5-rc7 next-20230825]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Geliang-Tang/mptcp-add-set-get-params-wrappers/20230823-190626
base:   https://github.com/multipath-tcp/mptcp_net-next.git export
patch link:    https://lore.kernel.org/r/486891cb494ba4e9eeb02b6e220ca670dbc80866.1692788531.git.geliang.tang%40suse.com
patch subject: [RFC mptcp-next v2 2/2] mptcp: add bpf_burst set/get params
config: powerpc-randconfig-r131-20230823 (https://download.01.org/0day-ci/archive/20230826/202308260938.lXj4ClGy-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230826/202308260938.lXj4ClGy-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308260938.lXj4ClGy-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> net/mptcp/sched.c:212:39: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected char const * @@     got char [noderef] __rcu * @@
   net/mptcp/sched.c:212:39: sparse:     expected char const *
   net/mptcp/sched.c:212:39: sparse:     got char [noderef] __rcu *
>> net/mptcp/sched.c:215:70: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected struct bpf_map *map @@     got struct bpf_map [noderef] __rcu * @@
   net/mptcp/sched.c:215:70: sparse:     expected struct bpf_map *map
   net/mptcp/sched.c:215:70: sparse:     got struct bpf_map [noderef] __rcu *
   net/mptcp/sched.c:240:39: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected char const * @@     got char [noderef] __rcu * @@
   net/mptcp/sched.c:240:39: sparse:     expected char const *
   net/mptcp/sched.c:240:39: sparse:     got char [noderef] __rcu *
   net/mptcp/sched.c:243:70: sparse: sparse: incorrect type in argument 2 (different address spaces) @@     expected struct bpf_map *map @@     got struct bpf_map [noderef] __rcu * @@
   net/mptcp/sched.c:243:70: sparse:     expected struct bpf_map *map
   net/mptcp/sched.c:243:70: sparse:     got struct bpf_map [noderef] __rcu *
>> net/mptcp/sched.c:211:37: sparse: sparse: dereference of noderef expression
   net/mptcp/sched.c:212:23: sparse: sparse: dereference of noderef expression
   net/mptcp/sched.c:215:54: sparse: sparse: dereference of noderef expression
   net/mptcp/sched.c:239:37: sparse: sparse: dereference of noderef expression
   net/mptcp/sched.c:240:23: sparse: sparse: dereference of noderef expression
   net/mptcp/sched.c:243:54: sparse: sparse: dereference of noderef expression

vim +212 net/mptcp/sched.c

   203	
   204	int mptcp_sched_get_params(struct mptcp_sock *msk)
   205	{
   206		struct sock *sk = (struct sock *)msk;
   207	
   208		if (msk->sched == &mptcp_sched_default)
   209			return msk->snd_burst;
   210	
 > 211		if (sk->sk_bpf_storage && sk->sk_bpf_storage->smap &&
 > 212		    !strcmp(sk->sk_bpf_storage->smap->map.name, "mptcp_burst_map")) {
   213			struct bpf_local_storage_data *sdata;
   214	
 > 215			sdata = bpf_sk_storage_lookup(sk, &sk->sk_bpf_storage->smap->map, true);
   216			if (sdata) {
   217				struct mptcp_burst_storage {
   218					int snd_burst;
   219				} *ptr;
   220	
   221				ptr = (struct mptcp_burst_storage *)sdata->data;
   222				if (ptr)
   223					return ptr->snd_burst;
   224			}
   225		}
   226	
   227		return 0;
   228	}
   229	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2023-08-26  1:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 11:04 [RFC mptcp-next v2 0/2] BPF packet scheduler updates part 4 Geliang Tang
2023-08-23 11:04 ` [RFC mptcp-next v2 1/2] mptcp: add set/get params wrappers Geliang Tang
2023-08-23 11:04 ` [RFC mptcp-next v2 2/2] mptcp: add bpf_burst set/get params Geliang Tang
2023-08-23 11:28   ` mptcp: add bpf_burst set/get params: Build Failure MPTCP CI
2023-08-23 12:11   ` mptcp: add bpf_burst set/get params: Tests Results MPTCP CI
2023-08-23 17:21   ` [RFC mptcp-next v2 2/2] mptcp: add bpf_burst set/get params kernel test robot
2023-08-23 17:21   ` kernel test robot
2023-08-23 20:09   ` kernel test robot
2023-08-23 21:12   ` kernel test robot
2023-08-26  1:21   ` kernel test robot [this message]
2023-08-26  1:44   ` kernel test robot
2023-09-01 23:53   ` Mat Martineau

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=202308260938.lXj4ClGy-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=geliang.tang@suse.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.