From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Mike Snitzer <snitzer@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: forced umount?
Date: Fri, 16 Mar 2007 21:27:30 -0700 [thread overview]
Message-ID: <45FB6E32.3050009@goop.org> (raw)
In-Reply-To: <170fa0d20703162106v47dc13e1u1ae5381576f372ed@mail.gmail.com>
Mike Snitzer wrote:
> Is this forced umount work even considered worthwhile by the greater
> Linux community? Is anyone actively working on this?
Have a look at all the discussion about revoke/frevoke on lkml over the
last week or two.
J
next prev parent reply other threads:[~2007-03-17 4:27 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 [this message]
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
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=45FB6E32.3050009@goop.org \
--to=jeremy@goop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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