diff options
author | Adam Kwolek <adam.kwolek@intel.com> | 2012-02-07 15:03:35 +0100 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2012-02-09 12:20:52 +1100 |
commit | 50927b1323a4cfcbf3729ff552c496695d6199eb (patch) | |
tree | 7e1f75daee6cbce097de4dca8690f7e8f7842c67 /part.h | |
parent | bf5cf7c705f292a070746c83f9dd00d7662f458d (diff) |
Fix: Sometimes mdmon throws core dump during reshape
Problem was found during reshaping 2 volumes /raid0 and raid5/ in container.
Sometimes mdmon throws core dump due to NULL pointer exception.
Problem occurs in scenario:
- managemon: is about spare activation (degraded raid4 volume == raid0 under takeover)
- managemon: detect level change and signals monitor (manage_member() calls replace_array())
- monitor: detects transition raid4/5->raid0 and sets a->container to NULL
to indicate array deactivation
- managemon : continues his work and tries to activate spare (a->check_degraded is set).
NULL pointer is passed to metadata handler activate_spare()
Core dump is generated.
To resolve this situation managemon (after monitor kick) checks again
a->container pointer to learn if current array is not to be deactivated.
Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'part.h')
0 files changed, 0 insertions, 0 deletions