Hi,
I've been playing with out-of-tree building of gfs related modules
(actually, creating ebuilds for gfs), and found out one really stupid
thing:
You cannot successfuly build gfs-kernel modules if you don't have at
least one "regular" filesystem build in kernel with Posix ACL support.
The thing is that gfs-kernel tree modules expect to have posix_acl*
symbols available from already build kernel.
Perhaps it's not a "bug" in gfs-kernel after all, since kernel
documentation states:
--- fs/KConfig ---
config FS_POSIX_ACL
# Posix ACL utility routines (for now, only ext2/ext3/jfs/reiserfs)
#
# NOTE: you can implement Posix ACLs without these helpers (XFS does).
# Never use this symbol for ifdefs.
#
bool
depends on EXT2_FS_POSIX_ACL || EXT3_FS_POSIX_ACL ||
JFS_POSIX_ACL || REISERFS_FS_POSIX_ACL
default y
--- fs/KConfig ---
but, on the other hand, it doesn't put CONFIG_FS_POSIX_ACL in .config,
so fs/Makefile ignores posix_acl.o and xattr.o when compiliing kernel.
Is this gfs or kernel issue? Can we locally correct this (somehow force
the compilation of fs/posix_acl.o and fs/xattr.o if not available) or do
we have report this to LKML?
Quick fix would be to compile kernel with EXT3_FS_POSIX_ACL, but i'm not
sure what side-effects would that have on ext3 filesystems.
--
Lazar Obradovic, System Engineer
-----
laza@xxxxxx
YUnet International http://www.EUnet.yu
Dubrovacka 35/III, 11000 Belgrade
Tel: +381 11 3119901; Fax: +381 11 3119901
-----
This e-mail is confidential and intended only for the recipient.
Unauthorized distribution, modification or disclosure of its
contents is prohibited. If you have received this e-mail in error,
please notify the sender by telephone +381 11 3119901.
-----
