From: kbuild test robot <fengguang.wu@intel.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: [mmotm:master 169/385] mm/debug.c:215:5: error: 'const struct mm_struct' has no member named 'owner'
Date: Tue, 23 Sep 2014 09:28:53 +0800 [thread overview]
Message-ID: <5420ccd5.miNNRyVn5wct+fk+%fengguang.wu@intel.com> (raw)
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: eb076320e4dbdf99513732811ed8730812b34b2f
commit: bac27df2312993aedf1cdfa2dad43e5aeb29504d [169/385] mm: introduce VM_BUG_ON_MM
config: arm-tegra_defconfig
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout bac27df2312993aedf1cdfa2dad43e5aeb29504d
make.cross ARCH=arm tegra_defconfig
make.cross ARCH=arm
All error/warnings:
mm/debug.c: In function 'dump_mm':
>> mm/debug.c:215:5: error: 'const struct mm_struct' has no member named 'owner'
mm->owner, mm->exe_file,
^
vim +215 mm/debug.c
209 mm->start_brk, mm->brk, mm->start_stack,
210 mm->arg_start, mm->arg_end, mm->env_start, mm->env_end,
211 mm->binfmt, mm->flags, mm->core_state,
212 #ifdef CONFIG_AIO
213 mm->ioctx_table,
214 #endif
> 215 mm->owner, mm->exe_file,
216 #ifdef CONFIG_MMU_NOTIFIER
217 mm->mmu_notifier_mm,
218 #endif
---
0-DAY kernel build testing backend 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:[~2014-09-23 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 1:28 kbuild test robot [this message]
2014-09-23 14:41 ` Michal Hocko
2014-09-23 14:43 ` Michal Hocko
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=5420ccd5.miNNRyVn5wct+fk+%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.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