1. 10 Jul, 2007 9 commits
  2. 03 Jun, 2007 2 commits
  3. 03 May, 2007 1 commit
  4. 25 Apr, 2007 4 commits
  5. 13 Apr, 2007 1 commit
    • Jerome Borsboom's avatar
      [VLAN]: Allow VLAN interface on top of bridge interface · 279e172a
      Jerome Borsboom authored
      When a VLAN interface is created on top of a bridge interface and 
      netfilter is enabled to see the bridged packets, the packets can be 
      corrupted when passing through the netfilter code. This is caused by the 
      VLAN driver not setting the 'protocol' and 'nh' members of the sk_buff 
      structure. In general, this is no problem as the VLAN interface is mostly 
      connected to a physical ethernet interface which does not use the 
      'protocol' and 'nh' members. For a bridge interface, however, these 
      members do matter.
      Signed-off-by: default avatarJerome Borsboom <j.borsboom@erasmusmc.nl>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  6. 02 Mar, 2007 1 commit
  7. 12 Feb, 2007 1 commit
  8. 11 Feb, 2007 1 commit
  9. 10 Oct, 2006 1 commit
  10. 24 Jul, 2006 1 commit
  11. 21 Jul, 2006 1 commit
  12. 03 Jul, 2006 1 commit
  13. 30 Jun, 2006 1 commit
  14. 20 Mar, 2006 2 commits
    • Herbert Xu's avatar
      [NET]: Replace skb_pull/skb_postpull_rcsum with skb_pull_rcsum · cbb042f9
      Herbert Xu authored
      We're now starting to have quite a number of places that do skb_pull
      followed immediately by an skb_postpull_rcsum.  We can merge these two
      operations into one function with skb_pull_rcsum.  This makes sense
      since most pull operations on receive skb's need to update the
      I've decided to make this out-of-line since it is fairly big and the
      fast path where hardware checksums are enabled need to call
      csum_partial anyway.
      Since this is a brand new function we get to add an extra check on the
      len argument.  As it is most callers of skb_pull ignore its return
      value which essentially means that there is no check on the len
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • Stefan Rompf's avatar
      [VLAN]: translate IF_OPER_DORMANT to netif_dormant_on() · ddd7bf9f
      Stefan Rompf authored
      this patch adds support to the VLAN driver to translate IF_OPER_DORMANT of the
      underlying device to netif_dormant_on(). Beside clean state forwarding, this
      allows running independant userspace supplicants on both the real device and
      the stacked VLAN. It depends on my RFC2863 patch.
      Signed-off-by: default avatarStefan Rompf <stefan@loplof.de>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  15. 11 Jan, 2006 1 commit
  16. 10 Jan, 2006 1 commit
  17. 21 Dec, 2005 1 commit
  18. 14 Dec, 2005 1 commit
  19. 19 Sep, 2005 1 commit
  20. 29 Aug, 2005 1 commit
    • David S. Miller's avatar
      [NET]: Kill skb->real_dev · f2ccd8fa
      David S. Miller authored
      Bonding just wants the device before the skb_bond()
      decapsulation occurs, so simply pass that original
      device into packet_type->func() as an argument.
      It remains to be seen whether we can use this same
      exact thing to get rid of skb->input_dev as well.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  21. 12 Jul, 2005 1 commit
    • Tommy Christensen's avatar
      [VLAN]: Fix early vlan adding leads to not functional device · f4637b55
      Tommy Christensen authored
      OK, I can see what's happening here. eth0 doesn't detect link-up until
      after a few seconds, so when the vlan interface is opened immediately
      after eth0 has been opened, it inherits the link-down state. Subsequently
      the vlan interface is never properly activated and are thus unable to
      transmit any packets.
      dev->state bits are not supposed to be manipulated directly. Something
      similar is probably needed for the netif_device_present() bit, although
      I don't know how this is meant to work for a virtual device.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  22. 11 Jul, 2005 1 commit
    • Sam Ravnborg's avatar
      [NET]: move config options out to individual protocols · 6a2e9b73
      Sam Ravnborg authored
      Move the protocol specific config options out to the specific protocols.
      With this change net/Kconfig now starts to become readable and serve as a
      good basis for further re-structuring.
      The menu structure is left almost intact, except that indention is
      fixed in most cases. Most visible are the INET changes where several
      "depends on INET" are replaced with a single ifdef INET / endif pair.
      Several new files were created to accomplish this change - they are
      small but serve the purpose that config options are now distributed
      out where they belongs.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  23. 01 May, 2005 1 commit
    • Jesper Juhl's avatar
      [PATCH] misc verify_area cleanups · e49332bd
      Jesper Juhl authored
      There were still a few comments left refering to verify_area, and two
      functions, verify_area_skas & verify_area_tt that just wrap corresponding
      access_ok_skas & access_ok_tt functions, just like verify_area does for
      access_ok - deprecate those.
      There was also a few places that still used verify_area in commented-out
      code, fix those up to use access_ok.
      After applying this one there should not be anything left but finally
      removing verify_area completely, which will happen after a kernel release
      or two.
      Signed-off-by: default avatarJesper Juhl <juhl-lkml@dif.dk>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  24. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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!