[Dev] Smack and xattr relationship - raw flash

Schaufler, Casey casey.schaufler at intel.com
Wed May 28 13:44:27 GMT 2014

> -----Original Message-----
> From: Dev [mailto:dev-bounces at lists.tizen.org] On Behalf Of Counihan, Tom
> Sent: Wednesday, May 28, 2014 3:31 AM
> To: dev at lists.tizen.org
> Subject: [Dev] Smack and xattr relationship - raw flash
> Hi Folks,
> Here: http://schaufler-ca.com/description_from_the_linux_source_tree  I
> read:
> " It requires netlabel and works best with file systems that support extended
> attributes, although xattr support is not strictly required".
> I'm curious to learn more the scalability of Smack across filesystems.
> The 'not strictly' statement implies a non-issue.
> What if my device uses raw flash - will for example ubifs work with Smack as
> comprehensively as say ext4 on a block device?

Filesystems that don't support xattrs can be used with Smack,
but files cannot be labeled individually. Instead, mount options
(smackfsroot and smackfsdefault) are used to specify the Smack
labels of all the files on the filesystem. You could construct a
system using only single-label filesystems if you had to.

I have not tried the xattr support in ubifs, but the literature
claims that it is "much improved" as of early last year. If
the xattr support in ubifs functions properly you will be able
to use it instead of ext4.

> Warm Regards
> Tom.
> Automotive Solutions Division (ASD)
> Intel Shannon,
> Brookvale Plaza,
> East Park,
> Shannon,
> Co. Clare,
> Ireland
> Tel : +353 61 477718
> --------------------------------------------------------------
> Intel Shannon Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263 Business address: Dromore House, East Park,
> Shannon, Co. Clare
> This e-mail and any attachments may contain confidential material for the
> sole use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact the
> sender and delete all copies.
> _______________________________________________
> Dev mailing list
> Dev at lists.tizen.org
> https://lists.tizen.org/listinfo/dev

More information about the Dev mailing list