From: kbuild test robot <fengguang.wu@intel.com>
To: "Jérôme Glisse" <jglisse@redhat.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 264/276] mm/migrate.c:2491:23: error: passing argument 2 of 'pud_alloc' from incompatible pointer type
Date: Sat, 8 Apr 2017 08:42:19 +0800 [thread overview]
Message-ID: <201704080813.5P08JrLI%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 5b220005fda0593464fc4549eea586e597bf783c
commit: ef10b10b090d7d9b151e774c6186daae983d9ef8 [264/276] mm/migrate: allow migrate_vma() to alloc new page on empty entry
config: x86_64-acpi-redef (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout ef10b10b090d7d9b151e774c6186daae983d9ef8
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
mm/migrate.c: In function 'migrate_vma_insert_page':
>> mm/migrate.c:2491:23: error: passing argument 2 of 'pud_alloc' from incompatible pointer type [-Werror=incompatible-pointer-types]
pudp = pud_alloc(mm, pgdp, addr);
^~~~
In file included from include/linux/migrate.h:4:0,
from mm/migrate.c:15:
include/linux/mm.h:1677:22: note: expected 'p4d_t * {aka struct <anonymous> *}' but argument is of type 'pgd_t * {aka struct <anonymous> *}'
static inline pud_t *pud_alloc(struct mm_struct *mm, p4d_t *p4d,
^~~~~~~~~
cc1: some warnings being treated as errors
vim +/pud_alloc +2491 mm/migrate.c
2485
2486 /* Only allow populating anonymous memory */
2487 if (!vma_is_anonymous(vma))
2488 goto abort;
2489
2490 pgdp = pgd_offset(mm, addr);
> 2491 pudp = pud_alloc(mm, pgdp, addr);
2492 if (!pudp)
2493 goto abort;
2494 pmdp = pmd_alloc(mm, pudp, addr);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29701 bytes --]
reply other threads:[~2017-04-08 0:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201704080813.5P08JrLI%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jglisse@redhat.com \
--cc=kbuild-all@01.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