On Mon, 30 Jun 2008, Stefan Becker wrote:It becomes unusable. In fact, I find it likely that shared IRQs are not safe for random data gathering at all in general. IRQs are not in fact completely random, they just (sometimes) have a very small ammount of randomness in them. And the combined result you see in a shared IRQ line could be correlated or "get somewhat more correlated" because of the sharing (they go over the same BUS -> one can delay the other, etc)... and that correlation might be dangerous. IMO, the safe thing to do is to block shared IRQs from being used as random sources. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh --
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| KAMEZAWA Hiroyuki | Re: 2.6.24-rc3-mm1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jarek Poplawski | Re: [BUG #12364] Re: HTB - very bad precision? HFSC works fine! 2.6.28 |
| Alexey Dobriyan | Re: [GIT]: Networking |
