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,
Cyrill Gorcunov <gorcunov@openvz.org>
Subject: Re: [PATCHv5 1/5] x86/mm: introduce arch_rnd() to compute 32/64 mmap rnd
Date: Wed, 15 Feb 2017 06:22:26 +0800 [thread overview]
Message-ID: <201702150640.DEwJ0Wro%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170214183621.2537-2-dsafonov@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 2857 bytes --]
Hi Dmitry,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc8 next-20170214]
[cannot apply to tip/x86/core]
[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/20170215-025132
config: x86_64-randconfig-x014-201707 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed by >>):
arch/x86/mm/mmap.c: In function 'arch_mmap_rnd':
>> arch/x86/mm/mmap.c:58:27: error: 'mmap_rnd_compat_bits' undeclared (first use in this function)
# define mmap32_rnd_bits mmap_rnd_compat_bits
^
>> arch/x86/mm/mmap.c:83:35: note: in expansion of macro 'mmap32_rnd_bits'
return arch_rnd(mmap_is_ia32() ? mmap32_rnd_bits : mmap64_rnd_bits);
^~~~~~~~~~~~~~~
arch/x86/mm/mmap.c:58:27: note: each undeclared identifier is reported only once for each function it appears in
# define mmap32_rnd_bits mmap_rnd_compat_bits
^
>> arch/x86/mm/mmap.c:83:35: note: in expansion of macro 'mmap32_rnd_bits'
return arch_rnd(mmap_is_ia32() ? mmap32_rnd_bits : mmap64_rnd_bits);
^~~~~~~~~~~~~~~
>> arch/x86/mm/mmap.c:84:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
vim +/mmap_rnd_compat_bits +58 arch/x86/mm/mmap.c
52 * Leave an at least ~128 MB hole with possible stack randomization.
53 */
54 #define MIN_GAP (128*1024*1024UL + stack_maxrandom_size())
55 #define MAX_GAP (TASK_SIZE/6*5)
56
57 #ifdef CONFIG_64BIT
> 58 # define mmap32_rnd_bits mmap_rnd_compat_bits
59 # define mmap64_rnd_bits mmap_rnd_bits
60 #else
61 # define mmap32_rnd_bits mmap_rnd_bits
62 # define mmap64_rnd_bits mmap_rnd_bits
63 #endif
64
65 static int mmap_is_legacy(void)
66 {
67 if (current->personality & ADDR_COMPAT_LAYOUT)
68 return 1;
69
70 if (rlimit(RLIMIT_STACK) == RLIM_INFINITY)
71 return 1;
72
73 return sysctl_legacy_va_layout;
74 }
75
76 static unsigned long arch_rnd(unsigned int rndbits)
77 {
78 return (get_random_long() & ((1UL << rndbits) - 1)) << PAGE_SHIFT;
79 }
80
81 unsigned long arch_mmap_rnd(void)
82 {
> 83 return arch_rnd(mmap_is_ia32() ? mmap32_rnd_bits : mmap64_rnd_bits);
> 84 }
85
86 static unsigned long mmap_base(unsigned long rnd)
87 {
---
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: 25588 bytes --]
next prev parent reply other threads:[~2017-02-14 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 18:36 [PATCHv5 0/5] Fix compatible mmap() return pointer over 4Gb Dmitry Safonov
2017-02-14 18:36 ` [PATCHv5 1/5] x86/mm: introduce arch_rnd() to compute 32/64 mmap rnd Dmitry Safonov
2017-02-14 22:22 ` kbuild test robot [this message]
2017-02-15 9:34 ` Dmitry Safonov
2017-02-14 18:36 ` [PATCHv5 2/5] x86/mm: add task_size parameter to mmap_base() Dmitry Safonov
2017-02-14 18:36 ` [PATCHv5 3/5] x86/mm: introduce mmap_compat_base for 32-bit mmap() Dmitry Safonov
2017-02-14 18:36 ` [PATCHv5 4/5] x86/mm: check in_compat_syscall() instead TIF_ADDR32 for mmap(MAP_32BIT) Dmitry Safonov
2017-02-14 18:36 ` [PATCHv5 5/5] selftests/x86: add test for 32-bit mmap() return addr Dmitry Safonov
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=201702150640.DEwJ0Wro%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=0x7f454c46@gmail.com \
--cc=bp@suse.de \
--cc=dsafonov@virtuozzo.com \
--cc=gorcunov@openvz.org \
--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