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: <20090127.102141.99756103.davem@davemloft.net>
Date:	Tue, 27 Jan 2009 10:21:41 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	hch@...radead.org
Cc:	nhorman@...driver.com, netdev@...r.kernel.org
Subject: Re: [PATCH] net: add tracepoints to socket api

From: Christoph Hellwig <hch@...radead.org>
Date: Tue, 27 Jan 2009 12:23:23 -0500

> On Tue, Jan 27, 2009 at 09:20:17AM -0800, David Miller wrote:
> > We're merging this stuff to solve the chicken and egg
> > problem wherein the lttng tree merge is basically
> > stalled.
> > 
> > If the individual subsystem annotations go in, the hope
> > is that they'll have less to merge and thus it's more likely
> > to actually happen.
> 
> I'm rather concerned as I haven't seen any progress on the lttng core
> lately.  I'd really prefer to have a version in close to mergeable shape
> first, that's actively beeing pushed.  Adding the instrumentation is
> trivial as seen by this small patch, but getting the core right (and who
> knows if that involves changing the way actual instrumentation works, it's
> not like that hasn't changed n million times yet) is essential.

The block layer already merged trace annotations.  I therefore see no
harm in merging the net bits.

If you disagree, either submit a revert of the block layer
annotations, or content yourself in being a hypocrite :-)
--
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