[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130417045703.GA29524@host2.jankratochvil.net>
Date: Wed, 17 Apr 2013 06:57:03 +0200
From: Jan Kratochvil <jan.kratochvil@...hat.com>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Alan Stern <stern@...land.harvard.edu>,
Ingo Molnar <mingo@...e.hu>,
Maneesh Soni <maneesh@...ux.vnet.ibm.com>,
Prasad <prasad@...ux.vnet.ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] ptrace/x86: simplify ptrace_write_dr7()
On Tue, 16 Apr 2013 15:25:45 +0200, Oleg Nesterov wrote:
> On 04/16, Frederic Weisbecker wrote:
> > On Sun, Apr 14, 2013 at 09:12:05PM +0200, Oleg Nesterov wrote:
> > Looking at the bug report, it seems they only reproduced with a homemade
> > test. No real app has reported that issue?
>
> iirc (Jan can correct me) gdb hit this problem, but it was already
> changed to change DR0 first.
Both old GDB and recent GDB handle it correctly (DR0 first, then DR7).
I do not remember how but I have hit this issue, probably during development
of the GDB watchpoint code, there were many variants of it in the past.
So it was not found just by an artificial testing.
My concern was not so much about GDB but rather about possible other existing
debugging/tracing software using DR.
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists