1. 23 3月, 2006 1 次提交
  2. 22 3月, 2006 2 次提交
    • S
      [X25]: allow ITU-T DTE facilities for x25 · a64b7b93
      Shaun Pereira 提交于
      Allows use of the optional user facility to insert ITU-T
      (http://www.itu.int/ITU-T/) specified DTE facilities in call set-up x25
      packets.  This feature is optional; no facilities will be added if the ioctl
      is not used, and call setup packet remains the same as before.
      
      If the ioctls provided by the patch are used, then a facility marker will be
      added to the x25 packet header so that the called dte address extension
      facility can be differentiated from other types of facilities (as described in
      the ITU-T X.25 recommendation) that are also allowed in the x25 packet header.
      
      Facility markers are made up of two octets, and may be present in the x25
      packet headers of call-request, incoming call, call accepted, clear request,
      and clear indication packets.  The first of the two octets represents the
      facility code field and is set to zero by this patch.  The second octet of the
      marker represents the facility parameter field and is set to 0x0F because the
      marker will be inserted before ITU-T type DTE facilities.
      
      Since according to ITU-T X.25 Recommendation X.25(10/96)- 7.1 "All networks
      will support the facility markers with a facility parameter field set to all
      ones or to 00001111", therefore this patch should work with all x.25 networks.
      
      While there are many ITU-T DTE facilities, this patch implements only the
      called and calling address extension, with placeholders in the
      x25_dte_facilities structure for the rest of the facilities.
      
      Testing:
      
      This patch was tested using a cisco xot router connected on its serial ports
      to an X.25 network, and on its lan ports to a host running an xotd daemon.
      
      It is also possible to test this patch using an xotd daemon and an x25tap
      patch, where the xotd daemons work back-to-back without actually using an x.25
      network.  See www.fyonne.net for details on how to do this.
      Signed-off-by: NShaun Pereira <spereira@tusc.com.au>
      Acked-by: NAndrew Hendry <ahendry@tusc.com.au>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a64b7b93
    • S
      [NET]: socket timestamp 32 bit handler for 64 bit kernel · f0ac2614
      Shaun Pereira 提交于
      Get socket timestamp handler function that does not use the
      ioctl32_hash_table.
      Signed-off-by: NShaun Pereira <spereira@tusc.com.au>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f0ac2614
  3. 21 3月, 2006 23 次提交
  4. 20 3月, 2006 1 次提交
    • R
      [AX.25]: Fix potencial memory hole. · c7c694d1
      Ralf Baechle DL5RB 提交于
      If the AX.25 dialect chosen by the sysadmin is set to DAMA master / 3
      (or DAMA slave / 2, if CONFIG_AX25_DAMA_SLAVE=n) ax25_kick() will fall
      through the switch statement without calling ax25_send_iframe() or any
      other function that would eventually free skbn thus leaking the packet.
      
      Fix by restricting the sysctl inferface to allow only actually supported
      AX.25 dialects.
      
      The system administration mistake needed for this to happen is rather
      unlikely, so this is an uncritical hole.
      
      Coverity #651.
      Signed-off-by: NRalf Baechle DL5RB <ralf@linux-mips.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c7c694d1
  5. 18 3月, 2006 1 次提交
  6. 28 2月, 2006 1 次提交
    • H
      [IPSEC]: Kill post_input hook and do NAT-T in esp_input directly · 752c1f4c
      Herbert Xu 提交于
      The only reason post_input exists at all is that it gives us the
      potential to adjust the checksums incrementally in future which
      we ought to do.
      
      However, after thinking about it for a bit we can adjust the
      checksums without using this post_input stuff at all.  The crucial
      point is that only the inner-most NAT-T SA needs to be considered
      when adjusting checksums.  What's more, the checksum adjustment
      comes down to a single u32 due to the linearity of IP checksums.
      
      We just happen to have a spare u32 lying around in our skb structure :)
      When ip_summed is set to CHECKSUM_NONE on input, the value of skb->csum
      is currently unused.  All we have to do is to make that the checksum
      adjustment and voila, there goes all the post_input and decap structures!
      
      I've left in the decap data structures for now since it's intricately
      woven into the sec_path stuff.  We can kill them later too.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      752c1f4c
  7. 24 2月, 2006 1 次提交
  8. 16 2月, 2006 1 次提交
    • P
      [XFRM]: Fix SNAT-related crash in xfrm4_output_finish · 48d5cad8
      Patrick McHardy 提交于
      When a packet matching an IPsec policy is SNATed so it doesn't match any
      policy anymore it looses its xfrm bundle, which makes xfrm4_output_finish
      crash because of a NULL pointer dereference.
      
      This patch directs these packets to the original output path instead. Since
      the packets have already passed the POST_ROUTING hook, but need to start at
      the beginning of the original output path which includes another
      POST_ROUTING invocation, a flag is added to the IPCB to indicate that the
      packet was rerouted and doesn't need to pass the POST_ROUTING hook again.
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      48d5cad8
  9. 14 2月, 2006 1 次提交
  10. 13 2月, 2006 1 次提交
  11. 10 2月, 2006 1 次提交
  12. 05 2月, 2006 1 次提交
  13. 03 2月, 2006 2 次提交
  14. 01 2月, 2006 1 次提交
  15. 31 1月, 2006 1 次提交
  16. 28 1月, 2006 1 次提交