1. 30 4月, 2011 1 次提交
  2. 14 4月, 2011 1 次提交
  3. 31 3月, 2011 1 次提交
  4. 15 3月, 2011 2 次提交
  5. 12 3月, 2011 4 次提交
  6. 08 3月, 2011 1 次提交
  7. 03 3月, 2011 1 次提交
  8. 24 2月, 2011 3 次提交
  9. 12 2月, 2011 1 次提交
  10. 24 1月, 2011 1 次提交
  11. 25 12月, 2010 4 次提交
  12. 12 12月, 2010 1 次提交
  13. 11 12月, 2010 1 次提交
  14. 28 11月, 2010 1 次提交
  15. 28 10月, 2010 1 次提交
  16. 21 10月, 2010 2 次提交
  17. 18 10月, 2010 1 次提交
  18. 15 10月, 2010 1 次提交
  19. 28 9月, 2010 1 次提交
  20. 27 9月, 2010 1 次提交
  21. 23 9月, 2010 3 次提交
  22. 03 9月, 2010 1 次提交
  23. 26 8月, 2010 1 次提交
  24. 19 8月, 2010 1 次提交
  25. 09 8月, 2010 2 次提交
    • S
      Fix spelling fuction -> function in comments · eef35c2d
      Stefan Weil 提交于
      To avoid more patches, I also fixed other spelling
      and grammar bugs when they were in the same or
      following line:
      
      successfull -> successful
      parse -> parses
      controler -> controller
      controlers -> controllers
      
      Cc: Jiri Kosina <trivial@kernel.org>
      Cc: linux-kernel@vger.kernel.org
      Signed-off-by: NStefan Weil <weil@mail.berlios.de>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      eef35c2d
    • J
      e100/e1000*/igb*/ixgb*: Add missing read memory barrier · 2d0bb1c1
      Jeff Kirsher 提交于
      Based on patches from Sonny Rao and Milton Miller...
      
      Combined the patches to fix up clean_tx_irq and clean_rx_irq.
      
      The PowerPC architecture does not require loads to independent bytes
      to be ordered without adding an explicit barrier.
      
      In ixgbe_clean_rx_irq we load the status bit then load the packet data.
      With packet split disabled if these loads go out of order we get a
      stale packet, but we will notice the bad sequence numbers and drop it.
      
      The problem occurs with packet split enabled where the TCP/IP header
      and data are in different descriptors. If the reads go out of order
      we may have data that doesn't match the TCP/IP header. Since we use
      hardware checksumming this bad data is never verified and it makes it
      all the way to the application.
      
      This bug was found during stress testing and adding this barrier has
      been shown to fix it.  The bug can manifest as a data integrity issue
      (bad payload data) or as a BUG in skb_pull().
      
      This was a nasty bug to hunt down, if people agree with the fix I think
      it's a candidate for stable.
      
      Previously Submitted to e1000-devel only for ixgbe
      
      http://marc.info/?l=e1000-devel&m=126593062701537&w=3
      
      We've now seen this problem hit with other device drivers (e1000e mostly)
      So I'm resubmitting with fixes for other Intel Device Drivers with
      similar issues.
      
      CC: Milton Miller <miltonm@bga.com>
      CC: Anton Blanchard <anton@samba.org>
      CC: Sonny Rao <sonnyrao@us.ibm.com>
      CC: stable <stable@kernel.org>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2d0bb1c1
  26. 03 8月, 2010 1 次提交
  27. 22 7月, 2010 1 次提交