Subject: Re: IDE locking problem
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Jens Axboe <axboe@suse.de>,
       linux-kernel mailing list <linux-kernel@vger.kernel.org>
In-Reply-To: <3F2D1884.3010001@colorfullife.com>
References: <3F2D1884.3010001@colorfullife.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1059920721.3524.137.camel@gaston>
Mime-Version: 1.0
Date: 03 Aug 2003 16:25:22 +0200
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 706
Lines: 16

> The last step is bad - sooner or later the queue will be kfreed, and if 
> there are bozos around that still have references, they would access 
> random memory. It must be guaranteed that all references expired before 
> the tear down begins. Just leaving a dead flag set is not sufficient.

Jens ? I see no refcounting of the queue, but then we enter the
deep guts of the block layer and all this is pretty much obscure
to me. What can be done here ?

Ben.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/