From: kbuild test robot <fengguang.wu@intel.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: kbuild-all@01.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [aa:userfault 17/19] mm/userfaultfd.c:48:6: sparse: symbol 'double_down_read' was not declared. Should it be static?
Date: Thu, 12 Feb 2015 16:54:04 +0800 [thread overview]
Message-ID: <201502121644.mekdzvbV%fengguang.wu@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/andrea/aa.git userfault
head: 9866337e3999d167b77303ad9e57fd20919893e3
commit: e2ccdb8c9f49438f9c8910f2f93c7e5ee35d8644 [17/19] userfaultfd: add new syscall to provide memory externalization
reproduce:
# apt-get install sparse
git checkout e2ccdb8c9f49438f9c8910f2f93c7e5ee35d8644
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> mm/userfaultfd.c:48:6: sparse: symbol 'double_down_read' was not declared. Should it be static?
>> mm/userfaultfd.c:67:6: sparse: symbol 'double_up_read' was not declared. Should it be static?
>> mm/userfaultfd.c:34:9: sparse: context imbalance in 'double_pt_lock' - different lock contexts for basic block
>> mm/userfaultfd.c:44:9: sparse: context imbalance in 'double_pt_unlock' - different lock contexts for basic block
>> mm/userfaultfd.c:63:9: sparse: context imbalance in 'double_down_read' - wrong count at exit
>> mm/userfaultfd.c:73:9: sparse: context imbalance in 'double_up_read' - wrong count at exit
>> mm/userfaultfd.c:551:9: sparse: context imbalance in 'remap_anon_pages' - different lock contexts for basic block
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2015-02-12 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 8:54 kbuild test robot [this message]
2015-02-12 8:54 ` [PATCH aa] userfaultfd: double_down_read() 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=201502121644.mekdzvbV%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=aarcange@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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