md: Drop sending a change uevent when stopping

When stopping an MD device, then its device node /dev/mdX may still
exist afterwards or it is recreated by udev. The next open() call
can lead to creation of an inoperable MD device. The reason for
this is that a change event (KOBJ_CHANGE) is sent to udev which
races against the remove event (KOBJ_REMOVE) from md_free().
So drop sending the change event.

A change is likely also required in mdadm as many versions send the
change event to udev as well.

Neil mentioned the change event is a workaround for old kernel
Commit: 934d9c23b4c7 ("md: destroy partitions and notify udev when md array is stopped.")
new mdadm can handle device remove now, so this isn't required any more.

Cc: NeilBrown <[email protected]>
Cc: Hannes Reinecke <[email protected]>
Cc: Jes Sorensen <[email protected]>
Signed-off-by: Sebastian Parschauer <[email protected]>
Signed-off-by: Shaohua Li <[email protected]>

0 files changed, 0 insertions, 0 deletions