On Thu, 24 Jul 2014, Theodore Ts'o wrote: > ERRORS > EINVAL An invalid flag was passed to getrandom(2) > > EFAULT buf is outside the accessible address space. > > EAGAIN The requested entropy was not available, and > getentropy(2) would have blocked if GRND_BLOCK flag > was set. > > EINTR While blocked waiting for entropy, the call was > interrupted by a signal handler; see the description > of how interrupted read(2) calls on "slow" devices > are handled with and without the SA_RESTART flag > in the signal(7) man page. Should we add E<SOMETHING> to be able to deny access to GRND_RANDOM or some future extension ? -- "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 -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
