1. 27 9月, 2016 4 次提交
  2. 16 9月, 2016 4 次提交
  3. 15 9月, 2016 18 次提交
  4. 13 9月, 2016 1 次提交
  5. 10 9月, 2016 1 次提交
  6. 08 9月, 2016 1 次提交
  7. 03 9月, 2016 1 次提交
  8. 31 8月, 2016 6 次提交
  9. 30 8月, 2016 1 次提交
  10. 24 8月, 2016 1 次提交
  11. 31 7月, 2016 1 次提交
    • M
      random: Fix crashes with sparse node ids · dd0f0cf5
      Michael Ellerman 提交于
      On a system with sparse node ids, eg. a powerpc system with 4 nodes
      numbered like so:
      
        node   0: [mem 0x0000000000000000-0x00000007ffffffff]
        node   1: [mem 0x0000000800000000-0x0000000fffffffff]
        node  16: [mem 0x0000001000000000-0x00000017ffffffff]
        node  17: [mem 0x0000001800000000-0x0000001fffffffff]
      
      The code in rand_initialize() will allocate 4 pointers for the pool
      array, and initialise them correctly.
      
      However when go to use the pool, in eg. extract_crng(), we use the
      numa_node_id() to index into the array. For the higher numbered node ids
      this leads to random memory corruption, depending on what was kmalloc'ed
      adjacent to the pool array.
      
      Fix it by using nr_node_ids to size the pool array.
      
      Fixes: 1e7f583a ("random: make /dev/urandom scalable for silly userspace programs")
      Signed-off-by: NMichael Ellerman <mpe@ellerman.id.au>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      dd0f0cf5
  12. 28 7月, 2016 1 次提交