[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cryptokit.Random unsuitable in cooperative multithreaded systems

To: Daniel Bünzli <daniel.buenzli@xxxxxxxxxxxx>
From: Thomas Gazagnaire <thomas@xxxxxxxxxxxxxx>
Date: Tue, 23 Apr 2013 21:36:45 +0200
Cc: "Vincent B." <vb@xxxxxxxxx>, cl-mirage@xxxxxxxxxxxxxxx
List-id: MirageOS development <cl-mirage.lists.cam.ac.uk>

> Besides the code really looks toyish, it seems to be allocation hell in 
> there. But it can make nice pseudo-code to read the spec.  

indeed, the (^) loop is devil :p

References:
- Cryptokit.Random unsuitable in cooperative multithreaded systems
  - From: David Sheets
- Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
  - From: Anil Madhavapeddy
- Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
  - From: Vincent Bernardoff
- Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
  - From: Anil Madhavapeddy
- Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
  - From: Thomas Gazagnaire
- Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
  - From: Anil Madhavapeddy
- Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
  - From: Vincent B.
- Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
  - From: Daniel BÃnzli

Prev by Date: Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
Next by Date: Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
Previous by thread: Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
Next by thread: Re: Cryptokit.Random unsuitable in cooperative multithreaded systems
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.