[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrXDZDfc2iGsn_UAgVsyGsUh5yj76E+=h3g9sK8LW5kE_A@mail.gmail.com>
Date: Wed, 6 Jul 2016 07:32:26 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Dmitry Safonov <dsafonov@...tuozzo.com>,
Pedro Alves <palves@...hat.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Dmitry Safonov <0x7f454c46@...il.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Ingo Molnar <mingo@...hat.com>,
Cyrill Gorcunov <gorcunov@...nvz.org>, xemul@...tuozzo.com,
Oleg Nesterov <oleg@...hat.com>,
Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>
Subject: Re: [PATCHv2 5/6] x86/ptrace: down with test_thread_flag(TIF_IA32)
On Wed, Jun 29, 2016 at 3:57 AM, Dmitry Safonov <dsafonov@...tuozzo.com> wrote:
> As the task isn't executing at the moment of {GET,SET}REGS,
> return regset that corresponds to code selector, rather than
> value of TIF_IA32 flag.
> I.e. if we ptrace i386 elf binary that has just changed it's
> code selector to __USER_CS, than GET_REGS will return
> full x86_64 register set.
Pedro, I think this will cause gdb to be a little less broken than it
is now. Am I right? Will this break anything?
--Andy
Powered by blists - more mailing lists