JFFS2 Extended attributes support & SELinux in handhelds
Hi,
I've been working in implementing extended attributes support in the JFFS2 filesystem.
During the (short) time I worked on it, I just decided to try to bring back the thread on SELinux in hand-held and embedded devices and see if there's someone interested in contributing to it and collaborating to make something out of it.
The current work is just a draft, I've started with the standard Vanilla kernel sources plus mtd JFFS2 sources, used to patch the vanilla ones for latest code (I'm confused on which one has the most updated tree or if there are special differences between mtd's trees and vanilla's), and implemented the skeleton using the reiserfs xattr code base.
Then Russell Coker commented to me that I should use the handhelds.org kernel, so, I have the doubt on which one use, even if porting the changes made to JFFS2 code base to vanilla sources wouldn't be difficult, at least I suppose.
I've opened a few wiki pages for discussion and documenting until it gets further developed:
http://wiki.tuxedo-es.org/tuxedo/JFFS2xattr
http://wiki.tuxedo-es.org/tuxedo/SELinuxEmbedded
In addition, having someone experienced with xattr API could be great, as development documentation seems inexistent, among James Morris' merged xattr consolidation code.
Thanks in advance,
Cheers.
Signature · 2 lines
Lorenzo Hernández García-Hierro <[email protected]> [1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
Quoted 4 lines · Lorenzo Hernández García-Hierro
Hi,
I've been working in implementing extended attributes support in the JFFS2 filesystem.
You should send this to the JFFS2 development list. The xattr support is probably a JFFS3 candidate.
Quoted 6 lines
The current work is just a draft, I've started with the standard Vanilla kernel sources plus mtd JFFS2 sources, used to patch the vanilla ones for latest code (I'm confused on which one has the most updated tree or if there are special differences between mtd's trees and vanilla's), and implemented the skeleton using the reiserfs xattr code base.
The mtd tree is the most current. Any development would probably get the most benefit from being done there. Especially since JFFS3 doesn't exist anywhere else :).
Quoted 3 lines
In addition, having someone experienced with xattr API could be great, as development documentation seems inexistent, among James Morris' merged xattr consolidation code.
There have been some xattr proposals discussed on the MTD and JFFS2 mailing lists. They might be a starting place for you.
josh
Quoted 6 lines · Josh Boyer
You should send this to the JFFS2 development list. The xattr support is probably a JFFS3 candidate.
The mtd tree is the most current. Any development would probably get the most benefit from being done there. Especially since JFFS3 doesn't exist anywhere else :).
As we have talked in #mtd, I've moved everything to JFFS3 code and re-worked the pretty basic stuff that was already done, as a really dirty night-hack.
I hadn't time to fix the remaining errors (no, it's not a working patch), nor the remaining "stolen" ReiserFS code that needs to be modified in order to make JFFS3 happy with it (priv. directory handling in xattr initialization, etc).
I'm going to have limited time for it, I have exams these two weeks and also finish some other work in progress.
I've uploaded a patch that applies to 2.6.11-rc4 tree, with latest mtd tree included.
http://pearls.tuxedo-es.org/patches/mtd-jffs3-xattr-20050222-2.6.11-rc4.patch
(998Kb)
I would appreciate any collaboration and help with it.
Cheers, thanks in advance and enjoy (not working) it. :)
Signature · 2 lines
Lorenzo Hernández García-Hierro <[email protected]> [1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]