1. 29 1月, 2008 3 次提交
  2. 20 11月, 2007 1 次提交
    • S
      [TCP]: Problem bug with sysctl_tcp_congestion_control function · 5487796f
      Sam Jansen 提交于
      From: "Sam Jansen" <sjansen@google.com>
      
      sysctl_tcp_congestion_control seems to have a bug that prevents it
      from actually calling the tcp_set_default_congestion_control
      function. This is not so apparent because it does not return an error
      and generally the /proc interface is used to configure the default TCP
      congestion control algorithm.  This is present in 2.6.18 onwards and
      probably earlier, though I have not inspected 2.6.15--2.6.17.
      
      sysctl_tcp_congestion_control calls sysctl_string and expects a successful
      return code of 0. In such a case it actually sets the congestion control
      algorithm with tcp_set_default_congestion_control. Otherwise, it returns the
      value returned by sysctl_string. This was correct in 2.6.14, as sysctl_string
      returned 0 on success. However, sysctl_string was updated to return 1 on
      success around about 2.6.15 and sysctl_tcp_congestion_control was not updated.
      Even though sysctl_tcp_congestion_control returns 1, do_sysctl_strategy
      converts this return code to '0', so the caller never notices the error.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5487796f
  3. 19 10月, 2007 2 次提交
  4. 16 10月, 2007 1 次提交
  5. 11 10月, 2007 1 次提交
  6. 08 6月, 2007 1 次提交
  7. 26 4月, 2007 2 次提交
  8. 11 2月, 2007 1 次提交
  9. 11 12月, 2006 1 次提交
  10. 03 12月, 2006 2 次提交
  11. 02 11月, 2006 1 次提交
  12. 25 9月, 2006 1 次提交
  13. 23 9月, 2006 1 次提交
    • P
      [NetLabel]: CIPSOv4 engine · 446fda4f
      Paul Moore 提交于
      Add support for the Commercial IP Security Option (CIPSO) to the IPv4
      network stack.  CIPSO has become a de-facto standard for
      trusted/labeled networking amongst existing Trusted Operating Systems
      such as Trusted Solaris, HP-UX CMW, etc.  This implementation is
      designed to be used with the NetLabel subsystem to provide explicit
      packet labeling to LSM developers.
      
      The CIPSO/IPv4 packet labeling works by the LSM calling a NetLabel API
      function which attaches a CIPSO label (IPv4 option) to a given socket;
      this in turn attaches the CIPSO label to every packet leaving the
      socket without any extra processing on the outbound side.  On the
      inbound side the individual packet's sk_buff is examined through a
      call to a NetLabel API function to determine if a CIPSO/IPv4 label is
      present and if so the security attributes of the CIPSO label are
      returned to the caller of the NetLabel API function.
      Signed-off-by: NPaul Moore <paul.moore@hp.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      446fda4f
  14. 01 7月, 2006 1 次提交
  15. 18 6月, 2006 3 次提交
  16. 21 3月, 2006 2 次提交
  17. 04 1月, 2006 2 次提交
  18. 11 11月, 2005 1 次提交
  19. 30 8月, 2005 2 次提交
  20. 24 6月, 2005 1 次提交
  21. 14 6月, 2005 1 次提交
    • J
      [IPV4]: Sysctl configurable icmp error source address. · 1c2fb7f9
      J. Simonetti 提交于
      This patch alows you to change the source address of icmp error
      messages. It applies cleanly to 2.6.11.11 and retains the default
      behaviour.
      
      In the old (default) behaviour icmp error messages are sent with the ip
      of the exiting interface.
      
      The new behaviour (when the sysctl variable is toggled on), it will send
      the message with the ip of the interface that received the packet that
      caused the icmp error. This is the behaviour network administrators will
      expect from a router. It makes debugging complicated network layouts
      much easier. Also, all 'vendor routers' I know of have the later
      behaviour.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1c2fb7f9
  22. 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