[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <17735.5821.446351.439032@cse.unsw.edu.au>
Date: Tue, 31 Oct 2006 20:26:21 +1100
From: Neil Brown <neilb@...e.de>
To: Jens Axboe <jens.axboe@...cle.com>
Cc: Andrew Morton <akpm@...l.org>, linux-raid@...r.kernel.org,
linux-kernel@...r.kernel.org, gregkh@...e.de
Subject: Re: [PATCH 002 of 6] md: Change lifetime rules for 'md' devices.
On Tuesday October 31, jens.axboe@...cle.com wrote:
> On Tue, Oct 31 2006, Neil Brown wrote:
> >
> > I'm guessing we need
> >
> > diff .prev/block/elevator.c ./block/elevator.c
> > --- .prev/block/elevator.c 2006-10-31 20:06:22.000000000 +1100
> > +++ ./block/elevator.c 2006-10-31 20:06:40.000000000 +1100
> > @@ -926,7 +926,7 @@ static void __elv_unregister_queue(eleva
> >
> > void elv_unregister_queue(struct request_queue *q)
> > {
> > - if (q)
> > + if (q && q->elevator)
> > __elv_unregister_queue(q->elevator);
> > }
> >
> >
> > Jens? md never registers and elevator for its queue.
>
> Hmm, but blk_unregister_queue() doesn't call elv_unregister_queue()
> unless q->request_fn is set. And in that case, you must have an io
> scheduler attached.
Hmm.. yes. Oh, I get it. I have
blk_cleanup_queue(mddev->queue);
mddev->queue = NULL;
del_gendisk(mddev->gendisk);
mddev->gendisk = NULL;
That's the wrong order, isn't it. :-(
Thanks,
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists