On Tue, Feb 2, 2016 at 12:29 AM, Roman Penyaev
<[email protected]> wrote:
> Hello, Jens.
>
> Could you please take a look at this patch.
> This issue happens quite often on our servers, when udevd
> tries to get detailed info about md raid starting mdadm,
> but this raid device is already in closing state and is
> about to free internal structures, afterwards an oops
> happens and mdadm gets killed.
Looks the issue is still there, so could we consider Roman's approach
for this issue?
Thanks,
Ming Lei