1. 27 5月, 2014 1 次提交
    • D
      e1000e: Failure to write SHRA turns on PROMISC mode · b3e5bf1f
      David Ertman 提交于
      Previously, the check to turn on promiscuous mode only took into account
      the total number of SHared Receive Address (SHRA) registers and if the
      request was for a register within that range.  It is possible that the
      Management Engine might have locked a number of SHRA and not allowed a
      new address to be written to the requested register.
      
      Add a function to determine the number of unlocked SHRA registers.  Then
      determine if the number of registers available is sufficient for our needs,
      if not then return -ENOMEM so that UNICAST PROMISC mode is activated.
      
      Since the method by which ME claims SHRA registers is non-deterministic,
      also add a return value to the function attempting to write an address
      to a SHRA, and return a -E1000_ERR_CONFIG if the write fails.  The error
      will be passed up the function chain and allow the driver to also set
      UNICAST PROMISC when this happens.
      
      Cc: Vlad Yasevich <vyasevic@redhat.com>
      Signed-off-by: NDave Ertman <davidx.m.ertman@intel.com>
      Tested-by: NAaron Brown <aaron.f.brown@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      b3e5bf1f
  2. 08 3月, 2014 1 次提交
  3. 05 2月, 2013 1 次提交