From: kbuild test robot <lkp@intel.com>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 200/348] mm/z3fold.c:1288:6: sparse: symbol 'z3fold_page_isolate' was not declared. Should it be static?
Date: Fri, 19 Apr 2019 21:09:23 +0800 [thread overview]
Message-ID: <201904192137.KiV8DXsU%lkp@intel.com> (raw)
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 0a5fb91e6404ba48c11565cc856f597311b21344
commit: eaa5a15c91fe04a61b97e14e5a2f229d0907678b [200/348] mm/z3fold.c: support page migration
reproduce:
# apt-get install sparse
git checkout eaa5a15c91fe04a61b97e14e5a2f229d0907678b
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
mm/z3fold.c:519:25: sparse: expression using sizeof(void)
mm/z3fold.c:519:25: sparse: expression using sizeof(void)
mm/z3fold.c:531:47: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] <asn:3>*__vpp_verify @@ got [noderef] <asn:3>*__vpp_verify @@
mm/z3fold.c:531:47: expected void const [noderef] <asn:3>*__vpp_verify
mm/z3fold.c:531:47: got struct list_head *<noident>
mm/z3fold.c:769:25: sparse: incorrect type in assignment (different address spaces) @@ expected struct list_head *unbuddied @@ got void struct list_head *unbuddied @@
mm/z3fold.c:769:25: expected struct list_head *unbuddied
mm/z3fold.c:769:25: got void [noderef] <asn:3>*
mm/z3fold.c:774:33: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] <asn:3>*__vpp_verify @@ got [noderef] <asn:3>*__vpp_verify @@
mm/z3fold.c:774:33: expected void const [noderef] <asn:3>*__vpp_verify
mm/z3fold.c:774:33: got struct list_head *<noident>
mm/z3fold.c:799:25: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] <asn:3>*__pdata @@ got [noderef] <asn:3>*__pdata @@
mm/z3fold.c:799:25: expected void [noderef] <asn:3>*__pdata
mm/z3fold.c:799:25: got struct list_head *unbuddied
mm/z3fold.c:653:21: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] <asn:3>*__vpp_verify @@ got [noderef] <asn:3>*__vpp_verify @@
mm/z3fold.c:653:21: expected void const [noderef] <asn:3>*__vpp_verify
mm/z3fold.c:653:21: got struct list_head *<noident>
mm/z3fold.c:708:37: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] <asn:3>*__vpp_verify @@ got [noderef] <asn:3>*__vpp_verify @@
mm/z3fold.c:708:37: expected void const [noderef] <asn:3>*__vpp_verify
mm/z3fold.c:708:37: got struct list_head *<noident>
mm/z3fold.c:531:47: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] <asn:3>*__vpp_verify @@ got [noderef] <asn:3>*__vpp_verify @@
mm/z3fold.c:531:47: expected void const [noderef] <asn:3>*__vpp_verify
mm/z3fold.c:531:47: got struct list_head *<noident>
>> mm/z3fold.c:1288:6: sparse: symbol 'z3fold_page_isolate' was not declared. Should it be static?
>> mm/z3fold.c:1323:5: sparse: symbol 'z3fold_page_migrate' was not declared. Should it be static?
>> mm/z3fold.c:1382:6: sparse: symbol 'z3fold_page_putback' was not declared. Should it be static?
mm/z3fold.c:443:35: sparse: context imbalance in '__release_z3fold_page' - unexpected unlock
mm/z3fold.c:462:9: sparse: context imbalance in 'release_z3fold_page_locked' - wrong count at exit
mm/z3fold.c:475:9: sparse: context imbalance in 'release_z3fold_page_locked_list' - wrong count at exit
mm/z3fold.c:610:13: sparse: context imbalance in 'do_compact_page' - different lock contexts for basic block
mm/z3fold.c:950:35: sparse: context imbalance in 'z3fold_alloc' - unexpected unlock
mm/z3fold.c:965:13: sparse: context imbalance in 'z3fold_free' - different lock contexts for basic block
mm/z3fold.c:1075:12: sparse: context imbalance in 'z3fold_reclaim_page' - different lock contexts for basic block
>> mm/z3fold.c:1382:6: sparse: context imbalance in 'z3fold_page_putback' - wrong count at exit
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2019-04-19 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 13:09 kbuild test robot [this message]
2019-04-19 13:09 ` [RFC PATCH mmotm] mm/z3fold.c: z3fold_page_isolate() can be static kbuild test robot
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=201904192137.KiV8DXsU%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=vitalywool@gmail.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