linux-kernel - Re: [PATCH 00/05] Linux Kernel Markers

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: <20070215141841.6eed5fbb.akpm@linux-foundation.org>
Date:	Thu, 15 Feb 2007 14:18:41 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	fche@...hat.com (Frank Ch. Eigler)
Cc:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	Ingo Molnar <mingo@...hat.com>, systemtap@...rces.redhat.com,
	ltt-dev@...fik.org
Subject: Re: [PATCH 00/05] Linux Kernel Markers - kernel 2.6.20

On 15 Feb 2007 10:28:57 -0500
fche@...hat.com (Frank Ch. Eigler) wrote:

> 
> akpm wrote:
> 
> > [...]  And what can I do with these markers?  And once I've done it,
> > are there any userspace applications I can use to get the data out
> > in human-usable form?  [...]
> 
> The LTTng user-space programs use it today.  Systemtap used to support
> the earlier marker prototype and will be rapidly ported over to this
> new API upon acceptance.
> 

That's good.

It would be beneficial if some people from those projects could spare the
cycles to carefully review and runtime test this code.

Also, I'm not 100% clear on where we ended up with the huge
static-vs-dynamic flamewar.  Did everyone end up happy?  Is this patchset a
reasonable compromise?  Or do we need a rematch?
-
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/