linux-kernel - Re: [PATCH 0/6] overlay filesystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTinNk=8F5qf13DJsKObJGLtQiRyA7A@mail.gmail.com>
Date:	Mon, 9 May 2011 21:14:44 +0200
From:	Michal Suchanek <hramrach@...trum.cz>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, apw@...onical.com, nbd@...nwrt.org,
	neilb@...e.de
Subject: Re: [PATCH 0/6] overlay filesystem

Hello

On 18 April 2011 18:00, Miklos Szeredi <miklos@...redi.hu> wrote:
> Here's an updated version of the overlay filesystem.
>
> Git tree is here:
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs.v8
>
> Changes from v7 to v8:
>
> - split overlayfs.c into smaller files
>
> - fix locking for copy up (reported by Al Viro)
>
> - locking analysis of copy up vs. directory rename added as a comment
>
> - tested with lockdep, fixed one lock annotation
>
> - other bug fixes
>
> To be done:
>
> - redo i_op->open, waiting for status of atomic_open() from Al
>
> - look into xattr support for tmpfs
>

What's still required for overlayfs to get into the kernel?

With the additional patches posted in the v8 branch (the modular build
fix and the xattr for tmpfs patch) overlayfs works for me.

I rebuilt my linux rescue system to use
overlayfs/tmpfs+squashfs/loop/fuse.httpfs and used it a few times
without any issues.

This system has about 1.6G data in 68599 files, 6960 directories and
7634 symlinks (compressed to about 630M squashfs).

Thanks

Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/