1. 28 9月, 2005 1 次提交
    • O
      [APPLETALK]: Fix broadcast bug. · 64233bff
      Oliver Dawid 提交于
      From: Oliver Dawid <oliver@helios.de>
      
      we found a bug in net/appletalk/ddp.c concerning broadcast packets. In 
      kernel 2.4 it was working fine. The bug first occured 4 years ago when 
      switching to new SNAP layer handling. This bug can be splitted up into a 
      sending(1) and reception(2) problem:
      
      Sending(1)
      In kernel 2.4 broadcast packets were sent to a matching ethernet device 
      and atalk_rcv() was called to receive it as "loopback" (so loopback 
      packets were shortcutted and handled in DDP layer).
      
      When switching to the new SNAP structure, this shortcut was removed and 
      the loopback packet was send to SNAP layer. The author forgot to replace 
      the remote device pointer by the loopback device pointer before sending 
      the packet to SNAP layer (by calling ddp_dl->request() ) therfor the 
      packet was not sent back by underlying layers to ddp's atalk_rcv().
      
      Reception(2)
      In atalk_rcv() a packet received by this loopback mechanism contains now 
      the (rigth) loopback device pointer (in Kernel 2.4 it was the (wrong) 
      remote ethernet device pointer) and therefor no matching socket will be 
      found to deliver this packet to. Because a broadcast packet should be 
      send to the first matching socket (as it is done in many other protocols 
      (?)), we removed the network comparison in broadcast case.
      
      Below you will find a patch to correct this bug. Its diffed to kernel 
      2.6.14-rc1
      Signed-off-by: NArnaldo Carvalho de Melo <acme@ghostprotocols.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      64233bff
  2. 30 8月, 2005 2 次提交
  3. 21 6月, 2005 1 次提交
  4. 20 4月, 2005 1 次提交
  5. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4