1. 12 Feb, 2009 8 commits
  2. 10 Feb, 2009 7 commits
  3. 07 Feb, 2009 1 commit
  4. 06 Feb, 2009 21 commits
  5. 05 Feb, 2009 3 commits
    • Andre Noll's avatar
      md: Fix a bug in linear.c causing which_dev() to return the wrong device. · 852c8bf4
      Andre Noll authored
      ab5bd5cb
      
       introduced the following
      bug in linear software raid for large arrays on 32 bit machines:
      
      which_dev() computes the device holding a given sector by shifting
      down the sector number to a 32 bit range, dividing by the array
      spacing and looking up the resulting index in the hash table of
      the array.
      
      Because the computed index might be slightly too small, a loop at
      the end of which_dev() increases the index until the given sector
      actually falls into the range of the device associated with that index.
      
      The changes of the above mentioned commit caused this loop to check
      whether the _index_ rather than the sector number is small enough,
      effectively bypassing the loop and thus possibly returning the wrong
      device.
      
      As reported by Simon Kirby, this leads to errors such as
      
      	linear_make_request: Sector 2340486136 out of bounds on dev sdi: 156301312 sectors, offset 2109870464
      
      Fix this bug by introducing a local variable for the index so that
      the variable containing the passed sector is left unchanged.
      
      Cc: stable@kernel.org
      Signed-off-by: default avatarAndre Noll <maan@systemlinux.org>
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      852c8bf4
    • NeilBrown's avatar
      md: Allow read error in a single drive raid1 to be passed up. · 4706b349
      NeilBrown authored
      
      
      If a raid1 only has a single working device and gets a read error, 
      we choose to simply return that error up to the filesystem (or whatever)
      rather than failing the whole array.
      
      However the codes doesn't quite do that.  We attempt a readbalance
      which allocates the same drive, so we retry the read - indefinitely. 
      
      Instead:  If read_balance in the error case chooses the same drive that just
      failed, treat it as a failure and don't retry.
      Signed-off-by: default avatarNeilBrown <neilb@suse.de>
      4706b349
    • Masami Hiramatsu's avatar
      prevent kprobes from catching spurious page faults · 9be260a6
      Masami Hiramatsu authored
      
      
      Prevent kprobes from catching spurious faults which will cause infinite
      recursive page-fault and memory corruption by stack overflow.
      Signed-off-by: default avatarMasami Hiramatsu <mhiramat@redhat.com>
      Cc: <stable@kernel.org>		[2.6.28.x]
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      9be260a6