[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57740440.9090302@nextfour.com>
Date: Wed, 29 Jun 2016 20:24:16 +0300
From: Mika Penttilä <mika.penttila@...tfour.com>
To: Andy Lutomirski <luto@...nel.org>, <x86@...nel.org>
CC: <linux-kernel@...r.kernel.org>, <linux-arch@...r.kernel.org>, Borislav
Petkov <bp@...en8.de>, Nadav Amit <nadav.amit@...il.com>, Kees Cook
<keescook@...omium.org>, Brian Gerst <brgerst@...il.com>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
Linus Torvalds <torvalds@...ux-foundation.org>, Josh Poimboeuf
<jpoimboe@...hat.com>, Jann Horn <jann@...jh.net>, Heiko Carstens
<heiko.carstens@...ibm.com>
Subject: Re: [PATCH v4 00/29] virtually mapped stacks and thread_info cleanup
On 29.06.2016 10:06, Mika Penttilä wrote:
> On 06/27/2016 12:55 AM, Andy Lutomirski wrote:
>> Hi all-
>>
>> Known issues:
>> - tcp md5, virtio_net, and virtio_console will have issues. Eric Dumazet
>> has a patch for tcp md5, and Michael Tsirkin says he'll fix virtio_net
>> and virtio_console.
>>
> How about PTRACE_SETREGS, it's using the child stack's vmapped address to put regs?
>
> --Mika
>
PTRACE_SETREGS is ok of course.
--Mika
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
