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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 30 Mar 2016 23:36:30 -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 4/8] sock: accept SO_TIMESTAMPING flags in socket cmsg

On Wed, Mar 30, 2016 at 6:37 PM, Soheil Hassas Yeganeh
<> wrote:
> From: Soheil Hassas Yeganeh <>
> Accept SO_TIMESTAMPING in control messages of the SOL_SOCKET level
> as a basis to accept timestamping requests per write.
> This implementation only accepts TX recording flags (i.e.,
> control messages. Users need to set reporting flags (e.g.,
> SOF_TIMESTAMPING_OPT_ID) per socket via socket options.
> This commit adds a tsflags field in sockcm_cookie which is
> set in __sock_cmsg_send. It only override the SOF_TIMESTAMPING_TX_*
> bits in sockcm_cookie.tsflags allowing the control message
> to override the recording behavior per write, yet maintaining
> the value of other flags.
> This patch implements validating the control message and setting
> tsflags in struct sockcm_cookie. Next commits in this series will
> actually implement timestamping per write for different protocols.
> Signed-off-by: Soheil Hassas Yeganeh <>

Acked-by: Willem de Bruijn <>

Powered by blists - more mailing lists