From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vivek Goyal Subject: Re: [PATCH] block: Check that queue is alive in blk_insert_cloned_request() Date: Tue, 12 Jul 2011 13:06:58 -0400 Message-ID: <20110712170658.GF1293@redhat.com> References: <1310166270-23196-1-git-send-email-roland@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Mike Snitzer Cc: Roland Dreier , Jens Axboe , James Bottomley , Alan Stern , Heiko Carstens , linux-scsi@vger.kernel.org, Steffen Maier , "Manvanthara B. Puttashankar" , Tarak Reddy , "Seshagiri N. Ippili" , linux-kernel@vger.kernel.org, device-mapper development , Tejun Heo List-Id: linux-scsi@vger.kernel.org On Mon, Jul 11, 2011 at 06:40:11PM -0400, Mike Snitzer wrote: > [cc'ing dm-devel, vivek and tejun] >=20 > On Fri, Jul 8, 2011 at 7:04 PM, Roland Dreier wro= te: > > From: Roland Dreier > > > > This fixes crashes such as the below that I see when the storage > > underlying a dm-multipath device is hot-removed. =A0The problem is = that > > dm requeues a request to a device whose block queue has already bee= n > > cleaned up, and blk_insert_cloned_request() doesn't check if the qu= eue > > is alive, but rather goes ahead and tries to queue the request. =A0= This > > ends up dereferencing the elevator that was already freed in > > blk_cleanup_queue(). >=20 > Your patch looks fine to me: > Acked-by: Mike Snitzer >=20 > And I looked at various code paths to arrive at the references DM tak= es. >=20 > A reference is taken on the underlying devices' block_device via > drivers/md/dm-table.c:open_dev() with blkdev_get_by_dev(). open_dev(= ) > also does bd_link_disk_holder(), resulting in the mpath device > becoming a holder of the underlying devices. e.g.: > /sys/block/sda/holders/dm-4 >=20 > But at no point does DM-mpath get a reference to the underlying > devices' request_queue that gets assigned to clone->q (in > drivers/md/dm-mpath.c:map_io). >=20 > Seems we should, though AFAIK it won't help with the issue you've > pointed out (because the hotplugged device's driver already called > blk_cleanup_queue and nuked the elevator). [Thinking loud] Could it be a driver specific issue that it cleaned up the request queue too early? Is there any notion of device reference which higher layers take and that should make sure request queue is intact till somebody is holding device reference. If yes, what't the connection between device reference and request queue reference. IOW, why request queue reference is needed and why device reference is not sufficient. (Because there is not necessarily one to one mapping between request queue and device?) I seem to just have lots of question about devices and referencing. Hopefully somebody with more knowledge in this area be able to shed some light on it. Thanks Vivek