diff options
author | NeilBrown <neilb@suse.de> | 2015-03-13 03:51:18 +0300 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2015-03-21 01:40:36 +0300 |
commit | 0c35bd4723e4a39ba2da4c13a22cb97986ee10c8 (patch) | |
tree | cb02268569a79cd8b7e898def4e86ba2707ed753 /drivers/md/raid0.c | |
parent | 06e5801b8cb3fc057d88cb4dc03c0b64b2744cda (diff) | |
download | linux-0c35bd4723e4a39ba2da4c13a22cb97986ee10c8.tar.xz |
md: fix problems with freeing private data after ->run failure.
If ->run() fails, it can either free the data structures it
allocated, or leave that task to ->free() which will be called
on failures.
However:
md.c calls ->free() even if ->private_data is NULL, which
causes problems in some personalities.
raid0.c frees the data, but doesn't clear ->private_data,
which will become a problem when we fix md.c
So better fix both these issues at once.
Reported-by: Richard W.M. Jones <rjones@redhat.com>
Fixes: 5aa61f427e4979be733e4847b9199ff9cc48a47e
URL: https://bugzilla.kernel.org/show_bug.cgi?id=94381
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/raid0.c')
-rw-r--r-- | drivers/md/raid0.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/md/raid0.c b/drivers/md/raid0.c index a13f738a7b39..3ed9f42ddca6 100644 --- a/drivers/md/raid0.c +++ b/drivers/md/raid0.c @@ -467,8 +467,6 @@ static int raid0_run(struct mddev *mddev) dump_zones(mddev); ret = md_integrity_register(mddev); - if (ret) - raid0_free(mddev, conf); return ret; } |