netdev - Re: [PATCH] net: add tracepoints to socket api

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: <20090127171857.GB14429@infradead.org>
Date:	Tue, 27 Jan 2009 12:18:57 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	Neil Horman <nhorman@...driver.com>
Cc:	netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: [PATCH] net: add tracepoints to socket api

On Mon, Jan 26, 2009 at 02:59:30PM -0500, Neil Horman wrote:
> Hey all-
> 	I've been working for a bit with the various tracepoints that have been
> developed in the lttng tree.  The infrastructure is available in the main line
> kernel.  All thats missing are the tracepoints themselves.  While some seem to
> be contentious for various reasons, most seem benign, and can be rather usefull,
> so I was thinking we could start importing Some for the net stack.  Heres a
> patch for the top level socket api tracepoints.  If these are acceptable, I'll
> begin porting over the rest for the remainder of the network stack.   This patch
> applies cleanly against the net-next tree.

Do we now have lttng in linux-next?  Otherwise these trace point would
be useless there without more patching.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html