Re: [PATCH+comment] fix tmpfs BUG and AOP_WRITEPAGE_ACTIVATE

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Hugh Dickins <hugh@...>
Cc: Pekka Enberg <penberg@...>, Andrew Morton <akpm@...>, <ezk@...>, <ryan@...>, <mhalcrow@...>, <cjwatson@...>, <linux-kernel@...>, <linux-fsdevel@...>, <linux-mm@...>, <stable@...>
Date: Thursday, October 25, 2007 - 12:01 pm

In message <Pine.LNX.4.64.0710250705510.9811@blonde.wat.veritas.com>, Hugh Dickins writes:


I think "future proof" for other stackable f/s is a good idea, esp. since
many of the stackable f/s we've developed and distributed over the past 10
years are in some use in various places: gzipfs, avfs, tracefs, replayfs,
ncryptfs, versionfs, wrapfs, i3fs, and more (see www.filesystems.org).

Cheers,
Erez.
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] fix tmpfs BUG and AOP_WRITEPAGE_ACTIVATE, Hugh Dickins, (Wed Oct 24, 5:02 pm)
Re: [PATCH] fix tmpfs BUG and AOP_WRITEPAGE_ACTIVATE, Andrew Morton, (Wed Oct 24, 5:08 pm)
Re: [PATCH+comment] fix tmpfs BUG and AOP_WRITEPAGE_ACTIVATE , Erez Zadok, (Thu Oct 25, 12:01 pm)