From: Linus Torvalds <torvalds@linux-foundation.org>
To: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
linux-mips <linux-mips@linux-mips.org>,
"Zubair Kakakhel" <Zubair.Kakakhel@imgtec.com>,
"David Daney" <david.daney@cavium.com>,
"Paul Gortmaker" <paul.gortmaker@windriver.com>,
"Davidlohr Bueso" <davidlohr@hp.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
"chenhc@lemote.com" <chenhc@lemote.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
"James Hogan" <James.Hogan@imgtec.com>,
"Kees Cook" <keescook@chromium.org>,
"alex@alex-smith.me.uk" <alex@alex-smith.me.uk>,
"Thomas Gleixner" <tglx@linutronix.de>,
"John Crispin" <blogic@openwrt.org>,
"jchandra@broadcom.com" <jchandra@broadcom.com>,
"Paul Burton" <Paul.Burton@imgtec.com>,
"Qais Yousef" <Qais.Yousef@imgtec.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Ralf Baechle" <ralf@linux-mips.org>,
"Markos Chandras" <Markos.Chandras@imgtec.com>,
"Manuel Lauss" <manuel.lauss@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"lars.persson@axis.com" <lars.persson@axis.com>
Subject: Re: [PATCH 0/3] MIPS executable stack protection
Date: Sat, 4 Oct 2014 09:27:59 -0700 [thread overview]
Message-ID: <CA+55aFxqip0m=Ohd-+VDEkzahhLDe+fj9kXY0bbQY8YMBTEc4A@mail.gmail.com> (raw)
In-Reply-To: <vi8ojsasknll8us53fy9myb8.1412439420039@email.android.com>
On Sat, Oct 4, 2014 at 9:17 AM, Leonid Yegoshin
<Leonid.Yegoshin@imgtec.com> wrote:
> Linus, it works on CPU with hardware page table walker - MIPS P5600 aka Apache.
>
> I was involved in architecture development of HTW and took care of it.
Ok, as long as it works architecturally, per-thread TLB fills are fine by me.
Linus
next prev parent reply other threads:[~2014-10-04 16:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 3:17 [PATCH 0/3] MIPS executable stack protection Leonid Yegoshin
2014-10-04 3:17 ` [PATCH 1/3] MIPS: mips_flush_cache_range is added Leonid Yegoshin
2014-10-04 3:17 ` [PATCH 2/3] MIPS: Setup an instruction emulation in VDSO protected page instead of user stack Leonid Yegoshin
2014-10-04 20:00 ` Peter Zijlstra
2014-10-05 5:52 ` Leonid Yegoshin
2014-10-06 12:29 ` Paul Burton
2014-10-06 20:42 ` Leonid Yegoshin
2014-10-06 18:05 ` David Daney
2014-10-06 20:03 ` Leonid Yegoshin
2014-10-04 3:17 ` [PATCH 3/3] MIPS: set stack/data protection as non-executable Leonid Yegoshin
2014-10-04 8:23 ` [PATCH 0/3] MIPS executable stack protection Peter Zijlstra
2014-10-04 16:03 ` Linus Torvalds
2014-10-04 16:17 ` Leonid Yegoshin
2014-10-04 16:27 ` Linus Torvalds [this message]
2014-10-04 15:33 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='CA+55aFxqip0m=Ohd-+VDEkzahhLDe+fj9kXY0bbQY8YMBTEc4A@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=James.Hogan@imgtec.com \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=Markos.Chandras@imgtec.com \
--cc=Paul.Burton@imgtec.com \
--cc=Qais.Yousef@imgtec.com \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=akpm@linux-foundation.org \
--cc=alex@alex-smith.me.uk \
--cc=blogic@openwrt.org \
--cc=chenhc@lemote.com \
--cc=david.daney@cavium.com \
--cc=davidlohr@hp.com \
--cc=jchandra@broadcom.com \
--cc=keescook@chromium.org \
--cc=lars.persson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=zajec5@gmail.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).