mkfs.jffs2 not compiling, which acl.h?

David Woodhouse dwmw2 at
Thu Dec 7 10:26:04 EST 2006

On Wed, 2006-12-06 at 08:56 -0500, Glen Johnson wrote:
> I tried #include <linux/posix_acl.h> in place of <sys/acl.h> and got
> warnings about not other info.  If I #include <asm-m68knommu/atomic.h>
> all the warnings and errors dissappear. 

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.

The acl.h which you should be using comes from libacl -- although we
only use about 6 #defines from it and don't link against the library.
Perhaps we should just copy those instead of requiring the header?

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? If you use mkfs.jffs2 on a big-endian
system, actually reading _from_ a jffs2 filesystem, does it do the right
thing? What about from other file systems?



More information about the linux-mtd mailing list