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]
Date:	Thu, 10 Dec 2009 19:16:38 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Frank Ch. Eigler" <fche@...hat.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org,
	utrace-devel <utrace-devel@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC] [PATCH] In-kernel gdbstub based on utrace Infrastructure.


* Frank Ch. Eigler <fche@...hat.com> wrote:

> 
> Ingo Molnar <mingo@...e.hu> writes:
> 
> > [...]  Since the speed of development in this area is truly glacial
> > at the moment and the practical advantages that i can experience
> > personally (directly as a Linux user and indirectly as a maintainer)
> > are miniscule so far, caution is warranted IMO. [...]
> 
> If the "caution" you suggest is operationally equivalent to 
> discouraging even miniscule improvements, is it any wonder that 
> progress is glacial?

I think you might be mixing up cause and causation ;-)

> The gdbstub prototype was constructed for two reasons: to demonstrate 
> utrace usage now, and in the future to be incrementally useful (over 
> ptrace, by moving into fast kernel-space operations like 
> multithreading control, gdb-tracepoint support, other stuff).  #1 is 
> about done.  With respect to #2, we can certainly commit to ongoing 
> work on improvements, provided the community shows interest and 
> goodwill.

What i'd like to see is measurable benefits to users, developers and 
maintainers. I'd like to see the same for SystemTap too btw.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ