From: David Daney <ddaney@caviumnetworks.com>
To: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Cc: <daniel.sanders@imgtec.com>, <linux-mips@linux-mips.org>,
<cernekee@gmail.com>, <Zubair.Kakakhel@imgtec.com>,
<geert+renesas@glider.be>, <david.daney@cavium.com>,
<peterz@infradead.org>, <heiko.carstens@de.ibm.com>,
<paul.gortmaker@windriver.com>, <behanw@converseincode.com>,
<macro@linux-mips.org>, <cl@linux.com>, <pkarat@mvista.com>,
<linux@roeck-us.net>, <tkhai@yandex.ru>, <james.hogan@imgtec.com>,
<alexinbeijing@gmail.com>, <rusty@rustcorp.com.au>,
<Steven.Hill@imgtec.com>, <lars.persson@axis.com>,
<aleksey.makarov@auriga.com>, <paul.burton@imgtec.com>,
<linux-kernel@vger.kernel.org>, <ralf@linux-mips.org>,
<luto@amacapital.net>, <dahi@linux.vnet.ibm.com>,
<markos.chandras@imgtec.com>, <eunb.song@samsung.com>,
<kumba@gentoo.org>
Subject: Re: [PATCH v4 0/3] MIPS executable stack protection
Date: Wed, 5 Aug 2015 17:00:15 -0700 [thread overview]
Message-ID: <55C2A38F.6000708@caviumnetworks.com> (raw)
In-Reply-To: <20150805234348.20722.71740.stgit@ubuntu-yegoshin>
On 08/05/2015 04:49 PM, Leonid Yegoshin wrote:
> The following series implements an executable stack protection in MIPS.
>
> It sets up a per-thread 'VDSO' page and appropriate TLB support.
> Page is set write-protected from user and is maintained via kernel VA.
> MIPS FPU emulation is shifted to new page and stack is relieved for
> execute protection as is as all data pages in default setup during ELF
> binary initialization.
Does it handle nested emulation?
1) Emulation started on instruction in main program flow, we are
about to re-enter user space..
2) Asynchronous signal is received.
3) Return to user space. Where do we go? Is it the signal handler
or the instruction emulation?
If we go to the signal handler and it needs emulation, what happens?
David Daney
> The real protection is controlled by GLIBC and
> it can do stack protected now as it is done in other architectures and
> I learned today that GLIBC team is ready for this.
>
> Note: actual execute-protection depends from HW capability, of course.
>
> This patch is required for MIPS32/64 R2 emulation on MIPS R6 architecture.
> Without it 'ssh-keygen' crashes pretty fast on attempt to execute instruction
> in stack.
>
> v2 changes:
> - Added an optimization during mmap switch - doesn't switch if the same
> thread is rescheduled and other threads don't intervene (Peter Zijlstra)
> - Fixed uMIPS support (Paul Burton)
> - Added unwinding of VDSO emulation stack at signal handler invocation,
> hiding an emulation page (Andy Lutomirski note in other patch comments)
>
> V3 change: heavy preemption friendly.
>
> V4 changes:
> - Fixed bug in supplementary TLB flush (change KVA to user address space)
> - Rebased to 4.X kernel
> ---
>
> Leonid Yegoshin (3):
> MIPS: mips_flush_cache_range is added
> MIPS: Setup an instruction emulation in VDSO protected page instead of user stack
> MIPS: set stack/data protection as non-executable
>
>
> arch/mips/include/asm/cacheflush.h | 3 +
> arch/mips/include/asm/fpu_emulator.h | 2
> arch/mips/include/asm/mmu.h | 3 +
> arch/mips/include/asm/page.h | 2
> arch/mips/include/asm/processor.h | 2
> arch/mips/include/asm/switch_to.h | 14 +++
> arch/mips/include/asm/thread_info.h | 3 +
> arch/mips/include/asm/tlbmisc.h | 1
> arch/mips/include/asm/vdso.h | 3 +
> arch/mips/kernel/mips-r2-to-r6-emul.c | 10 +-
> arch/mips/kernel/process.c | 7 ++
> arch/mips/kernel/signal.c | 4 +
> arch/mips/kernel/vdso.c | 44 +++++++++
> arch/mips/math-emu/cp1emu.c | 8 +-
> arch/mips/math-emu/dsemul.c | 154 +++++++++++++++++++++++++++------
> arch/mips/mm/c-octeon.c | 8 ++
> arch/mips/mm/c-r3k.c | 8 ++
> arch/mips/mm/c-r4k.c | 43 +++++++++
> arch/mips/mm/c-tx39.c | 9 ++
> arch/mips/mm/cache.c | 4 +
> arch/mips/mm/fault.c | 5 +
> arch/mips/mm/tlb-r4k.c | 42 +++++++++
> 22 files changed, 343 insertions(+), 36 deletions(-)
>
> --
> Signature
>
next prev parent reply other threads:[~2015-08-06 0:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 23:49 [PATCH v4 0/3] MIPS executable stack protection Leonid Yegoshin
2015-08-05 23:49 ` [PATCH v4 1/3] MIPS: mips_flush_cache_range is added Leonid Yegoshin
2015-08-05 23:49 ` [PATCH v4 2/3] MIPS: Setup an instruction emulation in VDSO protected page instead of user stack Leonid Yegoshin
2015-08-05 23:49 ` [PATCH v4 3/3] MIPS: set stack/data protection as non-executable Leonid Yegoshin
2015-08-05 23:55 ` Paul Burton
2015-08-06 0:06 ` Leonid Yegoshin
2015-08-06 0:14 ` David Daney
2015-08-06 0:23 ` Leonid Yegoshin
2015-08-06 0:37 ` David Daney
2015-08-06 0:46 ` Leonid Yegoshin
2015-08-06 1:07 ` David Daney
2015-08-06 0:40 ` Paul Burton
2015-08-05 23:55 ` David Daney
2015-08-06 0:00 ` David Daney [this message]
2015-08-06 0:02 ` [PATCH v4 0/3] MIPS executable stack protection Leonid Yegoshin
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=55C2A38F.6000708@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=Steven.Hill@imgtec.com \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=aleksey.makarov@auriga.com \
--cc=alexinbeijing@gmail.com \
--cc=behanw@converseincode.com \
--cc=cernekee@gmail.com \
--cc=cl@linux.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=daniel.sanders@imgtec.com \
--cc=david.daney@cavium.com \
--cc=eunb.song@samsung.com \
--cc=geert+renesas@glider.be \
--cc=heiko.carstens@de.ibm.com \
--cc=james.hogan@imgtec.com \
--cc=kumba@gentoo.org \
--cc=lars.persson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@roeck-us.net \
--cc=luto@amacapital.net \
--cc=macro@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=paul.burton@imgtec.com \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=pkarat@mvista.com \
--cc=ralf@linux-mips.org \
--cc=rusty@rustcorp.com.au \
--cc=tkhai@yandex.ru \
/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