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: <20141216.174524.888376617592272638.davem@davemloft.net>
Date:	Tue, 16 Dec 2014 17:45:24 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	jbaron@...mai.com
Cc:	jbacik@...com, eric.dumazet@...il.com,
	alexei.starovoitov@...il.com, chavey@...gle.com, ycheng@...gle.com,
	kafai@...com, netdev@...r.kernel.org, hannes@...essinduktion.org,
	rostedt@...dmis.org, brakmo@...com, Kernel-team@...com
Subject: Re: [RFC PATCH net-next 0/5] tcp: TCP tracer

From: Jason Baron <jbaron@...mai.com>
Date: Tue, 16 Dec 2014 17:40:47 -0500

> We are interested in tcp tracing as well. Another requirement that
> we have that I don't think I saw is the ability to start/stop
> tracing on sockets (potentially multiple times) during the lifetime
> of a connection. So for example, the ability to use setsockopt(), to
> selectively start/stop tracing on a connection, so as not to incur
> overhead for non-traced sockets.

This is so backwards.

You make the tracing cheap enough that this can never be an issue.

Your requirement can only exist if the implementation is broken
by design.
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ