diff options
| author | NeilBrown <neilb@suse.de> | 2014-08-18 13:59:50 +1000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-09-17 09:04:00 -0700 |
| commit | 26584e18c463bcf54fbd97e7c76f6f00ba13b1c9 (patch) | |
| tree | b5ebd57232d4971ee32e2f7aaf3423e38110f7f1 | |
| parent | 1075d2bdf6334b8373c00978403a69a4d9fdb883 (diff) | |
| download | lwn-26584e18c463bcf54fbd97e7c76f6f00ba13b1c9.tar.gz lwn-26584e18c463bcf54fbd97e7c76f6f00ba13b1c9.zip | |
md/raid10: Fix memory leak when raid10 reshape completes.
commit b39685526f46976bcd13aa08c82480092befa46c upstream.
When a raid10 commences a resync/recovery/reshape it allocates
some buffer space.
When a resync/recovery completes the buffer space is freed. But not
when the reshape completes.
This can result in a small memory leak.
There is a subtle side-effect of this bug. When a RAID10 is reshaped
to a larger array (more devices), the reshape is immediately followed
by a "resync" of the new space. This "resync" will use the buffer
space which was allocated for "reshape". This can cause problems
including a "BUG" in the SCSI layer. So this is suitable for -stable.
Fixes: 3ea7daa5d7fde47cd41f4d56c2deb949114da9d6
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| -rw-r--r-- | drivers/md/raid10.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c index 973e26fc18c1..353c2b392652 100644 --- a/drivers/md/raid10.c +++ b/drivers/md/raid10.c @@ -2948,6 +2948,7 @@ static sector_t sync_request(struct mddev *mddev, sector_t sector_nr, */ if (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery)) { end_reshape(conf); + close_sync(conf); return 0; } |