Message-ID: <3A89B3FD.62313E6C@egenera.com>
Date: Tue, 13 Feb 2001 17:23:57 -0500
From: Phil Auld <pauld@egenera.com>
Organization: Egenera Inc.
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: Stale super_blocks in 2.2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

Hello,

	It appears that the umount path in the 2.2 series kernels
does not do anything to invalidate the buffers associated with the
unmounted device. We then rely on disk change detection on a 
subsequent mount to prevent us from seeing the old super_block.

Since deja was gobbled by google it's hard to do a good search of 
this list. Can anyone take the time to help me understand the reason
for this choice? This seems to me to be backwards. When a device is 
unmounted there should be no cached information.

Thanks for the help,


Phil


-- 
------------------------------------------------------
Philip R. Auld, Ph.D.                  technical staff
Egenera Corp.                        pauld@egenera.com
165 Forest St, Marlboro, MA 01752        (508)786-9444
-
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/