From: kbuild test robot <lkp@intel.com>
To: Jonathan Lemon <jonathan.lemon@gmail.com>
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org,
davem@davemloft.net, kernel-team@fb.com, brouer@redhat.com,
ilias.apalodimas@linaro.org
Subject: Re: [net-next PATCH v2 2/2] page_pool: remove hold/release count from tracepoints
Date: Fri, 15 Nov 2019 04:53:10 +0800 [thread overview]
Message-ID: <201911150410.qnDePnp0%lkp@intel.com> (raw)
In-Reply-To: <20191114163715.4184099-3-jonathan.lemon@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2810 bytes --]
Hi Jonathan,
I love your patch! Yet something to improve:
[auto build test ERROR on net-next/master]
[also build test ERROR on v5.4-rc7 next-20191114]
[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/Jonathan-Lemon/page_pool-do-not-release-pool-until-inflight-0/20191115-024705
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 75a1ccfe6c726ba33a2f9859d39deb2eba620583
config: x86_64-randconfig-s1-20191115 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from net//core/page_pool.c:19:0:
include/trace/events/page_pool.h:57:1: error: macro "TRACE_EVENT" requires 6 arguments, but only 5 given
);
^
include/trace/events/page_pool.h:38:1: warning: data definition has no type or storage class
TRACE_EVENT(page_pool_page_release,
^~~~~~~~~~~
include/trace/events/page_pool.h:38:1: error: type defaults to 'int' in declaration of 'TRACE_EVENT' [-Werror=implicit-int]
net//core/page_pool.c: In function '__page_pool_clean_page':
>> net//core/page_pool.c:225:2: error: implicit declaration of function 'trace_page_pool_page_release'; did you mean 'trace_page_pool_page_hold'? [-Werror=implicit-function-declaration]
trace_page_pool_page_release(pool, page);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
trace_page_pool_page_hold
cc1: some warnings being treated as errors
vim +225 net//core/page_pool.c
208
209 /* Cleanup page_pool state from page */
210 static void __page_pool_clean_page(struct page_pool *pool,
211 struct page *page)
212 {
213 dma_addr_t dma;
214
215 if (!(pool->p.flags & PP_FLAG_DMA_MAP))
216 goto skip_dma_unmap;
217
218 dma = page->dma_addr;
219 /* DMA unmap */
220 dma_unmap_page_attrs(pool->p.dev, dma,
221 PAGE_SIZE << pool->p.order, pool->p.dma_dir,
222 DMA_ATTR_SKIP_CPU_SYNC);
223 page->dma_addr = 0;
224 skip_dma_unmap:
> 225 trace_page_pool_page_release(pool, page);
226 /* This may be the last page returned, releasing the pool, so
227 * it is not safe to reference pool afterwards.
228 */
229 atomic_inc(&pool->pages_state_release_cnt);
230 }
231
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35230 bytes --]
next prev parent reply other threads:[~2019-11-14 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 16:37 [net-next PATCH v2 0/2] Change page_pool timeout handling Jonathan Lemon
2019-11-14 16:37 ` [net-next PATCH v2 1/2] page_pool: do not release pool until inflight == 0 Jonathan Lemon
2019-11-14 21:27 ` Jesper Dangaard Brouer
2019-11-14 16:37 ` [net-next PATCH v2 2/2] page_pool: remove hold/release count from tracepoints Jonathan Lemon
2019-11-14 20:53 ` kbuild test robot [this message]
2019-11-14 21:07 ` Jesper Dangaard Brouer
2019-11-14 21:56 ` Jonathan Lemon
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=201911150410.qnDePnp0%lkp@intel.com \
--to=lkp@intel.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=ilias.apalodimas@linaro.org \
--cc=jonathan.lemon@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.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 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).