linux.git/drivers/md/linear.c, branch v2.6.30

md: centralize ->array_sectors modifications

2009-03-31T03:59:03+00:00

Get personalities out of the business of directly modifying
->array_sectors.  Lays groundwork to introduce policy on when
->array_sectors can be modified.

Reviewed-by: Andre Noll 
Signed-off-by: Dan Williams

md: add 'size' as a personality method

2009-03-31T03:57:49+00:00

In preparation for giving userspace control over ->array_sectors we need
to be able to retrieve the 'default' size, and the 'anticipated' size
when a reshape is requested.  For personalities that do not reshape emit
a warning if anything but the default size is requested.

In the raid5 case we need to update ->previous_raid_disks to make the
new 'default' size available.

Reviewed-by: Andre Noll 
Signed-off-by: Dan Williams

md: Represent raid device size in sectors.

2009-03-31T03:33:13+00:00

This patch renames the "size" field of struct mdk_rdev_s to
"sectors" and changes this field to store sectors instead of
blocks.

All users of this field, linear.c, raid0.c and md.c, are fixed up
accordingly which gets rid of many multiplications and divisions.

Signed-off-by: Andre Noll 
Signed-off-by: NeilBrown

md: move md_k.h from include/linux/raid/ to drivers/md/

2009-03-31T03:33:13+00:00

It really is nicer to keep related code together..

Signed-off-by: NeilBrown

md: move lots of #include lines out of .h files and into .c

2009-03-31T03:33:13+00:00

This makes the includes more explicit, and is preparation for moving
md_k.h to drivers/md/md.h

Remove include/raid/md.h as its only remaining use was to #include
other files.

Signed-off-by: NeilBrown

md: move headers out of include/linux/raid/

2009-03-31T03:27:03+00:00

Move the headers with the local structures for the disciplines and
bitmap.h into drivers/md/ so that they are more easily grepable for
hacking and not far away.  md.h is left where it is for now as there
are some uses from the outside.

Signed-off-by: Christoph Hellwig 
Signed-off-by: NeilBrown

md: Fix a bug in linear.c causing which_dev() to return the wrong device.

2009-02-06T04:10:52+00:00

ab5bd5cbc8d4b868378d062eed3d4240930fbb86 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: Andre Noll 
Signed-off-by: NeilBrown

md: use list_for_each_entry macro directly

2009-01-08T21:31:08+00:00

The rdev_for_each macro defined in  is identical to
list_for_each_entry_safe, from , it should be defined to
use list_for_each_entry_safe, instead of reinventing the wheel.

But some calls to each_entry_safe don't really need a safe version,
just a direct list_for_each_entry is enough, this could save a temp
variable (tmp) in every function that used rdev_for_each.

In this patch, most rdev_for_each loops are replaced by list_for_each_entry,
totally save many tmp vars; and only in the other situations that will call
list_del to delete an entry, the safe version is used.

Signed-off-by: Cheng Renquan 
Signed-off-by: NeilBrown

md: linear: Fix a division by zero bug for very small arrays.

2008-11-06T08:41:24+00:00

We currently oops with a divide error on starting a linear software
raid array consisting of at least two very small (< 500K) devices.

The bug is caused by the calculation of the hash table size which
tries to compute sector_div(sz, base) with "base" being zero due to
the small size of the component devices of the array.

Fix this by requiring the hash spacing to be at least one which
implies that also "base" is non-zero.

This bug has existed since about 2.6.14.

Cc: stable@kernel.org
Signed-off-by: Andre Noll 
Signed-off-by: NeilBrown

md: Remove unnecessary #includes, #defines, and function declarations.

2008-10-13T00:55:12+00:00

A lot of cruft has gathered over the years.  Time to remove it.

Signed-off-by: NeilBrown