| To: | nigel@xxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [xfs-masters] Re: freeze vs freezer |
| From: | Oliver Neukum <oliver@xxxxxxxxxx> |
| Date: | Thu, 3 Jan 2008 10:47:57 +0100 |
| Cc: | "Rafael J. Wysocki" <rjw@xxxxxxx>, Pavel Machek <pavel@xxxxxx>, Kyle Moffett <mrmacman_g4@xxxxxxx>, Matthew Garrett <mjg59@xxxxxxxxxxxxx>, David Chinner <dgc@xxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xfs-masters@xxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <477CA8A8.2090201@nigel.suspend2.net> |
| References: | <4744FD87.7010301@goop.org> <200801022304.19279.rjw@sisk.pl> <477CA8A8.2090201@nigel.suspend2.net> |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
| User-agent: | KMail/1.9.6 (enterprise 20070904.708012) |
Am Donnerstag 03 Januar 2008 schrieb Nigel Cunningham:
> On top of this, I made a (too simple at the moment) freeze_filesystems
> function which iterates through &super_blocks in reverse order, freezing
> fuse filesystems or ordinary ones. I say 'too simple' because it doesn't
> currently allow for the possibility of someone mounting (say) ext3 on
> fuse, but that would just be an extension of what's already done.
How do you deal with fuse server tasks using other fuse filesystems?
How does freeze_filesystems() look?
Regards
Oliver
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [xfs-masters] Re: freeze vs freezer, Nigel Cunningham |
|---|---|
| Next by Date: | [xfs-masters] Re: freeze vs freezer, Nigel Cunningham |
| Previous by Thread: | [xfs-masters] Re: freeze vs freezer, Nigel Cunningham |
| Next by Thread: | [xfs-masters] Re: freeze vs freezer, Nigel Cunningham |
| Indexes: | [Date] [Thread] [Top] [All Lists] |