1. 17 Sep, 2015 1 commit
    • Eric W. Biederman's avatar
      netfilter: Pass net into okfn · 0c4b51f0
      Eric W. Biederman authored
      This is immediately motivated by the bridge code that chains functions that
      call into netfilter.  Without passing net into the okfns the bridge code would
      need to guess about the best expression for the network namespace to process
      packets in.
      
      As net is frequently one of the first things computed in continuation functions
      after netfilter has done it's job passing in the desired network namespace is in
      many cases a code simplification.
      
      To support this change the function dst_output_okfn is introduced to
      simplify passing dst_output as an okfn.  For the moment dst_output_okfn
      just silently drops the struct net.
      Signed-off-by: default avatar"Eric W. Biederman" <ebiederm@xmission.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      0c4b51f0
  2. 07 Apr, 2015 1 commit
    • David Miller's avatar
      netfilter: Pass socket pointer down through okfn(). · 7026b1dd
      David Miller authored
      On the output paths in particular, we have to sometimes deal with two
      socket contexts.  First, and usually skb->sk, is the local socket that
      generated the frame.
      
      And second, is potentially the socket used to control a tunneling
      socket, such as one the encapsulates using UDP.
      
      We do not want to disassociate skb->sk when encapsulating in order
      to fix this, because that would break socket memory accounting.
      
      The most extreme case where this can cause huge problems is an
      AF_PACKET socket transmitting over a vxlan device.  We hit code
      paths doing checks that assume they are dealing with an ipv4
      socket, but are actually operating upon the AF_PACKET one.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      7026b1dd
  3. 06 Mar, 2015 1 commit
    • Eric W. Biederman's avatar
      DECnet: Only use neigh_ops for adding the link layer header · aaa4e704
      Eric W. Biederman authored
      Other users users of the neighbour table use neigh->output as the method
      to decided when and which link-layer header to place on a packet.
      DECnet has been using neigh->output to decide which DECnet headers to
      place on a packet depending which neighbour the packet is destined for.
      
      The DECnet usage isn't totally wrong but it can run into problems if the
      neighbour output function is run for a second time as the teql driver
      and the bridge netfilter code can do.
      
      Therefore to avoid pathologic problems later down the line and make the
      neighbour code easier to understand by refactoring the decnet output
      code to only use a neighbour method to add a link layer header to a
      packet.
      
      This is done by moving the neigbhour operations lookup from
      dn_to_neigh_output to dn_neigh_output_packet.
      Signed-off-by: default avatar"Eric W. Biederman" <ebiederm@xmission.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      aaa4e704
  4. 20 Sep, 2013 1 commit
  5. 20 Mar, 2006 1 commit
    • Steven Whitehouse's avatar
      [DECnet]: Endian annotation and fixes for DECnet. · c4ea94ab
      Steven Whitehouse authored
      The typedef for dn_address has been removed in favour of using __le16
      or __u16 directly as appropriate. All the DECnet header files are
      updated accordingly.
      
      The byte ordering of dn_eth2dn() and dn_dn2eth() are both changed
      since just about all their callers wanted network order rather than
      host order, so the conversion is now done in the functions themselves.
      
      Several missed endianess conversions have been picked up during the
      conversion process. The nh_gw field in struct dn_fib_info has been
      changed from a 32 bit field to 16 bits as it ought to be.
      
      One or two cases of using htons rather than dn_htons in the routing
      code have been found and fixed.
      
      There are still a few warnings to fix, but this patch deals with the
      important cases.
      Signed-off-by: default avatarSteven Whitehouse <steve@chygwyn.com>
      Signed-off-by: default avatarPatrick Caulfield <patrick@tykepenguin.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      c4ea94ab
  6. 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!
      1da177e4