linux-kernel - Re: [PATCH 3/6] x86: Allow the user not to build hw

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 4 May 2011 01:54:36 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Jason Wessel <jason.wessel@...driver.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 3/6] x86: Allow the user not to build hw_breakpoints

On Tue, May 03, 2011 at 04:40:14PM -0700, H. Peter Anvin wrote:
> On 05/03/2011 04:12 PM, Frederic Weisbecker wrote:
> >>
> >> It really is very bad... without breakpoints, you lose almost all
> >> debugging support.
> > 
> > Right, so it should be fine for embedded environment to disable breakpoints.
> > It depends on CONFIG_EXPERT now.
> 
> Uh... even embedded environments need to be able to debug.

For development yeah, but is it needed for production evironments?

May be sometimes. But even though, the main functionalities of
ptrace are still available since instruction breakpoints are
implemented through int3 and not debugreg in ptrace. Only data
breakpoints would be unusable, but I believe they are a minor use compared
to instruction breakpoints. I rarely make use of them for debugging
personally.

That's really deemed for specific cases where people know what
they are doing.
--
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/