kernel source refers to non-existent CONFIG variables
from the output of a scanning script i have, there are a number of
CONFIG variables that are tested in the linux kernel source but are not defined anywhere in a Kconfig file:
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
NILFS_FS_POSIX_ACL
fs/nilfs2/inode.c:312:#ifdef CONFIG_NILFS_FS_POSIX_ACL fs/nilfs2/inode.c:437:#ifdef CONFIG_NILFS_FS_POSIX_ACL
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
NILFS_POSIX_ACL
fs/nilfs2/nilfs.h:61:#ifdef CONFIG_NILFS_POSIX_ACL fs/nilfs2/nilfs.h:200:#ifdef CONFIG_NILFS_POSIX_ACL fs/nilfs2/super.c:192:#ifdef CONFIG_NILFS_POSIX_ACL
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
NILFS_XATTR
fs/nilfs2/nilfs.h:51:#ifdef CONFIG_NILFS_XATTR
fs/nilfs2/super.c:165:#ifdef CONFIG_NILFS_XATTR
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday
========================================================================
Hi!
Quoted 8 lines · Robert P. J. Day
from the output of a scanning script i have, there are a number of
CONFIG variables that are tested in the linux kernel source but are not defined anywhere in aKconfigfile:Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
NILFS_FS_POSIX_ACLfs/nilfs2/inode.c:312:#ifdef
CONFIG_NILFS_FS_POSIX_ACLfs/nilfs2/inode.c:437:#ifdefCONFIG_NILFS_FS_POSIX_ACLQuoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
NILFS_POSIX_ACL
Quoted 8 lines
fs/nilfs2/nilfs.h:61:#ifdef
CONFIG_NILFS_POSIX_ACLfs/nilfs2/nilfs.h:200:#ifdefCONFIG_NILFS_POSIX_ACLfs/nilfs2/super.c:192:#ifdefCONFIG_NILFS_POSIX_ACLQuoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
NILFS_XATTRfs/nilfs2/nilfs.h:51:#ifdef
CONFIG_NILFS_XATTR
fs/nilfs2/super.c:165:#ifdefCONFIG_NILFS_XATTRrday
These features are planned but not embarked on.
That is the reason why they are left there.
When we really implement them, of course, we will declare in the Kconfig file.
Thanks for the feedback.
Ryusuke Konishi