Verify that the counts for duptsns and gapacks can actually
fit in the skb so we won't underrun. 

into touki.austin.ibm.com:/home/jgrimm/bk/lksctp-2.5.work

Standford Checker reported direct touch of user space. 

into touki.austin.ibm.com:/home/jgrimm/bk/lksctp-2.5.work

sinfo_timetolive lets the application specify 'timed reliability'
for a message.  That is, the message really only has a use to
the peer up to this timeout.  Without PR-SCTP, we can throw away
such timed out messages if we haven't yet assigned TSN/SSNs to
them.  If we have, there is nothing we can do until we support
PR-SCTP extension.  

into us.ibm.com:/home/sridhar/BK/lksctp-2.5.68

Fix memory leak.  

into touki.austin.ibm.com:/home/jgrimm/bk/lksctp-2.5.work

If a message were fragmented, it was getting SEND_FAILed in all
sorts of random order or not at all.   Now each "message" tracks its
own fragments and can SEND_FAIL itself and all its fragments. 

into us.ibm.com:/home/sridhar/BK/lksctp-2.5.68

Control chunks should be bundled (implementor's guide advises
specifically of case were ERROR should be bundled with CE to avoid
race condition.   Patch introduces a outq_cork/outq_uncork to
immediate transferral of control chunks and then release to the
packet bundling code. 

Followup patch by Ardelle. 

Submitted by Ardelle Fan.  Implementation of Split Fast Retransmit -
Changeover Aware Congestion Control.  Certain conditions involving
multihoming changover can result in TCP-unfriendliness.  This
implements the IETF proposed method of dealing with this corner
case.

into touki.austin.ibm.com:/home/jgrimm/bk/lksctp-2.5.work

We'll fragment (if fragmentation not disabled) to the min of maxseg
or PMTU allowance.  

sctp_state(asoc, STATE)  // Is asoc in this state?
sctp_style(sk, STYLE)    // Is sock this style?
sctp_sstate(sk, SS_STATE) // Is sock in this state?

into us.ibm.com:/home/sridhar/BK/lksctp-2.5.68

       socket with a non-empty accept queue.

For SEND_FAILED support, we need to keep around data chunk fragments
that have been acked, where other fragments of the same message
have not.  With this, Ardelle should be able to finish up the
SEND_FAILED support. 

into us.ibm.com:/home/sridhar/BK/lksctp-2.5.68

- Cleaned up hostinfo usage in all drivers and created a central API to
  handle them all.
- Fixup some spinlock mis-usage.
- Remove devfs_handle mis-usage.
- Cleaned up some heavy handed spinlocking to use mutexes instead.
- Add function to send PHY config packets and use to to settle
  IRM/cycle-master/root descrepancies.

into home.transmeta.com:/home/torvalds/v2.5/linux

If copy_namespace() returns -EPERM, copy_process() will
return a confusing -ENOMEM. Fix it thus.

	new_ns = kmalloc(sizeof(struct namespace *), GFP_KERNEL);
thing wasn't a very good idea.

The rest are whitespace cleanups.

(i) Replace in struct loop_info the dev_t field by __kernel_old_dev_t,
where this type is defined in <asm/posix_types.h>, so that problems
with a differently sized dev_t in userspace are avoided.

(ii) Introduce a new loop_info64, with __u64 device, inode and offset
fields.

This replaces checkboxes by radiobuttons whereever necessary (menu
choices).  It partially fixes the #540 bug report.

into home.transmeta.com:/home/torvalds/v2.5/linux

Second try at the bridge driver module handling cleanup...

1) Eliminate keeping a seperate bridge_list and use a bit on
   the priv_flags structure.  This is equivalent to how the VLAN
   code works. Makes code cleaner and correctly handles cases like
   creating a bridge with the same name as an existing ether device etc.

2) Don't do own module ref counting that is inhernently racy.
   Instead set owner field and cleanup debris on unload.

3) Do last state cleanup in destructor

4) Change of bridge state (dev_open/stop) should use write_lock

5) Make sure timer is not running when cleared.

6) Use "const char *" where possible