Messages in this thread | | | Date | Tue, 22 Mar 2011 13:49:44 -0500 | Subject | Re: [PATCH 0/6 v7] overlay filesystem - request for inclusion | From | Xianghua Xiao <> |
| |
On Tue, Mar 22, 2011 at 1:22 PM, Felix Fietkau <nbd@openwrt.org> wrote: > On 2011-03-22 6:36 PM, Linus Torvalds wrote: >> On Tue, Mar 22, 2011 at 8:26 AM, Miklos Szeredi <miklos@szeredi.hu> wrote: >>> Here's an updated version of the overlay filesystem. I'd like to >>> propose it for inclusion into mainline. >> >> So on the whole it looked pretty small and simple. And most of the VFS >> level changes looked fine and I just reacted to the odd calling >> convention for open (I really think you should aim for ->open to have >> the basically same arguments as you made __dentry_open have: 'struct >> path', 'struct filp' and 'struct cred'). >> >> But I'd want Al's ack on the series. And also hear who uses it and how >> it's been tested? > We're using it in OpenWrt (an Embedded Linux distribution) for devices > with tiny amounts of flash for the entire system (e.g. 4 MB). > We're using it to provide a writable on-flash root filesystem with > squashfs for the read-only part and jffs2 for the writable overlay. This > saves some precious flash space compared to using only jffs2, and it > makes it easy for users to reset their device to defaults without having > to reflash. > With a backport of v6 of this series + my fixes that went into v7 this > is working quite well on 2.6.37 and 2.6.38 - I'm using it on a few > wireless access points at home. > > - Felix > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ >
how is this filesystem related to mini_fo and unionfs? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |