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: [RFC net-next 3/6] page_pool: DMA handling and frame recycling via SKBs
Date: Fri, 12 Mar 2021 05:38:22 +0800	[thread overview]
Message-ID: <202103120502.906pVZVL-lkp@intel.com> (raw)
In-Reply-To: <20210311194256.53706-4-mcroce@linux.microsoft.com>

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

Hi Matteo,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Matteo-Croce/page_pool-recycle-buffers/20210312-034745
base:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 34bb975126419e86bc3b95e200dc41de6c6ca69c
config: i386-randconfig-s002-20210311 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.3-262-g5e674421-dirty
        # https://github.com/0day-ci/linux/commit/0a15a8310c854a5bbec0a0e23000efb3f377e097
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Matteo-Croce/page_pool-recycle-buffers/20210312-034745
        git checkout 0a15a8310c854a5bbec0a0e23000efb3f377e097
        # 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/core/xdp.c:377:40: sparse: sparse: Using plain integer as NULL pointer

vim +377 net/core/xdp.c

   374	
   375	void xdp_return_skb_frame(void *data, struct xdp_mem_info *mem)
   376	{
 > 377		__xdp_return(data, mem, false, 0);
   378	}
   379	EXPORT_SYMBOL_GPL(xdp_return_skb_frame);
   380	

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

  reply	other threads:[~2021-03-11 21:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11 19:42 [RFC net-next 0/6] page_pool: recycle buffers Matteo Croce
2021-03-11 19:42 ` [RFC net-next 1/6] xdp: reduce size of struct xdp_mem_info Matteo Croce
2021-03-11 19:42 ` [RFC net-next 2/6] mm: add a signature in struct page Matteo Croce
2021-03-11 19:42 ` [RFC net-next 3/6] page_pool: DMA handling and frame recycling via SKBs Matteo Croce
2021-03-11 21:38   ` kernel test robot [this message]
2021-03-11 19:42 ` [RFC net-next 4/6] net: change users of __skb_frag_unref() and add an extra argument Matteo Croce
2021-03-11 19:42 ` [RFC net-next 5/6] mvpp2: recycle buffers Matteo Croce
2021-03-11 19:42 ` [RFC net-next 6/6] mvneta: " Matteo Croce

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=202103120502.906pVZVL-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.