If anyone has the same compile pronlem, move the "random_nonce"
definition up 10 lines to before the definition of extract_buf().
It compiles (and boots; I'm running it right now) for me as posted;
I'm not sure what the difference is. Compiler version? I'm running
gcc 5.2.1.
--
To unsubscribe
Hi George,
[auto build test ERROR on v4.3-rc5 -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/George-Spelvin/Alternate-sclable-urandom-patchset/20151016-133627
config: x86_64-randconfig-x010-10130227
Hi George,
[auto build test ERROR on v4.3-rc5 -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/George-Spelvin/Alternate-sclable-urandom-patchset/20151016-133627
config: i386-randconfig-i1-201541 (attached
Hi George,
[auto build test ERROR on v4.3-rc5 -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/George-Spelvin/Alternate-sclable-urandom-patchset/20151016-133627
config: i386-randconfig-i1-201541 (attached
Hi George,
[auto build test ERROR on v4.3-rc5 -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/George-Spelvin/Alternate-sclable-urandom-patchset/20151016-133627
config: x86_64-randconfig-x010-10130227
If anyone has the same compile pronlem, move the "random_nonce"
definition up 10 lines to before the definition of extract_buf().
It compiles (and boots; I'm running it right now) for me as posted;
I'm not sure what the difference is. Compiler version? I'm running
gcc 5.2.1.
--
To unsubscribe
Anti-backtracking is only required on read request boundaries, not on
each few bytes of output.
This reduces contention on the pool lock. Without mixback for each
block of output, some other mechanism must guarantee the hash result
will change each time the pool is hashed. This is provided by
Anti-backtracking is only required on read request boundaries, not on
each few bytes of output.
This reduces contention on the pool lock. Without mixback for each
block of output, some other mechanism must guarantee the hash result
will change each time the pool is hashed. This is provided by
8 matches
Mail list logo