ChangeSet@1.1473, 2005-03-24 09:17:10-03:00, horms@verge.net.au
  [PATCH] Backport v2.6 ATM copy-to-user signedness fix
  
  Applologies if this is already pending, but the signdness fix for
  atm_get_addr() in  2.6 seems to be needed for 2.4 as well.
  
  This relates to the bugs reported in this document
  http://www.guninski.com/where_do_you_want_billg_to_go_today_3.html
  
  Backport of  ATM copy-to-user signedness fix from 2.6
  
  Signed-off-by: Simon Horman <horms@verge.net.au>
  
  ===== net/atm/addr.h 1.2 vs edited =====

ChangeSet@1.1472, 2005-03-24 09:13:38-03:00, relf@os2.ru
  [PATCH] fs/hpfs/*: fix HPFS support under 64-bit kernel
  
  The provided patch fixes HPFS filesystem support under 64-bit Linux kernel
  and closes the bugreport http://bugme.osdl.org/show_bug.cgi?id=4333
  
  The problem is in 'time_t' size which is 8 bytes on 64-bit systems
  (comparing to 4 bytes on 32-bit systems).  The patch introduces local
  'time32_t' type of the fixed size 4 and uses it where required.
  
  Signed-off-by: Andrew Morton <akpm@osdl.org>

ChangeSet@1.1471, 2005-03-24 09:00:35-03:00, neilb@cse.unsw.edu.au
  [PATCH] [PATCH md: allow degraded raid1 array to resync after an unclean shutdown.
  
  The following is (I think) appropriate for 2.4.30.  The bug it fixes
  can result in data corruption in a fairly unusual circumstance (having
  a 3 drive raid1 array running in degraded mode, and suffering a system
  crash).
  
  ### Comments for Changeset
  
  If a raid1 array has more than two devices, and not all are working,
  then it will not resync after an unclean shutdown (as it will think
  that it should reconstruct a failed drive, and will find there aren't
  any spares...)
  
  This patch fixes the problem.
  
  Problem found by Mario Holbe <Mario.Holbe@TU-Ilmenau.DE> (thanks!)
  
  Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>

ChangeSet@1.1470, 2005-03-24 09:00:05-03:00, neilb@cse.unsw.edu.au
  [PATCH] nlm: fix f_count leak
  
   The following patch is probably appropriate for 2.4.30.  The problem
  it fixes is not a major one (no security or data corruption issues)
  but is an occasional annoyance, and the fix is trivial (and tested).
  
  ### Comments for Changeset
  
  I can't see any reason for this file->f_count++.  Removing it fixes a
  bug which leaves an exported filesystem busy (and so unmountable) if a
  callback for a lock held on that filesystem ever failed.
  
  Found by Terence Rokop.
  
  Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
  Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au>

ChangeSet@1.1469, 2005-03-23 13:00:39-03:00, zaitcev@redhat.com
  [PATCH] USB: Fix baud selection in mct_u232
  
  This is an obvious fix by Hansjoerg Lipp, which fixes baud rate selection
  for one of two types of MCT adapters. Unfortunately, I only have the other
  type, and so I let it slip in. I have tested this to build and not break
  my type. This fix is not yet present in Linus's 2.6, but I am confident
  that it will make it in due time. I keep MCT synched between 2.4 and 2.6,
  this patch applies to both trees.

ChangeSet@1.1468, 2005-03-22 14:30:33-03:00, zaitcev@redhat.com
  [PATCH] USB: fix oops in serial_write
  
  When I split the __serial_write off serial_write, the former took the NULL
  check away with it. However, the new serial_write still has an reference
  remaining in down(&port->sem). Joachim Nilsson corrected me.

ChangeSet@1.1466, 2005-03-18 13:47:58-07:00, kaos@sgi.com
  [IA64] Tighten up unw_unwind_to_user check
  
  Detect user space by the unwind frame with predicate PRED_USER_STACK
  set, instead of a user space IP.  Tighten up the last ditch check for
  running off the top of the kernel stack.
  
  Based on a suggestion by David Mosberger, reworked to fit the current
  tree.  This survives my stress test which used to break 2.6.9 kernels.
  Unlike 2.6.11, the stress test now unwinds to the correct point, so
  gdb can get the user space registers.
  
  Signed-off-by: Keith Owens <kaos@sgi.com>
  Signed-off-by: Tony Luck <tony.luck@intel.com>

ChangeSet@1.1448.1.137, 2005-03-18 14:09:27-03:00, shemminger@osdl.org
  [PATCH] TCP BIC not binary searching correctly
  
  2.4 version of same fix as 2.6.11.
  
  The problem is that BIC is supposed to reset the cwnd to the last loss value
  rather than ssthresh when loss is detected.  The correct code (from the BIC
  TCP code for Web100) is in this patch.
  
  Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
  TAG: v2.4.30-rc1