From: Fengguang Wu <fengguang.wu@intel.com>
To: Christoph Lameter <cl@linux.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: Re: [mmotm:master 463/499] mm/mprotect.c:46:14: sparse: context imbalance in 'lock_pte_protection' - different lock contexts for basic block
Date: Tue, 25 Mar 2014 10:28:33 +0800 [thread overview]
Message-ID: <20140325022833.GA19661@localhost> (raw)
In-Reply-To: <alpine.DEB.2.10.1403241559390.29809@nuc>
On Mon, Mar 24, 2014 at 04:00:32PM -0500, Christoph Lameter wrote:
> On Sun, 23 Mar 2014, kbuild test robot wrote:
>
> > >> mm/mprotect.c:46:14: sparse: context imbalance in 'lock_pte_protection' - different lock contexts for basic block
> > >> arch/x86/include/asm/paravirt.h:699:9: sparse: context imbalance in 'change_pte_range' - unexpected unlock
> > --
> > >> fs/ntfs/super.c:3100:1: sparse: directive in argument list
> > >> fs/ntfs/super.c:3102:1: sparse: directive in argument list
> > >> fs/ntfs/super.c:3104:1: sparse: directive in argument list
> > >> fs/ntfs/super.c:3105:1: sparse: directive in argument list
> > >> fs/ntfs/super.c:3107:1: sparse: directive in argument list
> > >> fs/ntfs/super.c:3108:1: sparse: directive in argument list
> > >> fs/ntfs/super.c:3110:1: sparse: directive in argument list
>
> Looked through these and I am a bit puzzled how they related to raw cpu
> ops patch.
Ah yes, this is false positive and is because the compilation on the
previous commit failed, so the sparse errors in fs/ntfs/super.c show
up as "new" ones in commit 6a9ad050.
wfg@bee ~/linux% git checkout 6a9ad050c521ac607a30a691042f2a5d24109b07~
...
HEAD is now at 1b1dc6d... arm: move arm_dma_limit to setup_dma_zone
wfg@bee ~/linux/obj-compiletest% make C=1 fs/ntfs/super.o
...
HOSTLD scripts/mod/modpost
In file included from /c/wfg/linux/include/linux/mm.h:897:0,
from /c/wfg/linux/include/linux/suspend.h:8,
from /c/wfg/linux/arch/x86/kernel/asm-offsets.c:12:
/c/wfg/linux/include/linux/vmstat.h: In function a??__count_vm_eventa??:
/c/wfg/linux/include/linux/vmstat.h:36:2: error: implicit declaration of function a??raw_cpu_inca?? [-Werror=implicit-function-declaration]
/c/wfg/linux/include/linux/vmstat.h: In function a??__count_vm_eventsa??:
/c/wfg/linux/include/linux/vmstat.h:46:2: error: implicit declaration of function a??raw_cpu_adda?? [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[2]: *** [arch/x86/kernel/asm-offsets.s] Error 1
make[1]: *** [prepare0] Error 2
make: *** [sub-make] Error 2
make: Leaving directory `/c/wfg/linux'
Thanks,
Fengguang
--
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>
prev parent reply other threads:[~2014-03-25 2:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 2:53 [mmotm:master 463/499] mm/mprotect.c:46:14: sparse: context imbalance in 'lock_pte_protection' - different lock contexts for basic block kbuild test robot
2014-03-24 21:00 ` Christoph Lameter
2014-03-25 2:28 ` Fengguang Wu [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=20140325022833.GA19661@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.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).