From: Eric Lin <tesheng@andestech.com>
To: "linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"penberg@kernel.org" <penberg@kernel.org>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>
Subject: Re: [PATCH v3 0/2] Let illegal access to user-space memory die
Date: Fri, 18 Dec 2020 12:03:49 +0800 [thread overview]
Message-ID: <20201218040349.GA13987@atcfdc88> (raw)
In-Reply-To: <20201204054259.32684-1-tesheng@andestech.com>
On Fri, Dec 04, 2020 at 01:42:57PM +0800, Eric Te-Sheng Lin(?L?w??) wrote:
> Accesses to user-space memory without calling uaccess routine
> leads to hanging in page fault handler. Like arm64, we let it
> die earlier in page fault handler.
Hi Palmer, kindly ping.
Thanks.
>
> Changes in v3:
> -Let no_context() use die_kernel_fault() helper
>
> Changes in v2:
> -Add a die_kernel_fault() helper
> -Split one long line code into two
>
> Eric Lin (2):
> riscv/mm: Introduce a die_kernel_fault() helper function
> riscv/mm: Prevent kernel module to access user memory without uaccess
> routines
>
> arch/riscv/mm/fault.c | 28 ++++++++++++++++++++++------
> 1 file changed, 22 insertions(+), 6 deletions(-)
>
> --
> 2.17.0
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2020-12-18 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 5:42 [PATCH v3 0/2] Let illegal access to user-space memory die Eric Lin
2020-12-04 5:42 ` [PATCH v3 1/2] riscv/mm: Introduce a die_kernel_fault() helper function Eric Lin
2020-12-04 5:42 ` [PATCH v3 2/2] riscv/mm: Prevent kernel module to access user memory without uaccess routines Eric Lin
2020-12-18 4:03 ` Eric Lin [this message]
2020-12-22 2:35 ` [PATCH v3 0/2] Let illegal access to user-space memory die Palmer Dabbelt
2021-02-01 13:18 ` Ben Dooks
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=20201218040349.GA13987@atcfdc88 \
--to=tesheng@andestech.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=penberg@kernel.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