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] [day] [month] [year] [list]
Date:	Sun, 6 Apr 2008 04:27:20 +0300
From:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
To:	Mathieu Desnoyers <compudj@...stal.dyndns.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Tom Zanussi <zanussi@...ibm.com>
Subject: Re: [PATCH] relay: add buffer-only functionality, allowing for
 early kernel tracing

On Fri, 4 Apr 2008 12:40:22 -0400
Mathieu Desnoyers <compudj@...stal.dyndns.org> wrote:

> As far as I am concerned, I can only merge this in the LTTng project
> to try it. I've added Tom Zanussi, the author of relay, who might
> have some ideas to share with us. I would wait until we have a more
> precise idea of the API before I modify LTTng to start using it.
> 
> Regards,
> 
> Mathieu

Hi,

I've tested my patch a bit more and ran into a problem, and fixed it.
Forget the old patch, it will panic the kernel if it has to cross
sub-buffer boundaries. I'll polish the new one a bit (maybe update the
docs) and resubmit, along with a piece of code from my GSoC project that
uses the early relay interface (may provide an easy to try demo).

Unfortunately, as for doing earlier than kmem_cache_init() tracing, I
don't have the time right now, as I have to carry on with my GSoC
project. I looked through the source more thoroughly and the needed
changes are not trivial at all. I'm not saying I won't work on it, but
it won't be a priority.

By the way, I got a "delivery failure" message... is something wrong
with Tom Zanussi's e-mail address? Google showed 2007 LKML entries with
his e-mail address as <zanussi at comcast dot net>. In any case, when
I'll resubmit the patch, I'll add this other address in the Cc list. Or
should we reach him another way?

I'd like to get this merged as it is so far, and mailing it directly to
akpm (or worse, Linus) doesn't sound like a good idea.


Cheers,
Eduard
--
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