Re: mkfs.jffs2 not compiling, which acl.h?

[Glen Johnson <gjohnson@valcom.com>]

David Woodhouse wrote:
> There is something broken about your toolchain if _either_
> <linux/posix_acl.h> or <asm/atomic.h> exist. Those are _not_ headers
> which the kernel exports when you run 'make headers_install' to generate
> the headers for userspace to use. Please make sure you report this
> problem to whoever generated your toolchain.
>   
I am using m68k-uclinux-tools-20060615 used with the uClinux
distribution for embedded systems. 
> Actually, I'm not entirely sure what this code is doing at all -- isn't
> it interpreting on-disk xattrs representing ACLs assuming that they're
> in the same format as ext3 uses? 
I was pointed to this link to answer why ACL is used in mkfs.jffs2.

http://thread.gmane.org/gmane.linux.drivers.mtd/16740/focus=16745

This is an excerpt from the above link.
"The access control list(ACL) enables higher flexible access control
based on UNIX users and groups than traditional user/group/others model.
'--with-xattr' or '--with-posix-acl' options on mkfs.jffs2 enables to
copy the ACLs associated with any files in host environment into jffs2
image file.
The purpose of this feature is improvement of security in embedded region."

This link also describes the compile flag WITHOUT_XATTR=1 which will disable this code.