1. 09 2月, 2007 1 次提交
    • P
      [NETLINK]: Don't BUG on undersized allocations · 26932566
      Patrick McHardy 提交于
      Currently netlink users BUG when the allocated skb for an event
      notification is undersized. While this is certainly a kernel bug,
      its not critical and crashing the kernel is too drastic, especially
      when considering that these errors have appeared multiple times in
      the past and it BUGs even if no listeners are present.
      
      This patch replaces BUG by WARN_ON and changes the notification
      functions to inform potential listeners of undersized allocations
      using a unique error code (EMSGSIZE).
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      26932566
  2. 26 1月, 2007 1 次提交
  3. 11 12月, 2006 1 次提交
  4. 08 12月, 2006 2 次提交
  5. 03 12月, 2006 15 次提交
  6. 08 11月, 2006 1 次提交
  7. 19 10月, 2006 1 次提交
  8. 16 10月, 2006 1 次提交
  9. 12 10月, 2006 2 次提交
    • P
      [DECNET]: Fix sfuzz hanging on 2.6.18 · 52c41a32
      Patrick McHardy 提交于
      Dave Jones wrote:
      > sfuzz         D 724EF62A  2828 28717  28691                     (NOTLB)
      >        cd69fe98 00000082 0000012d 724ef62a 0001971a 00000010 00000007 df6d22b0 
      >        dfd81080 725bbc5e 0001971a 000cc634 00000001 df6d23bc c140e260 00000202 
      >        de1d5ba0 cd69fea0 de1d5ba0 00000000 00000000 de1d5b60 de1d5b8c de1d5ba0 
      > Call Trace:
      >  [<c05b1708>] lock_sock+0x75/0xa6
      >  [<e0b0b604>] dn_getname+0x18/0x5f [decnet]
      >  [<c05b083b>] sys_getsockname+0x5c/0xb0
      >  [<c05b0b46>] sys_socketcall+0xef/0x261
      >  [<c0403f97>] syscall_call+0x7/0xb
      > DWARF2 unwinder stuck at syscall_call+0x7/0xb
      > 
      > I wonder if the plethora of lockdep related changes inadvertantly broke something?
      
      Looks like unbalanced locking.
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      52c41a32
    • D
      [NET]: Do not memcmp() over pad bytes of struct flowi. · 8238b218
      David S. Miller 提交于
      They are not necessarily initialized to zero by the compiler,
      for example when using run-time initializers of automatic
      on-stack variables.
      
      Noticed by Eric Dumazet and Patrick McHardy.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8238b218
  10. 23 9月, 2006 15 次提交