From: David Miller <davem@davemloft.net>
To: jmorris@namei.org
Cc: dada1@cosmosbay.com, andi@firstfloor.org, netdev@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] NET : secure sequence number functions can use nsec resolution instead of usec
Date: Wed, 28 Mar 2007 14:22:54 -0700 (PDT) [thread overview]
Message-ID: <20070328.142254.94073845.davem@davemloft.net> (raw)
In-Reply-To: <Line.LNX.4.64.0703281231200.3715@d.namei>
From: James Morris <jmorris@namei.org>
Date: Wed, 28 Mar 2007 12:31:56 -0400 (EDT)
> On Wed, 28 Mar 2007, Eric Dumazet wrote:
>
> > 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 <dada1@cosmosbay.com>
>
> Looks good to me.
>
> Acked-by: James Morris <jmorris@namei.org>
To me too, patch applied, thanks everyone.
next prev parent reply other threads:[~2007-03-28 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 15:43 [PATCH] NET : secure sequence number functions can use nsec resolution instead of usec Eric Dumazet
2007-03-28 16:31 ` James Morris
2007-03-28 21:22 ` David Miller [this message]
2007-03-28 16:41 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070328.142254.94073845.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=dada1@cosmosbay.com \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).