1. 28 6月, 2017 1 次提交
  2. 02 6月, 2017 1 次提交
  3. 05 5月, 2017 5 次提交
  4. 29 4月, 2017 6 次提交
  5. 26 4月, 2017 1 次提交
  6. 21 4月, 2017 3 次提交
  7. 06 4月, 2017 2 次提交
  8. 19 2月, 2017 4 次提交
  9. 12 12月, 2016 1 次提交
  10. 16 11月, 2016 8 次提交
  11. 02 10月, 2016 5 次提交
  12. 03 9月, 2016 2 次提交
  13. 23 8月, 2016 1 次提交
    • M
      IB/hfi1: Improve J_KEY generation · 08fe16f6
      Mitko Haralanov 提交于
      Previously, J_KEY generation was based on the lower 16 bits
      of the user's UID. While this works, it was not good enough
      as a non-root user could collide with a root user given a
      sufficiently large UID.
      
      This patch attempt to improve the J_KEY generation by using
      the following algorithm:
      
      The 16 bit J_KEY space is partitioned into 3 separate spaces
      reserved for different user classes:
         * all users with administtor privileges (including 'root')
           will use J_KEYs in the range of 0 to 31,
         * all kernel protocols, which use KDETH packets will use
           J_KEYs in the range of 32 to 63, and
         * all other users will use J_KEYs in the range of 64 to
           65535.
      
      The above separation is aimed at preventing different user levels
      from sending packets to each other and, additionally, separate
      kernel protocols from all other types of users. The later is meant
      to prevent the potential corruption of kernel memory by any other
      type of user.
      Reviewed-by: NIra Weiny <ira.weiny@intel.com>
      Signed-off-by: NMitko Haralanov <mitko.haralanov@intel.com>
      Signed-off-by: NDennis Dalessandro <dennis.dalessandro@intel.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      08fe16f6