From: kbuild test robot <lkp@intel.com>
To: zhongjiang <zhongjiang@huawei.com>
Cc: kbuild-all@01.org, mhocko@kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/huge_memory: fix the memory leak due to the race
Date: Tue, 21 Jun 2016 22:42:21 +0800 [thread overview]
Message-ID: <201606212210.EM0LuKCE%fengguang.wu@intel.com> (raw)
In-Reply-To: <1466517956-13875-1-git-send-email-zhongjiang@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]
Hi,
[auto build test ERROR on v4.7-rc4]
[also build test ERROR on next-20160621]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/zhongjiang/mm-huge_memory-fix-the-memory-leak-due-to-the-race/20160621-221736
config: s390-allyesconfig (attached as .config)
compiler: s390x-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
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
# save the attached .config to linux build tree
make.cross ARCH=s390
All errors (new ones prefixed by >>):
mm/huge_memory.c: In function 'do_huge_pmd_wp_page':
>> mm/huge_memory.c:1383:25: error: incompatible type for argument 3 of 'pmd_populate'
pmd_populate(mm, pmd, entry);
^
In file included from arch/s390/include/asm/tlbflush.h:7:0,
from include/linux/hugetlb.h:21,
from mm/huge_memory.c:13:
arch/s390/include/asm/pgalloc.h:120:20: note: expected 'pgtable_t {aka struct <anonymous> *}' but argument is of type 'pmd_t {aka struct <anonymous>}'
static inline void pmd_populate(struct mm_struct *mm,
^
vim +/pmd_populate +1383 mm/huge_memory.c
1377 entry = mk_huge_pmd(new_page, vma->vm_page_prot);
1378 entry = maybe_pmd_mkwrite(pmd_mkdirty(entry), vma);
1379 pmdp_invalidate(vma, haddr, pmd);
1380 page_add_new_anon_rmap(new_page, vma, haddr, true);
1381 mem_cgroup_commit_charge(new_page, memcg, false, true);
1382 lru_cache_add_active_or_unevictable(new_page, vma);
> 1383 pmd_populate(mm, pmd, entry);
1384 update_mmu_cache_pmd(vma, address, pmd);
1385 if (!page) {
1386 add_mm_counter(mm, MM_ANONPAGES, HPAGE_PMD_NR);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 41724 bytes --]
next prev parent reply other threads:[~2016-06-21 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 14:05 [PATCH] mm/huge_memory: fix the memory leak due to the race zhongjiang
2016-06-21 14:32 ` kbuild test robot
2016-06-21 14:37 ` Kirill A. Shutemov
2016-06-21 15:19 ` zhong jiang
2016-06-21 15:29 ` Kirill A. Shutemov
2016-06-22 2:55 ` zhong jiang
2016-06-22 9:52 ` zhong jiang
2016-06-21 14:37 ` Michal Hocko
2016-06-21 14:42 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-21 14:57 zhongjiang
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=201606212210.EM0LuKCE%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=zhongjiang@huawei.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;
as well as URLs for NNTP newsgroup(s).