linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Dmitry Safonov <dsafonov@virtuozzo.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	0x7f454c46@gmail.com, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@suse.de>,
	x86@kernel.org, linux-mm@kvack.org
Subject: Re: [PATCHv2 2/5] x86/mm: introduce mmap_{,legacy}_base
Date: Mon, 16 Jan 2017 22:28:10 +0800	[thread overview]
Message-ID: <201701162216.Z8cympIj%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170116123310.22697-3-dsafonov@virtuozzo.com>

[-- Attachment #1: Type: text/plain, Size: 2064 bytes --]

Hi Dmitry,

[auto build test ERROR on tip/x86/core]
[also build test ERROR on v4.10-rc4 next-20170116]
[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/Dmitry-Safonov/Fix-compatible-mmap-return-pointer-over-4Gb/20170116-204523
config: i386-randconfig-i1-201703 (attached as .config)
compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   mm/mmap.c: In function 'arch_get_unmapped_area_topdown':
>> mm/mmap.c:2039:20: error: 'TASK_UNMAPPED_BASE' undeclared (first use in this function)
      info.low_limit = TASK_UNMAPPED_BASE;
                       ^
   mm/mmap.c:2039:20: note: each undeclared identifier is reported only once for each function it appears in

vim +/TASK_UNMAPPED_BASE +2039 mm/mmap.c

^1da177e Linus Torvalds     2005-04-16  2033  	 * can happen with large stack limits and large mmap()
^1da177e Linus Torvalds     2005-04-16  2034  	 * allocations.
^1da177e Linus Torvalds     2005-04-16  2035  	 */
de1741a1 Alexander Kuleshov 2015-11-05  2036  	if (offset_in_page(addr)) {
db4fbfb9 Michel Lespinasse  2012-12-11  2037  		VM_BUG_ON(addr != -ENOMEM);
db4fbfb9 Michel Lespinasse  2012-12-11  2038  		info.flags = 0;
db4fbfb9 Michel Lespinasse  2012-12-11 @2039  		info.low_limit = TASK_UNMAPPED_BASE;
db4fbfb9 Michel Lespinasse  2012-12-11  2040  		info.high_limit = TASK_SIZE;
db4fbfb9 Michel Lespinasse  2012-12-11  2041  		addr = vm_unmapped_area(&info);
db4fbfb9 Michel Lespinasse  2012-12-11  2042  	}

:::::: The code at line 2039 was first introduced by commit
:::::: db4fbfb9523c93583c339e66023506f651c1d54b mm: vm_unmapped_area() lookup function

:::::: TO: Michel Lespinasse <walken@google.com>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>

---
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: 24559 bytes --]

  reply	other threads:[~2017-01-16 14:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 12:33 [PATCHv2 0/5] Fix compatible mmap() return pointer over 4Gb Dmitry Safonov
2017-01-16 12:33 ` [PATCHv2 1/5] x86/mm: split arch_mmap_rnd() on compat/native versions Dmitry Safonov
2017-01-16 12:33 ` [PATCHv2 2/5] x86/mm: introduce mmap_{,legacy}_base Dmitry Safonov
2017-01-16 14:28   ` kbuild test robot [this message]
2017-01-17 20:27   ` Andy Lutomirski
2017-01-18 11:26     ` Dmitry Safonov
2017-01-16 12:33 ` [PATCHv2 3/5] x86/mm: fix native mmap() in compat bins and vice-versa Dmitry Safonov
2017-01-16 13:31   ` kbuild test robot
2017-01-16 14:59   ` kbuild test robot
2017-01-17 20:29   ` Andy Lutomirski
2017-01-18 11:33     ` Dmitry Safonov
2017-01-16 12:33 ` [PATCHv2 4/5] x86/mm: for MAP_32BIT check in_compat_syscall() instead TIF_ADDR32 Dmitry Safonov
2017-01-17 20:30   ` Andy Lutomirski
2017-01-18 11:39     ` Dmitry Safonov
2017-01-16 12:33 ` [PATCHv2 5/5] selftests/x86: add test to check compat mmap() return addr Dmitry Safonov
2017-01-17 20:31 ` [PATCHv2 0/5] Fix compatible mmap() return pointer over 4Gb Andy Lutomirski

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=201701162216.Z8cympIj%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=0x7f454c46@gmail.com \
    --cc=bp@suse.de \
    --cc=dsafonov@virtuozzo.com \
    --cc=hpa@zytor.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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