From: Pekka J Enberg <penberg@cs.helsinki.fi>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: Mike Snitzer <snitzer@gmail.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: forced umount?
Date: Tue, 27 Mar 2007 09:32:05 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0703270929030.31885@sbz-30.cs.Helsinki.FI> (raw)
In-Reply-To: <46083C79.1080108@cfl.rr.com>
On Mon, 26 Mar 2007, Phillip Susi wrote:
> Is this revoke system supported for the filesystem as a whole? I thought it
> was just to force specific files closed, not the whole filesystem. What if
> the filesystem itself has pending IO to say, update inodes or block bitmaps?
> Can these be aborted?
We never want to _abort_ pending updates only pending reads. So, even with
revoke(), we need to be careful which is why we do do_fsync() in
generic_revoke_file() to make sure pending updates are flushed before we
declare the inode revoked.
But, I haven't looked at forced unmount that much so there may be other
issues I am not aware of.
Pekka
next prev parent reply other threads:[~2007-03-27 6:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 4:06 forced umount? Mike Snitzer
2007-03-17 4:27 ` Jeremy Fitzhardinge
2007-03-17 5:37 ` Mike Snitzer
2007-03-17 10:53 ` Pekka Enberg
2007-03-26 21:34 ` Phillip Susi
2007-03-27 6:32 ` Pekka J Enberg [this message]
2007-03-28 14:46 ` Phillip Susi
2007-03-17 5:24 ` Gene Heskett
2007-03-18 19:16 ` Arjan van de Ven
2007-03-18 20:13 ` Matthew Wilcox
2007-03-18 23:45 ` Jan Engelhardt
2007-03-18 20:20 ` Mike Snitzer
2007-03-26 11:21 ` Pozsar Balazs
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=Pine.LNX.4.64.0703270929030.31885@sbz-30.cs.Helsinki.FI \
--to=penberg@cs.helsinki.fi \
--cc=jeremy@goop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
--cc=snitzer@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).