From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: [PATCH md 3 of 4] Delete unplug timer before shutting down md array. Date: Thu, 4 Nov 2004 10:21:08 +0100 Message-ID: <20041104092107.GE14993@suse.de> References: <20041102143440.12019.patches@notabene> <20041103150315.47a7982e.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20041103150315.47a7982e.akpm@osdl.org> Sender: linux-raid-owner@vger.kernel.org To: Andrew Morton Cc: NeilBrown , linux-raid@vger.kernel.org List-Id: linux-raid.ids On Wed, Nov 03 2004, Andrew Morton wrote: > NeilBrown wrote: > > > > As the unplug timer can potentially fire at any time, and > > and it access data that is released by the md ->stop function, > > we need to del_timer_sync before releasing that data. > > I don't think I saw an update to this patch so I just knocked up the below > simple conversion. If anyone can think up a nice description of what > blk_sync_queue() should do, it would be appreciated ;) I don't see much merrit in this patch, you have to prevent new requests from setting it off again. Basically, from my understanding, Neil needs a way to atomically kill the timer and the unplug function. Correct? -- Jens Axboe