From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Linux Embedded Maillist <linux-embedded@vger.kernel.org>
Cc: Phillip Lougher <phillip.lougher@gmail.com>
Subject: Squashfs extended attribute file system support
Date: Wed, 19 May 2010 04:41:49 +0100 [thread overview]
Message-ID: <4BF35DFD.7050609@lougher.demon.co.uk> (raw)
Hi,
As promised way back in 2008, I have finished xattr support for Squashfs.
Xattr layout highlights
1. Layout can store up to 2^48 bytes of compressed xattr data.
2. Number of xattrs per inode unlimited.
3. Total size of xattr data per inode 2^48 bytes of compressed data.
4. Up to 4 Gbytes of data per xattr value.
5. Inline and out-of-line xattr values supported for higher performance
in xattr scanning (listxattr & getxattr), and to allow xattr value
de-duplication.
6. Both whole inode xattr duplicate detection and individual xattr value
duplicate detection supported. These can obviously nest, file C's
xattrs can be a complete duplicate of file B, and file B's xattrs
can be a partial duplicate of file A.
7. Xattr name prefix types stored, allowing the redundant "user.", "trusted."
etc. characters to be eliminated and more concisely stored.
8. Support for files, directories, symbolic links, device nodes, fifos
and sockets.
Xattr support for mksquashfs is now in squashfs CVS. Support for xattrs in
mksquashfs append mode, and in Unsquashfs will be finished ASAP.
The latest version of mksquashfs in CVS can be obtained here
http://sourceforge.net/projects/squashfs/develop
Kernel xattr support is in git, here
git://git.kernel.org/pub/scm/linux/kernel/git/pkl/squashfs-xattr.git master
gitweb http://git.kernel.org/?p=linux/kernel/git/pkl/squashfs-xattr.git;a=summary
Phillip
reply other threads:[~2010-05-19 3:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BF35DFD.7050609@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=linux-embedded@vger.kernel.org \
--cc=phillip.lougher@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).