BPF List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ryan Wilson <ryantimwilson@gmail.com>,
	bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net
Cc: oe-kbuild-all@lists.linux.dev, ryantimwilson@meta.com
Subject: Re: [PATCH bpf-next] bpf: Add multi-prog support for XDP BPF programs
Date: Sun, 1 Dec 2024 01:54:05 +0800	[thread overview]
Message-ID: <202412010119.qyfY5hLk-lkp@intel.com> (raw)
In-Reply-To: <20241114170721.3939099-1-ryantimwilson@gmail.com>

Hi Ryan,

kernel test robot noticed the following build warnings:

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

url:    https://github.com/intel-lab-lkp/linux/commits/Ryan-Wilson/bpf-Add-multi-prog-support-for-XDP-BPF-programs/20241115-015104
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link:    https://lore.kernel.org/r/20241114170721.3939099-1-ryantimwilson%40gmail.com
patch subject: [PATCH bpf-next] bpf: Add multi-prog support for XDP BPF programs
config: x86_64-randconfig-122-20241117 (https://download.01.org/0day-ci/archive/20241201/202412010119.qyfY5hLk-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241201/202412010119.qyfY5hLk-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/202412010119.qyfY5hLk-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   net/core/dev.c:3387:23: sparse: sparse: incorrect type in argument 4 (different base types) @@     expected restricted __wsum [usertype] csum @@     got unsigned int @@
   net/core/dev.c:3387:23: sparse:     expected restricted __wsum [usertype] csum
   net/core/dev.c:3387:23: sparse:     got unsigned int
   net/core/dev.c:3387:23: sparse: sparse: cast from restricted __wsum
>> net/core/dev.c:9416:76: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected struct bpf_mprog_entry *entry @@     got struct bpf_mprog_entry [noderef] __rcu * @@
   net/core/dev.c:9416:76: sparse:     expected struct bpf_mprog_entry *entry
   net/core/dev.c:9416:76: sparse:     got struct bpf_mprog_entry [noderef] __rcu *
   net/core/dev.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/xarray.h, ...):
   include/linux/page-flags.h:237:46: sparse: sparse: self-comparison always evaluates to false
   include/linux/page-flags.h:237:46: sparse: sparse: self-comparison always evaluates to false
   net/core/dev.c:3837:17: sparse: sparse: context imbalance in '__dev_queue_xmit' - different lock contexts for basic block
   net/core/dev.c:4800:9: sparse: sparse: context imbalance in 'kick_defer_list_purge' - different lock contexts for basic block
   net/core/dev.c:4901:19: sparse: sparse: context imbalance in 'enqueue_to_backlog' - different lock contexts for basic block
   net/core/dev.c:5315:17: sparse: sparse: context imbalance in 'net_tx_action' - different lock contexts for basic block
   net/core/dev.c:5996:9: sparse: sparse: context imbalance in 'flush_backlog' - different lock contexts for basic block
   net/core/dev.c:6123:9: sparse: sparse: context imbalance in 'process_backlog' - different lock contexts for basic block

vim +9416 net/core/dev.c

  9409	
  9410	u8 dev_xdp_prog_count(struct net_device *dev)
  9411	{
  9412		u8 count = 0;
  9413		int i;
  9414	
  9415		for (i = 0; i < __MAX_XDP_MODE; i++)
> 9416			if (dev->xdp_state[i] && xdp_entry_is_active(dev->xdp_state[i]))
  9417				count++;
  9418		return count;
  9419	}
  9420	EXPORT_SYMBOL_GPL(dev_xdp_prog_count);
  9421	

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

      parent reply	other threads:[~2024-11-30 17:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 17:07 [PATCH bpf-next] bpf: Add multi-prog support for XDP BPF programs Ryan Wilson
2024-11-15  0:52 ` Alexei Starovoitov
2024-11-15  2:41   ` Ryan Wilson
2024-11-15 11:07     ` Toke Høiland-Jørgensen
2024-11-15 16:06       ` Ryan Wilson
2024-11-18 12:30         ` Toke Høiland-Jørgensen
2024-11-15 22:08 ` Andrii Nakryiko
2024-11-15 22:31   ` Ryan Wilson
2024-11-17  3:36 ` kernel test robot
2024-11-17  4:33 ` kernel test robot
2024-11-17  4:43 ` kernel test robot
2024-11-17 13:44 ` kernel test robot
2024-11-30 17:54 ` kernel test robot [this message]

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=202412010119.qyfY5hLk-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ryantimwilson@gmail.com \
    --cc=ryantimwilson@meta.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