Messages in this thread | | | From | Subodh Nijsure <> | Subject | RE: [v4] Add security.* XATTR support for the UBIFS | Date | Wed, 16 Jan 2013 22:38:31 +0000 |
| |
Marc,
On 01/15/2013 04:48 PM, Marc Kleine-Budde wrote: > On 05/13/2012 05:24 AM, Subodh Nijsure wrote: >> From: Subodh Nijsure <snijsure@grid-net.com> >> >> Also fix couple of bugs in UBIFS extended attribute length calculation. >> >> Changes in v4: >> Fix lock issues introduced in v3. >> Tested with CONFIG_SECURITY enabled & disabled. >> >> Changes in v3: >> Remove #ifdef CONFIG_UBIFS_FS_XATTR >> >> Changes in v2: >> Instead of just handling security.selinux extended attribute handle >> all security.* attributes. >> >> TESTING: Tested on MX28 based platforms using Micron MT29F2G08ABAEAH4 NAND >> With these change we are able to label UBIFS filesystem with >> security.selinux and run system with selinux enabled. >> This change also allows one to set other security.* extended >> attributes, such as security.smack security.evm, security.ima >> Ran integck test on UBI filesystem. >> This patch set has been tested with CONFIG_LOCKDEP=y and other options >> suggested in Submitchecklist >> >> Signed-off-by: Subodh Nijsure <snijsure@grid-net.com> > > What's the status of this patch? Was there a v5?
>I've ported v4 to v3.7.2 and get this deadlock:
Sorry I didn't try to push it and now I am on family leave to take care of new baby at home till end of March. I don't have access to hardware any more to try this at home, so I would certainly get to it till beginning of April.
-Subodh
| |