On Wed, 15 Dec 2010 17:23:56 +0000 "Labun, Marcin" <Marcin.Labun@xxxxxxxxx> wrote: > Hi Neil, > We have spotted that when RAID 1 array is assembled and stopped in a loop, there is an occasional kernel oops in raid1 module. > It occurs in make_request function on wait_barrier(conf). In this case mddev->private was NULL, since probably it was not yet initialized in run() function. > The straightforward approach is test for mdadm->private and return bio_endio with an error if private not set. > The question is: > Since raid1 module might receive IO request when it is not ready, what make_request can check for to test if for instance run() function has finished. > > Thanks, > Marcin Labun I cannot imagine how this would happen. It should not be possible to call do_md_stop while there are any requests still in flight. Are you generating any IO between assembling the RAID1 and stopping it? If so, how? Can you get me the full oops message? Thanks, NeilBrown -- 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
