From: Phil Auld <pauld@egenera.com>
To: linux-kernel@vger.kernel.org
Subject: Stale super_blocks in 2.2
Date: Tue, 13 Feb 2001 17:23:57 -0500 [thread overview]
Message-ID: <3A89B3FD.62313E6C@egenera.com> (raw)
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
next reply other threads:[~2001-02-13 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 22:23 Phil Auld [this message]
2001-02-13 22:28 ` Alan Cox
2001-02-13 22:34 ` Phil Auld
2001-02-13 22:38 ` Alan Cox
2001-02-14 13:27 ` Phil Auld
2001-02-14 13:32 ` Alan Cox
2001-02-13 22:55 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A89B3FD.62313E6C@egenera.com \
--to=pauld@egenera.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®