From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Lichao Liu <liulichao@loongson.cn>
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH] MIPS: Grant pte read permission, even if vma only have VM_WRITE permission.
Date: Wed, 22 Jul 2020 11:36:03 +0200 [thread overview]
Message-ID: <20200722093603.GA10090@alpha.franken.de> (raw)
In-Reply-To: <20200717095536.45011-1-liulichao@loongson.cn>
On Fri, Jul 17, 2020 at 05:55:36PM +0800, Lichao Liu wrote:
> If a page can be written, then it can definitely be read.
IMHO it's exactly the point of RIXI enabled CPUs to support a
writeonly mapping even if most of other archs aren't able to
support it. So if there is no real good reason to change this,
I'm going to leave it this way.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-07-22 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 9:55 [PATCH] MIPS: Grant pte read permission, even if vma only have VM_WRITE permission Lichao Liu
2020-07-22 9:36 ` Thomas Bogendoerfer [this message]
2020-07-24 1:50 ` Lichao Liu
2020-07-31 22:37 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2020-06-30 0:58 Lichao Liu
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=20200722093603.GA10090@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@vger.kernel.org \
--cc=liulichao@loongson.cn \
/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).