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] [day] [month] [year] [list]
Date:	Tue, 16 Mar 2010 18:24:58 -0000
From:	"MacCana, Mike" <mike.maccana@...dit-suisse.com>
To:	<linux-kernel@...r.kernel.org>
Subject: RE: Seeing TCP socket options (nodelay, cork, etc) in Linux procfs or elsewhere?

-----Original Message-----
From: Eric Dumazet [mailto:eric.dumazet@...il.com]
Sent: 15 March 2010 16:21
To: MacCana, Mike
Cc: linux-kernel@...r.kernel.org
Subject: Re: Seeing TCP socket options (nodelay, cork, etc) in Linux procfs or elsewhere?

>>Le lundi 15 mars 2010 à 15:49 +0000, MacCana, Mike a écrit :
>>> Hi kernel folks,
>>>  
>>> I was wondering if there was a standard location to see TCP socket 
>>> options (eg, nodelay, cork, etc), perhaps via procfs or some other 
>>> means? I'd like to check whether arbitrary apps (for which I don't 
>>> have
>>> code) are using particular TCP options. 

> the SystemTap Networking Tapset provides a tcp.setsockopt breakpoint which I can use.
> Mike

Here's the tap I used (included for anyone reading on a list archive if there's still no /proc implementation):

sockettest.stap
# Show sockets setting options
probe begin
{
	print ("\nChecking for apps making socket calls\n")
}
probe tcp.setsockopt
{
	printf ("  App '%s' (PID %d) set socket with args %s \n", execname(), pid(), optstr)
}

Mike

=============================================================================== 
 Please access the attached hyperlink for an important electronic communications disclaimer: 
 http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html 
 =============================================================================== 
 
--
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