linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Cashman <dcashman@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	kbuild-all@01.org, Mark Brown <broonie@kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 4174/4356] kernel/built-in.o:undefined reference to `mmap_rnd_bits'
Date: Fri, 4 Dec 2015 16:56:19 -0800	[thread overview]
Message-ID: <CAJQetW4L6Zuzd9GENK6XMg+OVtFUjyE4jOzoG+VB3HtwmoUmiA@mail.gmail.com> (raw)
In-Reply-To: <20151204151913.166e5cb795359ff1a53d26ac@linux-foundation.org>

Yes, patch-set v5 addressed the MMU case.  As for
HAVE_ARCH_MMAP_RND_BITS=n, I deliberately made it such that once an
arch implements the feature it selects it in its Kconfig, so we
shouldn't have the situation where an arch relies on an mmap_rnd_bits*
in its mmap.c, but doesn't find one defined.

At present, I am planning to change the arm64/Kconfing to get rid of
the "if MMU" portion, per Will Deacon's request, adjust the min bit
value, and add a comment.  I've left the question of whether or not
the value should be the number of randomized bits (current situation)
or the size of the address space chunk affected up to akpm@.  Please
let me know what else should be done in v6 to keep these in.

Thank You,
Dan

On Fri, Dec 4, 2015 at 3:19 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 4 Dec 2015 15:14:24 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
>> There's also the matter of CONFIG_MMU=n.
>
> ah, Arnd already fixed this one.  I guess I'll retain the patches
> for now.
>
>
>
> From: Arnd Bergmann <arnd@arndb.de>
> Subject: ARM: avoid ARCH_MMAP_RND_BITS for NOMMU
>
> ARM kernels with MMU disabled fail to build because of CONFIG_ARCH_MMAP_RND_BITS:
>
> kernel/built-in.o:(.data+0x754): undefined reference to `mmap_rnd_bits'
> kernel/built-in.o:(.data+0x76c): undefined reference to `mmap_rnd_bits_min'
> kernel/built-in.o:(.data+0x770): undefined reference to `mmap_rnd_bits_max'
>
> This changes the newly added line to only select this allow for
> MMU-enabled kernels.
>
> Fixes: 14570b3fd31a ("arm: mm: support ARCH_MMAP_RND_BITS")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Cc: Daniel Cashman <dcashman@google.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
>  arch/arm/Kconfig |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -puN arch/arm/Kconfig~arm-mm-support-arch_mmap_rnd_bits-fix arch/arm/Kconfig
> --- a/arch/arm/Kconfig~arm-mm-support-arch_mmap_rnd_bits-fix
> +++ a/arch/arm/Kconfig
> @@ -35,7 +35,7 @@ config ARM
>         select HAVE_ARCH_BITREVERSE if (CPU_32v7M || CPU_32v7) && !CPU_32v6
>         select HAVE_ARCH_JUMP_LABEL if !XIP_KERNEL && !CPU_ENDIAN_BE32
>         select HAVE_ARCH_KGDB if !CPU_ENDIAN_BE32
> -       select HAVE_ARCH_MMAP_RND_BITS
> +       select HAVE_ARCH_MMAP_RND_BITS if MMU
>         select HAVE_ARCH_SECCOMP_FILTER if (AEABI && !OABI_COMPAT)
>         select HAVE_ARCH_TRACEHOOK
>         select HAVE_BPF_JIT
> _
>



-- 
Dan Cashman

--
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>

  reply	other threads:[~2015-12-05  0:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 16:18 [linux-next:master 4174/4356] kernel/built-in.o:undefined reference to `mmap_rnd_bits' kbuild test robot
2015-12-04 23:14 ` Andrew Morton
2015-12-04 23:19   ` Andrew Morton
2015-12-05  0:56     ` Daniel Cashman [this message]
2015-12-05  1:01       ` Andrew Morton
2015-12-05  1:46         ` Daniel Cashman
2015-12-07 18:13           ` Daniel Cashman

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=CAJQetW4L6Zuzd9GENK6XMg+OVtFUjyE4jOzoG+VB3HtwmoUmiA@mail.gmail.com \
    --to=dcashman@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=fengguang.wu@intel.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;
as well as URLs for NNTP newsgroup(s).