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  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:	Wed, 30 Mar 2016 23:39:09 -0400
From:	Willem de Bruijn <>
To:	Soheil Hassas Yeganeh <>
Cc:	David Miller <>,
	Network Development <>,
	Willem de Bruijn <>,
	Eric Dumazet <>,
	Yuchung Cheng <>,
	Neal Cardwell <>,
	Martin KaFai Lau <>,
	Soheil Hassas Yeganeh <>
Subject: Re: [PATCH net-next 7/8] sock: enable timestamping using control messages

On Wed, Mar 30, 2016 at 6:37 PM, Soheil Hassas Yeganeh
<> wrote:
> From: Soheil Hassas Yeganeh <>
> Currently, SOL_TIMESTAMPING can only be enabled using setsockopt.
> This is very costly when users want to sample writes to gather
> tx timestamps.
> Add support for enabling SO_TIMESTAMPING via control messages by
> using tsflags added in `struct sockcm_cookie` (added in the previous
> patches in this series) to set the tx_flags of the last skb created in
> a sendmsg. With this patch, the timestamp recording bits in tx_flags
> of the skbuff is overridden if SO_TIMESTAMPING is passed in a cmsg.
> Please note that this is only effective for overriding the recording
> timestamps flags. Users should enable timestamp reporting (e.g.,
> socket options and then should ask for SOF_TIMESTAMPING_TX_*
> using control messages per sendmsg to sample timestamps for each
> write.
> Signed-off-by: Soheil Hassas Yeganeh <>

Acked-by: Willem de Bruijn <>

Powered by blists - more mailing lists