linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] vmemmap fix for bug introduced by extending VA range
Date: Fri, 26 Feb 2016 17:57:12 +0100	[thread overview]
Message-ID: <1456505834-8638-1-git-send-email-ard.biesheuvel@linaro.org> (raw)

This is a followup to patch [1] (part of [2]) where I fixed an issue that I
identified related to commit dd006da21646 ("arm64: mm: increase VA range of
identity map").

Patch #1 fixes the issue in a way that should be compatible with v4.5 and
-stable, although it may conflict trivially on hunk context.

Patch #2 is a followup that changes memstart_addr to a signed type, which is
necessary when combining patch #1 with the linear region randomization patch
that is currently queued in -next.

[1] http://article.gmane.org/gmane.linux.ports.arm.kernel/481330
[2] http://thread.gmane.org/gmane.linux.ports.arm.kernel/481327


Ard Biesheuvel (2):
  arm64: vmemmap: use virtual projection of linear region
  arm64: mm: treat memstart_addr as a signed quantity

 arch/arm64/include/asm/memory.h  | 2 +-
 arch/arm64/include/asm/pgtable.h | 7 ++++---
 arch/arm64/mm/init.c             | 6 +++---
 3 files changed, 8 insertions(+), 7 deletions(-)

-- 
2.5.0

             reply	other threads:[~2016-02-26 16:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 16:57 Ard Biesheuvel [this message]
2016-02-26 16:57 ` [PATCH v2 1/2] arm64: vmemmap: use virtual projection of linear region Ard Biesheuvel
2016-03-08  1:07   ` David Daney
2016-03-08  2:15     ` Ard Biesheuvel
2016-03-08 10:31       ` Ard Biesheuvel
2016-03-08 13:17         ` Mark Langsdorf
2016-03-08 15:21           ` Ard Biesheuvel
2016-03-09 11:32         ` Robert Richter
2016-03-09 11:36           ` Robert Richter
2016-02-26 16:57 ` [PATCH v2 2/2] arm64: mm: treat memstart_addr as a signed quantity Ard Biesheuvel
2016-02-29 12:39   ` Ard Biesheuvel
2016-02-29 18:36   ` Catalin Marinas

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=1456505834-8638-1-git-send-email-ard.biesheuvel@linaro.org \
    --to=ard.biesheuvel@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).