You need to sign in or sign up before continuing.
  1. 07 5月, 2014 1 次提交
    • G
      bignum: allow concurrent BN_MONT_CTX_set_locked() · 12e9f627
      Geoff Thorpe 提交于
      The lazy-initialisation of BN_MONT_CTX was serialising all threads, as
      noted by Daniel Sands and co at Sandia. This was to handle the case that
      2 or more threads race to lazy-init the same context, but stunted all
      scalability in the case where 2 or more threads are doing unrelated
      things! We favour the latter case by punishing the former. The init work
      gets done by each thread that finds the context to be uninitialised, and
      we then lock the "set" logic after that work is done - the winning
      thread's work gets used, the losing threads throw away what they've done.
      Signed-off-by: NGeoff Thorpe <geoff@openssl.org>
      12e9f627
  2. 06 5月, 2014 3 次提交
  3. 05 5月, 2014 1 次提交
  4. 04 5月, 2014 6 次提交
  5. 02 5月, 2014 1 次提交
  6. 01 5月, 2014 2 次提交
  7. 30 4月, 2014 2 次提交
    • G
      bignum: fix boundary condition in montgomery logic · a5292618
      Geoff Thorpe 提交于
      It's not clear whether this inconsistency could lead to an actual
      computation error, but it involved a BIGNUM being passed around the
      montgomery logic in an inconsistent state. This was found using flags
      -DBN_DEBUG -DBN_DEBUG_RAND, and working backwards from this assertion
      in 'ectest';
      
      ectest: bn_mul.c:960: BN_mul: Assertion `(_bnum2->top == 0) ||
      (_bnum2->d[_bnum2->top - 1] != 0)' failed
      Signed-off-by: NGeoff Thorpe <geoff@openssl.org>
      a5292618
    • B
      More warnings. · 9cabf6bb
      Ben Laurie 提交于
      9cabf6bb
  8. 28 4月, 2014 1 次提交
  9. 27 4月, 2014 3 次提交
  10. 26 4月, 2014 5 次提交
  11. 25 4月, 2014 2 次提交
  12. 24 4月, 2014 3 次提交
  13. 23 4月, 2014 1 次提交
  14. 22 4月, 2014 1 次提交
  15. 21 4月, 2014 1 次提交
  16. 16 4月, 2014 3 次提交
  17. 11 4月, 2014 1 次提交
  18. 09 4月, 2014 3 次提交