Bug#462154: mdadm: It's not only --monitor --scan

[Neil Brown]

On Tuesday March 4, pernegger at gmail.com wrote:
> Package: mdadm
> Version: 2.6.4-1
> Followup-For: Bug #462154
> 
> 
> I've had it after a few creates (raid benchmarking atm) as well, and assembles.
> 
> It seems to crash *after* what it's supposed to do, though, i. e.:
> 
> segfault at 0000000000000000 rip 0000000000412d2c rsp 00007fffc0bf9eb0 error 4
> segfault at 0000000000000000 rip 0000000000412d2c rsp 00007fff9f31b5d0 error 4
> segfault at 0000000000000000 rip 0000000000412d2c rsp 00007fffd6f371f0 error 4
> segfault at 0000000000000000 rip 0000000000412d2c rsp 00007fffa08b5b70 error 4
> segfault at 0000000000000000 rip 0000000000412d2c rsp 00007fff78944c00 error 4
> segfault at 0000000000000000 rip 0000000000412d2c rsp 00007fffc0bf9eb0 error 4

If this is at all repeatable, then it would be great if you can run it
under 'gdb' and get a stack trace.
i.e
   gdb `which mdadm`
   run ...mdadm options....
  wait for segfault
   where

Thanks,
NeilBrown