linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, 周琰杰 <zhouyanjie@wanyeetech.com>
Subject: Re: [PATCH] Revert "MIPS: make userspace mapping young by default"
Date: Wed, 26 May 2021 13:49:42 -0700	[thread overview]
Message-ID: <20210526134942.2bf26d5cf5a9243583aec131@linux-foundation.org> (raw)
In-Reply-To: <20210526094335.92948-1-tsbogend@alpha.franken.de>

On Wed, 26 May 2021 11:43:35 +0200 Thomas Bogendoerfer <tsbogend@alpha.franken.de> wrote:

> This reverts commit f685a533a7fab35c5d069dcd663f59c8e4171a75.
> 
> MIPS cache flush logic needs to know whether the mapping was already
> established to decide how to flush caches. This is done by checking the
> valid bit in the PTE. The commit above breaks this logic by setting
> the valid in the PTE in new mappings, which causes kernel crashes.

Thanks.  I added

Fixes: f685a533a7f ("MIPS: make userspace mapping young by default")
Cc: <stable@vger.kernel.org>

  reply	other threads:[~2021-05-26 20:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  9:43 [PATCH] Revert "MIPS: make userspace mapping young by default" Thomas Bogendoerfer
2021-05-26 20:49 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-16  8:47 周琰杰 (Zhou Yanjie)
2021-04-16  9:20 ` 黄沛
     [not found]   ` <ae06522f-eda8-96d1-6f58-072905afa65c@wanyeetech.com>
2021-04-19  4:56     ` Huang Pei
2021-04-19 14:21       ` Zhou Yanjie
2021-04-20  2:48         ` Huang Pei
2021-04-20 13:47           ` Zhou Yanjie
2021-04-20 14:03           ` Zhou Yanjie
2021-04-23 14:51             ` Thomas Bogendoerfer
2021-04-24 11:24               ` Zhou Yanjie
2021-04-26 13:11                 ` Huang Pei
2021-04-29 18:04                   ` Thomas Bogendoerfer
2021-04-30  2:07                     ` Huang Pei
2021-05-08  8:48                     ` Zhou Yanjie

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=20210526134942.2bf26d5cf5a9243583aec131@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=zhouyanjie@wanyeetech.com \
    /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).