1. 09 11月, 2005 1 次提交
  2. 06 11月, 2005 1 次提交
  3. 05 11月, 2005 4 次提交
  4. 01 11月, 2005 1 次提交
  5. 31 10月, 2005 1 次提交
  6. 26 10月, 2005 1 次提交
  7. 14 10月, 2005 1 次提交
  8. 11 10月, 2005 8 次提交
  9. 05 10月, 2005 1 次提交
  10. 04 10月, 2005 2 次提交
    • H
      [IPV4]: Replace __in_dev_get with __in_dev_get_rcu/rtnl · e5ed6399
      Herbert Xu 提交于
      The following patch renames __in_dev_get() to __in_dev_get_rtnl() and
      introduces __in_dev_get_rcu() to cover the second case.
      
      1) RCU with refcnt should use in_dev_get().
      2) RCU without refcnt should use __in_dev_get_rcu().
      3) All others must hold RTNL and use __in_dev_get_rtnl().
      
      There is one exception in net/ipv4/route.c which is in fact a pre-existing
      race condition.  I've marked it as such so that we remember to fix it.
      
      This patch is based on suggestions and prior work by Suzanne Wood and
      Paul McKenney.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e5ed6399
    • H
      [NET]: Fix packet timestamping. · 325ed823
      Herbert Xu 提交于
      I've found the problem in general.  It affects any 64-bit
      architecture.  The problem occurs when you change the system time.
      
      Suppose that when you boot your system clock is forward by a day.
      This gets recorded down in skb_tv_base.  You then wind the clock back
      by a day.  From that point onwards the offset will be negative which
      essentially overflows the 32-bit variables they're stored in.
      
      In fact, why don't we just store the real time stamp in those 32-bit
      variables? After all, we're not going to overflow for quite a while
      yet.
      
      When we do overflow, we'll need a better solution of course.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      325ed823
  11. 27 9月, 2005 1 次提交
    • H
      [NETFILTER]: Fix invalid module autoloading by splitting iptable_nat · 188bab3a
      Harald Welte 提交于
      When you've enabled conntrack and NAT as a module (standard case in all
      distributions), and you've also enabled the new conntrack netlink
      interface, loading ip_conntrack_netlink.ko will auto-load iptable_nat.ko.
      This causes a huge performance penalty, since for every packet you iterate
      the nat code, even if you don't want it.
      
      This patch splits iptable_nat.ko into the NAT core (ip_nat.ko) and the
      iptables frontend (iptable_nat.ko).  Threfore, ip_conntrack_netlink.ko will
      only pull ip_nat.ko, but not the frontend.  ip_nat.ko will "only" allocate
      some resources, but not affect runtime performance.
      
      This separation is also a nice step in anticipation of new packet filters
      (nf-hipac, ipset, pkttables) being able to use the NAT core.
      Signed-off-by: NHarald Welte <laforge@netfilter.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      188bab3a
  12. 25 9月, 2005 2 次提交
  13. 23 9月, 2005 3 次提交
  14. 20 9月, 2005 3 次提交
  15. 18 9月, 2005 1 次提交
  16. 17 9月, 2005 4 次提交
  17. 14 9月, 2005 4 次提交
  18. 10 9月, 2005 1 次提交