1. 12 Dec, 2010 2 commits
  2. 10 Dec, 2010 12 commits
  3. 09 Dec, 2010 3 commits
    • Thomas Bogendoerfer's avatar
      hso: IP checksuming doesn't work on GE0301 option cards · 6934d335
      Thomas Bogendoerfer authored
      There is definitly a problem, that some option cards send up broken
      IP pakets leading to corrupted IP packets. These corruptions aren't
      detected, because the driver claims that the packets are already
      checksummed. This change removes the CHECKSUM_UNNECESSARY option
      and let IP detect broken data.
      Signed-off-by: default avatarThomas Bogendoerfer <tsbogend@alpha.franken.de>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • Thomas Egerer's avatar
      xfrm: Fix xfrm_state_migrate leak · 78347c8c
      Thomas Egerer authored
      xfrm_state_migrate calls kfree instead of xfrm_state_put to free
      a failed state. According to git commit 553f9118
       this can cause
      memory leaks.
      Signed-off-by: default avatarThomas Egerer <thomas.egerer@secunet.com>
      Signed-off-by: default avatarSteffen Klassert <steffen.klassert@secunet.com>
      Acked-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • Neil Horman's avatar
      net: Convert netpoll blocking api in bonding driver to be a counter · fb4fa76a
      Neil Horman authored
      A while back I made some changes to enable netpoll in the bonding driver.  Among
      them was a per-cpu flag that indicated we were in a path that held locks which
      could cause the netpoll path to block in during tx, and as such the tx path
      should queue the frame for later use.  This appears to have given rise to a
      regression.  If one of those paths on which we hold the per-cpu flag yields the
      cpu, its possible for us to come back on a different cpu, leading to us clearing
      a different flag than we set.  This results in odd netpoll drops, and BUG
      backtraces appearing in the log, as we check to make sure that we only clear set
      bits, and only set clear bits.  I had though briefly about changing the
      offending paths so that they wouldn't sleep, but looking at my origional work
      more closely, it doesn't appear that a per-cpu flag is warranted.  We alrady
      gate the checking of this flag on IFF_IN_NETPOLL, so we don't hit this in the
      normal tx case anyway.  And practically speaking, the normal use case for
      netpoll is to only have one client anyway, so we're not going to erroneously
      queue netpoll frames when its actually safe to do so.  As such, lets just
      convert that per-cpu flag to an atomic counter.  It fixes the rescheduling bugs,
      is equivalent from a performance perspective and actually eliminates some code
      in the process.
      Tested by the reporter and myself, successfully
      Reported-by: default avatarLiang Zheng <lzheng@redhat.com>
      CC: Jay Vosburgh <fubar@us.ibm.com>
      CC: Andy Gospodarek <andy@greyhouse.net>
      CC: David S. Miller <davem@davemloft.net>
      Signed-off-by: default avatarNeil Horman <nhorman@tuxdriver.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  4. 08 Dec, 2010 23 commits