From: Rabin Vincent <rabin@rab.in>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Russell King <linux@arm.linux.org.uk>,
Kees Cook <keescook@chromium.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.3-rc7
Date: Sun, 25 Oct 2015 23:32:52 +0100 [thread overview]
Message-ID: <20151025223252.GB5635@debian> (raw)
In-Reply-To: <CAMuHMdUkNad7-zHSEfy__rPXKV2t0_7O+MtHiW1hUN=t30KWoA@mail.gmail.com>
On Sun, Oct 25, 2015 at 11:39:15AM +0100, Geert Uytterhoeven wrote:
> On Sun, Oct 25, 2015 at 11:18 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > On Sun, Oct 25, 2015 at 11:12 AM, Geert Uytterhoeven
> > <geert@linux-m68k.org> wrote:
> >> JFYI, when comparing v4.3-rc7[1] to v4.3-rc6[3], the summaries are:
> >> - build errors: +12/-4
>From the quoted lines above one I got the impression that this was a
regression from v4.3-rc6 to 4.3-rc7, but that's not the case. The
failing config also fails with v4.3-rc6. It is however a regression
from v4.2 to v4.3-rc1, and started failing after the changes in
a5f4c561b3b19a ("ARM: 8415/1: early fixmap support for earlycon").
> > + /home/kisskb/slave/src/arch/arm/kernel/patch.c: error: 'L_PTE_DIRTY' undeclared (first use in this function): => 39:2
> > + /home/kisskb/slave/src/arch/arm/kernel/patch.c: error: 'L_PTE_MT_WRITEBACK' undeclared (first use in this function): => 39:2
> > + /home/kisskb/slave/src/arch/arm/kernel/patch.c: error: 'L_PTE_PRESENT' undeclared (first use in this function): => 39:2
> > + /home/kisskb/slave/src/arch/arm/kernel/patch.c: error: 'L_PTE_XN' undeclared (first use in this function): => 39:2
> > + /home/kisskb/slave/src/arch/arm/kernel/patch.c: error: 'L_PTE_YOUNG' undeclared (first use in this function): => 39:2
>
> Caused by:
>
> commit ab0615e2d6fb074764a3e4d05f1326fa2fdb4627
> Author: Rabin Vincent <rabin@rab.in>
> Date: Thu Apr 24 23:28:57 2014 +0200
>
> arm: use fixmap for text patching when text is RO
>
> Should the call to set_fixmap() in arch/arm/kernel/patch.c
> just be protected by #ifdef CONFIG_MMU?
Yes, and the call to clear_fixmap() too. This part of the code will
never actually be called on !MMU because patch_map() will always exit
early with nothing to remap. Will you send a patch?
(More code can be ifdef'd out to make a cleaner solution but I think that
really needs a simplification of the locking to be done first, which is
bit much for a late -rc.)
next prev parent reply other threads:[~2015-10-25 22:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 10:12 Build regressions/improvements in v4.3-rc7 Geert Uytterhoeven
2015-10-25 10:18 ` Geert Uytterhoeven
2015-10-25 10:39 ` Geert Uytterhoeven
2015-10-25 14:08 ` Russell King - ARM Linux
2015-10-25 17:38 ` Geert Uytterhoeven
2015-10-25 18:23 ` Russell King - ARM Linux
2015-10-25 19:03 ` Afzal Mohammed
2015-10-25 22:07 ` Rabin Vincent
2015-10-25 22:32 ` Rabin Vincent [this message]
2015-10-26 7:56 ` Geert Uytterhoeven
2015-10-25 17:34 ` Geert Uytterhoeven
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=20151025223252.GB5635@debian \
--to=rabin@rab.in \
--cc=geert@linux-m68k.org \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).