Re: [PATCH] NET : secure sequence number functions can use nsec resolution instead of usec
From: David Miller <davem@davemloft.net>
Date: 2007-03-28 21:22:54
From: David Miller <davem@davemloft.net>
Date: 2007-03-28 21:22:54
From: James Morris <jmorris@namei.org> Date: Wed, 28 Mar 2007 12:31:56 -0400 (EDT)
On Wed, 28 Mar 2007, Eric Dumazet wrote:quoted
Hello David We could use the nanosec resolution for various functions defined in drivers/char/random.c (secure_tcpv6_sequence_number(), secure_tcp_sequence_number(), secure_dccp_sequence_number()) I am not sure if it's a netdev related patch or core kernel, so I have CC Andrew. Thank you [PATCH] NET : random functions can use nsec resolution instead of usec In order to get more randomness for secure_tcpv6_sequence_number(), secure_tcp_sequence_number(), secure_dccp_sequence_number() functions, we can use the high resolution time services, providing nanosec resolution. I've also done two kmalloc()/kzalloc() conversions. Signed-off-by: Eric Dumazet <redacted>Looks good to me. Acked-by: James Morris <jmorris@namei.org>
To me too, patch applied, thanks everyone.