From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Mika Kukkonen <mika@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
cgl_discussion@osdl.org, Mark Huth <mark.huth@mvista.com>,
Tigran Aivazian <tigran@veritas.com>
Subject: Re: OSDL CGL-WG draft specs available for review
Date: Thu, 24 Apr 2003 11:39:29 +0200 [thread overview]
Message-ID: <3EA7B0D1.8090604@gmx.net> (raw)
In-Reply-To: <20030423174958.A2603@infradead.org>
[CC:ed Mark Huth and Tigran Aivazian]
Christoph Hellwig wrote:
> 4.10 Force unmount (2) 2 Experimental Availability Core
> 4.10 Description:
>
> CGL shall support forced unmounting of a filesystem.
> * The unmount should work even if there are open files or processes
> in the file system.
> * Pending requests should be ended with an error return when the
> file system is unmounted.
>
>
> This is very hard to get right. What the expermintel implementation
> you're referring to?
IIRC, Mark Huth from MontaVista and Tigran Aivazian from Veritas both
developed such an implementation independently of each other.
Maybe they can offer some insight.
Regards,
Carl-Daniel
next prev parent reply other threads:[~2003-04-24 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 20:46 OSDL CGL-WG draft specs available for review Mika Kukkonen
2003-04-22 20:55 ` Christoph Hellwig
2003-04-22 21:22 ` [cgl_discussion] " Mika Kukkonen
2003-04-22 21:25 ` Christoph Hellwig
2003-04-23 16:18 ` Mika Kukkonen
2003-04-23 16:26 ` Christoph Hellwig
2003-04-23 16:49 ` Christoph Hellwig
2003-04-23 18:32 ` [cgl_discussion] " Mika Kukkonen
2003-04-23 20:22 ` Christoph Hellwig
2003-04-23 22:03 ` [cgl_discussion] Re: OSDL CGL-WG draft specs available forreview Peter Badovinatz
2003-04-24 9:39 ` Carl-Daniel Hailfinger [this message]
2003-04-24 9:46 ` OSDL CGL-WG draft specs available for review Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2003-04-23 21:57 Fleischer, Julie N
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=3EA7B0D1.8090604@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=cgl_discussion@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.huth@mvista.com \
--cc=mika@osdl.org \
--cc=tigran@veritas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.