All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Nowakowski <marcin.nowakowski@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>,
	Marcin Nowakowski <marcin.nowakowski@imgtec.com>
Subject: [PATCH 0/3] mips highmem fixes
Date: Tue, 11 Apr 2017 09:00:33 +0200	[thread overview]
Message-ID: <1491894036-5440-1-git-send-email-marcin.nowakowski@imgtec.com> (raw)

There are currently a few incorrect assumptions made about the location
and alignment of fixed memory mappings that lead to random crashes when
using highmem with large (>4k) pages

Marcin Nowakowski (3):
  MIPS: mm: fixed mappings: correct initialisation
  MIPS: highmem: ensure that we don't use more than one page for PTEs
  MIPS: mm: adjust PKMAP location

 arch/mips/include/asm/highmem.h    | 5 +++++
 arch/mips/include/asm/pgtable-32.h | 7 ++++++-
 arch/mips/mm/pgtable-32.c          | 6 +++---
 3 files changed, 14 insertions(+), 4 deletions(-)

-- 
2.7.4

WARNING: multiple messages have this Message-ID (diff)
From: Marcin Nowakowski <marcin.nowakowski@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org,
	Marcin Nowakowski <marcin.nowakowski@imgtec.com>
Subject: [PATCH 0/3] mips highmem fixes
Date: Tue, 11 Apr 2017 09:00:33 +0200	[thread overview]
Message-ID: <1491894036-5440-1-git-send-email-marcin.nowakowski@imgtec.com> (raw)
Message-ID: <20170411070033.lhDbviS8MtBDjFwhkUbMZP1H9_YiHxWdXRZGJVFKSXo@z> (raw)

There are currently a few incorrect assumptions made about the location
and alignment of fixed memory mappings that lead to random crashes when
using highmem with large (>4k) pages

Marcin Nowakowski (3):
  MIPS: mm: fixed mappings: correct initialisation
  MIPS: highmem: ensure that we don't use more than one page for PTEs
  MIPS: mm: adjust PKMAP location

 arch/mips/include/asm/highmem.h    | 5 +++++
 arch/mips/include/asm/pgtable-32.h | 7 ++++++-
 arch/mips/mm/pgtable-32.c          | 6 +++---
 3 files changed, 14 insertions(+), 4 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-04-11  7:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  7:00 Marcin Nowakowski [this message]
2017-04-11  7:00 ` [PATCH 0/3] mips highmem fixes Marcin Nowakowski
2017-04-11  7:00 ` [PATCH 1/3] MIPS: mm: fixed mappings: correct initialisation Marcin Nowakowski
2017-04-11  7:00   ` Marcin Nowakowski
2017-04-11  7:00 ` [PATCH 2/3] MIPS: highmem: ensure that we don't use more than one page for PTEs Marcin Nowakowski
2017-04-11  7:00   ` Marcin Nowakowski
2017-04-11  7:00 ` [PATCH 3/3] MIPS: mm: adjust PKMAP location Marcin Nowakowski
2017-04-11  7:00   ` Marcin Nowakowski
2017-04-11  9:49   ` Sergei Shtylyov

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=1491894036-5440-1-git-send-email-marcin.nowakowski@imgtec.com \
    --to=marcin.nowakowski@imgtec.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.