netdev - RE: [PATCH v2 0/2] Tracepoint for tcp retransmission

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]

Date:	Fri, 3 Feb 2012 15:31:48 -0500
From:	Satoru Moriya <satoru.moriya@....com>
To:	Eric Dumazet <eric.dumazet@...il.com>,
	Hagen Paul Pfeifer <hagen@...u.net>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"davem@...emloft.net" <davem@...emloft.net>,
	"nhorman@...driver.com" <nhorman@...driver.com>,
	"tgraf@...radead.org" <tgraf@...radead.org>,
	Stephen Hemminger <stephen.hemminger@...tta.com>,
	Seiji Aguchi <seiji.aguchi@....com>
Subject: RE: [PATCH v2 0/2] Tracepoint for tcp retransmission

On 01/25/2012 09:44 AM, Eric Dumazet wrote:
> Agreed, but last time I tried systemtap I failed miserably.
> It was on a debian distro.
> 
> Anyway, it seems we lack a LINUX_MIB_TCPRETRANSFAIL counter.
> 
> "netstat -s" is an incredible universal tool.
> 
> [PATCH net-next] tcp: add LINUX_MIB_TCPRETRANSFAIL counter
> 
> It might be useful to get a counter of failed tcp_retransmit_skb() 
> calls.

Thank you, Eric.

This is a good first step for us to grab the failure of
retransmission. But unfortunately, it's not enough because
when we analyze incidents and report to our customers,
we need more detailed information such as when it happened,
why it failed etc.

Therefore I proposed this tracepoint.

Regards,
Satoru