mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-23 20:53:53 +08:00
573ea5fcf0
There exist two build failures reported by Randy Dunlap as follows. (on i386) a. (config-r8857) ERROR: "f2fs_xattr_advise_handler" [fs/f2fs/f2fs.ko] undefined! Key configs in (config-r8857) are as follows. CONFIG_F2FS_FS=m # CONFIG_F2FS_STAT_FS is not set CONFIG_F2FS_FS_XATTR=y # CONFIG_F2FS_FS_POSIX_ACL is not set The error was occurred due to the function location that we made a mistake. Recently we added a new functionality for users to indicate cold files explicitly through xattr operations (i.e., f2fs_xattr_advise_handler). This handler should have been added in xattr.c instead of acl.c in order to avoid an undefined operation like in this case where XATTR is set and ACL is not set. b. (config-r8855) fs/f2fs/file.c: In function 'f2fs_vm_page_mkwrite': fs/f2fs/file.c:97:2: error: implicit declaration of function 'block_page_mkwrite_return' Key config in (config-r8855) is CONFIG_BLOCK. Obviously, f2fs works on top of the block device so that we should consider carefully a sort of config dependencies. The reason why this error was occurred was that f2fs_vm_page_mkwrite() calls block_page_mkwrite_return() which is enalbed only if CONFIG_BLOCK is set. Reported-by: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com> Acked-by: Randy Dunlap <rdunlap@xenotime.net>
54 lines
1.8 KiB
Plaintext
54 lines
1.8 KiB
Plaintext
config F2FS_FS
|
|
tristate "F2FS filesystem support (EXPERIMENTAL)"
|
|
depends on BLOCK
|
|
help
|
|
F2FS is based on Log-structured File System (LFS), which supports
|
|
versatile "flash-friendly" features. The design has been focused on
|
|
addressing the fundamental issues in LFS, which are snowball effect
|
|
of wandering tree and high cleaning overhead.
|
|
|
|
Since flash-based storages show different characteristics according to
|
|
the internal geometry or flash memory management schemes aka FTL, F2FS
|
|
and tools support various parameters not only for configuring on-disk
|
|
layout, but also for selecting allocation and cleaning algorithms.
|
|
|
|
If unsure, say N.
|
|
|
|
config F2FS_STAT_FS
|
|
bool "F2FS Status Information"
|
|
depends on F2FS_FS && DEBUG_FS
|
|
default y
|
|
help
|
|
/sys/kernel/debug/f2fs/ contains information about all the partitions
|
|
mounted as f2fs. Each file shows the whole f2fs information.
|
|
|
|
/sys/kernel/debug/f2fs/status includes:
|
|
- major file system information managed by f2fs currently
|
|
- average SIT information about whole segments
|
|
- current memory footprint consumed by f2fs.
|
|
|
|
config F2FS_FS_XATTR
|
|
bool "F2FS extended attributes"
|
|
depends on F2FS_FS
|
|
default y
|
|
help
|
|
Extended attributes are name:value pairs associated with inodes by
|
|
the kernel or by users (see the attr(5) manual page, or visit
|
|
<http://acl.bestbits.at/> for details).
|
|
|
|
If unsure, say N.
|
|
|
|
config F2FS_FS_POSIX_ACL
|
|
bool "F2FS Access Control Lists"
|
|
depends on F2FS_FS_XATTR
|
|
select FS_POSIX_ACL
|
|
default y
|
|
help
|
|
Posix Access Control Lists (ACLs) support permissions for users and
|
|
gourps beyond the owner/group/world scheme.
|
|
|
|
To learn more about Access Control Lists, visit the POSIX ACLs for
|
|
Linux website <http://acl.bestbits.at/>.
|
|
|
|
If you don't know what Access Control Lists are, say N
|