summaryrefslogtreecommitdiff
path: root/drivers/infiniband
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2014-08-18 13:59:50 +1000
committerJiri Slaby <jslaby@suse.cz>2014-09-17 17:06:51 +0200
commit326d57f8a0437e8d1296e6e76f1ee81728b0afda (patch)
treed4f2c4f6676db33cff77fe7a4ce05f25a74b80b7 /drivers/infiniband
parent9fdaa2cdfcc03ae10c27863d601dccaac184403a (diff)
downloadlwn-326d57f8a0437e8d1296e6e76f1ee81728b0afda.tar.gz
lwn-326d57f8a0437e8d1296e6e76f1ee81728b0afda.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: Jiri Slaby <jslaby@suse.cz>
Diffstat (limited to 'drivers/infiniband')
0 files changed, 0 insertions, 0 deletions