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] [day] [month] [year] [list]
Date:	Wed, 4 May 2011 02:13:29 +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:56:03PM -0700, H. Peter Anvin wrote:
> On 05/03/2011 04:54 PM, Frederic Weisbecker wrote:
> > 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?
> > 
> 
> Most of the time people don't want to debug something other than they're
> going to ship.


Well, it's like systems that don't care about having BUG(), sysctl, futexes, etc...
support in the kernel, or whatever standard feature that makes sense most of the time
but sometimes you simply don't need it.

Also consider that as a first step to be able to build a !CONFIG_PERF_EVENTS
kernel. If people show strong interest in beeing able to build a kernel
with breakpoints but without perf events, then I'll invest more efforts in
breaking the dependency.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ