1. 03 12月, 2006 4 次提交
  2. 12 10月, 2006 1 次提交
  3. 23 9月, 2006 1 次提交
  4. 11 4月, 2006 1 次提交
  5. 18 1月, 2006 2 次提交
    • V
      [SCTP]: Fix sctp_assoc_seq_show() panics on big-endian systems. · 38b0e42a
      Vlad Yasevich 提交于
      This patch corrects the panic by casting the argument to the
      pointer of correct size.  On big-endian systems we ended up loading
      only 32 bits of data because we are treating the pointer as an int*.
      By treating this pointer as loff_t*, we'll load the full 64 bits
      and then let regular integer demotion take place which will give us
      the correct value.
      Signed-off-by: NVlad Yaseivch <vladislav.yasevich@hp.com>
      Signed-off-by: NSridhar Samudrala <sri@us.ibm.com>
      38b0e42a
    • V
      [SCTP]: sctp doesn't show all associations/endpoints in /proc · 49392e5e
      Vlad Yasevich 提交于
      When creating a very large number of associations (and endpoints),
      /proc/assocs and /proc/eps will not show all of them.  As a result
      netstat will not show all of the either.  This is particularly evident
      when creating 1000+ associations (or endpoints).  As an example with
      1500 tcp style associations over loopback, netstat showed 1420 on my
      system instead of 3000.
      
      The reason for this is that the seq_operations start method is invoked
      multiple times bacause of the amount of data that is provided.  The
      start method always increments the position parameter and since we use
      the position as the hash bucket id, we end up skipping hash buckets.
      
      This patch corrects this situation and get's rid of the silly hash-1
      decrement.
      Signed-off-by: NVlad Yasevich <vladislav.yasevich@hp.com>
      Signed-off-by: NSridhar Samudrala <sri@us.ibm.com>
      49392e5e
  6. 26 10月, 2005 1 次提交
  7. 24 8月, 2005 1 次提交
  8. 14 6月, 2005 1 次提交
  9. 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