While working with mdadm policy/udev to add slaves when they are
inserted, I notices
mdadm is segfaulting if it gets a blank drive and action is set to
spare or above.
Looking into the code, this segfault is caused by the following code:
Incremental.c line 965
st2->ss->avail_size(st2, devsize,
sra->devs
? sra->devs->data_offset
: INVALID_SECTORS)
avail_size in my case is super1.c avail_size1
and here the code sets:
struct mdp_superblock_1 *super = st->sb;
and later tries accessing i.e super->feature_map, where it segfaults
because in the case
of an empty drive, st2 is created in super1.c/match_metadata_desc1
where it sets:
st->sb = NULL;
I am not entirely sure how this is supposed to work, but atleast
currently it segfaults.
--
Bj(/)rnar
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
