From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: Sudip Mukherjee
<sudipm.mukherjee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
Konstantin Khlebnikov
<koct9i-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: mm: provide reference to READ_IMPLIES_EXEC
Date: Thu, 28 Jan 2016 06:38:52 -0800 [thread overview]
Message-ID: <20160128143852.GA22099@roeck-us.net> (raw)
In-Reply-To: <1453972263-25907-1-git-send-email-sudipm.mukherjee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Thu, Jan 28, 2016 at 02:41:03PM +0530, Sudip Mukherjee wrote:
> blackfin defconfig fails with the error:
> mm/internal.h: In function 'is_stack_mapping':
> arch/blackfin/include/asm/page.h:15:27: error: 'READ_IMPLIES_EXEC' undeclared
>
> Commit 07dff8ae2bc5 has added is_stack_mapping in mm/internal.h but it
> also needs personality.h.
>
> Fixes: 07dff8ae2bc5 ("mm: warn about VmData over RLIMIT_DATA")
FWIW, this is just one of many build failures due to this patch.
Pretty much all non-MMU builds fail, plus several MMU builds.
I had prepared a patch for mn10300, but gave up after I noticed
all the other failures.
Build results in next-20160128:
total: 146 pass: 121 fail: 25
Failed builds:
alpha:allmodconfig
arm64:allnoconfig
arm64:allmodconfig
avr32:defconfig
avr32:merisc_defconfig
avr32:atngw100mkii_evklcd101_defconfig
blackfin:defconfig
blackfin:BF561-EZKIT-SMP_defconfig
c6x:dsk6455_defconfig
c6x:evmc6457_defconfig
c6x:evmc6678_defconfig
frv:defconfig
ia64:defconfig
ia64:allnoconfig
m68k:allmodconfig
microblaze:nommu_defconfig
microblaze:allnoconfig
mn10300:asb2303_defconfig
mn10300:asb2364_defconfig
parisc:allmodconfig
powerpc:ppc6xx_defconfig
s390:defconfig
s390:allmodconfig
s390:allnoconfig
xtensa:allmodconfig
Qemu test results:
total: 96 pass: 83 fail: 13
Failed tests:
arm:kzm:imx_v6_v7_defconfig
arm64:smp:defconfig
arm64:nosmp:defconfig
microblaze:microblaze_defconfig
microblaze:microblazeel_defconfig
powerpc:mac99:ppc_book3s_defconfig
powerpc:mpc8544ds:mpc85xx_smp_defconfig
powerpc:smp4:ppc64_book3s_defconfig
powerpc:nosmp:ppc64_e5500_defconfig
powerpc:smp:ppc64_e5500_defconfig
s390:defconfig
sparc64:sun4u:nosmp:sparc64_defconfig
sparc64:sun4v:nosmp:sparc64_defconfig
Not all, but most of the failures are due to 07dff8ae2bc5.
Guenter
next prev parent reply other threads:[~2016-01-28 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 9:11 [PATCH] mm: provide reference to READ_IMPLIES_EXEC Sudip Mukherjee
2016-01-28 9:33 ` Konstantin Khlebnikov
[not found] ` <1453972263-25907-1-git-send-email-sudipm.mukherjee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-28 14:38 ` Guenter Roeck [this message]
2016-01-28 15:29 ` Konstantin Khlebnikov
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=20160128143852.GA22099@roeck-us.net \
--to=linux-0h96xk9xttrk1umjsbkqmq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=koct9i-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=sudipm.mukherjee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).