diff options
| author | NeilBrown <neilb@suse.de> | 2012-08-16 16:46:12 +1000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-10-02 09:47:25 -0700 |
| commit | f2657804a840a7c5ed60b9a96c8e81e845579a25 (patch) | |
| tree | 829011d843d30ace6341172d09e66b60f6ddfa72 /mm | |
| parent | 5e5369da75bc02e9e0bfdd5c1bb64a70021f1d8b (diff) | |
| download | kernel_samsung_crespo-f2657804a840a7c5ed60b9a96c8e81e845579a25.zip kernel_samsung_crespo-f2657804a840a7c5ed60b9a96c8e81e845579a25.tar.gz kernel_samsung_crespo-f2657804a840a7c5ed60b9a96c8e81e845579a25.tar.bz2 | |
md: Don't truncate size at 4TB for RAID0 and Linear
commit 667a5313ecd7308d79629c0738b0db588b0b0a4e upstream.
commit 27a7b260f71439c40546b43588448faac01adb93
md: Fix handling for devices from 2TB to 4TB in 0.90 metadata.
changed 0.90 metadata handling to truncated size to 4TB as that is
all that 0.90 can record.
However for RAID0 and Linear, 0.90 doesn't need to record the size, so
this truncation is not needed and causes working arrays to become too small.
So avoid the truncation for RAID0 and Linear
This bug was introduced in 3.1 and is suitable for any stable kernels
from then onwards.
As the offending commit was tagged for 'stable', any stable kernel
that it was applied to should also get this patch. That includes
at least 2.6.32, 2.6.33 and 3.0. (Thanks to Ben Hutchings for
providing that list).
Signed-off-by: Neil Brown <neilb@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions