linux-kernel - Re: [RFC] Fix 2.6.33 x86 regression to kgdb hw breakpoints

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091212135216.GA18597@elte.hu>
Date:	Sat, 12 Dec 2009 14:52:16 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jason Wessel <jason.wessel@...driver.com>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Alan Stern <stern@...land.harvard.edu>,
	"K.Prasad" <prasad@...ux.vnet.ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC] Fix 2.6.33 x86 regression to kgdb hw breakpoints - due to
 perf API changes


* Ingo Molnar <mingo@...e.hu> wrote:

> Hm, the kgdb hw-breakpoint changes freshly put into v2.6.33 look 
> pretty broken: [...]

Sorry - i thought for a moment that it was introduced by this recent 
change:

  7f8b7ed: kgdb: Always process the whole breakpoint list on activate or deactivate

but it's deeper than that indeed.

Basically we have two options:

 A- change kgdb to use the hw-breakpoints highlevel APIs (i'd prefer 
    that)

 B- or keep what we had so far: kgdb overrides existing GDB (and now 
    perf) breakpoints

I havent noticed that hw-breakpoints lock up under kgdb.

	Ingo
--
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/