Файловый менеджер - Редактировать - /var/www/html/fs.zip
Ðазад
PK ! 9��6T T romfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config ROMFS_FS tristate "ROM file system support" depends on BLOCK || MTD help This is a very small read-only file system mainly intended for initial ram disks of installation disks, but it could be used for other read-only media as well. Read <file:Documentation/filesystems/romfs.rst> for details. To compile this file system support as a module, choose M here: the module will be called romfs. Note that the file system of your root partition (the one containing the directory /) cannot be a module. If you don't know whether you need it, then you don't need it: answer N. # # Select the backing stores to be supported # choice prompt "RomFS backing stores" depends on ROMFS_FS default ROMFS_BACKED_BY_BLOCK help Select the backing stores to be supported. config ROMFS_BACKED_BY_BLOCK bool "Block device-backed ROM file system support" depends on BLOCK help This permits ROMFS to use block devices buffered through the page cache as the medium from which to retrieve data. It does not allow direct mapping of the medium. If unsure, answer Y. config ROMFS_BACKED_BY_MTD bool "MTD-backed ROM file system support" depends on MTD=y || (ROMFS_FS=m && MTD) help This permits ROMFS to use MTD based devices directly, without the intercession of the block layer (which may have been disabled). It also allows direct mapping of MTD devices through romfs files under NOMMU conditions if the underlying device is directly addressable by the CPU. If unsure, answer Y. config ROMFS_BACKED_BY_BOTH bool "Both the above" depends on BLOCK && (MTD=y || (ROMFS_FS=m && MTD)) endchoice config ROMFS_ON_BLOCK bool default y if ROMFS_BACKED_BY_BLOCK || ROMFS_BACKED_BY_BOTH config ROMFS_ON_MTD bool default y if ROMFS_BACKED_BY_MTD || ROMFS_BACKED_BY_BOTH PK ! ���� � romfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the linux RomFS filesystem routines. # obj-$(CONFIG_ROMFS_FS) += romfs.o romfs-y := storage.o super.o ifneq ($(CONFIG_MMU),y) romfs-$(CONFIG_ROMFS_ON_MTD) += mmap-nommu.o endif PK ! W�״ � devpts/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Linux /dev/pts virtual filesystem. # obj-$(CONFIG_UNIX98_PTYS) += devpts.o devpts-$(CONFIG_UNIX98_PTYS) := inode.o PK ! �� � jbd2/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config JBD2 tristate select CRC32 select CRYPTO select CRYPTO_CRC32C help This is a generic journaling layer for block devices that support both 32-bit and 64-bit block numbers. It is currently used by the ext4 and OCFS2 filesystems, but it could also be used to add journal support to other file systems or block devices such as RAID or LVM. If you are using ext4 or OCFS2, you need to say Y here. If you are not using ext4 or OCFS2 then you will probably want to say N. To compile this device as a module, choose M here. The module will be called jbd2. If you are compiling ext4 or OCFS2 into the kernel, you cannot compile this code as a module. config JBD2_DEBUG bool "JBD2 (ext4) debugging support" depends on JBD2 help If you are using the ext4 journaled file system (or potentially any other filesystem/device using JBD2), this option allows you to enable debugging output while the system is running, in order to help track down any problems you are having. By default, the debugging output will be turned off. If you select Y here, then you will be able to turn on debugging with "echo N > /sys/module/jbd2/parameters/jbd2_debug", where N is a number between 1 and 5. The higher the number, the more debugging output is generated. To turn debugging off again, do "echo 0 > /sys/module/jbd2/parameters/jbd2_debug". PK ! i�=Z� � jbd2/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux journaling routines. # obj-$(CONFIG_JBD2) += jbd2.o jbd2-objs := transaction.o commit.o recovery.o checkpoint.o revoke.o journal.o PK ! F�w�8 8 xfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config XFS_FS tristate "XFS filesystem support" depends on BLOCK select EXPORTFS select LIBCRC32C select FS_IOMAP help XFS is a high performance journaling filesystem which originated on the SGI IRIX platform. It is completely multi-threaded, can support large files and large filesystems, extended attributes, variable block sizes, is extent based, and makes extensive use of Btrees (directories, extents, free space) to aid both performance and scalability. Refer to the documentation at <http://oss.sgi.com/projects/xfs/> for complete details. This implementation is on-disk compatible with the IRIX version of XFS. To compile this file system support as a module, choose M here: the module will be called xfs. Be aware, however, that if the file system of your root partition is compiled as a module, you'll need to use an initial ramdisk (initrd) to boot. config XFS_SUPPORT_V4 bool "Support deprecated V4 (crc=0) format" depends on XFS_FS default y help The V4 filesystem format lacks certain features that are supported by the V5 format, such as metadata checksumming, strengthened metadata verification, and the ability to store timestamps past the year 2038. Because of this, the V4 format is deprecated. All users should upgrade by backing up their files, reformatting, and restoring from the backup. Administrators and users can detect a V4 filesystem by running xfs_info against a filesystem mountpoint and checking for a string beginning with "crc=". If the string "crc=0" is found, the filesystem is a V4 filesystem. If no such string is found, please upgrade xfsprogs to the latest version and try again. This option will become default N in September 2025. Support for the V4 format will be removed entirely in September 2030. Distributors can say N here to withdraw support earlier. To continue supporting the old V4 format (crc=0), say Y. To close off an attack surface, say N. config XFS_QUOTA bool "XFS Quota support" depends on XFS_FS select QUOTACTL help If you say Y here, you will be able to set limits for disk usage on a per user and/or a per group basis under XFS. XFS considers quota information as filesystem metadata and uses journaling to provide a higher level guarantee of consistency. The on-disk data format for quota is also compatible with the IRIX version of XFS, allowing a filesystem to be migrated between Linux and IRIX without any need for conversion. If unsure, say N. More comprehensive documentation can be found in README.quota in the xfsprogs package. XFS quota can be used either with or without the generic quota support enabled (CONFIG_QUOTA) - they are completely independent subsystems. config XFS_POSIX_ACL bool "XFS POSIX ACL support" depends on XFS_FS select FS_POSIX_ACL help POSIX Access Control Lists (ACLs) support permissions for users and groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N. config XFS_RT bool "XFS Realtime subvolume support" depends on XFS_FS help If you say Y here you will be able to mount and use XFS filesystems which contain a realtime subvolume. The realtime subvolume is a separate area of disk space where only file data is stored. It was originally designed to provide deterministic data rates suitable for media streaming applications, but is also useful as a generic mechanism for ensuring data and metadata/log I/Os are completely separated. Regular file I/Os are isolated to a separate device from all other requests, and this can be done quite transparently to applications via the inherit-realtime directory inode flag. See the xfs man page in section 5 for additional information. If unsure, say N. config XFS_ONLINE_SCRUB bool "XFS online metadata check support" default n depends on XFS_FS help If you say Y here you will be able to check metadata on a mounted XFS filesystem. This feature is intended to reduce filesystem downtime by supplementing xfs_repair. The key advantage here is to look for problems proactively so that they can be dealt with in a controlled manner. This feature is considered EXPERIMENTAL. Use with caution! See the xfs_scrub man page in section 8 for additional information. If unsure, say N. config XFS_ONLINE_REPAIR bool "XFS online metadata repair support" default n depends on XFS_FS && XFS_ONLINE_SCRUB help If you say Y here you will be able to repair metadata on a mounted XFS filesystem. This feature is intended to reduce filesystem downtime by fixing minor problems before they cause the filesystem to go down. However, it requires that the filesystem be formatted with secondary metadata, such as reverse mappings and inode parent pointers. This feature is considered EXPERIMENTAL. Use with caution! See the xfs_scrub man page in section 8 for additional information. If unsure, say N. config XFS_WARN bool "XFS Verbose Warnings" depends on XFS_FS && !XFS_DEBUG help Say Y here to get an XFS build with many additional warnings. It converts ASSERT checks to WARN, so will log any out-of-bounds conditions that occur that would otherwise be missed. It is much lighter weight than XFS_DEBUG and does not modify algorithms and will not cause the kernel to panic on non-fatal errors. However, similar to XFS_DEBUG, it is only advisable to use this if you are debugging a particular problem. config XFS_DEBUG bool "XFS Debugging support" depends on XFS_FS help Say Y here to get an XFS build with many debugging features, including ASSERT checks, function wrappers around macros, and extra sanity-checking functions in various code paths. Note that the resulting code will be HUGE and SLOW, and probably not useful unless you are debugging a particular problem. Say N unless you are an XFS developer, or you play one on TV. config XFS_ASSERT_FATAL bool "XFS fatal asserts" default y depends on XFS_FS && XFS_DEBUG help Set the default DEBUG mode ASSERT failure behavior. Say Y here to cause DEBUG mode ASSERT failures to result in fatal errors that BUG() the kernel by default. If you say N, ASSERT failures result in warnings. This behavior can be modified at runtime via sysfs. PK ! j�b xfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Copyright (c) 2000-2005 Silicon Graphics, Inc. # All Rights Reserved. # ccflags-y += -I $(srctree)/$(src) # needed for trace events ccflags-y += -I $(srctree)/$(src)/libxfs obj-$(CONFIG_XFS_FS) += xfs.o # this one should be compiled first, as the tracing macros can easily blow up xfs-y += xfs_trace.o # build the libxfs code first xfs-y += $(addprefix libxfs/, \ xfs_ag.o \ xfs_alloc.o \ xfs_alloc_btree.o \ xfs_attr.o \ xfs_attr_leaf.o \ xfs_attr_remote.o \ xfs_bit.o \ xfs_bmap.o \ xfs_bmap_btree.o \ xfs_btree.o \ xfs_btree_staging.o \ xfs_da_btree.o \ xfs_defer.o \ xfs_dir2.o \ xfs_dir2_block.o \ xfs_dir2_data.o \ xfs_dir2_leaf.o \ xfs_dir2_node.o \ xfs_dir2_sf.o \ xfs_dquot_buf.o \ xfs_ialloc.o \ xfs_ialloc_btree.o \ xfs_iext_tree.o \ xfs_inode_fork.o \ xfs_inode_buf.o \ xfs_log_rlimit.o \ xfs_ag_resv.o \ xfs_rmap.o \ xfs_rmap_btree.o \ xfs_refcount.o \ xfs_refcount_btree.o \ xfs_sb.o \ xfs_symlink_remote.o \ xfs_trans_inode.o \ xfs_trans_resv.o \ xfs_types.o \ ) # xfs_rtbitmap is shared with libxfs xfs-$(CONFIG_XFS_RT) += $(addprefix libxfs/, \ xfs_rtbitmap.o \ ) # highlevel code xfs-y += xfs_aops.o \ xfs_attr_inactive.o \ xfs_attr_list.o \ xfs_bmap_util.o \ xfs_bio_io.o \ xfs_buf.o \ xfs_dir2_readdir.o \ xfs_discard.o \ xfs_error.o \ xfs_export.o \ xfs_extent_busy.o \ xfs_file.o \ xfs_filestream.o \ xfs_fsmap.o \ xfs_fsops.o \ xfs_globals.o \ xfs_health.o \ xfs_icache.o \ xfs_ioctl.o \ xfs_iomap.o \ xfs_iops.o \ xfs_inode.o \ xfs_itable.o \ xfs_iwalk.o \ xfs_message.o \ xfs_mount.o \ xfs_mru_cache.o \ xfs_pwork.o \ xfs_reflink.o \ xfs_stats.o \ xfs_super.o \ xfs_symlink.o \ xfs_sysfs.o \ xfs_trans.o \ xfs_xattr.o \ kmem.o # low-level transaction/log code xfs-y += xfs_log.o \ xfs_log_cil.o \ xfs_bmap_item.o \ xfs_buf_item.o \ xfs_buf_item_recover.o \ xfs_dquot_item_recover.o \ xfs_extfree_item.o \ xfs_icreate_item.o \ xfs_inode_item.o \ xfs_inode_item_recover.o \ xfs_refcount_item.o \ xfs_rmap_item.o \ xfs_log_recover.o \ xfs_trans_ail.o \ xfs_trans_buf.o # optional features xfs-$(CONFIG_XFS_QUOTA) += xfs_dquot.o \ xfs_dquot_item.o \ xfs_trans_dquot.o \ xfs_qm_syscalls.o \ xfs_qm_bhv.o \ xfs_qm.o \ xfs_quotaops.o # xfs_rtbitmap is shared with libxfs xfs-$(CONFIG_XFS_RT) += xfs_rtalloc.o xfs-$(CONFIG_XFS_POSIX_ACL) += xfs_acl.o xfs-$(CONFIG_SYSCTL) += xfs_sysctl.o xfs-$(CONFIG_COMPAT) += xfs_ioctl32.o xfs-$(CONFIG_EXPORTFS_BLOCK_OPS) += xfs_pnfs.o # online scrub/repair ifeq ($(CONFIG_XFS_ONLINE_SCRUB),y) # Tracepoints like to blow up, so build that before everything else xfs-y += $(addprefix scrub/, \ trace.o \ agheader.o \ alloc.o \ attr.o \ bmap.o \ btree.o \ common.o \ dabtree.o \ dir.o \ fscounters.o \ health.o \ ialloc.o \ inode.o \ parent.o \ refcount.o \ rmap.o \ scrub.o \ symlink.o \ ) xfs-$(CONFIG_XFS_RT) += scrub/rtbitmap.o xfs-$(CONFIG_XFS_QUOTA) += scrub/quota.o # online repair ifeq ($(CONFIG_XFS_ONLINE_REPAIR),y) xfs-y += $(addprefix scrub/, \ agheader_repair.o \ bitmap.o \ repair.o \ ) endif endif PK ! ��n� � afs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config AFS_FS tristate "Andrew File System support (AFS)" depends on INET select AF_RXRPC select DNS_RESOLVER select NETFS_SUPPORT help If you say Y here, you will get an experimental Andrew File System driver. It currently only supports unsecured read-only AFS access. See <file:Documentation/filesystems/afs.rst> for more information. If unsure, say N. config AFS_DEBUG bool "AFS dynamic debugging" depends on AFS_FS help Say Y here to make runtime controllable debugging messages appear. See <file:Documentation/filesystems/afs.rst> for more information. If unsure, say N. config AFS_FSCACHE bool "Provide AFS client caching support" depends on AFS_FS=m && FSCACHE || AFS_FS=y && FSCACHE=y help Say Y here if you want AFS data to be cached locally on disk through the generic filesystem cache manager config AFS_DEBUG_CURSOR bool "AFS server cursor debugging" depends on AFS_FS help Say Y here to cause the contents of a server cursor to be dumped to the dmesg log if the server rotation algorithm fails to successfully contact a server. See <file:Documentation/filesystems/afs.rst> for more information. If unsure, say N. PK ! �mf�u u afs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for Red Hat Linux AFS client. # afs-cache-$(CONFIG_AFS_FSCACHE) := cache.o kafs-y := \ $(afs-cache-y) \ addr_list.o \ callback.o \ cell.o \ cmservice.o \ dir.o \ dir_edit.o \ dir_silly.o \ dynroot.o \ file.o \ flock.o \ fsclient.o \ fs_operation.o \ fs_probe.o \ inode.o \ main.o \ misc.o \ mntpt.o \ rotate.o \ rxrpc.o \ security.o \ server.o \ server_list.o \ super.o \ vlclient.o \ vl_alias.o \ vl_list.o \ vl_probe.o \ vl_rotate.o \ volume.o \ write.o \ xattr.o \ yfsclient.o kafs-$(CONFIG_PROC_FS) += proc.o obj-$(CONFIG_AFS_FS) := kafs.o PK ! pEc�} } lockd/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the linux lock manager stuff # obj-$(CONFIG_LOCKD) += lockd.o lockd-objs-y := clntlock.o clntproc.o clntxdr.o host.o svc.o svclock.o \ svcshare.o svcproc.o svcsubs.o mon.o xdr.o lockd-objs-$(CONFIG_LOCKD_V4) += clnt4xdr.o xdr4.o svc4proc.o lockd-objs-$(CONFIG_PROC_FS) += procfs.o lockd-objs := $(lockd-objs-y) PK ! ��~)� � ceph/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config CEPH_FS tristate "Ceph distributed file system" depends on INET select CEPH_LIB select LIBCRC32C select CRYPTO_AES select CRYPTO select NETFS_SUPPORT default n help Choose Y or M here to include support for mounting the experimental Ceph distributed file system. Ceph is an extremely scalable file system designed to provide high performance, reliable access to petabytes of storage. More information at https://ceph.io/. If unsure, say N. if CEPH_FS config CEPH_FSCACHE bool "Enable Ceph client caching support" depends on CEPH_FS=m && FSCACHE || CEPH_FS=y && FSCACHE=y help Choose Y here to enable persistent, read-only local caching support for Ceph clients using FS-Cache endif config CEPH_FS_POSIX_ACL bool "Ceph POSIX Access Control Lists" depends on CEPH_FS select FS_POSIX_ACL help POSIX Access Control Lists (ACLs) support permissions for users and groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N config CEPH_FS_SECURITY_LABEL bool "CephFS Security Labels" depends on CEPH_FS && SECURITY help Security labels support alternative access control models implemented by security modules like SELinux. This option enables an extended attribute handler for file security labels in the Ceph filesystem. If you are not using a security module that requires using extended attributes for file security labels, say N. PK ! oy+�t t ceph/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for CEPH filesystem. # obj-$(CONFIG_CEPH_FS) += ceph.o ceph-y := super.o inode.o dir.o file.o locks.o addr.o ioctl.o \ export.o caps.o snap.o xattr.o quota.o io.o \ mds_client.o mdsmap.o strings.o ceph_frag.o \ debugfs.o util.o metric.o ceph-$(CONFIG_CEPH_FSCACHE) += cache.o ceph-$(CONFIG_CEPH_FS_POSIX_ACL) += acl.o PK ! �!��� � fat/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config FAT_FS tristate select NLS help If you want to use one of the FAT-based file systems (the MS-DOS and VFAT (Windows 95) file systems), then you must say Y or M here to include FAT support. You will then be able to mount partitions or diskettes with FAT-based file systems and transparently access the files on them, i.e. MSDOS files will look and behave just like all other Unix files. This FAT support is not a file system in itself, it only provides the foundation for the other file systems. You will have to say Y or M to at least one of "MSDOS fs support" or "VFAT fs support" in order to make use of it. Another way to read and write MSDOS floppies and hard drive partitions from within Linux (but not transparently) is with the mtools ("man mtools") program suite. You don't need to say Y here in order to do that. If you need to move large files on floppies between a DOS and a Linux box, say Y here, mount the floppy under Linux with an MSDOS file system and use GNU tar's M option. GNU tar is a program available for Unix and DOS ("man tar" or "info tar"). The FAT support will enlarge your kernel by about 37 KB. If unsure, say Y. To compile this as a module, choose M here: the module will be called fat. Note that if you compile the FAT support as a module, you cannot compile any of the FAT-based file systems into the kernel -- they will have to be modules as well. config MSDOS_FS tristate "MSDOS fs support" select FAT_FS help This allows you to mount MSDOS partitions of your hard drive (unless they are compressed; to access compressed MSDOS partitions under Linux, you can either use the DOS emulator DOSEMU, described in the DOSEMU-HOWTO, available from <https://www.tldp.org/docs.html#howto>, or try dmsdosfs in <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you intend to use dosemu with a non-compressed MSDOS partition, say Y here) and MSDOS floppies. This means that file access becomes transparent, i.e. the MSDOS files look and behave just like all other Unix files. If you have Windows 95 or Windows NT installed on your MSDOS partitions, you should use the VFAT file system (say Y to "VFAT fs support" below), or you will not be able to see the long filenames generated by Windows 95 / Windows NT. This option will enlarge your kernel by about 7 KB. If unsure, answer Y. This will only work if you said Y to "DOS FAT fs support" as well. To compile this as a module, choose M here: the module will be called msdos. config VFAT_FS tristate "VFAT (Windows-95) fs support" select FAT_FS help This option provides support for normal Windows file systems with long filenames. That includes non-compressed FAT-based file systems used by Windows 95, Windows 98, Windows NT 4.0, and the Unix programs from the mtools package. The VFAT support enlarges your kernel by about 10 KB and it only works if you said Y to the "DOS FAT fs support" above. Please read the file <file:Documentation/filesystems/vfat.rst> for details. If unsure, say Y. To compile this as a module, choose M here: the module will be called vfat. config FAT_DEFAULT_CODEPAGE int "Default codepage for FAT" depends on FAT_FS default 437 help This option should be set to the codepage of your FAT filesystems. It can be overridden with the "codepage" mount option. See <file:Documentation/filesystems/vfat.rst> for more information. config FAT_DEFAULT_IOCHARSET string "Default iocharset for FAT" depends on VFAT_FS default "iso8859-1" help Set this to the default input/output character set you'd like FAT to use. It should probably match the character set that most of your FAT filesystems use, and can be overridden with the "iocharset" mount option for FAT filesystems. Note that "utf8" is not recommended for FAT filesystems. If unsure, you shouldn't set "utf8" here - select the next option instead if you would like to use UTF-8 encoded file names by default. See <file:Documentation/filesystems/vfat.rst> for more information. Enable any character sets you need in File Systems/Native Language Support. config FAT_DEFAULT_UTF8 bool "Enable FAT UTF-8 option by default" depends on VFAT_FS default n help Set this if you would like to have "utf8" mount option set by default when mounting FAT filesystems. Even if you say Y here can always disable UTF-8 for particular mount by adding "utf8=0" to mount options. Say Y if you use UTF-8 encoding for file names, N otherwise. See <file:Documentation/filesystems/vfat.rst> for more information. config FAT_KUNIT_TEST tristate "Unit Tests for FAT filesystems" if !KUNIT_ALL_TESTS depends on KUNIT && FAT_FS default KUNIT_ALL_TESTS help This builds the FAT KUnit tests For more information on KUnit and unit tests in general, please refer to the KUnit documentation in Documentation/dev-tools/kunit If unsure, say N PK ! �@��R R fat/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux fat filesystem support. # obj-$(CONFIG_FAT_FS) += fat.o obj-$(CONFIG_VFAT_FS) += vfat.o obj-$(CONFIG_MSDOS_FS) += msdos.o fat-y := cache.o dir.o fatent.o file.o inode.o misc.o nfs.o vfat-y := namei_vfat.o msdos-y := namei_msdos.o obj-$(CONFIG_FAT_KUNIT_TEST) += fat_test.o PK ! ��Y?! ?! pstore/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config PSTORE tristate "Persistent store support" select CRYPTO if PSTORE_COMPRESS default n help This option enables generic access to platform level persistent storage via "pstore" filesystem that can be mounted as /dev/pstore. Only useful if you have a platform level driver that registers with pstore to provide the data, so you probably should just go say "Y" (or "M") to a platform specific persistent store driver (e.g. ACPI_APEI on X86) which will select this for you. If you don't have a platform persistent store driver, say N. config PSTORE_DEFAULT_KMSG_BYTES int "Default kernel log storage space" if EXPERT depends on PSTORE default "10240" help Defines default size of pstore kernel log storage. Can be enlarged if needed, not recommended to shrink it. config PSTORE_DEFLATE_COMPRESS tristate "DEFLATE (ZLIB) compression" default y depends on PSTORE select CRYPTO_DEFLATE help This option enables DEFLATE (also known as ZLIB) compression algorithm support. config PSTORE_LZO_COMPRESS tristate "LZO compression" depends on PSTORE select CRYPTO_LZO help This option enables LZO compression algorithm support. config PSTORE_LZ4_COMPRESS tristate "LZ4 compression" depends on PSTORE select CRYPTO_LZ4 help This option enables LZ4 compression algorithm support. config PSTORE_LZ4HC_COMPRESS tristate "LZ4HC compression" depends on PSTORE select CRYPTO_LZ4HC help This option enables LZ4HC (high compression) mode algorithm. config PSTORE_842_COMPRESS bool "842 compression" depends on PSTORE select CRYPTO_842 help This option enables 842 compression algorithm support. config PSTORE_ZSTD_COMPRESS bool "zstd compression" depends on PSTORE select CRYPTO_ZSTD help This option enables zstd compression algorithm support. config PSTORE_COMPRESS def_bool y depends on PSTORE depends on PSTORE_DEFLATE_COMPRESS || PSTORE_LZO_COMPRESS || \ PSTORE_LZ4_COMPRESS || PSTORE_LZ4HC_COMPRESS || \ PSTORE_842_COMPRESS || PSTORE_ZSTD_COMPRESS choice prompt "Default pstore compression algorithm" depends on PSTORE_COMPRESS help This option chooses the default active compression algorithm. This change be changed at boot with "pstore.compress=..." on the kernel command line. Currently, pstore has support for 6 compression algorithms: deflate, lzo, lz4, lz4hc, 842 and zstd. The default compression algorithm is deflate. config PSTORE_DEFLATE_COMPRESS_DEFAULT bool "deflate" if PSTORE_DEFLATE_COMPRESS config PSTORE_LZO_COMPRESS_DEFAULT bool "lzo" if PSTORE_LZO_COMPRESS config PSTORE_LZ4_COMPRESS_DEFAULT bool "lz4" if PSTORE_LZ4_COMPRESS config PSTORE_LZ4HC_COMPRESS_DEFAULT bool "lz4hc" if PSTORE_LZ4HC_COMPRESS config PSTORE_842_COMPRESS_DEFAULT bool "842" if PSTORE_842_COMPRESS config PSTORE_ZSTD_COMPRESS_DEFAULT bool "zstd" if PSTORE_ZSTD_COMPRESS endchoice config PSTORE_COMPRESS_DEFAULT string depends on PSTORE_COMPRESS default "deflate" if PSTORE_DEFLATE_COMPRESS_DEFAULT default "lzo" if PSTORE_LZO_COMPRESS_DEFAULT default "lz4" if PSTORE_LZ4_COMPRESS_DEFAULT default "lz4hc" if PSTORE_LZ4HC_COMPRESS_DEFAULT default "842" if PSTORE_842_COMPRESS_DEFAULT default "zstd" if PSTORE_ZSTD_COMPRESS_DEFAULT config PSTORE_CONSOLE bool "Log kernel console messages" depends on PSTORE help When the option is enabled, pstore will log all kernel messages, even if no oops or panic happened. config PSTORE_PMSG bool "Log user space messages" depends on PSTORE select RT_MUTEXES help When the option is enabled, pstore will export a character interface /dev/pmsg0 to log user space messages. On reboot data can be retrieved from /sys/fs/pstore/pmsg-ramoops-[ID]. If unsure, say N. config PSTORE_FTRACE bool "Persistent function tracer" depends on PSTORE depends on FUNCTION_TRACER depends on DEBUG_FS help With this option kernel traces function calls into a persistent ram buffer that can be decoded and dumped after reboot through pstore filesystem. It can be used to determine what function was last called before a reset or panic. If unsure, say N. config PSTORE_RAM tristate "Log panic/oops to a RAM buffer" depends on PSTORE depends on HAS_IOMEM select REED_SOLOMON select REED_SOLOMON_ENC8 select REED_SOLOMON_DEC8 help This enables panic and oops messages to be logged to a circular buffer in RAM where it can be read back at some later point. Note that for historical reasons, the module will be named "ramoops.ko". For more information, see Documentation/admin-guide/ramoops.rst. config PSTORE_ZONE tristate depends on PSTORE help The common layer for pstore/blk (and pstore/ram in the future) to manage storage in zones. config PSTORE_BLK tristate "Log panic/oops to a block device" depends on PSTORE depends on BLOCK select PSTORE_ZONE default n help This enables panic and oops message to be logged to a block dev where it can be read back at some later point. For more information, see Documentation/admin-guide/pstore-blk.rst If unsure, say N. config PSTORE_BLK_BLKDEV string "block device identifier" depends on PSTORE_BLK default "" help Which block device should be used for pstore/blk. It accepts the following variants: 1) <hex_major><hex_minor> device number in hexadecimal representation, with no leading 0x, for example b302. 2) /dev/<disk_name> represents the device name of disk 3) /dev/<disk_name><decimal> represents the device name and number of partition - device number of disk plus the partition number 4) /dev/<disk_name>p<decimal> - same as the above, this form is used when disk name of partitioned disk ends with a digit. 5) PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF representing the unique id of a partition if the partition table provides it. The UUID may be either an EFI/GPT UUID, or refer to an MSDOS partition using the format SSSSSSSS-PP, where SSSSSSSS is a zero- filled hex representation of the 32-bit "NT disk signature", and PP is a zero-filled hex representation of the 1-based partition number. 6) PARTUUID=<UUID>/PARTNROFF=<int> to select a partition in relation to a partition with a known unique id. 7) <major>:<minor> major and minor number of the device separated by a colon. NOTE that, both Kconfig and module parameters can configure pstore/blk, but module parameters have priority over Kconfig. config PSTORE_BLK_KMSG_SIZE int "Size in Kbytes of kmsg dump log to store" depends on PSTORE_BLK default 64 help This just sets size of kmsg dump (oops, panic, etc) log for pstore/blk. The size is in KB and must be a multiple of 4. NOTE that, both Kconfig and module parameters can configure pstore/blk, but module parameters have priority over Kconfig. config PSTORE_BLK_MAX_REASON int "Maximum kmsg dump reason to store" depends on PSTORE_BLK default 2 help The maximum reason for kmsg dumps to store. The default is 2 (KMSG_DUMP_OOPS), see include/linux/kmsg_dump.h's enum kmsg_dump_reason for more details. NOTE that, both Kconfig and module parameters can configure pstore/blk, but module parameters have priority over Kconfig. config PSTORE_BLK_PMSG_SIZE int "Size in Kbytes of pmsg to store" depends on PSTORE_BLK depends on PSTORE_PMSG default 64 help This just sets size of pmsg (pmsg_size) for pstore/blk. The size is in KB and must be a multiple of 4. NOTE that, both Kconfig and module parameters can configure pstore/blk, but module parameters have priority over Kconfig. config PSTORE_BLK_CONSOLE_SIZE int "Size in Kbytes of console log to store" depends on PSTORE_BLK depends on PSTORE_CONSOLE default 64 help This just sets size of console log (console_size) to store via pstore/blk. The size is in KB and must be a multiple of 4. NOTE that, both Kconfig and module parameters can configure pstore/blk, but module parameters have priority over Kconfig. config PSTORE_BLK_FTRACE_SIZE int "Size in Kbytes of ftrace log to store" depends on PSTORE_BLK depends on PSTORE_FTRACE default 64 help This just sets size of ftrace log (ftrace_size) for pstore/blk. The size is in KB and must be a multiple of 4. NOTE that, both Kconfig and module parameters can configure pstore/blk, but module parameters have priority over Kconfig. PK ! � � pstore/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the linux pstorefs routines. # obj-$(CONFIG_PSTORE) += pstore.o pstore-objs += inode.o platform.o pstore-$(CONFIG_PSTORE_FTRACE) += ftrace.o pstore-$(CONFIG_PSTORE_PMSG) += pmsg.o ramoops-objs += ram.o ram_core.o obj-$(CONFIG_PSTORE_RAM) += ramoops.o pstore_zone-objs += zone.o obj-$(CONFIG_PSTORE_ZONE) += pstore_zone.o pstore_blk-objs += blk.o obj-$(CONFIG_PSTORE_BLK) += pstore_blk.o PK ! Jz�+t t ntfs3/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NTFS3_FS tristate "NTFS Read-Write file system support" select NLS help Windows OS native file system (NTFS) support up to NTFS version 3.1. Y or M enables the NTFS3 driver with full features enabled (read, write, journal replaying, sparse/compressed files support). File system type to use on mount is "ntfs3". Module name (M option) is also "ntfs3". Documentation: <file:Documentation/filesystems/ntfs3.rst> config NTFS3_64BIT_CLUSTER bool "64 bits per NTFS clusters" depends on NTFS3_FS && 64BIT help Windows implementation of ntfs.sys uses 32 bits per clusters. If activated 64 bits per clusters you will be able to use 4k cluster for 16T+ volumes. Windows will not be able to mount such volumes. It is recommended to say N here. config NTFS3_LZX_XPRESS bool "activate support of external compressions lzx/xpress" depends on NTFS3_FS help In Windows 10 one can use command "compact" to compress any files. 4 possible variants of compression are: xpress4k, xpress8k, xpress16k and lzx. If activated you will be able to read such files correctly. It is recommended to say Y here. config NTFS3_FS_POSIX_ACL bool "NTFS POSIX Access Control Lists" depends on NTFS3_FS select FS_POSIX_ACL help POSIX Access Control Lists (ACLs) support additional access rights for users and groups beyond the standard owner/group/world scheme, and this option selects support for ACLs specifically for ntfs filesystems. NOTE: this is linux only feature. Windows will ignore these ACLs. If you don't know what Access Control Lists are, say N. PK ! �� � � ntfs3/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the ntfs3 filesystem support. # # to check robot warnings ccflags-y += -Wint-to-pointer-cast \ $(call cc-option,-Wunused-but-set-variable,-Wunused-const-variable) \ $(call cc-option,-Wold-style-declaration,-Wout-of-line-declaration) obj-$(CONFIG_NTFS3_FS) += ntfs3.o ntfs3-y := attrib.o \ attrlist.o \ bitfunc.o \ bitmap.o \ dir.o \ fsntfs.o \ frecord.o \ file.o \ fslog.o \ inode.o \ index.o \ lznt.o \ namei.o \ record.o \ run.o \ super.o \ upcase.o \ xattr.o ntfs3-$(CONFIG_NTFS3_LZX_XPRESS) += $(addprefix lib/,\ decompress_common.o \ lzx_decompress.o \ xpress_decompress.o \ )PK ! tpd+ + zonefs/Kconfignu �[��� config ZONEFS_FS tristate "zonefs filesystem support" depends on BLOCK depends on BLK_DEV_ZONED select FS_IOMAP select CRC32 help zonefs is a simple file system which exposes zones of a zoned block device (e.g. host-managed or host-aware SMR disk drives) as files. If unsure, say N. PK ! �J Hv v zonefs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 ccflags-y += -I$(src) obj-$(CONFIG_ZONEFS_FS) += zonefs.o zonefs-y := super.o PK ! "\�Ac c cramfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config CRAMFS tristate "Compressed ROM file system support (cramfs)" select ZLIB_INFLATE help Saying Y here includes support for CramFs (Compressed ROM File System). CramFs is designed to be a simple, small, and compressed file system for ROM based embedded systems. CramFs is read-only, limited to 256MB file systems (with 16MB files), and doesn't support 16/32 bits uid/gid, hard links and timestamps. See <file:Documentation/filesystems/cramfs.rst> and <file:fs/cramfs/README> for further information. To compile this as a module, choose M here: the module will be called cramfs. Note that the root file system (the one containing the directory /) cannot be compiled as a module. This filesystem is limited in capabilities and performance on purpose to remain small and low on RAM usage. It is most suitable for small embedded systems. If you have ample RAM to spare, you may consider a more capable compressed filesystem such as SquashFS which is much better in terms of performance and features. If unsure, say N. config CRAMFS_BLOCKDEV bool "Support CramFs image over a regular block device" if EXPERT depends on CRAMFS && BLOCK default y help This option allows the CramFs driver to load data from a regular block device such a disk partition or a ramdisk. config CRAMFS_MTD bool "Support CramFs image directly mapped in physical memory" depends on CRAMFS && CRAMFS <= MTD default y if !CRAMFS_BLOCKDEV help This option allows the CramFs driver to load data directly from a linear adressed memory range (usually non volatile memory like flash) instead of going through the block device layer. This saves some memory since no intermediate buffering is necessary. The location of the CramFs image is determined by a MTD device capable of direct memory mapping e.g. from the 'physmap' map driver or a resulting MTD partition. For example, this would mount the cramfs image stored in the MTD partition named "xip_fs" on the /mnt mountpoint: mount -t cramfs mtd:xip_fs /mnt If unsure, say N. PK ! ��-�� � cramfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux cramfs routines. # obj-$(CONFIG_CRAMFS) += cramfs.o cramfs-objs := inode.o uncompress.o PK ! �g�m� � freevxfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config VXFS_FS tristate "FreeVxFS file system support (VERITAS VxFS(TM) compatible)" depends on BLOCK help FreeVxFS is a file system driver that support the VERITAS VxFS(TM) file system format. VERITAS VxFS(TM) is the standard file system of SCO UnixWare (and possibly others) and optionally available for Sunsoft Solaris, HP-UX and many other operating systems. However these particular OS implementations of vxfs may differ in on-disk data endianess and/or superblock offset. The vxfs module has been tested with SCO UnixWare and HP-UX B.10.20 (pa-risc 1.1 arch.) Currently only readonly access is supported and VxFX versions 2, 3 and 4. Tests were performed with HP-UX VxFS version 3. NOTE: the file system type as used by mount(1), mount(2) and fstab(5) is 'vxfs' as it describes the file system format, not the actual driver. There is a userspace utility for HP-UX logical volumes which makes creating HP-UX logical volumes easy from HP-UX disk block device file or regular file with image of the disk. See: https://sourceforge.net/projects/linux-vxfs/ To compile this as a module, choose M here: the module will be called freevxfs. If unsure, say N. PK ! ��(� � freevxfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # VxFS Makefile # obj-$(CONFIG_VXFS_FS) += freevxfs.o freevxfs-objs := vxfs_bmap.o vxfs_fshead.o vxfs_immed.o vxfs_inode.o \ vxfs_lookup.o vxfs_olt.o vxfs_subr.o vxfs_super.o PK ! \� �� � configfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config CONFIGFS_FS tristate "Userspace-driven configuration filesystem" select SYSFS help configfs is a RAM-based filesystem that provides the converse of sysfs's functionality. Where sysfs is a filesystem-based view of kernel objects, configfs is a filesystem-based manager of kernel objects, or config_items. Both sysfs and configfs can and should exist together on the same system. One is not a replacement for the other. PK ! �t�e� � configfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the configfs virtual filesystem # obj-$(CONFIG_CONFIGFS_FS) += configfs.o configfs-objs := inode.o file.o dir.o symlink.o mount.o item.o PK ! ��H�u u crypto/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config FS_ENCRYPTION bool "FS Encryption (Per-file encryption)" select CRYPTO select CRYPTO_HASH select CRYPTO_SKCIPHER select CRYPTO_LIB_SHA256 select KEYS help Enable encryption of files and directories. This feature is similar to ecryptfs, but it is more memory efficient since it avoids caching the encrypted and decrypted pages in the page cache. Currently Ext4, F2FS and UBIFS make use of this feature. # Filesystems supporting encryption must select this if FS_ENCRYPTION. This # allows the algorithms to be built as modules when all the filesystems are, # whereas selecting them from FS_ENCRYPTION would force them to be built-in. # # Note: this option only pulls in the algorithms that filesystem encryption # needs "by default". If userspace will use "non-default" encryption modes such # as Adiantum encryption, then those other modes need to be explicitly enabled # in the crypto API; see Documentation/filesystems/fscrypt.rst for details. # # Also note that this option only pulls in the generic implementations of the # algorithms, not any per-architecture optimized implementations. It is # strongly recommended to enable optimized implementations too. It is safe to # disable these generic implementations if corresponding optimized # implementations will always be available too; for this reason, these are soft # dependencies ('imply' rather than 'select'). Only disable these generic # implementations if you're sure they will never be needed, though. config FS_ENCRYPTION_ALGS tristate imply CRYPTO_AES imply CRYPTO_CBC imply CRYPTO_CTS imply CRYPTO_ECB imply CRYPTO_HMAC imply CRYPTO_SHA512 imply CRYPTO_XTS config FS_ENCRYPTION_INLINE_CRYPT bool "Enable fscrypt to use inline crypto" depends on FS_ENCRYPTION && BLK_INLINE_ENCRYPTION help Enable fscrypt to use inline encryption hardware if available. PK ! �!- O O crypto/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_FS_ENCRYPTION) += fscrypto.o fscrypto-y := crypto.o \ fname.o \ hkdf.o \ hooks.o \ keyring.o \ keysetup.o \ keysetup_v1.o \ policy.o fscrypto-$(CONFIG_BLOCK) += bio.o fscrypto-$(CONFIG_FS_ENCRYPTION_INLINE_CRYPT) += inline_crypt.o PK ! w��� � affs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config AFFS_FS tristate "Amiga FFS file system support" depends on BLOCK help The Fast File System (FFS) is the common file system used on hard disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y if you want to be able to read and write files from and to an Amiga FFS partition on your hard drive. Amiga floppies however cannot be read with this driver due to an incompatibility of the floppy controller used in an Amiga and the standard floppy controller in PCs and workstations. Read <file:Documentation/filesystems/affs.rst> and <file:fs/affs/Changes>. With this driver you can also mount disk files used by Bernd Schmidt's Un*X Amiga Emulator (<http://www.freiburg.linux.de/~uae/>). If you want to do this, you will also need to say Y or M to "Loop device support", above. To compile this file system support as a module, choose M here: the module will be called affs. If unsure, say N. PK ! ��N�� � affs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Linux affs filesystem routines. # #ccflags-y := -DDEBUG=1 obj-$(CONFIG_AFFS_FS) += affs.o affs-objs := super.o namei.o inode.o file.o dir.o amigaffs.o bitmap.o symlink.o PK ! �1�� ubifs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config UBIFS_FS tristate "UBIFS file system support" select CRC16 select CRC32 select CRYPTO if UBIFS_FS_ADVANCED_COMPR select CRYPTO if UBIFS_FS_LZO select CRYPTO if UBIFS_FS_ZLIB select CRYPTO if UBIFS_FS_ZSTD select CRYPTO_LZO if UBIFS_FS_LZO select CRYPTO_DEFLATE if UBIFS_FS_ZLIB select CRYPTO_ZSTD if UBIFS_FS_ZSTD select CRYPTO_HASH_INFO select UBIFS_FS_XATTR if FS_ENCRYPTION select FS_ENCRYPTION_ALGS if FS_ENCRYPTION depends on MTD_UBI help UBIFS is a file system for flash devices which works on top of UBI. if UBIFS_FS config UBIFS_FS_ADVANCED_COMPR bool "Advanced compression options" help This option allows to explicitly choose which compressions, if any, are enabled in UBIFS. Removing compressors means inability to read existing file systems. If unsure, say 'N'. config UBIFS_FS_LZO bool "LZO compression support" if UBIFS_FS_ADVANCED_COMPR default y help LZO compressor is generally faster than zlib but compresses worse. Say 'Y' if unsure. config UBIFS_FS_ZLIB bool "ZLIB compression support" if UBIFS_FS_ADVANCED_COMPR default y help Zlib compresses better than LZO but it is slower. Say 'Y' if unsure. config UBIFS_FS_ZSTD bool "ZSTD compression support" if UBIFS_FS_ADVANCED_COMPR depends on UBIFS_FS default y help ZSTD compresses is a big win in speed over Zlib and in compression ratio over LZO. Say 'Y' if unsure. config UBIFS_ATIME_SUPPORT bool "Access time support" default n help Originally UBIFS did not support atime, because it looked like a bad idea due increased flash wear. This option adds atime support and it is disabled by default to preserve the old behavior. If you enable this option, UBIFS starts updating atime, which means that file-system read operations will cause writes (inode atime updates). This may affect file-system performance and increase flash device wear, so be careful. How often atime is updated depends on the selected strategy: strictatime is the "heavy", relatime is "lighter", etc. If unsure, say 'N' config UBIFS_FS_XATTR bool "UBIFS XATTR support" default y help Saying Y here includes support for extended attributes (xattrs). Xattrs are name:value pairs associated with inodes by the kernel or by users (see the attr(5) manual page). If unsure, say Y. config UBIFS_FS_SECURITY bool "UBIFS Security Labels" depends on UBIFS_FS_XATTR default y help Security labels provide an access control facility to support Linux Security Models (LSMs) accepted by AppArmor, SELinux, Smack and TOMOYO Linux. This option enables an extended attribute handler for file security labels in the ubifs filesystem, so that it requires enabling the extended attribute support in advance. If you are not using a security module, say N. config UBIFS_FS_AUTHENTICATION bool "UBIFS authentication support" select KEYS select CRYPTO_HMAC select SYSTEM_DATA_VERIFICATION help Enable authentication support for UBIFS. This feature offers protection against offline changes for both data and metadata of the filesystem. If you say yes here you should also select a hashing algorithm such as sha256, these are not selected automatically since there are many different options. endif # UBIFS_FS PK ! ��U� � ubifs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_UBIFS_FS) += ubifs.o ubifs-y += shrinker.o journal.o file.o dir.o super.o sb.o io.o ubifs-y += tnc.o master.o scan.o replay.o log.o commit.o gc.o orphan.o ubifs-y += budget.o find.o tnc_commit.o compress.o lpt.o lprops.o ubifs-y += recovery.o ioctl.o lpt_commit.o tnc_misc.o debug.o ubifs-y += misc.o ubifs-$(CONFIG_FS_ENCRYPTION) += crypto.o ubifs-$(CONFIG_UBIFS_FS_XATTR) += xattr.o ubifs-$(CONFIG_UBIFS_FS_AUTHENTICATION) += auth.o PK ! ��<A� � 9p/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config 9P_FS tristate "Plan 9 Resource Sharing Support (9P2000)" depends on INET && NET_9P help If you say Y here, you will get experimental support for Plan 9 resource sharing via the 9P2000 protocol. See <http://v9fs.sf.net> for more information. If unsure, say N. if 9P_FS config 9P_FSCACHE bool "Enable 9P client caching support" depends on 9P_FS=m && FSCACHE || 9P_FS=y && FSCACHE=y help Choose Y here to enable persistent, read-only local caching support for 9p clients using FS-Cache config 9P_FS_POSIX_ACL bool "9P POSIX Access Control Lists" select FS_POSIX_ACL help POSIX Access Control Lists (ACLs) support permissions for users and groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N endif config 9P_FS_SECURITY bool "9P Security Labels" depends on 9P_FS help Security labels support alternative access control models implemented by security modules like SELinux. This option enables an extended attribute handler for file security labels in the 9P filesystem. If you are not using a security module that requires using extended attributes for file security labels, say N. PK ! �H�� 9p/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_9P_FS) := 9p.o 9p-objs := \ vfs_super.o \ vfs_inode.o \ vfs_inode_dotl.o \ vfs_addr.o \ vfs_file.o \ vfs_dir.o \ vfs_dentry.o \ v9fs.o \ fid.o \ xattr.o 9p-$(CONFIG_9P_FSCACHE) += cache.o 9p-$(CONFIG_9P_FS_POSIX_ACL) += acl.o PK ! W���� � udf/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config UDF_FS tristate "UDF file system support" select CRC_ITU_T select NLS help This is a file system used on some CD-ROMs and DVDs. Since the file system is supported by multiple operating systems and is more compatible with standard unix file systems, it is also suitable for removable USB disks. Say Y if you intend to mount DVD discs or CDRW's written in packet mode, or if you want to use UDF for removable USB disks. Please read <file:Documentation/filesystems/udf.rst>. To compile this file system support as a module, choose M here: the module will be called udf. If unsure, say N. PK ! 8bi� udf/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux udf-filesystem routines. # obj-$(CONFIG_UDF_FS) += udf.o udf-objs := balloc.o dir.o file.o ialloc.o inode.o lowlevel.o namei.o \ partition.o super.o truncate.o symlink.o \ directory.o misc.o udftime.o unicode.o PK ! �r�� � overlayfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config OVERLAY_FS tristate "Overlay filesystem support" select EXPORTFS help An overlay filesystem combines two filesystems - an 'upper' filesystem and a 'lower' filesystem. When a name exists in both filesystems, the object in the 'upper' filesystem is visible while the object in the 'lower' filesystem is either hidden or, in the case of directories, merged with the 'upper' object. For more information see Documentation/filesystems/overlayfs.rst config OVERLAY_FS_REDIRECT_DIR bool "Overlayfs: turn on redirect directory feature by default" depends on OVERLAY_FS help If this config option is enabled then overlay filesystems will use redirects when renaming directories by default. In this case it is still possible to turn off redirects globally with the "redirect_dir=off" module option or on a filesystem instance basis with the "redirect_dir=off" mount option. Note, that redirects are not backward compatible. That is, mounting an overlay which has redirects on a kernel that doesn't support this feature will have unexpected results. If unsure, say N. config OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW bool "Overlayfs: follow redirects even if redirects are turned off" default y depends on OVERLAY_FS help Disable this to get a possibly more secure configuration, but that might not be backward compatible with previous kernels. If backward compatibility is not an issue, then it is safe and recommended to say N here. For more information, see Documentation/filesystems/overlayfs.rst If unsure, say Y. config OVERLAY_FS_INDEX bool "Overlayfs: turn on inodes index feature by default" depends on OVERLAY_FS help If this config option is enabled then overlay filesystems will use the index directory to map lower inodes to upper inodes by default. In this case it is still possible to turn off index globally with the "index=off" module option or on a filesystem instance basis with the "index=off" mount option. The inodes index feature prevents breaking of lower hardlinks on copy up. Note, that the inodes index feature is not backward compatible. That is, mounting an overlay which has an inodes index on a kernel that doesn't support this feature will have unexpected results. If unsure, say N. config OVERLAY_FS_NFS_EXPORT bool "Overlayfs: turn on NFS export feature by default" depends on OVERLAY_FS depends on OVERLAY_FS_INDEX depends on !OVERLAY_FS_METACOPY help If this config option is enabled then overlay filesystems will use the index directory to decode overlay NFS file handles by default. In this case, it is still possible to turn off NFS export support globally with the "nfs_export=off" module option or on a filesystem instance basis with the "nfs_export=off" mount option. The NFS export feature creates an index on copy up of every file and directory. This full index is used to detect overlay filesystems inconsistencies on lookup, like redirect from multiple upper dirs to the same lower dir. The full index may incur some overhead on mount time, especially when verifying that directory file handles are not stale. Note, that the NFS export feature is not backward compatible. That is, mounting an overlay which has a full index on a kernel that doesn't support this feature will have unexpected results. Most users should say N here and enable this feature on a case-by- case basis with the "nfs_export=on" mount option. Say N unless you fully understand the consequences. config OVERLAY_FS_XINO_AUTO bool "Overlayfs: auto enable inode number mapping" default n depends on OVERLAY_FS depends on 64BIT help If this config option is enabled then overlay filesystems will use unused high bits in undelying filesystem inode numbers to map all inodes to a unified address space. The mapped 64bit inode numbers might not be compatible with applications that expect 32bit inodes. If compatibility with applications that expect 32bit inodes is not an issue, then it is safe and recommended to say Y here. For more information, see Documentation/filesystems/overlayfs.rst If unsure, say N. config OVERLAY_FS_METACOPY bool "Overlayfs: turn on metadata only copy up feature by default" depends on OVERLAY_FS select OVERLAY_FS_REDIRECT_DIR help If this config option is enabled then overlay filesystems will copy up only metadata where appropriate and data copy up will happen when a file is opened for WRITE operation. It is still possible to turn off this feature globally with the "metacopy=off" module option or on a filesystem instance basis with the "metacopy=off" mount option. Note, that this feature is not backward compatible. That is, mounting an overlay which has metacopy only inodes on a kernel that doesn't support this feature will have unexpected results. If unsure, say N. PK ! �� � � overlayfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the overlay filesystem. # obj-$(CONFIG_OVERLAY_FS) += overlay.o overlay-objs := super.o namei.o util.o inode.o file.o dir.o readdir.o \ copy_up.o export.o PK ! {ڿ�� � ocfs2/dlm/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_OCFS2_FS_O2CB) += ocfs2_dlm.o ocfs2_dlm-objs := dlmdomain.o dlmdebug.o dlmthread.o dlmrecovery.o \ dlmmaster.o dlmast.o dlmconvert.o dlmlock.o dlmunlock.o PK ! J\�w w ocfs2/dlmfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_OCFS2_FS) += ocfs2_dlmfs.o ocfs2_dlmfs-objs := userdlm.o dlmfs.o PK ! ��� � ocfs2/cluster/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_OCFS2_FS) += ocfs2_nodemanager.o ocfs2_nodemanager-objs := heartbeat.o masklog.o sys.o nodemanager.o \ quorum.o tcp.o netdebug.o PK ! ��X�� � ocfs2/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config OCFS2_FS tristate "OCFS2 file system support" depends on INET && SYSFS && CONFIGFS_FS select JBD2 select CRC32 select QUOTA select QUOTA_TREE select FS_POSIX_ACL help OCFS2 is a general purpose extent based shared disk cluster file system with many similarities to ext3. It supports 64 bit inode numbers, and has automatically extending metadata groups which may also make it attractive for non-clustered use. You'll want to install the ocfs2-tools package in order to at least get "mount.ocfs2". Project web page: https://oss.oracle.com/projects/ocfs2 Tools web page: https://oss.oracle.com/projects/ocfs2-tools OCFS2 mailing lists: https://oss.oracle.com/projects/ocfs2/mailman/ For more information on OCFS2, see the file <file:Documentation/filesystems/ocfs2.rst>. config OCFS2_FS_O2CB tristate "O2CB Kernelspace Clustering" depends on OCFS2_FS default y help OCFS2 includes a simple kernelspace clustering package, the OCFS2 Cluster Base. It only requires a very small userspace component to configure it. This comes with the standard ocfs2-tools package. O2CB is limited to maintaining a cluster for OCFS2 file systems. It cannot manage any other cluster applications. It is always safe to say Y here, as the clustering method is run-time selectable. config OCFS2_FS_USERSPACE_CLUSTER tristate "OCFS2 Userspace Clustering" depends on OCFS2_FS && DLM default y help This option will allow OCFS2 to use userspace clustering services in conjunction with the DLM in fs/dlm. If you are using a userspace cluster manager, say Y here. It is safe to say Y, as the clustering method is run-time selectable. config OCFS2_FS_STATS bool "OCFS2 statistics" depends on OCFS2_FS && DEBUG_FS default y help This option allows some fs statistics to be captured. Enabling this option may increase the memory consumption. config OCFS2_DEBUG_MASKLOG bool "OCFS2 logging support" depends on OCFS2_FS default y help The ocfs2 filesystem has an extensive logging system. The system allows selection of events to log via files in /sys/o2cb/logmask/. This option will enlarge your kernel, but it allows debugging of ocfs2 filesystem issues. config OCFS2_DEBUG_FS bool "OCFS2 expensive checks" depends on OCFS2_FS default n help This option will enable expensive consistency checks. Enable this option for debugging only as it is likely to decrease performance of the filesystem. PK ! P�� ocfs2/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 ccflags-y := -I$(src) obj-$(CONFIG_OCFS2_FS) += \ ocfs2.o \ ocfs2_stackglue.o obj-$(CONFIG_OCFS2_FS_O2CB) += ocfs2_stack_o2cb.o obj-$(CONFIG_OCFS2_FS_USERSPACE_CLUSTER) += ocfs2_stack_user.o ocfs2-objs := \ alloc.o \ aops.o \ blockcheck.o \ buffer_head_io.o \ dcache.o \ dir.o \ dlmglue.o \ export.o \ extent_map.o \ file.o \ heartbeat.o \ inode.o \ ioctl.o \ journal.o \ localalloc.o \ locks.o \ mmap.o \ namei.o \ refcounttree.o \ reservations.o \ move_extents.o \ resize.o \ slot_map.o \ suballoc.o \ super.o \ symlink.o \ sysfile.o \ uptodate.o \ quota_local.o \ quota_global.o \ xattr.o \ acl.o \ filecheck.o ocfs2_stackglue-objs := stackglue.o ocfs2_stack_o2cb-objs := stack_o2cb.o ocfs2_stack_user-objs := stack_user.o obj-$(CONFIG_OCFS2_FS) += dlmfs/ # cluster/ is always needed when OCFS2_FS for masklog support obj-$(CONFIG_OCFS2_FS) += cluster/ obj-$(CONFIG_OCFS2_FS_O2CB) += dlm/ PK ! Y���} } verity/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0 config FS_VERITY bool "FS Verity (read-only file-based authenticity protection)" select CRYPTO # SHA-256 is implied as it's intended to be the default hash algorithm. # To avoid bloat, other wanted algorithms must be selected explicitly. # Note that CRYPTO_SHA256 denotes the generic C implementation, but # some architectures provided optimized implementations of the same # algorithm that may be used instead. In this case, CRYPTO_SHA256 may # be omitted even if SHA-256 is being used. imply CRYPTO_SHA256 help This option enables fs-verity. fs-verity is the dm-verity mechanism implemented at the file level. On supported filesystems (currently EXT4 and F2FS), userspace can use an ioctl to enable verity for a file, which causes the filesystem to build a Merkle tree for the file. The filesystem will then transparently verify any data read from the file against the Merkle tree. The file is also made read-only. This serves as an integrity check, but the availability of the Merkle tree root hash also allows efficiently supporting various use cases where normally the whole file would need to be hashed at once, such as: (a) auditing (logging the file's hash), or (b) authenticity verification (comparing the hash against a known good value, e.g. from a digital signature). fs-verity is especially useful on large files where not all the contents may actually be needed. Also, fs-verity verifies data each time it is paged back in, which provides better protection against malicious disks vs. an ahead-of-time hash. If unsure, say N. config FS_VERITY_DEBUG bool "FS Verity debugging" depends on FS_VERITY help Enable debugging messages related to fs-verity by default. Say N unless you are an fs-verity developer. config FS_VERITY_BUILTIN_SIGNATURES bool "FS Verity builtin signature support" depends on FS_VERITY select SYSTEM_DATA_VERIFICATION help Support verifying signatures of verity files against the X.509 certificates that have been loaded into the ".fs-verity" kernel keyring. This is meant as a relatively simple mechanism that can be used to provide an authenticity guarantee for verity files, as an alternative to IMA appraisal. Userspace programs still need to check that the verity bit is set in order to get an authenticity guarantee. If unsure, say N. PK ! g2>�� � verity/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_FS_VERITY) += enable.o \ hash_algs.o \ init.o \ measure.o \ open.o \ read_metadata.o \ verify.o obj-$(CONFIG_FS_VERITY_BUILTIN_SIGNATURES) += signature.o PK ! ��� J J aufs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0 config AUFS_FS tristate "Aufs (Advanced multi layered unification filesystem) support" help Aufs is a stackable unification filesystem such as Unionfs, which unifies several directories and provides a merged single directory. In the early days, aufs was entirely re-designed and re-implemented Unionfs Version 1.x series. Introducing many original ideas, approaches and improvements, it becomes totally different from Unionfs while keeping the basic features. if AUFS_FS choice prompt "Maximum number of branches" default AUFS_BRANCH_MAX_127 help Specifies the maximum number of branches (or member directories) in a single aufs. The larger value consumes more system resources and has a minor impact to performance. config AUFS_BRANCH_MAX_127 bool "127" help Specifies the maximum number of branches (or member directories) in a single aufs. The larger value consumes more system resources and has a minor impact to performance. config AUFS_BRANCH_MAX_511 bool "511" help Specifies the maximum number of branches (or member directories) in a single aufs. The larger value consumes more system resources and has a minor impact to performance. config AUFS_BRANCH_MAX_1023 bool "1023" help Specifies the maximum number of branches (or member directories) in a single aufs. The larger value consumes more system resources and has a minor impact to performance. config AUFS_BRANCH_MAX_32767 bool "32767" help Specifies the maximum number of branches (or member directories) in a single aufs. The larger value consumes more system resources and has a minor impact to performance. endchoice config AUFS_SBILIST bool depends on AUFS_MAGIC_SYSRQ || PROC_FS default y help Automatic configuration for internal use. When aufs supports Magic SysRq or /proc, enabled automatically. config AUFS_HNOTIFY bool "Detect direct branch access (bypassing aufs)" help If you want to modify files on branches directly, eg. bypassing aufs, and want aufs to detect the changes of them fully, then enable this option and use 'udba=notify' mount option. Currently there is only one available configuration, "fsnotify". It will have a negative impact to the performance. See detail in aufs.5. choice prompt "method" if AUFS_HNOTIFY default AUFS_HFSNOTIFY config AUFS_HFSNOTIFY bool "fsnotify" select FSNOTIFY endchoice config AUFS_EXPORT bool "NFS-exportable aufs" depends on EXPORTFS help If you want to export your mounted aufs via NFS, then enable this option. There are several requirements for this configuration. See detail in aufs.5. config AUFS_INO_T_64 bool depends on AUFS_EXPORT depends on 64BIT default y help Automatic configuration for internal use. /* typedef unsigned long/int __kernel_ino_t */ /* alpha and s390x are int */ config AUFS_XATTR bool "support for XATTR/EA (including Security Labels)" help If your branch fs supports XATTR/EA and you want to make them available in aufs too, then enable this opsion and specify the branch attributes for EA. See detail in aufs.5. config AUFS_FHSM bool "File-based Hierarchical Storage Management" help Hierarchical Storage Management (or HSM) is a well-known feature in the storage world. Aufs provides this feature as file-based. with multiple branches. These multiple branches are prioritized, ie. the topmost one should be the fastest drive and be used heavily. config AUFS_RDU bool "Readdir in userspace" help Aufs has two methods to provide a merged view for a directory, by a user-space library and by kernel-space natively. The latter is always enabled but sometimes large and slow. If you enable this option, install the library in aufs2-util package, and set some environment variables for your readdir(3), then the work will be handled in user-space which generally shows better performance in most cases. See detail in aufs.5. config AUFS_DIRREN bool "Workaround for rename(2)-ing a directory" help By default, aufs returns EXDEV error in renameing a dir who has his child on the lower branch, since it is a bad idea to issue rename(2) internally for every lower branch. But user may not accept this behaviour. So here is a workaround to allow such rename(2) and store some extra infromation on the writable branch. Obviously this costs high (and I don't like it). To use this feature, you need to enable this configuration AND to specify the mount option `dirren.' See details in aufs.5 and the design documents. config AUFS_SHWH bool "Show whiteouts" help If you want to make the whiteouts in aufs visible, then enable this option and specify 'shwh' mount option. Although it may sounds like philosophy or something, but in technically it simply shows the name of whiteout with keeping its behaviour. config AUFS_BR_RAMFS bool "Ramfs (initramfs/rootfs) as an aufs branch" help If you want to use ramfs as an aufs branch fs, then enable this option. Generally tmpfs is recommended. Aufs prohibited them to be a branch fs by default, because initramfs becomes unusable after switch_root or something generally. If you sets initramfs as an aufs branch and boot your system by switch_root, you will meet a problem easily since the files in initramfs may be inaccessible. Unless you are going to use ramfs as an aufs branch fs without switch_root or something, leave it N. config AUFS_BR_FUSE bool "Fuse fs as an aufs branch" depends on FUSE_FS select AUFS_POLL help If you want to use fuse-based userspace filesystem as an aufs branch fs, then enable this option. It implements the internal poll(2) operation which is implemented by fuse only (curretnly). config AUFS_POLL bool help Automatic configuration for internal use. config AUFS_BR_HFSPLUS bool "Hfsplus as an aufs branch" depends on HFSPLUS_FS default y help If you want to use hfsplus fs as an aufs branch fs, then enable this option. This option introduces a small overhead at copying-up a file on hfsplus. config AUFS_BDEV_LOOP bool depends on BLK_DEV_LOOP default y help Automatic configuration for internal use. Convert =[ym] into =y. config AUFS_DEBUG bool "Debug aufs" help Enable this to compile aufs internal debug code. It will have a negative impact to the performance. config AUFS_MAGIC_SYSRQ bool depends on AUFS_DEBUG && MAGIC_SYSRQ default y help Automatic configuration for internal use. When aufs supports Magic SysRq, enabled automatically. endif PK ! r +�C C aufs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 include ${src}/magic.mk ifeq (${CONFIG_AUFS_FS},m) include ${src}/conf.mk endif -include ${src}/priv_def.mk # cf. include/linux/kernel.h # enable pr_debug ccflags-y += -DDEBUG # sparse requires the full pathname ifdef M ccflags-y += -include ${M}/../../include/uapi/linux/aufs_type.h else ccflags-y += -include ${srctree}/include/uapi/linux/aufs_type.h endif obj-$(CONFIG_AUFS_FS) += aufs.o aufs-y := module.o sbinfo.o super.o branch.o xino.o sysaufs.o opts.o \ wkq.o vfsub.o dcsub.o \ cpup.o whout.o wbr_policy.o \ dinfo.o dentry.o \ dynop.o \ finfo.o file.o f_op.o \ dir.o vdir.o \ iinfo.o inode.o i_op.o i_op_add.o i_op_del.o i_op_ren.o \ mvdown.o ioctl.o # all are boolean aufs-$(CONFIG_PROC_FS) += procfs.o plink.o aufs-$(CONFIG_SYSFS) += sysfs.o aufs-$(CONFIG_DEBUG_FS) += dbgaufs.o aufs-$(CONFIG_AUFS_BDEV_LOOP) += loop.o aufs-$(CONFIG_AUFS_HNOTIFY) += hnotify.o aufs-$(CONFIG_AUFS_HFSNOTIFY) += hfsnotify.o aufs-$(CONFIG_AUFS_EXPORT) += export.o aufs-$(CONFIG_AUFS_XATTR) += xattr.o aufs-$(CONFIG_FS_POSIX_ACL) += posix_acl.o aufs-$(CONFIG_AUFS_DIRREN) += dirren.o aufs-$(CONFIG_AUFS_FHSM) += fhsm.o aufs-$(CONFIG_AUFS_POLL) += poll.o aufs-$(CONFIG_AUFS_RDU) += rdu.o aufs-$(CONFIG_AUFS_BR_HFSPLUS) += hfsplus.o aufs-$(CONFIG_AUFS_DEBUG) += debug.o aufs-$(CONFIG_AUFS_MAGIC_SYSRQ) += sysrq.o PK ! 7�?K� � nfs/flexfilelayout/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the pNFS Flexfile Layout Driver kernel module # obj-$(CONFIG_PNFS_FLEXFILE_LAYOUT) += nfs_layout_flexfiles.o nfs_layout_flexfiles-y := flexfilelayout.o flexfilelayoutdev.o PK ! ���� � nfs/blocklayout/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the pNFS block layout driver kernel module # obj-$(CONFIG_PNFS_BLOCK) += blocklayoutdriver.o blocklayoutdriver-y += blocklayout.o dev.o extent_tree.o rpc_pipefs.o PK ! 6gؓ� � nfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NFS_FS tristate "NFS client support" depends on INET && FILE_LOCKING && MULTIUSER select CRC32 select LOCKD select SUNRPC select NFS_ACL_SUPPORT if NFS_V3_ACL help Choose Y here if you want to access files residing on other computers using Sun's Network File System protocol. To compile this file system support as a module, choose M here: the module will be called nfs. To mount file systems exported by NFS servers, you also need to install the user space mount.nfs command which can be found in the Linux nfs-utils package, available from http://linux-nfs.org/. Information about using the mount command is available in the mount(8) man page. More detail about the Linux NFS client implementation is available via the nfs(5) man page. Below you can choose which versions of the NFS protocol are available in the kernel to mount NFS servers. Support for NFS version 2 (RFC 1094) is always available when NFS_FS is selected. To configure a system which mounts its root file system via NFS at boot time, say Y here, select "Kernel level IP autoconfiguration" in the NETWORK menu, and select "Root file system on NFS" below. You cannot compile this file system as a module in this case. If unsure, say N. config NFS_V2 tristate "NFS client support for NFS version 2" depends on NFS_FS default y help This option enables support for version 2 of the NFS protocol (RFC 1094) in the kernel's NFS client. If unsure, say Y. config NFS_V3 tristate "NFS client support for NFS version 3" depends on NFS_FS default y help This option enables support for version 3 of the NFS protocol (RFC 1813) in the kernel's NFS client. If unsure, say Y. config NFS_V3_ACL bool "NFS client support for the NFSv3 ACL protocol extension" depends on NFS_V3 help Some NFS servers support an auxiliary NFSv3 ACL protocol that Sun added to Solaris but never became an official part of the NFS version 3 protocol. This protocol extension allows applications on NFS clients to manipulate POSIX Access Control Lists on files residing on NFS servers. NFS servers enforce ACLs on local files whether this protocol is available or not. Choose Y here if your NFS server supports the Solaris NFSv3 ACL protocol extension and you want your NFS client to allow applications to access and modify ACLs on files on the server. Most NFS servers don't support the Solaris NFSv3 ACL protocol extension. You can choose N here or specify the "noacl" mount option to prevent your NFS client from trying to use the NFSv3 ACL protocol. If unsure, say N. config NFS_V4 tristate "NFS client support for NFS version 4" depends on NFS_FS select SUNRPC_GSS select KEYS help This option enables support for version 4 of the NFS protocol (RFC 3530) in the kernel's NFS client. To mount NFS servers using NFSv4, you also need to install user space programs which can be found in the Linux nfs-utils package, available from http://linux-nfs.org/. If unsure, say Y. config NFS_SWAP bool "Provide swap over NFS support" default n depends on NFS_FS && SWAP select SUNRPC_SWAP help This option enables swapon to work on files located on NFS mounts. config NFS_V4_1 bool "NFS client support for NFSv4.1" depends on NFS_V4 select SUNRPC_BACKCHANNEL help This option enables support for minor version 1 of the NFSv4 protocol (RFC 5661) in the kernel's NFS client. If unsure, say N. config NFS_V4_2 bool "NFS client support for NFSv4.2" depends on NFS_V4_1 help This option enables support for minor version 2 of the NFSv4 protocol in the kernel's NFS client. If unsure, say N. config PNFS_FILE_LAYOUT tristate depends on NFS_V4_1 default NFS_V4 config PNFS_BLOCK tristate depends on NFS_V4_1 && BLK_DEV_DM default NFS_V4 config PNFS_FLEXFILE_LAYOUT tristate depends on NFS_V4_1 && NFS_V3 default NFS_V4 config NFS_V4_1_IMPLEMENTATION_ID_DOMAIN string "NFSv4.1 Implementation ID Domain" depends on NFS_V4_1 default "kernel.org" help This option defines the domain portion of the implementation ID that may be sent in the NFS exchange_id operation. The value must be in the format of a DNS domain name and should be set to the DNS domain name of the distribution. If the NFS client is unchanged from the upstream kernel, this option should be set to the default "kernel.org". config NFS_V4_1_MIGRATION bool "NFSv4.1 client support for migration" depends on NFS_V4_1 default n help This option makes the NFS client advertise to NFSv4.1 servers that it can support NFSv4 migration. The NFSv4.1 pieces of the Linux NFSv4 migration implementation are still experimental. If you are not an NFSv4 developer, say N here. config NFS_V4_SECURITY_LABEL bool depends on NFS_V4_2 && SECURITY default y config ROOT_NFS bool "Root file system on NFS" depends on NFS_FS=y && IP_PNP help If you want your system to mount its root file system via NFS, choose Y here. This is common practice for managing systems without local permanent storage. For details, read <file:Documentation/admin-guide/nfs/nfsroot.rst>. Most people say N here. config NFS_FSCACHE bool "Provide NFS client caching support" depends on NFS_FS=m && FSCACHE || NFS_FS=y && FSCACHE=y help Say Y here if you want NFS data to be cached locally on disc through the general filesystem cache manager config NFS_USE_LEGACY_DNS bool "Use the legacy NFS DNS resolver" depends on NFS_V4 help The kernel now provides a method for translating a host name into an IP address. Select Y here if you would rather use your own DNS resolver script. If unsure, say N config NFS_USE_KERNEL_DNS bool depends on NFS_V4 && !NFS_USE_LEGACY_DNS select DNS_RESOLVER default y config NFS_DEBUG bool depends on NFS_FS && SUNRPC_DEBUG default y config NFS_DISABLE_UDP_SUPPORT bool "NFS: Disable NFS UDP protocol support" depends on NFS_FS default y help Choose Y here to disable the use of NFS over UDP. NFS over UDP on modern networks (1Gb+) can lead to data corruption caused by fragmentation during high loads. config NFS_V4_2_READ_PLUS bool "NFS: Enable support for the NFSv4.2 READ_PLUS operation" depends on NFS_V4_2 default n help This is intended for developers only. The READ_PLUS operation has been shown to have issues under specific conditions and should not be used in production. PK ! �9�$9 9 nfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux nfs filesystem routines. # obj-$(CONFIG_NFS_FS) += nfs.o CFLAGS_nfstrace.o += -I$(src) nfs-y := client.o dir.o file.o getroot.o inode.o super.o \ io.o direct.o pagelist.o read.o symlink.o unlink.o \ write.o namespace.o mount_clnt.o nfstrace.o \ export.o sysfs.o fs_context.o nfs-$(CONFIG_ROOT_NFS) += nfsroot.o nfs-$(CONFIG_SYSCTL) += sysctl.o nfs-$(CONFIG_NFS_FSCACHE) += fscache.o fscache-index.o obj-$(CONFIG_NFS_V2) += nfsv2.o nfsv2-y := nfs2super.o proc.o nfs2xdr.o obj-$(CONFIG_NFS_V3) += nfsv3.o nfsv3-y := nfs3super.o nfs3client.o nfs3proc.o nfs3xdr.o nfsv3-$(CONFIG_NFS_V3_ACL) += nfs3acl.o obj-$(CONFIG_NFS_V4) += nfsv4.o CFLAGS_nfs4trace.o += -I$(src) nfsv4-y := nfs4proc.o nfs4xdr.o nfs4state.o nfs4renewd.o nfs4super.o nfs4file.o \ delegation.o nfs4idmap.o callback.o callback_xdr.o callback_proc.o \ nfs4namespace.o nfs4getroot.o nfs4client.o nfs4session.o \ dns_resolve.o nfs4trace.o nfsv4-$(CONFIG_NFS_USE_LEGACY_DNS) += cache_lib.o nfsv4-$(CONFIG_SYSCTL) += nfs4sysctl.o nfsv4-$(CONFIG_NFS_V4_1) += pnfs.o pnfs_dev.o pnfs_nfs.o nfsv4-$(CONFIG_NFS_V4_2) += nfs42proc.o nfs42xattr.o obj-$(CONFIG_PNFS_FILE_LAYOUT) += filelayout/ obj-$(CONFIG_PNFS_BLOCK) += blocklayout/ obj-$(CONFIG_PNFS_FLEXFILE_LAYOUT) += flexfilelayout/ PK ! �� � nfs/filelayout/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the pNFS Files Layout Driver kernel module # obj-$(CONFIG_PNFS_FILE_LAYOUT) += nfs_layout_nfsv41_files.o nfs_layout_nfsv41_files-y := filelayout.o filelayoutdev.o PK ! X7`je e tracefs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only tracefs-objs := inode.o obj-$(CONFIG_TRACING) += tracefs.o PK ! w� ntfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NTFS_FS tristate "NTFS file system support" select NLS help NTFS is the file system of Microsoft Windows NT, 2000, XP and 2003. Saying Y or M here enables read support. There is partial, but safe, write support available. For write support you must also say Y to "NTFS write support" below. There are also a number of user-space tools available, called ntfsprogs. These include ntfsundelete and ntfsresize, that work without NTFS support enabled in the kernel. This is a rewrite from scratch of Linux NTFS support and replaced the old NTFS code starting with Linux 2.5.11. A backport to the Linux 2.4 kernel series is separately available as a patch from the project web site. For more information see <file:Documentation/filesystems/ntfs.rst> and <http://www.linux-ntfs.org/>. To compile this file system support as a module, choose M here: the module will be called ntfs. If you are not using Windows NT, 2000, XP or 2003 in addition to Linux on your computer it is safe to say N. config NTFS_DEBUG bool "NTFS debugging support" depends on NTFS_FS help If you are experiencing any problems with the NTFS file system, say Y here. This will result in additional consistency checks to be performed by the driver as well as additional debugging messages to be written to the system log. Note that debugging messages are disabled by default. To enable them, supply the option debug_msgs=1 at the kernel command line when booting the kernel or as an option to insmod when loading the ntfs module. Once the driver is active, you can enable debugging messages by doing (as root): echo 1 > /proc/sys/fs/ntfs-debug Replacing the "1" with "0" would disable debug messages. If you leave debugging messages disabled, this results in little overhead, but enabling debug messages results in very significant slowdown of the system. When reporting bugs, please try to have available a full dump of debugging messages while the misbehaviour was occurring. config NTFS_RW bool "NTFS write support" depends on NTFS_FS help This enables the partial, but safe, write support in the NTFS driver. The only supported operation is overwriting existing files, without changing the file length. No file or directory creation, deletion or renaming is possible. Note only non-resident files can be written to so you may find that some very small files (<500 bytes or so) cannot be written to. While we cannot guarantee that it will not damage any data, we have so far not received a single report where the driver would have damaged someones data so we assume it is perfectly safe to use. Note: While write support is safe in this version (a rewrite from scratch of the NTFS support), it should be noted that the old NTFS write support, included in Linux 2.5.10 and before (since 1997), is not safe. This is currently useful with TopologiLinux. TopologiLinux is run on top of any DOS/Microsoft Windows system without partitioning your hard disk. Unlike other Linux distributions TopologiLinux does not need its own partition. For more information see <http://topologi-linux.sourceforge.net/> It is perfectly safe to say N here. PK ! �=��� � ntfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Rules for making the NTFS driver. obj-$(CONFIG_NTFS_FS) += ntfs.o ntfs-y := aops.o attrib.o collate.o compress.o debug.o dir.o file.o \ index.o inode.o mft.o mst.o namei.o runlist.o super.o sysctl.o \ unistr.o upcase.o ntfs-$(CONFIG_NTFS_RW) += bitmap.o lcnalloc.o logfile.o quota.o usnjrnl.o ccflags-y := -DNTFS_VERSION=\"2.1.32\" ccflags-$(CONFIG_NTFS_DEBUG) += -DDEBUG ccflags-$(CONFIG_NTFS_RW) += -DNTFS_RW PK ! �K K ecryptfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config ECRYPT_FS tristate "eCrypt filesystem layer support" depends on KEYS && CRYPTO && (ENCRYPTED_KEYS || ENCRYPTED_KEYS=n) select CRYPTO_ECB select CRYPTO_CBC select CRYPTO_MD5 help Encrypted filesystem that operates on the VFS layer. See <file:Documentation/filesystems/ecryptfs.rst> to learn more about eCryptfs. Userspace components are required and can be obtained from <http://ecryptfs.sf.net>. To compile this file system support as a module, choose M here: the module will be called ecryptfs. config ECRYPT_FS_MESSAGING bool "Enable notifications for userspace key wrap/unwrap" depends on ECRYPT_FS help Enables the /dev/ecryptfs entry for use by ecryptfsd. This allows for userspace to wrap/unwrap file encryption keys by other backends, like OpenSSL. PK ! �XZ/ / ecryptfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Linux eCryptfs # obj-$(CONFIG_ECRYPT_FS) += ecryptfs.o ecryptfs-y := dentry.o file.o inode.o main.o super.o mmap.o read_write.o \ crypto.o keystore.o kthread.o debug.o ecryptfs-$(CONFIG_ECRYPT_FS_MESSAGING) += messaging.o miscdev.o PK ! bJT=o o erofs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config EROFS_FS tristate "EROFS filesystem support" depends on BLOCK select FS_IOMAP select LIBCRC32C help EROFS (Enhanced Read-Only File System) is a lightweight read-only file system with modern designs (eg. page-sized blocks, inline xattrs/data, etc.) for scenarios which need high-performance read-only requirements, e.g. Android OS for mobile phones and LIVECDs. It also provides fixed-sized output compression support, which improves storage density, keeps relatively higher compression ratios, which is more useful to achieve high performance for embedded devices with limited memory. If unsure, say N. config EROFS_FS_DEBUG bool "EROFS debugging feature" depends on EROFS_FS help Print debugging messages and enable more BUG_ONs which check filesystem consistency and find potential issues aggressively, which can be used for Android eng build, for example. For daily use, say N. config EROFS_FS_XATTR bool "EROFS extended attributes" depends on EROFS_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 EROFS_FS_POSIX_ACL bool "EROFS Access Control Lists" depends on EROFS_FS_XATTR select FS_POSIX_ACL default y help Posix Access Control Lists (ACLs) support permissions for users and groups 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. config EROFS_FS_SECURITY bool "EROFS Security Labels" depends on EROFS_FS_XATTR default y help Security labels provide an access control facility to support Linux Security Models (LSMs) accepted by AppArmor, SELinux, Smack and TOMOYO Linux. This option enables an extended attribute handler for file security labels in the erofs filesystem, so that it requires enabling the extended attribute support in advance. If you are not using a security module, say N. config EROFS_FS_ZIP bool "EROFS Data Compression Support" depends on EROFS_FS select LZ4_DECOMPRESS default y help Enable fixed-sized output compression for EROFS. If you don't want to enable compression feature, say N. PK ! kߤ� � erofs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_EROFS_FS) += erofs.o erofs-objs := super.o inode.o data.o namei.o dir.o utils.o pcpubuf.o erofs-$(CONFIG_EROFS_FS_XATTR) += xattr.o erofs-$(CONFIG_EROFS_FS_ZIP) += decompressor.o zmap.o zdata.o PK ! ̓e3� � btrfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0 config BTRFS_FS tristate "Btrfs filesystem support" select CRYPTO select CRYPTO_CRC32C select LIBCRC32C select CRYPTO_XXHASH select CRYPTO_SHA256 select CRYPTO_BLAKE2B select ZLIB_INFLATE select ZLIB_DEFLATE select LZO_COMPRESS select LZO_DECOMPRESS select ZSTD_COMPRESS select ZSTD_DECOMPRESS select FS_IOMAP select RAID6_PQ select XOR_BLOCKS select SRCU depends on !PPC_256K_PAGES # powerpc depends on !PAGE_SIZE_256KB # hexagon help Btrfs is a general purpose copy-on-write filesystem with extents, writable snapshotting, support for multiple devices and many more features focused on fault tolerance, repair and easy administration. The filesystem disk format is no longer unstable, and it's not expected to change unless there are strong reasons to do so. If there is a format change, file systems with a unchanged format will continue to be mountable and usable by newer kernels. For more information, please see the web pages at http://btrfs.wiki.kernel.org. To compile this file system support as a module, choose M here. The module will be called btrfs. If unsure, say N. config BTRFS_FS_POSIX_ACL bool "Btrfs POSIX Access Control Lists" depends on BTRFS_FS select FS_POSIX_ACL help POSIX Access Control Lists (ACLs) support permissions for users and groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N config BTRFS_FS_CHECK_INTEGRITY bool "Btrfs with integrity check tool compiled in (DANGEROUS)" depends on BTRFS_FS help Adds code that examines all block write requests (including writes of the super block). The goal is to verify that the state of the filesystem on disk is always consistent, i.e., after a power-loss or kernel panic event the filesystem is in a consistent state. If the integrity check tool is included and activated in the mount options, plenty of kernel memory is used, and plenty of additional CPU cycles are spent. Enabling this functionality is not intended for normal use. In most cases, unless you are a btrfs developer who needs to verify the integrity of (super)-block write requests during the run of a regression test, say N config BTRFS_FS_RUN_SANITY_TESTS bool "Btrfs will run sanity tests upon loading" depends on BTRFS_FS help This will run some basic sanity tests on the free space cache code to make sure it is acting as it should. These are mostly regression tests and are only really interesting to btrfs developers. If unsure, say N. config BTRFS_DEBUG bool "Btrfs debugging support" depends on BTRFS_FS help Enable run-time debugging support for the btrfs filesystem. This may enable additional and expensive checks with negative impact on performance, or export extra information via sysfs. If unsure, say N. config BTRFS_ASSERT bool "Btrfs assert support" depends on BTRFS_FS help Enable run-time assertion checking. This will result in panics if any of the assertions trip. This is meant for btrfs developers only. If unsure, say N. config BTRFS_FS_REF_VERIFY bool "Btrfs with the ref verify tool compiled in" depends on BTRFS_FS default n help Enable run-time extent reference verification instrumentation. This is meant to be used by btrfs developers for tracking down extent reference problems or verifying they didn't break something. If unsure, say N. PK ! ߳u�� � btrfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Subset of W=1 warnings subdir-ccflags-y += -Wextra -Wunused -Wno-unused-parameter subdir-ccflags-y += -Wmissing-declarations subdir-ccflags-y += -Wmissing-format-attribute subdir-ccflags-y += -Wmissing-prototypes subdir-ccflags-y += -Wold-style-definition subdir-ccflags-y += -Wmissing-include-dirs condflags := \ $(call cc-option, -Wunused-but-set-variable) \ $(call cc-option, -Wunused-const-variable) \ $(call cc-option, -Wpacked-not-aligned) \ $(call cc-option, -Wstringop-truncation) subdir-ccflags-y += $(condflags) # The following turn off the warnings enabled by -Wextra subdir-ccflags-y += -Wno-missing-field-initializers subdir-ccflags-y += -Wno-sign-compare subdir-ccflags-y += -Wno-type-limits obj-$(CONFIG_BTRFS_FS) := btrfs.o btrfs-y += super.o ctree.o extent-tree.o print-tree.o root-tree.o dir-item.o \ file-item.o inode-item.o disk-io.o \ transaction.o inode.o file.o tree-defrag.o \ extent_map.o sysfs.o struct-funcs.o xattr.o ordered-data.o \ extent_io.o volumes.o async-thread.o ioctl.o locking.o orphan.o \ export.o tree-log.o free-space-cache.o zlib.o lzo.o zstd.o \ compression.o delayed-ref.o relocation.o delayed-inode.o scrub.o \ reada.o backref.o ulist.o qgroup.o send.o dev-replace.o raid56.o \ uuid-tree.o props.o free-space-tree.o tree-checker.o space-info.o \ block-rsv.o delalloc-space.o block-group.o discard.o reflink.o \ subpage.o tree-mod-log.o btrfs-$(CONFIG_BTRFS_FS_POSIX_ACL) += acl.o btrfs-$(CONFIG_BTRFS_FS_CHECK_INTEGRITY) += check-integrity.o btrfs-$(CONFIG_BTRFS_FS_REF_VERIFY) += ref-verify.o btrfs-$(CONFIG_BLK_DEV_ZONED) += zoned.o btrfs-$(CONFIG_FS_VERITY) += verity.o btrfs-$(CONFIG_BTRFS_FS_RUN_SANITY_TESTS) += tests/free-space-tests.o \ tests/extent-buffer-tests.o tests/btrfs-tests.o \ tests/extent-io-tests.o tests/inode-tests.o tests/qgroup-tests.o \ tests/free-space-tree-tests.o tests/extent-map-tests.o PK ! J(�u u kernfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # KERNFS should be selected by its users # config KERNFS bool default n PK ! f�)d� � kernfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the kernfs pseudo filesystem # obj-y := mount.o inode.o dir.o file.o symlink.o PK ! �<=� � hugetlbfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux ramfs routines. # obj-$(CONFIG_HUGETLBFS) += hugetlbfs.o hugetlbfs-objs := inode.o PK ! �z��T T squashfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config SQUASHFS tristate "SquashFS 4.0 - Squashed file system support" depends on BLOCK help Saying Y here includes support for SquashFS 4.0 (a Compressed Read-Only File System). Squashfs is a highly compressed read-only filesystem for Linux. It uses zlib, lzo or xz compression to compress both files, inodes and directories. Inodes in the system are very small and all blocks are packed to minimise data overhead. Block sizes greater than 4K are supported up to a maximum of 1 Mbytes (default block size 128K). SquashFS 4.0 supports 64 bit filesystems and files (larger than 4GB), full uid/gid information, hard links and timestamps. Squashfs is intended for general read-only filesystem use, for archival use (i.e. in cases where a .tar.gz file may be used), and in embedded systems where low overhead is needed. Further information and tools are available from http://squashfs.sourceforge.net. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here. The module will be called squashfs. Note that the root file system (the one containing the directory /) cannot be compiled as a module. If unsure, say N. choice prompt "File decompression options" depends on SQUASHFS help Squashfs now supports two options for decompressing file data. Traditionally Squashfs has decompressed into an intermediate buffer and then memcopied it into the page cache. Squashfs now supports the ability to decompress directly into the page cache. If unsure, select "Decompress file data into an intermediate buffer" config SQUASHFS_FILE_CACHE bool "Decompress file data into an intermediate buffer" help Decompress file data into an intermediate buffer and then memcopy it into the page cache. config SQUASHFS_FILE_DIRECT bool "Decompress files directly into the page cache" help Directly decompress file data into the page cache. Doing so can significantly improve performance because it eliminates a memcpy and it also removes the lock contention on the single buffer. endchoice choice prompt "Decompressor parallelisation options" depends on SQUASHFS help Squashfs now supports three parallelisation options for decompression. Each one exhibits various trade-offs between decompression performance and CPU and memory usage. If in doubt, select "Single threaded compression" config SQUASHFS_DECOMP_SINGLE bool "Single threaded compression" help Traditionally Squashfs has used single-threaded decompression. Only one block (data or metadata) can be decompressed at any one time. This limits CPU and memory usage to a minimum. config SQUASHFS_DECOMP_MULTI bool "Use multiple decompressors for parallel I/O" help By default Squashfs uses a single decompressor but it gives poor performance on parallel I/O workloads when using multiple CPU machines due to waiting on decompressor availability. If you have a parallel I/O workload and your system has enough memory, using this option may improve overall I/O performance. This decompressor implementation uses up to two parallel decompressors per core. It dynamically allocates decompressors on a demand basis. config SQUASHFS_DECOMP_MULTI_PERCPU bool "Use percpu multiple decompressors for parallel I/O" help By default Squashfs uses a single decompressor but it gives poor performance on parallel I/O workloads when using multiple CPU machines due to waiting on decompressor availability. This decompressor implementation uses a maximum of one decompressor per core. It uses percpu variables to ensure decompression is load-balanced across the cores. endchoice config SQUASHFS_XATTR bool "Squashfs XATTR support" depends on SQUASHFS help Saying Y here includes support for extended attributes (xattrs). Xattrs are name:value pairs associated with inodes by the kernel or by users (see the attr(5) manual page). If unsure, say N. config SQUASHFS_ZLIB bool "Include support for ZLIB compressed file systems" depends on SQUASHFS select ZLIB_INFLATE default y help ZLIB compression is the standard compression used by Squashfs file systems. It offers a good trade-off between compression achieved and the amount of CPU time and memory necessary to compress and decompress. If unsure, say Y. config SQUASHFS_LZ4 bool "Include support for LZ4 compressed file systems" depends on SQUASHFS select LZ4_DECOMPRESS help Saying Y here includes support for reading Squashfs file systems compressed with LZ4 compression. LZ4 compression is mainly aimed at embedded systems with slower CPUs where the overheads of zlib are too high. LZ4 is not the standard compression used in Squashfs and so most file systems will be readable without selecting this option. If unsure, say N. config SQUASHFS_LZO bool "Include support for LZO compressed file systems" depends on SQUASHFS select LZO_DECOMPRESS help Saying Y here includes support for reading Squashfs file systems compressed with LZO compression. LZO compression is mainly aimed at embedded systems with slower CPUs where the overheads of zlib are too high. LZO is not the standard compression used in Squashfs and so most file systems will be readable without selecting this option. If unsure, say N. config SQUASHFS_XZ bool "Include support for XZ compressed file systems" depends on SQUASHFS select XZ_DEC help Saying Y here includes support for reading Squashfs file systems compressed with XZ compression. XZ gives better compression than the default zlib compression, at the expense of greater CPU and memory overhead. XZ is not the standard compression used in Squashfs and so most file systems will be readable without selecting this option. If unsure, say N. config SQUASHFS_ZSTD bool "Include support for ZSTD compressed file systems" depends on SQUASHFS select ZSTD_DECOMPRESS help Saying Y here includes support for reading Squashfs file systems compressed with ZSTD compression. ZSTD gives better compression than the default ZLIB compression, while using less CPU. ZSTD is not the standard compression used in Squashfs and so most file systems will be readable without selecting this option. If unsure, say N. config SQUASHFS_4K_DEVBLK_SIZE bool "Use 4K device block size?" depends on SQUASHFS help By default Squashfs sets the dev block size (sb_min_blocksize) to 1K or the smallest block size supported by the block device (if larger). This, because blocks are packed together and unaligned in Squashfs, should reduce latency. This, however, gives poor performance on MTD NAND devices where the optimal I/O size is 4K (even though the devices can support smaller block sizes). Using a 4K device block size may also improve overall I/O performance for some file access patterns (e.g. sequential accesses of files in filesystem order) on all media. Setting this option will force Squashfs to use a 4K device block size by default. If unsure, say N. config SQUASHFS_EMBEDDED bool "Additional option for memory-constrained systems" depends on SQUASHFS help Saying Y here allows you to specify cache size. If unsure, say N. config SQUASHFS_FRAGMENT_CACHE_SIZE int "Number of fragments cached" if SQUASHFS_EMBEDDED depends on SQUASHFS default "3" help By default SquashFS caches the last 3 fragments read from the filesystem. Increasing this amount may mean SquashFS has to re-read fragments less often from disk, at the expense of extra system memory. Decreasing this amount will mean SquashFS uses less memory at the expense of extra reads from disk. Note there must be at least one cached fragment. Anything much more than three will probably not make much difference. PK ! bav�{ { squashfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the linux squashfs routines. # obj-$(CONFIG_SQUASHFS) += squashfs.o squashfs-y += block.o cache.o dir.o export.o file.o fragment.o id.o inode.o squashfs-y += namei.o super.o symlink.o decompressor.o squashfs-$(CONFIG_SQUASHFS_FILE_CACHE) += file_cache.o squashfs-$(CONFIG_SQUASHFS_FILE_DIRECT) += file_direct.o page_actor.o squashfs-$(CONFIG_SQUASHFS_DECOMP_SINGLE) += decompressor_single.o squashfs-$(CONFIG_SQUASHFS_DECOMP_MULTI) += decompressor_multi.o squashfs-$(CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU) += decompressor_multi_percpu.o squashfs-$(CONFIG_SQUASHFS_XATTR) += xattr.o xattr_id.o squashfs-$(CONFIG_SQUASHFS_LZ4) += lz4_wrapper.o squashfs-$(CONFIG_SQUASHFS_LZO) += lzo_wrapper.o squashfs-$(CONFIG_SQUASHFS_XZ) += xz_wrapper.o squashfs-$(CONFIG_SQUASHFS_ZLIB) += zlib_wrapper.o squashfs-$(CONFIG_SQUASHFS_ZSTD) += zstd_wrapper.o PK ! �)b_� � fscache/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config FSCACHE tristate "General filesystem local caching manager" select NETFS_SUPPORT help This option enables a generic filesystem caching manager that can be used by various network and other filesystems to cache data locally. Different sorts of caches can be plugged in, depending on the resources available. See Documentation/filesystems/caching/fscache.rst for more information. config FSCACHE_STATS bool "Gather statistical information on local caching" depends on FSCACHE && PROC_FS select NETFS_STATS help This option causes statistical information to be gathered on local caching and exported through file: /proc/fs/fscache/stats The gathering of statistics adds a certain amount of overhead to execution as there are a quite a few stats gathered, and on a multi-CPU system these may be on cachelines that keep bouncing between CPUs. On the other hand, the stats are very useful for debugging purposes. Saying 'Y' here is recommended. See Documentation/filesystems/caching/fscache.rst for more information. config FSCACHE_DEBUG bool "Debug FS-Cache" depends on FSCACHE help This permits debugging to be dynamically enabled in the local caching management module. If this is set, the debugging output may be enabled by setting bits in /sys/modules/fscache/parameter/debug. See Documentation/filesystems/caching/fscache.rst for more information. PK ! ��]< < fscache/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for general filesystem caching code # fscache-y := \ cache.o \ cookie.o \ fsdef.o \ io.o \ main.o \ netfs.o \ object.o \ operation.o \ page.o fscache-$(CONFIG_PROC_FS) += proc.o fscache-$(CONFIG_FSCACHE_STATS) += stats.o obj-$(CONFIG_FSCACHE) := fscache.o PK ! ��� � exportfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the filesystem export support routines. obj-$(CONFIG_EXPORTFS) += exportfs.o exportfs-objs := expfs.o PK ! �ϳ�� � sysv/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config SYSV_FS tristate "System V/Xenix/V7/Coherent file system support" depends on BLOCK help SCO, Xenix and Coherent are commercial Unix systems for Intel machines, and Version 7 was used on the DEC PDP-11. Saying Y here would allow you to read from their floppies and hard disk partitions. If you have floppies or hard disk partitions like that, it is likely that they contain binaries from those other Unix systems; in order to run these binaries, you will want to install linux-abi which is a set of kernel modules that lets you run SCO, Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux. It is available via FTP (user: ftp) from <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>). NOTE: that will work only for binaries from Intel-based systems; PDP ones will have to wait until somebody ports Linux to -11 ;-) If you only intend to mount files from some other Unix over the network using NFS, you don't need the System V file system support (but you need NFS file system support obviously). Note that this option is generally not needed for floppies, since a good portable way to transport files and directories between unixes (and even other operating systems) is given by the tar program ("man tar" or preferably "info tar"). Note also that this option has nothing whatsoever to do with the option "System V IPC". Read about the System V file system in <file:Documentation/filesystems/sysv-fs.rst>. Saying Y here will enlarge your kernel by about 27 KB. To compile this as a module, choose M here: the module will be called sysv. If you haven't heard about all of this before, it's safe to say N. PK ! �ŀ@� � sysv/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Linux SystemV/Coherent filesystem routines. # obj-$(CONFIG_SYSV_FS) += sysv.o sysv-objs := ialloc.o balloc.o inode.o itree.o file.o dir.o \ namei.o super.o PK ! ��� ufs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config UFS_FS tristate "UFS file system support (read only)" depends on BLOCK help BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD, OpenBSD and NeXTstep) use a file system called UFS. Some System V Unixes can create and mount hard disk partitions and diskettes using this file system as well. Saying Y here will allow you to read from these partitions; if you also want to write to them, say Y to the experimental "UFS file system write support", below. Please read the file <file:Documentation/admin-guide/ufs.rst> for more information. The recently released UFS2 variant (used in FreeBSD 5.x) is READ-ONLY supported. Note that this option is generally not needed for floppies, since a good portable way to transport files and directories between unixes (and even other operating systems) is given by the tar program ("man tar" or preferably "info tar"). When accessing NeXTstep files, you may need to convert them from the NeXT character set to the Latin1 character set; use the program recode ("info recode") for this purpose. To compile the UFS file system support as a module, choose M here: the module will be called ufs. If you haven't heard about all of this before, it's safe to say N. config UFS_FS_WRITE bool "UFS file system write support (DANGEROUS)" depends on UFS_FS help Say Y here if you want to try writing to UFS partitions. This is experimental, so you should back up your UFS partitions beforehand. config UFS_DEBUG bool "UFS debugging" depends on UFS_FS help If you are experiencing any problems with the UFS filesystem, say Y here. This will result in _many_ additional debugging messages to be written to the system log. PK ! jZ ufs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Linux ufs filesystem routines. # obj-$(CONFIG_UFS_FS) += ufs.o ufs-objs := balloc.o cylinder.o dir.o file.o ialloc.o inode.o \ namei.o super.o util.o ccflags-$(CONFIG_UFS_DEBUG) += -DDEBUG PK ! ��� � ksmbd/Kconfignu �[��� config SMB_SERVER tristate "SMB3 server support" depends on INET depends on MULTIUSER depends on FILE_LOCKING select NLS select NLS_UTF8 select CRYPTO select CRYPTO_MD5 select CRYPTO_HMAC select CRYPTO_ECB select CRYPTO_LIB_DES select CRYPTO_SHA256 select CRYPTO_CMAC select CRYPTO_SHA512 select CRYPTO_AEAD2 select CRYPTO_CCM select CRYPTO_GCM select ASN1 select OID_REGISTRY select CRC32 default n help Choose Y here if you want to allow SMB3 compliant clients to access files residing on this system using SMB3 protocol. To compile the SMB3 server support as a module, choose M here: the module will be called ksmbd. You may choose to use a samba server instead, in which case you can choose N here. You also need to install user space programs which can be found in ksmbd-tools, available from https://github.com/cifsd-team/ksmbd-tools. More detail about how to run the ksmbd kernel server is available via the README file (https://github.com/cifsd-team/ksmbd-tools/blob/master/README). ksmbd kernel server includes support for auto-negotiation, Secure negotiate, Pre-authentication integrity, oplock/lease, compound requests, multi-credit, packet signing, RDMA(smbdirect), smb3 encryption, copy-offload, secure per-user session establishment via Kerberos or NTLMv2. if SMB_SERVER config SMB_SERVER_SMBDIRECT bool "Support for SMB Direct protocol" depends on SMB_SERVER=m && INFINIBAND && INFINIBAND_ADDR_TRANS || SMB_SERVER=y && INFINIBAND=y && INFINIBAND_ADDR_TRANS=y select SG_POOL default n help Enables SMB Direct support for SMB 3.0, 3.02 and 3.1.1. SMB Direct allows transferring SMB packets over RDMA. If unsure, say N. endif config SMB_SERVER_CHECK_CAP_NET_ADMIN bool "Enable check network administration capability" depends on SMB_SERVER default y help Prevent unprivileged processes to start the ksmbd kernel server. config SMB_SERVER_KERBEROS5 bool "Support for Kerberos 5" depends on SMB_SERVER default n PK ! �~� � ksmbd/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-or-later # # Makefile for Linux SMB3 kernel server # obj-$(CONFIG_SMB_SERVER) += ksmbd.o ksmbd-y := unicode.o auth.o vfs.o vfs_cache.o server.o ndr.o \ misc.o oplock.o connection.o ksmbd_work.o crypto_ctx.o \ mgmt/ksmbd_ida.o mgmt/user_config.o mgmt/share_config.o \ mgmt/tree_connect.o mgmt/user_session.o smb_common.o \ transport_tcp.o transport_ipc.o smbacl.o smb2pdu.o \ smb2ops.o smb2misc.o ksmbd_spnego_negtokeninit.asn1.o \ ksmbd_spnego_negtokentarg.asn1.o asn1.o $(obj)/asn1.o: $(obj)/ksmbd_spnego_negtokeninit.asn1.h $(obj)/ksmbd_spnego_negtokentarg.asn1.h $(obj)/ksmbd_spnego_negtokeninit.asn1.o: $(obj)/ksmbd_spnego_negtokeninit.asn1.c $(obj)/ksmbd_spnego_negtokeninit.asn1.h $(obj)/ksmbd_spnego_negtokentarg.asn1.o: $(obj)/ksmbd_spnego_negtokentarg.asn1.c $(obj)/ksmbd_spnego_negtokentarg.asn1.h ksmbd-$(CONFIG_SMB_SERVER_SMBDIRECT) += transport_rdma.o PK ! _���O O netfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NETFS_SUPPORT tristate help This option enables support for network filesystems, including helpers for high-level buffered I/O, abstracting out read segmentation, local caching and transparent huge page support. config NETFS_STATS bool "Gather statistical information on local caching" depends on NETFS_SUPPORT && PROC_FS help This option causes statistical information to be gathered on local caching and exported through file: /proc/fs/fscache/stats The gathering of statistics adds a certain amount of overhead to execution as there are a quite a few stats gathered, and on a multi-CPU system these may be on cachelines that keep bouncing between CPUs. On the other hand, the stats are very useful for debugging purposes. Saying 'Y' here is recommended. PK ! <*m m netfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 netfs-y := read_helper.o stats.o obj-$(CONFIG_NETFS_SUPPORT) := netfs.o PK ! � .� � cachefiles/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config CACHEFILES tristate "Filesystem caching on files" depends on FSCACHE && BLOCK help This permits use of a mounted filesystem as a cache for other filesystems - primarily networking filesystems - thus allowing fast local disk to enhance the speed of slower devices. See Documentation/filesystems/caching/cachefiles.rst for more information. config CACHEFILES_DEBUG bool "Debug CacheFiles" depends on CACHEFILES help This permits debugging to be dynamically enabled in the filesystem caching on files module. If this is set, the debugging output may be enabled by setting bits in /sys/modules/cachefiles/parameter/debug or by including a debugging specifier in /etc/cachefilesd.conf. PK ! �}|� � cachefiles/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for caching in a mounted filesystem # cachefiles-y := \ bind.o \ daemon.o \ interface.o \ io.o \ key.o \ main.o \ namei.o \ rdwr.o \ security.o \ xattr.o obj-$(CONFIG_CACHEFILES) := cachefiles.o PK ! 2&�� � autofs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config AUTOFS4_FS tristate "Old Kconfig name for Kernel automounter support" select AUTOFS_FS help This name exists for people to just automatically pick up the new name of the autofs Kconfig option. All it does is select the new option name. It will go away in a release or two as people have transitioned to just plain AUTOFS_FS. config AUTOFS_FS tristate "Kernel automounter support (supports v3, v4 and v5)" default n help The automounter is a tool to automatically mount remote file systems on demand. This implementation is partially kernel-based to reduce overhead in the already-mounted case; this is unlike the BSD automounter (amd), which is a pure user space daemon. To use the automounter you need the user-space tools from <https://www.kernel.org/pub/linux/daemons/autofs/>; you also want to answer Y to "NFS file system support", below. To compile this support as a module, choose M here: the module will be called autofs. If you are not a part of a fairly large, distributed network or don't have a laptop which needs to dynamically reconfigure to the local network, you probably do not need an automounter, and can say N here. PK ! �_V� � autofs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux autofs-filesystem routines. # obj-$(CONFIG_AUTOFS_FS) += autofs4.o autofs4-objs := init.o inode.o root.o symlink.o waitq.o expire.o dev-ioctl.o PK ! v� coda/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config CODA_FS tristate "Coda file system support (advanced network fs)" depends on INET help Coda is an advanced network file system, similar to NFS in that it enables you to mount file systems of a remote server and access them with regular Unix commands as if they were sitting on your hard disk. Coda has several advantages over NFS: support for disconnected operation (e.g. for laptops), read/write server replication, security model for authentication and encryption, persistent client caches and write back caching. If you say Y here, your Linux box will be able to act as a Coda *client*. You will need user level code as well, both for the client and server. Servers are currently user level, i.e. they need no kernel support. Please read <file:Documentation/filesystems/coda.rst> and check out the Coda home page <http://www.coda.cs.cmu.edu/>. To compile the coda client support as a module, choose M here: the module will be called coda. PK ! r�>0� � coda/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Linux Coda filesystem routines. # obj-$(CONFIG_CODA_FS) += coda.o coda-objs := psdev.o cache.o cnode.o inode.o dir.o file.o upcall.o \ coda_linux.o symlink.o pioctl.o coda-$(CONFIG_SYSCTL) += sysctl.o # If you want debugging output, please uncomment the following line. # ccflags-y := -DDEBUG -DDEBUG_SMB_MALLOC=1 PK ! ���� � orangefs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config ORANGEFS_FS tristate "ORANGEFS (Powered by PVFS) support" select FS_POSIX_ACL help Orange is a parallel file system designed for use on high end computing (HEC) systems. PK ! �Dk�d d orangefs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the ORANGEFS filesystem. # obj-$(CONFIG_ORANGEFS_FS) += orangefs.o orangefs-objs := acl.o file.o orangefs-cache.o orangefs-utils.o xattr.o \ dcache.o inode.o orangefs-sysfs.o orangefs-mod.o super.o \ devorangefs-req.o namei.o symlink.o dir.o orangefs-bufmap.o \ orangefs-debugfs.o waitqueue.o PK ! &�� dlm/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only menuconfig DLM tristate "Distributed Lock Manager (DLM)" depends on INET depends on SYSFS && CONFIGFS_FS && (IPV6 || IPV6=n) select IP_SCTP select SRCU help A general purpose distributed lock manager for kernel or userspace applications. config DLM_DEBUG bool "DLM debugging" depends on DLM help Under the debugfs mount point, the name of each lockspace will appear as a file in the "dlm" directory. The output is the list of resource and locks the local node knows about. PK ! �$��z z dlm/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_DLM) += dlm.o dlm-y := ast.o \ config.o \ dir.o \ lock.o \ lockspace.o \ main.o \ member.o \ memory.o \ midcomms.o \ netlink.o \ lowcomms.o \ plock.o \ rcom.o \ recover.o \ recoverd.o \ requestqueue.o \ user.o \ util.o dlm-$(CONFIG_DLM_DEBUG) += debug_fs.o PK ! "N�)b b proc/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config PROC_FS bool "/proc file system support" if EXPERT default y help This is a virtual file system providing information about the status of the system. "Virtual" means that it doesn't take up any space on your hard disk: the files are created on the fly by the kernel when you try to access them. Also, you cannot read the files with older version of the program less: you need to use more or cat. It's totally cool; for example, "cat /proc/interrupts" gives information about what the different IRQs are used for at the moment (there is a small number of Interrupt ReQuest lines in your computer that are used by the attached devices to gain the CPU's attention -- often a source of trouble if two devices are mistakenly configured to use the same IRQ). The program procinfo to display some information about your system gathered from the /proc file system. Before you can use the /proc file system, it has to be mounted, meaning it has to be given a location in the directory hierarchy. That location should be /proc. A command such as "mount -t proc proc /proc" or the equivalent line in /etc/fstab does the job. The /proc file system is explained in the file <file:Documentation/filesystems/proc.rst> and on the proc(5) manpage ("man 5 proc"). This option will enlarge your kernel by about 67 KB. Several programs depend on this, so everyone should say Y here. config PROC_KCORE bool "/proc/kcore support" if !ARM depends on PROC_FS && MMU select CRASH_CORE help Provides a virtual ELF core file of the live kernel. This can be read with gdb and other ELF tools. No modifications can be made using this mechanism. config PROC_VMCORE bool "/proc/vmcore support" depends on PROC_FS && CRASH_DUMP default y help Exports the dump image of crashed kernel in ELF format. config PROC_VMCORE_DEVICE_DUMP bool "Device Hardware/Firmware Log Collection" depends on PROC_VMCORE default n help After kernel panic, device drivers can collect the device specific snapshot of their hardware or firmware before the underlying devices are initialized in crash recovery kernel. Note that the device driver must be present in the crash recovery kernel's initramfs to collect its underlying device snapshot. If you say Y here, the collected device dumps will be added as ELF notes to /proc/vmcore. You can still disable device dump using the kernel command line option 'novmcoredd'. config PROC_SYSCTL bool "Sysctl support (/proc/sys)" if EXPERT depends on PROC_FS select SYSCTL default y help The sysctl interface provides a means of dynamically changing certain kernel parameters and variables on the fly without requiring a recompile of the kernel or reboot of the system. The primary interface is through /proc/sys. If you say Y here a tree of modifiable sysctl entries will be generated beneath the /proc/sys directory. They are explained in the files in <file:Documentation/admin-guide/sysctl/>. Note that enabling this option will enlarge the kernel by at least 8 KB. As it is generally a good thing, you should say Y here unless building a kernel for install/rescue disks or your system is very limited in memory. config PROC_PAGE_MONITOR default y depends on PROC_FS && MMU bool "Enable /proc page monitoring" if EXPERT help Various /proc files exist to monitor process memory utilization: /proc/pid/smaps, /proc/pid/clear_refs, /proc/pid/pagemap, /proc/kpagecount, and /proc/kpageflags. Disabling these interfaces will reduce the size of the kernel by approximately 4kb. config PROC_CHILDREN bool "Include /proc/<pid>/task/<tid>/children file" default n help Provides a fast way to retrieve first level children pids of a task. See <file:Documentation/filesystems/proc.rst> for more information. Say Y if you are running any user-space software which takes benefit from this interface. For example, rkt is such a piece of software. config PROC_PID_ARCH_STATUS def_bool n depends on PROC_FS config PROC_CPU_RESCTRL def_bool n depends on PROC_FS PK ! �c�ͥ � proc/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux proc filesystem routines. # obj-y += proc.o CFLAGS_task_mmu.o += $(call cc-option,-Wno-override-init,) proc-y := nommu.o task_nommu.o proc-$(CONFIG_MMU) := task_mmu.o proc-y += inode.o root.o base.o generic.o array.o \ fd.o proc-$(CONFIG_TTY) += proc_tty.o proc-y += cmdline.o proc-y += consoles.o proc-y += cpuinfo.o proc-y += devices.o proc-y += interrupts.o proc-y += loadavg.o proc-y += meminfo.o proc-y += stat.o proc-y += uptime.o proc-y += util.o proc-y += version.o proc-y += softirqs.o proc-y += namespaces.o proc-y += self.o proc-y += thread_self.o proc-$(CONFIG_PROC_SYSCTL) += proc_sysctl.o proc-$(CONFIG_NET) += proc_net.o proc-$(CONFIG_PROC_KCORE) += kcore.o proc-$(CONFIG_PROC_VMCORE) += vmcore.o proc-$(CONFIG_PRINTK) += kmsg.o proc-$(CONFIG_PROC_PAGE_MONITOR) += page.o proc-$(CONFIG_BOOT_CONFIG) += bootconfig.o version_signature.o PK ! �&>� nfs_common/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for Linux filesystem routines that are shared by client and server. # obj-$(CONFIG_NFS_ACL_SUPPORT) += nfs_acl.o nfs_acl-objs := nfsacl.o obj-$(CONFIG_GRACE_PERIOD) += grace.o obj-$(CONFIG_NFS_V4_2_SSC_HELPER) += nfs_ssc.o PK ! es� � hpfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config HPFS_FS tristate "OS/2 HPFS file system support" depends on BLOCK select FS_IOMAP help OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS is the file system used for organizing files on OS/2 hard disk partitions. Say Y if you want to be able to read files from and write files to an OS/2 HPFS partition on your hard drive. OS/2 floppies however are in regular MSDOS format, so you don't need this option in order to be able to read them. Read <file:Documentation/filesystems/hpfs.rst>. To compile this file system support as a module, choose M here: the module will be called hpfs. If unsure, say N. PK ! M��j� � hpfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Linux hpfs filesystem routines. # obj-$(CONFIG_HPFS_FS) += hpfs.o hpfs-objs := alloc.o anode.o buffer.o dentry.o dir.o dnode.o ea.o file.o \ inode.o map.o name.o namei.o super.o PK ! Ph)�� � befs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config BEFS_FS tristate "BeOS file system (BeFS) support (read only)" depends on BLOCK select NLS help The BeOS File System (BeFS) is the native file system of Be, Inc's BeOS. Notable features include support for arbitrary attributes on files and directories, and database-like indices on selected attributes. (Also note that this driver doesn't make those features available at this time). It is a 64 bit filesystem, so it supports extremely large volumes and files. If you use this filesystem, you should also say Y to at least one of the NLS (native language support) options below. If you don't know what this is about, say N. To compile this as a module, choose M here: the module will be called befs. config BEFS_DEBUG bool "Debug BeFS" depends on BEFS_FS help If you say Y here, you can use the 'debug' mount option to enable debugging output from the driver. PK ! ���� � befs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux BeOS filesystem routines. # obj-$(CONFIG_BEFS_FS) += befs.o ccflags-$(CONFIG_BEFS_DEBUG) += -DDEBUG befs-objs := datastream.o btree.o super.o inode.o debug.o io.o linuxvfs.o PK ! ��\�| | gfs2/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config GFS2_FS tristate "GFS2 file system support" select FS_POSIX_ACL select CRC32 select LIBCRC32C select QUOTACTL select FS_IOMAP help A cluster filesystem. Allows a cluster of computers to simultaneously use a block device that is shared between them (with FC, iSCSI, NBD, etc...). GFS reads and writes to the block device like a local filesystem, but also uses a lock module to allow the computers coordinate their I/O so filesystem consistency is maintained. One of the nifty features of GFS is perfect consistency -- changes made to the filesystem on one machine show up immediately on all other machines in the cluster. To use the GFS2 filesystem in a cluster, you will need to enable the locking module below. Documentation and utilities for GFS2 can be found here: http://sources.redhat.com/cluster The "nolock" lock module is now built in to GFS2 by default. If you want to use the DLM, be sure to enable IPv4/6 networking. config GFS2_FS_LOCKING_DLM bool "GFS2 DLM locking" depends on (GFS2_FS!=n) && NET && INET && (IPV6 || IPV6=n) && \ CONFIGFS_FS && SYSFS && (DLM=y || DLM=GFS2_FS) help Multiple node locking module for GFS2 Most users of GFS2 will require this. It provides the locking interface between GFS2 and the DLM, which is required to use GFS2 in a cluster environment. PK ! �HW W gfs2/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 ccflags-y := -I$(src) obj-$(CONFIG_GFS2_FS) += gfs2.o gfs2-y := acl.o bmap.o dir.o xattr.o glock.o \ glops.o log.o lops.o main.o meta_io.o \ aops.o dentry.o export.o file.o \ ops_fstype.o inode.o quota.o \ recovery.o rgrp.o super.o sys.o trans.o util.o gfs2-$(CONFIG_GFS2_FS_LOCKING_DLM) += lock_dlm.o PK ! K�1�� � reiserfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config REISERFS_FS tristate "Reiserfs support" select CRC32 help Stores not just filenames but the files themselves in a balanced tree. Uses journalling. Balanced trees are more efficient than traditional file system architectural foundations. In general, ReiserFS is as fast as ext2, but is very efficient with large directories and small files. Additional patches are needed for NFS and quotas, please see <https://reiser4.wiki.kernel.org/index.php/Main_Page> for links. It is more easily extended to have features currently found in database and keyword search systems than block allocation based file systems are. The next version will be so extended, and will support plugins consistent with our motto ``It takes more than a license to make source code open.'' Read <https://reiser4.wiki.kernel.org/index.php/Main_Page> to learn more about reiserfs. Sponsored by Threshold Networks, Emusic.com, and Bigstorage.com. If you like it, you can pay us to add new features to it that you need, buy a support contract, or pay us to port it to another OS. config REISERFS_CHECK bool "Enable reiserfs debug mode" depends on REISERFS_FS help If you set this to Y, then ReiserFS will perform every check it can possibly imagine of its internal consistency throughout its operation. It will also go substantially slower. More than once we have forgotten that this was on, and then gone despondent over the latest benchmarks.:-) Use of this option allows our team to go all out in checking for consistency when debugging without fear of its effect on end users. If you are on the verge of sending in a bug report, say Y and you might get a useful error message. Almost everyone should say N. config REISERFS_PROC_INFO bool "Stats in /proc/fs/reiserfs" depends on REISERFS_FS && PROC_FS help Create under /proc/fs/reiserfs a hierarchy of files, displaying various ReiserFS statistics and internal data at the expense of making your kernel or module slightly larger (+8 KB). This also increases the amount of kernel memory required for each mount. Almost everyone but ReiserFS developers and people fine-tuning reiserfs or tracing problems should say N. config REISERFS_FS_XATTR bool "ReiserFS extended attributes" depends on REISERFS_FS help Extended attributes are name:value pairs associated with inodes by the kernel or by users (see the attr(5) manual page for details). If unsure, say N. config REISERFS_FS_POSIX_ACL bool "ReiserFS POSIX Access Control Lists" depends on REISERFS_FS_XATTR select FS_POSIX_ACL help Posix Access Control Lists (ACLs) support permissions for users and groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N config REISERFS_FS_SECURITY bool "ReiserFS Security Labels" depends on REISERFS_FS_XATTR help Security labels support alternative access control models implemented by security modules like SELinux. This option enables an extended attribute handler for file security labels in the ReiserFS filesystem. If you are not using a security module that requires using extended attributes for file security labels, say N. PK ! ���ڽ � reiserfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the linux reiser-filesystem routines. # obj-$(CONFIG_REISERFS_FS) += reiserfs.o reiserfs-objs := bitmap.o do_balan.o namei.o inode.o file.o dir.o fix_node.o \ super.o prints.o objectid.o lbalance.o ibalance.o stree.o \ hashes.o tail_conversion.o journal.o resize.o \ item_ops.o ioctl.o xattr.o lock.o ifeq ($(CONFIG_REISERFS_PROC_INFO),y) reiserfs-objs += procfs.o endif ifeq ($(CONFIG_REISERFS_FS_XATTR),y) reiserfs-objs += xattr_user.o xattr_trusted.o endif ifeq ($(CONFIG_REISERFS_FS_SECURITY),y) reiserfs-objs += xattr_security.o endif ifeq ($(CONFIG_REISERFS_FS_POSIX_ACL),y) reiserfs-objs += xattr_acl.o endif TAGS: etags *.c PK ! ��'E= = adfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config ADFS_FS tristate "ADFS file system support" depends on BLOCK help The Acorn Disc Filing System is the standard file system of the RiscOS operating system which runs on Acorn's ARM-based Risc PC systems and the Acorn Archimedes range of machines. If you say Y here, Linux will be able to read from ADFS partitions on hard drives and from ADFS-formatted floppy discs. If you also want to be able to write to those devices, say Y to "ADFS write support" below. The ADFS partition should be the first partition (i.e., /dev/[hs]d?1) on each of your drives. Please read the file <file:Documentation/filesystems/adfs.rst> for further details. To compile this code as a module, choose M here: the module will be called adfs. If unsure, say N. config ADFS_FS_RW bool "ADFS write support (DANGEROUS)" depends on ADFS_FS help If you say Y here, you will be able to write to ADFS partitions on hard drives and ADFS-formatted floppy disks. This is experimental codes, so if you're unsure, say N. PK ! Wɏ� � adfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux adfs filesystem routines. # obj-$(CONFIG_ADFS_FS) += adfs.o adfs-objs := dir.o dir_f.o dir_fplus.o file.o inode.o map.o super.o PK ! 5ѫ<� � ramfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux ramfs routines. # obj-y += ramfs.o file-mmu-y := file-nommu.o file-mmu-$(CONFIG_MMU) := file-mmu.o ramfs-objs += inode.o $(file-mmu-y) PK ! DC�_ _ iomap/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-or-later # # Copyright (c) 2019 Oracle. # All Rights Reserved. # ccflags-y += -I $(srctree)/$(src) # needed for trace events obj-$(CONFIG_FS_IOMAP) += iomap.o iomap-y += trace.o \ buffered-io.o \ direct-io.o \ fiemap.o \ iter.o \ seek.o iomap-$(CONFIG_SWAP) += swapfile.o PK ! ��5�� � hostfs/Makefilenu �[��� # # Copyright (C) 2000 Jeff Dike (jdike@karaya.com) # Licensed under the GPL # hostfs-objs := hostfs_kern.o hostfs_user.o obj-y := obj-$(CONFIG_HOSTFS) += hostfs.o include arch/um/scripts/Makefile.rules PK ! � <n ext4/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # Ext3 configs are here for backward compatibility with old configs which may # have EXT3_FS set but not EXT4_FS set and thus would result in non-bootable # kernels after the removal of ext3 driver. config EXT3_FS tristate "The Extended 3 (ext3) filesystem" select EXT4_FS help This config option is here only for backward compatibility. ext3 filesystem is now handled by the ext4 driver. config EXT3_FS_POSIX_ACL bool "Ext3 POSIX Access Control Lists" depends on EXT3_FS select EXT4_FS_POSIX_ACL select FS_POSIX_ACL help This config option is here only for backward compatibility. ext3 filesystem is now handled by the ext4 driver. config EXT3_FS_SECURITY bool "Ext3 Security Labels" depends on EXT3_FS select EXT4_FS_SECURITY help This config option is here only for backward compatibility. ext3 filesystem is now handled by the ext4 driver. config EXT4_FS tristate "The Extended 4 (ext4) filesystem" select JBD2 select CRC16 select CRYPTO select CRYPTO_CRC32C select FS_IOMAP select FS_ENCRYPTION_ALGS if FS_ENCRYPTION help This is the next generation of the ext3 filesystem. Unlike the change from ext2 filesystem to ext3 filesystem, the on-disk format of ext4 is not forwards compatible with ext3; it is based on extent maps and it supports 48-bit physical block numbers. The ext4 filesystem also supports delayed allocation, persistent preallocation, high resolution time stamps, and a number of other features to improve performance and speed up fsck time. For more information, please see the web pages at http://ext4.wiki.kernel.org. The ext4 filesystem supports mounting an ext3 filesystem; while there are some performance gains from the delayed allocation and inode table readahead, the best performance gains require enabling ext4 features in the filesystem using tune2fs, or formatting a new filesystem as an ext4 filesystem initially. Without explicit enabling of ext4 features, the on disk filesystem format stays fully backward compatible. To compile this file system support as a module, choose M here. The module will be called ext4. If unsure, say N. config EXT4_USE_FOR_EXT2 bool "Use ext4 for ext2 file systems" depends on EXT4_FS depends on EXT2_FS=n default y help Allow the ext4 file system driver code to be used for ext2 file system mounts. This allows users to reduce their compiled kernel size by using one file system driver for ext2, ext3, and ext4 file systems. config EXT4_FS_POSIX_ACL bool "Ext4 POSIX Access Control Lists" depends on EXT4_FS select FS_POSIX_ACL help POSIX Access Control Lists (ACLs) support permissions for users and groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N config EXT4_FS_SECURITY bool "Ext4 Security Labels" depends on EXT4_FS help Security labels support alternative access control models implemented by security modules like SELinux. This option enables an extended attribute handler for file security labels in the ext4 filesystem. If you are not using a security module that requires using extended attributes for file security labels, say N. config EXT4_DEBUG bool "Ext4 debugging support" depends on EXT4_FS help Enables run-time debugging support for the ext4 filesystem. If you select Y here, then you will be able to turn on debugging using dynamic debug control for mb_debug() / ext_debug() msgs. config EXT4_KUNIT_TESTS tristate "KUnit tests for ext4" if !KUNIT_ALL_TESTS depends on EXT4_FS && KUNIT default KUNIT_ALL_TESTS help This builds the ext4 KUnit tests. KUnit tests run during boot and output the results to the debug log in TAP format (https://testanything.org/). Only useful for kernel devs running KUnit test harness and are not for inclusion into a production build. For more information on KUnit and unit tests in general please refer to the KUnit documentation in Documentation/dev-tools/kunit/. If unsure, say N. PK ! }���� � ext4/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the linux ext4-filesystem routines. # obj-$(CONFIG_EXT4_FS) += ext4.o ext4-y := balloc.o bitmap.o block_validity.o dir.o ext4_jbd2.o extents.o \ extents_status.o file.o fsmap.o fsync.o hash.o ialloc.o \ indirect.o inline.o inode.o ioctl.o mballoc.o migrate.o \ mmp.o move_extent.o namei.o page-io.o readpage.o resize.o \ super.o symlink.o sysfs.o xattr.o xattr_hurd.o xattr_trusted.o \ xattr_user.o fast_commit.o orphan.o ext4-$(CONFIG_EXT4_FS_POSIX_ACL) += acl.o ext4-$(CONFIG_EXT4_FS_SECURITY) += xattr_security.o ext4-inode-test-objs += inode-test.o obj-$(CONFIG_EXT4_KUNIT_TESTS) += ext4-inode-test.o ext4-$(CONFIG_FS_VERITY) += verity.o PK ! �l5u u vboxsf/Kconfignu �[��� config VBOXSF_FS tristate "VirtualBox guest shared folder (vboxsf) support" depends on X86 && VBOXGUEST select NLS help VirtualBox hosts can share folders with guests, this driver implements the Linux-guest side of this allowing folders exported by the host to be mounted under Linux. If you want to use shared folders in VirtualBox guests, answer Y or M. PK ! �Ɏ|� � vboxsf/Makefilenu �[��� # SPDX-License-Identifier: MIT obj-$(CONFIG_VBOXSF_FS) += vboxsf.o vboxsf-y := dir.o file.o utils.o vboxsf_wrappers.o super.o PK ! ��[^� � efivarfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config EFIVAR_FS tristate "EFI Variable filesystem" depends on EFI default m help efivarfs is a replacement filesystem for the old EFI variable support via sysfs, as it doesn't suffer from the same 1024-byte variable size limit. To compile this file system support as a module, choose M here. The module will be called efivarfs. If unsure, say N. PK ! �x�� � efivarfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the efivarfs filesystem # obj-$(CONFIG_EFIVAR_FS) += efivarfs.o efivarfs-objs := inode.o file.o super.o PK ! �&|' ' hfsplus/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config HFSPLUS_FS tristate "Apple Extended HFS file system support" depends on BLOCK select NLS select NLS_UTF8 help If you say Y here, you will be able to mount extended format Macintosh-formatted hard drive partitions with full read-write access. This file system is often called HFS+ and was introduced with MacOS 8. It includes all Mac specific filesystem data such as data forks and creator codes, but it also has several UNIX style features such as file ownership and permissions. PK ! �nm m hfsplus/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # ## Makefile for the linux hfsplus filesystem routines. # obj-$(CONFIG_HFSPLUS_FS) += hfsplus.o hfsplus-objs := super.o options.o inode.o ioctl.o extents.o catalog.o dir.o btree.o \ bnode.o brec.o bfind.o tables.o unicode.o wrapper.o bitmap.o part_tbl.o \ attributes.o xattr.o xattr_user.o xattr_security.o xattr_trusted.o PK ! �۩u sysfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config SYSFS bool "sysfs file system support" if EXPERT default y select KERNFS help The sysfs filesystem is a virtual filesystem that the kernel uses to export internal kernel objects, their attributes, and their relationships to one another. Users can use sysfs to ascertain useful information about the running kernel, such as the devices the kernel has discovered on each bus and which driver each is bound to. sysfs can also be used to tune devices and other kernel subsystems. Some system agents rely on the information in sysfs to operate. /sbin/hotplug uses device and object attributes in sysfs to assist in delegating policy decisions, like persistently naming devices. sysfs is currently used by the block subsystem to mount the root partition. If sysfs is disabled you must specify the boot device on the kernel boot command line via its major and minor numbers. For example, "root=03:01" for /dev/hda1. Designers of embedded systems may wish to say N here to conserve space. PK ! )�T� � sysfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the sysfs virtual filesystem # obj-y := file.o dir.o symlink.o mount.o group.o PK ! �|�� � jfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config JFS_FS tristate "JFS filesystem support" select NLS select CRC32 help This is a port of IBM's Journaled Filesystem . More information is available in the file <file:Documentation/admin-guide/jfs.rst>. If you do not intend to use the JFS filesystem, say N. config JFS_POSIX_ACL bool "JFS POSIX Access Control Lists" depends on JFS_FS select FS_POSIX_ACL help Posix Access Control Lists (ACLs) support permissions for users and groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N config JFS_SECURITY bool "JFS Security Labels" depends on JFS_FS help Security labels support alternative access control models implemented by security modules like SELinux. This option enables an extended attribute handler for file security labels in the jfs filesystem. If you are not using a security module that requires using extended attributes for file security labels, say N. config JFS_DEBUG bool "JFS debugging" depends on JFS_FS help If you are experiencing any problems with the JFS filesystem, say Y here. This will result in additional debugging messages to be written to the system log. Under normal circumstances, this results in very little overhead. config JFS_STATISTICS bool "JFS statistics" depends on JFS_FS help Enabling this option will cause statistics from the JFS file system to be made available to the user in the /proc/fs/jfs/ directory. PK ! �oR� � jfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux JFS filesystem routines. # obj-$(CONFIG_JFS_FS) += jfs.o jfs-y := super.o file.o inode.o namei.o jfs_mount.o jfs_umount.o \ jfs_xtree.o jfs_imap.o jfs_debug.o jfs_dmap.o \ jfs_unicode.o jfs_dtree.o jfs_inode.o jfs_discard.o \ jfs_extent.o symlink.o jfs_metapage.o \ jfs_logmgr.o jfs_txnmgr.o jfs_uniupr.o \ resize.o xattr.o ioctl.o jfs-$(CONFIG_JFS_POSIX_ACL) += acl.o ccflags-y := -D_JFS_4K PK ! �%�m� � exfat/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-or-later config EXFAT_FS tristate "exFAT filesystem support" select NLS help This allows you to mount devices formatted with the exFAT file system. exFAT is typically used on SD-Cards or USB sticks. To compile this as a module, choose M here: the module will be called exfat. config EXFAT_DEFAULT_IOCHARSET string "Default iocharset for exFAT" default "utf8" depends on EXFAT_FS help Set this to the default input/output character set to use for converting between the encoding that is used for user visible filenames and the UTF-16 character encoding that the exFAT filesystem uses. This can be overridden with the "iocharset" mount option for the exFAT filesystems. PK ! ,�� � exfat/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-or-later # # Makefile for the linux exFAT filesystem support. # obj-$(CONFIG_EXFAT_FS) += exfat.o exfat-y := inode.o namei.o dir.o super.o fatent.o cache.o nls.o misc.o \ file.o balloc.o PK ! H� TD D omfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config OMFS_FS tristate "SonicBlue Optimized MPEG File System support" depends on BLOCK select CRC_ITU_T help This is the proprietary file system used by the Rio Karma music player and ReplayTV DVR. Despite the name, this filesystem is not more efficient than a standard FS for MPEG files, in fact likely the opposite is true. Say Y if you have either of these devices and wish to mount its disk. To compile this file system support as a module, choose M here: the module will be called omfs. If unsure, say N. PK ! ^�+�r r omfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_OMFS_FS) += omfs.o omfs-y := bitmap.o dir.o file.o inode.o PK ! |�!�A A minix/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config MINIX_FS tristate "Minix file system support" depends on BLOCK help Minix is a simple operating system used in many classes about OS's. The minix file system (method to organize files on a hard disk partition or a floppy disk) was the original file system for Linux, but has been superseded by the second extended file system ext2fs. You don't want to use the minix file system on your hard disk because of certain built-in restrictions, but it is sometimes found on older Linux floppy disks. This option will enlarge your kernel by about 28 KB. If unsure, say N. To compile this file system support as a module, choose M here: the module will be called minix. Note that the file system of your root partition (the one containing the directory /) cannot be compiled as a module. config MINIX_FS_NATIVE_ENDIAN def_bool MINIX_FS depends on MICROBLAZE || MIPS || S390 || SUPERH || SPARC || XTENSA || (M68K && !MMU) config MINIX_FS_BIG_ENDIAN_16BIT_INDEXED def_bool MINIX_FS depends on M68K && MMU PK ! OG�� � minix/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Linux minix filesystem routines. # obj-$(CONFIG_MINIX_FS) += minix.o minix-objs := bitmap.o itree_v1.o itree_v2.o namei.o inode.o file.o dir.o PK ! 0y�5� � smbfs_common/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for Linux filesystem routines that are shared by client and server. # obj-$(CONFIG_SMBFS_COMMON) += cifs_arc4.o obj-$(CONFIG_SMBFS_COMMON) += cifs_md4.o PK ! ���e e qnx6/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config QNX6FS_FS tristate "QNX6 file system support (read only)" depends on BLOCK && CRC32 help This is the file system used by the real-time operating systems QNX 6 (also called QNX RTP). Further information is available at <http://www.qnx.com/>. Say Y if you intend to mount QNX hard disks or floppies formatted with a mkqnx6fs. However, keep in mind that this currently is a readonly driver! To compile this file system support as a module, choose M here: the module will be called qnx6. If you don't know whether you need it, then you don't need it: answer N. config QNX6FS_DEBUG bool "QNX6 debugging information" depends on QNX6FS_FS help Turns on extended debugging output. If you are not a developer working on the QNX6FS, you probably don't want this: answer N. PK ! ��m;� � qnx6/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux qnx4-filesystem routines. # obj-$(CONFIG_QNX6FS_FS) += qnx6.o qnx6-objs := inode.o dir.o namei.o super_mmi.o ccflags-$(CONFIG_QNX6FS_DEBUG) += -DDEBUG PK ! �٪ư � bfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config BFS_FS tristate "BFS file system support" depends on BLOCK help Boot File System (BFS) is a file system used under SCO UnixWare to allow the bootloader access to the kernel image and other important files during the boot process. It is usually mounted under /stand and corresponds to the slice marked as "STAND" in the UnixWare partition. You should say Y if you want to read or write the files on your /stand slice from within Linux. You then also need to say Y to "UnixWare slices support", below. More information about the BFS file system is contained in the file <file:Documentation/filesystems/bfs.rst>. If you don't know what this is about, say N. To compile this as a module, choose M here: the module will be called bfs. Note that the file system of your root partition (the one containing the directory /) cannot be compiled as a module. PK ! �e (� � bfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for BFS filesystem. # obj-$(CONFIG_BFS_FS) += bfs.o bfs-objs := inode.o file.o dir.o PK ! �WWr� � hfs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config HFS_FS tristate "Apple Macintosh file system support" depends on BLOCK select NLS help If you say Y here, you will be able to mount Macintosh-formatted floppy disks and hard drive partitions with full read-write access. Please read <file:Documentation/filesystems/hfs.rst> to learn about the available mount options. To compile this file system support as a module, choose M here: the module will be called hfs. PK ! �%# # hfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Linux hfs filesystem routines. # obj-$(CONFIG_HFS_FS) += hfs.o hfs-objs := bitmap.o bfind.o bnode.o brec.o btree.o \ catalog.o dir.o extent.o inode.o attr.o mdb.o \ part_tbl.o string.o super.o sysdep.o trans.o PK ! �F�� � cifs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config CIFS tristate "SMB3 and CIFS support (advanced network filesystem)" depends on INET select NLS select CRYPTO select CRYPTO_MD5 select CRYPTO_SHA256 select CRYPTO_SHA512 select CRYPTO_CMAC select CRYPTO_HMAC select CRYPTO_AEAD2 select CRYPTO_CCM select CRYPTO_GCM select CRYPTO_ECB select CRYPTO_AES select KEYS select DNS_RESOLVER select ASN1 select OID_REGISTRY help This is the client VFS module for the SMB3 family of NAS protocols, (including support for the most recent, most secure dialect SMB3.1.1) as well as for earlier dialects such as SMB2.1, SMB2 and the older Common Internet File System (CIFS) protocol. CIFS was the successor to the original dialect, the Server Message Block (SMB) protocol, the native file sharing mechanism for most early PC operating systems. The SMB3 protocol is supported by most modern operating systems and NAS appliances (e.g. Samba, Windows 10, Windows Server 2016, MacOS) and even in the cloud (e.g. Microsoft Azure). The older CIFS protocol was included in Windows NT4, 2000 and XP (and later) as well by Samba (which provides excellent CIFS and SMB3 server support for Linux and many other operating systems). Use of dialects older than SMB2.1 is often discouraged on public networks. This module also provides limited support for OS/2 and Windows ME and similar very old servers. This module provides an advanced network file system client for mounting to SMB3 (and CIFS) compliant servers. It includes support for DFS (hierarchical name space), secure per-user session establishment via Kerberos or NTLM or NTLMv2, RDMA (smbdirect), advanced security features, per-share encryption, directory leases, safe distributed caching (oplock), optional packet signing, Unicode and other internationalization improvements. In general, the default dialects, SMB3 and later, enable better performance, security and features, than would be possible with CIFS. Note that when mounting to Samba, due to the CIFS POSIX extensions, CIFS mounts can provide slightly better POSIX compatibility than SMB3 mounts. SMB2/SMB3 mount options are also slightly simpler (compared to CIFS) due to protocol improvements. If you need to mount to Samba, Azure, Macs or Windows from this machine, say Y. config CIFS_STATS2 bool "Extended statistics" depends on CIFS default y help Enabling this option will allow more detailed statistics on SMB request timing to be displayed in /proc/fs/cifs/DebugData and also allow optional logging of slow responses to dmesg (depending on the value of /proc/fs/cifs/cifsFYI). See Documentation/admin-guide/cifs/usage.rst for more details. These additional statistics may have a minor effect on performance and memory utilization. If unsure, say Y. config CIFS_ALLOW_INSECURE_LEGACY bool "Support legacy servers which use less secure dialects" depends on CIFS default y help Modern dialects, SMB2.1 and later (including SMB3 and 3.1.1), have additional security features, including protection against man-in-the-middle attacks and stronger crypto hashes, so the use of legacy dialects (SMB1/CIFS and SMB2.0) is discouraged. Disabling this option prevents users from using vers=1.0 or vers=2.0 on mounts with cifs.ko If unsure, say Y. config CIFS_UPCALL bool "Kerberos/SPNEGO advanced session setup" depends on CIFS help Enables an upcall mechanism for CIFS which accesses userspace helper utilities to provide SPNEGO packaged (RFC 4178) Kerberos tickets which are needed to mount to certain secure servers (for which more secure Kerberos authentication is required). If unsure, say Y. config CIFS_XATTR bool "CIFS extended attributes" depends on CIFS help Extended attributes are name:value pairs associated with inodes by the kernel or by users (see the attr(5) manual page for details). CIFS maps the name of extended attributes beginning with the user namespace prefix to SMB/CIFS EAs. EAs are stored on Windows servers without the user namespace prefix, but their names are seen by Linux cifs clients prefaced by the user namespace prefix. The system namespace (used by some filesystems to store ACLs) is not supported at this time. If unsure, say Y. config CIFS_POSIX bool "CIFS POSIX Extensions" depends on CIFS && CIFS_ALLOW_INSECURE_LEGACY && CIFS_XATTR help Enabling this option will cause the cifs client to attempt to negotiate a newer dialect with servers, such as Samba 3.0.5 or later, that optionally can handle more POSIX like (rather than Windows like) file behavior. It also enables support for POSIX ACLs (getfacl and setfacl) to servers (such as Samba 3.10 and later) which can negotiate CIFS POSIX ACL support. If unsure, say N. config CIFS_DEBUG bool "Enable CIFS debugging routines" default y depends on CIFS help Enabling this option adds helpful debugging messages to the cifs code which increases the size of the cifs module. If unsure, say Y. config CIFS_DEBUG2 bool "Enable additional CIFS debugging routines" depends on CIFS_DEBUG help Enabling this option adds a few more debugging routines to the cifs code which slightly increases the size of the cifs module and can cause additional logging of debug messages in some error paths, slowing performance. This option can be turned off unless you are debugging cifs problems. If unsure, say N. config CIFS_DEBUG_DUMP_KEYS bool "Dump encryption keys for offline decryption (Unsafe)" depends on CIFS_DEBUG help Enabling this will dump the encryption and decryption keys used to communicate on an encrypted share connection on the console. This allows Wireshark to decrypt and dissect encrypted network captures. Enable this carefully. If unsure, say N. config CIFS_DFS_UPCALL bool "DFS feature support" depends on CIFS help Distributed File System (DFS) support is used to access shares transparently in an enterprise name space, even if the share moves to a different server. This feature also enables an upcall mechanism for CIFS which contacts userspace helper utilities to provide server name resolution (host names to IP addresses) which is needed in order to reconnect to servers if their addresses change or for implicit mounts of DFS junction points. If unsure, say Y. config CIFS_SWN_UPCALL bool "SWN feature support" depends on CIFS help The Service Witness Protocol (SWN) is used to get notifications from a highly available server of resource state changes. This feature enables an upcall mechanism for CIFS which contacts a userspace daemon to establish the DCE/RPC connection to retrieve the cluster available interfaces and resource change notifications. If unsure, say Y. config CIFS_NFSD_EXPORT bool "Allow nfsd to export CIFS file system" depends on CIFS && BROKEN help Allows NFS server to export a CIFS mounted share (nfsd over cifs) config CIFS_SMB_DIRECT bool "SMB Direct support" depends on CIFS=m && INFINIBAND && INFINIBAND_ADDR_TRANS || CIFS=y && INFINIBAND=y && INFINIBAND_ADDR_TRANS=y help Enables SMB Direct support for SMB 3.0, 3.02 and 3.1.1. SMB Direct allows transferring SMB packets over RDMA. If unsure, say Y. config CIFS_FSCACHE bool "Provide CIFS client caching support" depends on CIFS=m && FSCACHE || CIFS=y && FSCACHE=y help Makes CIFS FS-Cache capable. Say Y here if you want your CIFS data to be cached locally on disk through the general filesystem cache manager. If unsure, say N. config CIFS_ROOT bool "SMB root file system (Experimental)" depends on CIFS=y && IP_PNP help Enables root file system support over SMB protocol. Most people say N here. PK ! E���H H cifs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for Linux CIFS/SMB2/SMB3 VFS client # ccflags-y += -I$(src) # needed for trace events obj-$(CONFIG_CIFS) += cifs.o cifs-y := trace.o cifsfs.o cifssmb.o cifs_debug.o connect.o dir.o file.o \ inode.o link.o misc.o netmisc.o smbencrypt.o transport.o \ cifs_unicode.o nterr.o cifsencrypt.o \ readdir.o ioctl.o sess.o export.o smb1ops.o unc.o winucase.o \ smb2ops.o smb2maperror.o smb2transport.o \ smb2misc.o smb2pdu.o smb2inode.o smb2file.o cifsacl.o fs_context.o \ dns_resolve.o cifs_spnego_negtokeninit.asn1.o asn1.o $(obj)/asn1.o: $(obj)/cifs_spnego_negtokeninit.asn1.h $(obj)/cifs_spnego_negtokeninit.asn1.o: $(obj)/cifs_spnego_negtokeninit.asn1.c $(obj)/cifs_spnego_negtokeninit.asn1.h cifs-$(CONFIG_CIFS_XATTR) += xattr.o cifs-$(CONFIG_CIFS_UPCALL) += cifs_spnego.o cifs-$(CONFIG_CIFS_DFS_UPCALL) += cifs_dfs_ref.o dfs_cache.o cifs-$(CONFIG_CIFS_SWN_UPCALL) += netlink.o cifs_swn.o cifs-$(CONFIG_CIFS_FSCACHE) += fscache.o cache.o cifs-$(CONFIG_CIFS_SMB_DIRECT) += smbdirect.o cifs-$(CONFIG_CIFS_ROOT) += cifsroot.o PK ! ��t5� � isofs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config ISO9660_FS tristate "ISO 9660 CDROM file system support" help This is the standard file system used on CD-ROMs. It was previously known as "High Sierra File System" and is called "hsfs" on other Unix systems. The so-called Rock-Ridge extensions which allow for long Unix filenames and symbolic links are also supported by this driver. If you have a CD-ROM drive and want to do more with it than just listen to audio CDs and watch its LEDs, say Y (and read <file:Documentation/filesystems/isofs.rst> and the CD-ROM-HOWTO, available from <http://www.tldp.org/docs.html#howto>), thereby enlarging your kernel by about 27 KB; otherwise say N. To compile this file system support as a module, choose M here: the module will be called isofs. config JOLIET bool "Microsoft Joliet CDROM extensions" depends on ISO9660_FS select NLS help Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system which allows for long filenames in unicode format (unicode is the new 16 bit character code, successor to ASCII, which encodes the characters of almost all languages of the world; see <http://www.unicode.org/> for more information). Say Y here if you want to be able to read Joliet CD-ROMs under Linux. config ZISOFS bool "Transparent decompression extension" depends on ISO9660_FS select ZLIB_INFLATE help This is a Linux-specific extension to RockRidge which lets you store data in compressed form on a CD-ROM and have it transparently decompressed when the CD-ROM is accessed. See <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools necessary to create such a filesystem. Say Y here if you want to be able to read such compressed CD-ROMs. PK ! �X�3 3 isofs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux isofs filesystem routines. # obj-$(CONFIG_ISO9660_FS) += isofs.o isofs-objs-y := namei.o inode.o dir.o util.o rock.o export.o isofs-objs-$(CONFIG_JOLIET) += joliet.o isofs-objs-$(CONFIG_ZISOFS) += compress.o isofs-objs := $(isofs-objs-y) PK ! �i#�( �( Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # File system configuration # menu "File systems" # Use unaligned word dcache accesses config DCACHE_WORD_ACCESS bool config VALIDATE_FS_PARSER bool "Validate filesystem parameter description" help Enable this to perform validation of the parameter description for a filesystem when it is registered. if BLOCK config FS_IOMAP bool source "fs/ext2/Kconfig" source "fs/ext4/Kconfig" source "fs/jbd2/Kconfig" config FS_MBCACHE # Meta block cache for Extended Attributes (ext2/ext3/ext4) tristate default y if EXT2_FS=y && EXT2_FS_XATTR default y if EXT4_FS=y default m if EXT2_FS_XATTR || EXT4_FS source "fs/reiserfs/Kconfig" source "fs/jfs/Kconfig" source "fs/xfs/Kconfig" source "fs/gfs2/Kconfig" source "fs/ocfs2/Kconfig" source "fs/btrfs/Kconfig" source "fs/nilfs2/Kconfig" source "fs/f2fs/Kconfig" source "fs/zonefs/Kconfig" config FS_DAX bool "File system based Direct Access (DAX) support" depends on MMU depends on !(ARM || MIPS || SPARC) select DEV_PAGEMAP_OPS if (ZONE_DEVICE && !FS_DAX_LIMITED) select FS_IOMAP select DAX help Direct Access (DAX) can be used on memory-backed block devices. If the block device supports DAX and the filesystem supports DAX, then you can avoid using the pagecache to buffer I/Os. Turning on this option will compile in support for DAX. For a DAX device to support file system access it needs to have struct pages. For the nfit based NVDIMMs this can be enabled using the ndctl utility: # ndctl create-namespace --force --reconfig=namespace0.0 \ --mode=fsdax --map=mem See the 'create-namespace' man page for details on the overhead of --map=mem: https://docs.pmem.io/ndctl-user-guide/ndctl-man-pages/ndctl-create-namespace For ndctl to work CONFIG_DEV_DAX needs to be enabled as well. For most file systems DAX support needs to be manually enabled globally or per-inode using a mount option as well. See the file documentation in Documentation/filesystems/dax.rst for details. If you do not have a block device that is capable of using this, or if unsure, say N. Saying Y will increase the size of the kernel by about 5kB. config FS_DAX_PMD bool default FS_DAX depends on FS_DAX depends on ZONE_DEVICE depends on TRANSPARENT_HUGEPAGE # Selected by DAX drivers that do not expect filesystem DAX to support # get_user_pages() of DAX mappings. I.e. "limited" indicates no support # for fork() of processes with MAP_SHARED mappings or support for # direct-I/O to a DAX mapping. config FS_DAX_LIMITED bool endif # BLOCK # Posix ACL utility routines # # Note: Posix ACLs can be implemented without these helpers. Never use # this symbol for ifdefs in core code. # config FS_POSIX_ACL def_bool n config EXPORTFS tristate config EXPORTFS_BLOCK_OPS bool "Enable filesystem export operations for block IO" help This option enables the export operations for a filesystem to support external block IO. config FILE_LOCKING bool "Enable POSIX file locking API" if EXPERT default y help This option enables standard file locking support, required for filesystems like NFS and for the flock() system call. Disabling this option saves about 11k. source "fs/crypto/Kconfig" source "fs/verity/Kconfig" source "fs/notify/Kconfig" source "fs/quota/Kconfig" source "fs/autofs/Kconfig" source "fs/fuse/Kconfig" source "fs/overlayfs/Kconfig" config SHIFT_FS tristate "UID/GID shifting overlay filesystem for containers" help This filesystem can overlay any mounted filesystem and shift the uid/gid the files appear at. The idea is that unprivileged containers can use this to mount root volumes using this technique. config SHIFT_FS_POSIX_ACL bool "shiftfs POSIX Access Control Lists" depends on SHIFT_FS select FS_POSIX_ACL help POSIX Access Control Lists (ACLs) support permissions for users and groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N. menu "Caches" source "fs/netfs/Kconfig" source "fs/fscache/Kconfig" source "fs/cachefiles/Kconfig" endmenu if BLOCK menu "CD-ROM/DVD Filesystems" source "fs/isofs/Kconfig" source "fs/udf/Kconfig" endmenu endif # BLOCK if BLOCK menu "DOS/FAT/EXFAT/NT Filesystems" source "fs/fat/Kconfig" source "fs/exfat/Kconfig" source "fs/ntfs/Kconfig" source "fs/ntfs3/Kconfig" endmenu endif # BLOCK menu "Pseudo filesystems" source "fs/proc/Kconfig" source "fs/kernfs/Kconfig" source "fs/sysfs/Kconfig" config TMPFS bool "Tmpfs virtual memory file system support (former shm fs)" depends on SHMEM help Tmpfs is a file system which keeps all files in virtual memory. Everything in tmpfs is temporary in the sense that no files will be created on your hard drive. The files live in memory and swap space. If you unmount a tmpfs instance, everything stored therein is lost. See <file:Documentation/filesystems/tmpfs.rst> for details. config TMPFS_POSIX_ACL bool "Tmpfs POSIX Access Control Lists" depends on TMPFS select TMPFS_XATTR select FS_POSIX_ACL help POSIX Access Control Lists (ACLs) support additional access rights for users and groups beyond the standard owner/group/world scheme, and this option selects support for ACLs specifically for tmpfs filesystems. If you've selected TMPFS, it's possible that you'll also need this option as there are a number of Linux distros that require POSIX ACL support under /dev for certain features to work properly. For example, some distros need this feature for ALSA-related /dev files for sound to work properly. In short, if you're not sure, say Y. config TMPFS_XATTR bool "Tmpfs extended attributes" depends on TMPFS default n help Extended attributes are name:value pairs associated with inodes by the kernel or by users (see the attr(5) manual page for details). Currently this enables support for the trusted.* and security.* namespaces. You need this for POSIX ACL support on tmpfs. If unsure, say N. config TMPFS_INODE64 bool "Use 64-bit ino_t by default in tmpfs" depends on TMPFS && 64BIT default n help tmpfs has historically used only inode numbers as wide as an unsigned int. In some cases this can cause wraparound, potentially resulting in multiple files with the same inode number on a single device. This option makes tmpfs use the full width of ino_t by default, without needing to specify the inode64 option when mounting. But if a long-lived tmpfs is to be accessed by 32-bit applications so ancient that opening a file larger than 2GiB fails with EINVAL, then the INODE64 config option and inode64 mount option risk operations failing with EOVERFLOW once 33-bit inode numbers are reached. To override this configured default, use the inode32 or inode64 option when mounting. If unsure, say N. config ARCH_SUPPORTS_HUGETLBFS def_bool n config HUGETLBFS bool "HugeTLB file system support" depends on X86 || IA64 || SPARC64 || ARCH_SUPPORTS_HUGETLBFS || BROKEN help hugetlbfs is a filesystem backing for HugeTLB pages, based on ramfs. For architectures that support it, say Y here and read <file:Documentation/admin-guide/mm/hugetlbpage.rst> for details. If unsure, say N. config HUGETLB_PAGE def_bool HUGETLBFS config HUGETLB_PAGE_FREE_VMEMMAP def_bool HUGETLB_PAGE depends on X86_64 depends on SPARSEMEM_VMEMMAP config HUGETLB_PAGE_FREE_VMEMMAP_DEFAULT_ON bool "Default freeing vmemmap pages of HugeTLB to on" default n depends on HUGETLB_PAGE_FREE_VMEMMAP help When using HUGETLB_PAGE_FREE_VMEMMAP, the freeing unused vmemmap pages associated with each HugeTLB page is default off. Say Y here to enable freeing vmemmap pages of HugeTLB by default. It can then be disabled on the command line via hugetlb_free_vmemmap=off. config MEMFD_CREATE def_bool TMPFS || HUGETLBFS config ARCH_HAS_GIGANTIC_PAGE bool source "fs/configfs/Kconfig" source "fs/efivarfs/Kconfig" endmenu menuconfig MISC_FILESYSTEMS bool "Miscellaneous filesystems" default y help Say Y here to get to see options for various miscellaneous filesystems, such as filesystems that came from other operating systems. This option alone does not add any kernel code. If you say N, all options in this submenu will be skipped and disabled; if unsure, say Y here. if MISC_FILESYSTEMS source "fs/orangefs/Kconfig" source "fs/adfs/Kconfig" source "fs/affs/Kconfig" source "fs/ecryptfs/Kconfig" source "fs/hfs/Kconfig" source "fs/hfsplus/Kconfig" source "fs/befs/Kconfig" source "fs/bfs/Kconfig" source "fs/efs/Kconfig" source "fs/jffs2/Kconfig" # UBIFS File system configuration source "fs/ubifs/Kconfig" source "fs/cramfs/Kconfig" source "fs/squashfs/Kconfig" source "fs/freevxfs/Kconfig" source "fs/minix/Kconfig" source "fs/omfs/Kconfig" source "fs/hpfs/Kconfig" source "fs/qnx4/Kconfig" source "fs/qnx6/Kconfig" source "fs/romfs/Kconfig" source "fs/pstore/Kconfig" source "fs/sysv/Kconfig" source "fs/ufs/Kconfig" source "fs/erofs/Kconfig" source "fs/vboxsf/Kconfig" source "fs/aufs/Kconfig" endif # MISC_FILESYSTEMS menuconfig NETWORK_FILESYSTEMS bool "Network File Systems" default y depends on NET help Say Y here to get to see options for network filesystems and filesystem-related networking code, such as NFS daemon and RPCSEC security modules. This option alone does not add any kernel code. If you say N, all options in this submenu will be skipped and disabled; if unsure, say Y here. if NETWORK_FILESYSTEMS source "fs/nfs/Kconfig" source "fs/nfsd/Kconfig" config GRACE_PERIOD tristate config LOCKD tristate depends on FILE_LOCKING select CRC32 select GRACE_PERIOD config LOCKD_V4 bool depends on NFSD || NFS_V3 depends on FILE_LOCKING default y config NFS_ACL_SUPPORT tristate select FS_POSIX_ACL config NFS_COMMON bool depends on NFSD || NFS_FS || LOCKD default y config NFS_V4_2_SSC_HELPER bool default y if NFS_V4_2 source "net/sunrpc/Kconfig" source "fs/ceph/Kconfig" source "fs/cifs/Kconfig" source "fs/ksmbd/Kconfig" config SMBFS_COMMON tristate default y if CIFS=y || SMB_SERVER=y default m if CIFS=m || SMB_SERVER=m source "fs/coda/Kconfig" source "fs/afs/Kconfig" source "fs/9p/Kconfig" endif # NETWORK_FILESYSTEMS source "fs/nls/Kconfig" source "fs/dlm/Kconfig" source "fs/unicode/Kconfig" config IO_WQ bool endmenu PK ! ��8�1 1 Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux filesystems. # # 14 Sep 2000, Christoph Hellwig <hch@infradead.org> # Rewritten to use lists instead of if-statements. # obj-y := open.o read_write.o file_table.o super.o \ char_dev.o stat.o exec.o pipe.o namei.o fcntl.o \ ioctl.o readdir.o select.o dcache.o inode.o \ attr.o bad_inode.o file.o filesystems.o namespace.o \ seq_file.o xattr.o libfs.o fs-writeback.o \ pnode.o splice.o sync.o utimes.o d_path.o \ stack.o fs_struct.o statfs.o fs_pin.o nsfs.o \ fs_types.o fs_context.o fs_parser.o fsopen.o init.o \ kernel_read_file.o remap_range.o ifeq ($(CONFIG_BLOCK),y) obj-y += buffer.o direct-io.o mpage.o else obj-y += no-block.o endif obj-$(CONFIG_PROC_FS) += proc_namespace.o obj-y += notify/ obj-$(CONFIG_EPOLL) += eventpoll.o obj-y += anon_inodes.o obj-$(CONFIG_SIGNALFD) += signalfd.o obj-$(CONFIG_TIMERFD) += timerfd.o obj-$(CONFIG_EVENTFD) += eventfd.o obj-$(CONFIG_USERFAULTFD) += userfaultfd.o obj-$(CONFIG_AIO) += aio.o obj-$(CONFIG_FS_DAX) += dax.o obj-$(CONFIG_FS_ENCRYPTION) += crypto/ obj-$(CONFIG_FS_VERITY) += verity/ obj-$(CONFIG_FILE_LOCKING) += locks.o obj-$(CONFIG_BINFMT_AOUT) += binfmt_aout.o obj-$(CONFIG_BINFMT_MISC) += binfmt_misc.o obj-$(CONFIG_BINFMT_SCRIPT) += binfmt_script.o obj-$(CONFIG_BINFMT_ELF) += binfmt_elf.o obj-$(CONFIG_COMPAT_BINFMT_ELF) += compat_binfmt_elf.o obj-$(CONFIG_BINFMT_ELF_FDPIC) += binfmt_elf_fdpic.o obj-$(CONFIG_BINFMT_FLAT) += binfmt_flat.o obj-$(CONFIG_FS_MBCACHE) += mbcache.o obj-$(CONFIG_FS_POSIX_ACL) += posix_acl.o obj-$(CONFIG_NFS_COMMON) += nfs_common/ obj-$(CONFIG_COREDUMP) += coredump.o obj-$(CONFIG_SYSCTL) += drop_caches.o obj-$(CONFIG_FHANDLE) += fhandle.o obj-y += iomap/ obj-y += quota/ obj-$(CONFIG_PROC_FS) += proc/ obj-$(CONFIG_KERNFS) += kernfs/ obj-$(CONFIG_SYSFS) += sysfs/ obj-$(CONFIG_CONFIGFS_FS) += configfs/ obj-y += devpts/ obj-$(CONFIG_DLM) += dlm/ # Do not add any filesystems before this line obj-$(CONFIG_NETFS_SUPPORT) += netfs/ obj-$(CONFIG_FSCACHE) += fscache/ obj-$(CONFIG_REISERFS_FS) += reiserfs/ obj-$(CONFIG_EXT4_FS) += ext4/ # We place ext4 before ext2 so that clean ext3 root fs's do NOT mount using the # ext2 driver, which doesn't know about journalling! Explicitly request ext2 # by giving the rootfstype= parameter. obj-$(CONFIG_EXT2_FS) += ext2/ obj-$(CONFIG_JBD2) += jbd2/ obj-$(CONFIG_CRAMFS) += cramfs/ obj-$(CONFIG_SQUASHFS) += squashfs/ obj-y += ramfs/ obj-$(CONFIG_HUGETLBFS) += hugetlbfs/ obj-$(CONFIG_CODA_FS) += coda/ obj-$(CONFIG_MINIX_FS) += minix/ obj-$(CONFIG_FAT_FS) += fat/ obj-$(CONFIG_EXFAT_FS) += exfat/ obj-$(CONFIG_BFS_FS) += bfs/ obj-$(CONFIG_ISO9660_FS) += isofs/ obj-$(CONFIG_HFSPLUS_FS) += hfsplus/ # Before hfs to find wrapped HFS+ obj-$(CONFIG_HFS_FS) += hfs/ obj-$(CONFIG_ECRYPT_FS) += ecryptfs/ obj-$(CONFIG_VXFS_FS) += freevxfs/ obj-$(CONFIG_NFS_FS) += nfs/ obj-$(CONFIG_EXPORTFS) += exportfs/ obj-$(CONFIG_NFSD) += nfsd/ obj-$(CONFIG_LOCKD) += lockd/ obj-$(CONFIG_NLS) += nls/ obj-$(CONFIG_UNICODE) += unicode/ obj-$(CONFIG_SYSV_FS) += sysv/ obj-$(CONFIG_SMBFS_COMMON) += smbfs_common/ obj-$(CONFIG_CIFS) += cifs/ obj-$(CONFIG_SMB_SERVER) += ksmbd/ obj-$(CONFIG_HPFS_FS) += hpfs/ obj-$(CONFIG_NTFS_FS) += ntfs/ obj-$(CONFIG_NTFS3_FS) += ntfs3/ obj-$(CONFIG_UFS_FS) += ufs/ obj-$(CONFIG_EFS_FS) += efs/ obj-$(CONFIG_JFFS2_FS) += jffs2/ obj-$(CONFIG_UBIFS_FS) += ubifs/ obj-$(CONFIG_AFFS_FS) += affs/ obj-$(CONFIG_ROMFS_FS) += romfs/ obj-$(CONFIG_QNX4FS_FS) += qnx4/ obj-$(CONFIG_QNX6FS_FS) += qnx6/ obj-$(CONFIG_AUTOFS_FS) += autofs/ obj-$(CONFIG_ADFS_FS) += adfs/ obj-$(CONFIG_FUSE_FS) += fuse/ obj-$(CONFIG_OVERLAY_FS) += overlayfs/ obj-$(CONFIG_ORANGEFS_FS) += orangefs/ obj-$(CONFIG_UDF_FS) += udf/ obj-$(CONFIG_SUN_OPENPROMFS) += openpromfs/ obj-$(CONFIG_OMFS_FS) += omfs/ obj-$(CONFIG_JFS_FS) += jfs/ obj-$(CONFIG_XFS_FS) += xfs/ obj-$(CONFIG_9P_FS) += 9p/ obj-$(CONFIG_AFS_FS) += afs/ obj-$(CONFIG_NILFS2_FS) += nilfs2/ obj-$(CONFIG_BEFS_FS) += befs/ obj-$(CONFIG_HOSTFS) += hostfs/ obj-$(CONFIG_CACHEFILES) += cachefiles/ obj-$(CONFIG_DEBUG_FS) += debugfs/ obj-$(CONFIG_TRACING) += tracefs/ obj-$(CONFIG_OCFS2_FS) += ocfs2/ obj-$(CONFIG_BTRFS_FS) += btrfs/ obj-$(CONFIG_GFS2_FS) += gfs2/ obj-$(CONFIG_F2FS_FS) += f2fs/ obj-$(CONFIG_CEPH_FS) += ceph/ obj-$(CONFIG_PSTORE) += pstore/ obj-$(CONFIG_EFIVAR_FS) += efivarfs/ obj-$(CONFIG_EROFS_FS) += erofs/ obj-$(CONFIG_VBOXSF_FS) += vboxsf/ obj-$(CONFIG_ZONEFS_FS) += zonefs/ obj-$(CONFIG_AUFS_FS) += aufs/ obj-$(CONFIG_SHIFT_FS) += shiftfs.o PK ! H 0� � ext2/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config EXT2_FS tristate "Second extended fs support" select FS_IOMAP help Ext2 is a standard Linux file system for hard disks. To compile this file system support as a module, choose M here: the module will be called ext2. If unsure, say Y. config EXT2_FS_XATTR bool "Ext2 extended attributes" depends on EXT2_FS help Extended attributes are name:value pairs associated with inodes by the kernel or by users (see the attr(5) manual page for details). If unsure, say N. config EXT2_FS_POSIX_ACL bool "Ext2 POSIX Access Control Lists" depends on EXT2_FS_XATTR select FS_POSIX_ACL help Posix Access Control Lists (ACLs) support permissions for users and groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N config EXT2_FS_SECURITY bool "Ext2 Security Labels" depends on EXT2_FS_XATTR help Security labels support alternative access control models implemented by security modules like SELinux. This option enables an extended attribute handler for file security labels in the ext2 filesystem. If you are not using a security module that requires using extended attributes for file security labels, say N. PK ! >��z z ext2/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the linux ext2-filesystem routines. # obj-$(CONFIG_EXT2_FS) += ext2.o ext2-y := balloc.o dir.o file.o ialloc.o inode.o \ ioctl.o namei.o super.o symlink.o ext2-$(CONFIG_EXT2_FS_XATTR) += xattr.o xattr_user.o xattr_trusted.o ext2-$(CONFIG_EXT2_FS_POSIX_ACL) += acl.o ext2-$(CONFIG_EXT2_FS_SECURITY) += xattr_security.o PK ! �S<� � nilfs2/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NILFS2_FS tristate "NILFS2 file system support" select CRC32 help NILFS2 is a log-structured file system (LFS) supporting continuous snapshotting. In addition to versioning capability of the entire file system, users can even restore files mistakenly overwritten or destroyed just a few seconds ago. Since this file system can keep consistency like conventional LFS, it achieves quick recovery after system crashes. NILFS2 creates a number of checkpoints every few seconds or per synchronous write basis (unless there is no change). Users can select significant versions among continuously created checkpoints, and can change them into snapshots which will be preserved for long periods until they are changed back to checkpoints. Each snapshot is mountable as a read-only file system concurrently with its writable mount, and this feature is convenient for online backup. Some features including atime, extended attributes, and POSIX ACLs, are not supported yet. To compile this file system support as a module, choose M here: the module will be called nilfs2. If unsure, say N. PK ! � �� nilfs2/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_NILFS2_FS) += nilfs2.o nilfs2-y := inode.o file.o dir.o super.o namei.o page.o mdt.o \ btnode.o bmap.o btree.o direct.o dat.o recovery.o \ the_nilfs.o segbuf.o segment.o cpfile.o sufile.o \ ifile.o alloc.o gcinode.o ioctl.o sysfs.o PK ! ����q q fuse/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config FUSE_FS tristate "FUSE (Filesystem in Userspace) support" select FS_POSIX_ACL help With FUSE it is possible to implement a fully functional filesystem in a userspace program. There's also a companion library: libfuse2. This library is available from the FUSE homepage: <https://github.com/libfuse/> although chances are your distribution already has that library installed if you've installed the "fuse" package itself. See <file:Documentation/filesystems/fuse.rst> for more information. See <file:Documentation/Changes> for needed library/utility version. If you want to develop a userspace FS, or if you want to use a filesystem based on FUSE, answer Y or M. config CUSE tristate "Character device in Userspace support" depends on FUSE_FS help This FUSE extension allows character devices to be implemented in userspace. If you want to develop or use a userspace character device based on CUSE, answer Y or M. config VIRTIO_FS tristate "Virtio Filesystem" depends on FUSE_FS select VIRTIO help The Virtio Filesystem allows guests to mount file systems from the host. If you want to share files between guests or with the host, answer Y or M. config FUSE_DAX bool "Virtio Filesystem Direct Host Memory Access support" default y select INTERVAL_TREE depends on VIRTIO_FS depends on FS_DAX depends on DAX_DRIVER help This allows bypassing guest page cache and allows mapping host page cache directly in guest address space. If you want to allow mounting a Virtio Filesystem with the "dax" option, answer Y. PK ! {�� @ @ fuse/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the FUSE filesystem. # obj-$(CONFIG_FUSE_FS) += fuse.o obj-$(CONFIG_CUSE) += cuse.o obj-$(CONFIG_VIRTIO_FS) += virtiofs.o fuse-y := dev.o dir.o file.o inode.o control.o xattr.o acl.o readdir.o ioctl.o fuse-$(CONFIG_FUSE_DAX) += dax.o virtiofs-y := virtio_fs.o PK ! �EĻ2 2 jffs2/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config JFFS2_FS tristate "Journalling Flash File System v2 (JFFS2) support" select CRC32 depends on MTD help JFFS2 is the second generation of the Journalling Flash File System for use on diskless embedded devices. It provides improved wear levelling, compression and support for hard links. You cannot use this on normal block devices, only on 'MTD' devices. Further information on the design and implementation of JFFS2 is available at <http://sources.redhat.com/jffs2/>. config JFFS2_FS_DEBUG int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)" depends on JFFS2_FS default "0" help This controls the amount of debugging messages produced by the JFFS2 code. Set it to zero for use in production systems. For evaluation, testing and debugging, it's advisable to set it to one. This will enable a few assertions and will print debugging messages at the KERN_DEBUG loglevel, where they won't normally be visible. Level 2 is unlikely to be useful - it enables extra debugging in certain areas which at one point needed debugging, but when the bugs were located and fixed, the detailed messages were relegated to level 2. If reporting bugs, please try to have available a full dump of the messages at debug level 1 while the misbehaviour was occurring. config JFFS2_FS_WRITEBUFFER bool "JFFS2 write-buffering support" depends on JFFS2_FS default y help This enables the write-buffering support in JFFS2. This functionality is required to support JFFS2 on the following types of flash devices: - NAND flash - NOR flash with transparent ECC - DataFlash config JFFS2_FS_WBUF_VERIFY bool "Verify JFFS2 write-buffer reads" depends on JFFS2_FS_WRITEBUFFER default n help This causes JFFS2 to read back every page written through the write-buffer, and check for errors. config JFFS2_SUMMARY bool "JFFS2 summary support" depends on JFFS2_FS default n help This feature makes it possible to use summary information for faster filesystem mount. The summary information can be inserted into a filesystem image by the utility 'sumtool'. If unsure, say 'N'. config JFFS2_FS_XATTR bool "JFFS2 XATTR support" depends on JFFS2_FS default n help Extended attributes are name:value pairs associated with inodes by the kernel or by users (see the attr(5) manual page for details). If unsure, say N. config JFFS2_FS_POSIX_ACL bool "JFFS2 POSIX Access Control Lists" depends on JFFS2_FS_XATTR default y select FS_POSIX_ACL help Posix Access Control Lists (ACLs) support permissions for users and groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N config JFFS2_FS_SECURITY bool "JFFS2 Security Labels" depends on JFFS2_FS_XATTR default y help Security labels support alternative access control models implemented by security modules like SELinux. This option enables an extended attribute handler for file security labels in the jffs2 filesystem. If you are not using a security module that requires using extended attributes for file security labels, say N. config JFFS2_COMPRESSION_OPTIONS bool "Advanced compression options for JFFS2" depends on JFFS2_FS default n help Enabling this option allows you to explicitly choose which compression modules, if any, are enabled in JFFS2. Removing compressors can mean you cannot read existing file systems, and enabling experimental compressors can mean that you write a file system which cannot be read by a standard kernel. If unsure, you should _definitely_ say 'N'. config JFFS2_ZLIB bool "JFFS2 ZLIB compression support" if JFFS2_COMPRESSION_OPTIONS select ZLIB_INFLATE select ZLIB_DEFLATE depends on JFFS2_FS default y help Zlib is designed to be a free, general-purpose, legally unencumbered, lossless data-compression library for use on virtually any computer hardware and operating system. See <http://www.gzip.org/zlib/> for further information. Say 'Y' if unsure. config JFFS2_LZO bool "JFFS2 LZO compression support" if JFFS2_COMPRESSION_OPTIONS select LZO_COMPRESS select LZO_DECOMPRESS depends on JFFS2_FS default n help minilzo-based compression. Generally works better than Zlib. This feature was added in July, 2007. Say 'N' if you need compatibility with older bootloaders or kernels. config JFFS2_RTIME bool "JFFS2 RTIME compression support" if JFFS2_COMPRESSION_OPTIONS depends on JFFS2_FS default y help Rtime does manage to recompress already-compressed data. Say 'Y' if unsure. config JFFS2_RUBIN bool "JFFS2 RUBIN compression support" if JFFS2_COMPRESSION_OPTIONS depends on JFFS2_FS default n help RUBINMIPS and DYNRUBIN compressors. Say 'N' if unsure. choice prompt "JFFS2 default compression mode" if JFFS2_COMPRESSION_OPTIONS default JFFS2_CMODE_PRIORITY depends on JFFS2_FS help You can set here the default compression mode of JFFS2 from the available compression modes. Don't touch if unsure. config JFFS2_CMODE_NONE bool "no compression" help Uses no compression. config JFFS2_CMODE_PRIORITY bool "priority" help Tries the compressors in a predefined order and chooses the first successful one. config JFFS2_CMODE_SIZE bool "size" help Tries all compressors and chooses the one which has the smallest result. config JFFS2_CMODE_FAVOURLZO bool "Favour LZO" help Tries all compressors and chooses the one which has the smallest result but gives some preference to LZO (which has faster decompression) at the expense of size. endchoice PK ! ��+ jffs2/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux Journalling Flash File System v2 (JFFS2) # # obj-$(CONFIG_JFFS2_FS) += jffs2.o jffs2-y := compr.o dir.o file.o ioctl.o nodelist.o malloc.o jffs2-y += read.o nodemgmt.o readinode.o write.o scan.o gc.o jffs2-y += symlink.o build.o erase.o background.o fs.o writev.o jffs2-y += super.o debug.o jffs2-$(CONFIG_JFFS2_FS_WRITEBUFFER) += wbuf.o jffs2-$(CONFIG_JFFS2_FS_XATTR) += xattr.o xattr_trusted.o xattr_user.o jffs2-$(CONFIG_JFFS2_FS_SECURITY) += security.o jffs2-$(CONFIG_JFFS2_FS_POSIX_ACL) += acl.o jffs2-$(CONFIG_JFFS2_RUBIN) += compr_rubin.o jffs2-$(CONFIG_JFFS2_RTIME) += compr_rtime.o jffs2-$(CONFIG_JFFS2_ZLIB) += compr_zlib.o jffs2-$(CONFIG_JFFS2_LZO) += compr_lzo.o jffs2-$(CONFIG_JFFS2_SUMMARY) += summary.o PK ! �^NwQ Q unicode/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # UTF-8 normalization # config UNICODE bool "UTF-8 normalization and casefolding support" help Say Y here to enable UTF-8 NFD normalization and NFD+CF casefolding support. config UNICODE_NORMALIZATION_SELFTEST tristate "Test UTF-8 normalization support" depends on UNICODE default n PK ! :Y!. . unicode/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_UNICODE) += unicode.o obj-$(CONFIG_UNICODE_NORMALIZATION_SELFTEST) += utf8-selftest.o unicode-y := utf8-norm.o utf8-core.o $(obj)/utf8-norm.o: $(obj)/utf8data.h # In the normal build, the checked-in utf8data.h is just shipped. # # To generate utf8data.h from UCD, put *.txt files in this directory # and pass REGENERATE_UTF8DATA=1 from the command line. ifdef REGENERATE_UTF8DATA quiet_cmd_utf8data = GEN $@ cmd_utf8data = $< \ -a $(srctree)/$(src)/DerivedAge.txt \ -c $(srctree)/$(src)/DerivedCombiningClass.txt \ -p $(srctree)/$(src)/DerivedCoreProperties.txt \ -d $(srctree)/$(src)/UnicodeData.txt \ -f $(srctree)/$(src)/CaseFolding.txt \ -n $(srctree)/$(src)/NormalizationCorrections.txt \ -t $(srctree)/$(src)/NormalizationTest.txt \ -o $@ $(obj)/utf8data.h: $(obj)/mkutf8data $(filter %.txt, $(cmd_utf8data)) FORCE $(call if_changed,utf8data) else $(obj)/utf8data.h: $(src)/utf8data.h_shipped FORCE $(call if_changed,shipped) endif targets += utf8data.h hostprogs += mkutf8data PK ! �8� � openpromfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Linux Sun Openprom filesystem routines. # obj-$(CONFIG_SUN_OPENPROMFS) += openpromfs.o openpromfs-objs := inode.o PK ! ٶj�: : f2fs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config F2FS_FS tristate "F2FS filesystem support" depends on BLOCK select NLS select CRYPTO select CRYPTO_CRC32 select F2FS_FS_XATTR if FS_ENCRYPTION select FS_ENCRYPTION_ALGS if FS_ENCRYPTION select LZ4_COMPRESS if F2FS_FS_LZ4 select LZ4_DECOMPRESS if F2FS_FS_LZ4 select LZ4HC_COMPRESS if F2FS_FS_LZ4HC select LZO_COMPRESS if F2FS_FS_LZO select LZO_DECOMPRESS if F2FS_FS_LZO select ZSTD_COMPRESS if F2FS_FS_ZSTD select ZSTD_DECOMPRESS if F2FS_FS_ZSTD 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 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 filesystem 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 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 groups beyond the owner/group/world scheme. If you don't know what Access Control Lists are, say N config F2FS_FS_SECURITY bool "F2FS Security Labels" depends on F2FS_FS_XATTR help Security labels provide an access control facility to support Linux Security Models (LSMs) accepted by AppArmor, SELinux, Smack and TOMOYO Linux. This option enables an extended attribute handler for file security labels in the f2fs filesystem, so that it requires enabling the extended attribute support in advance. In particular you need this option if you use the setcap command to assign initial process capabi- lities to executables (the security.* extended attributes). If you are not using a security module, say N. config F2FS_CHECK_FS bool "F2FS consistency checking feature" depends on F2FS_FS help Enables BUG_ONs which check the filesystem consistency in runtime. If you want to improve the performance, say N. config F2FS_FAULT_INJECTION bool "F2FS fault injection facility" depends on F2FS_FS help Test F2FS to inject faults such as ENOMEM, ENOSPC, and so on. If unsure, say N. config F2FS_FS_COMPRESSION bool "F2FS compression feature" depends on F2FS_FS help Enable filesystem-level compression on f2fs regular files, multiple back-end compression algorithms are supported. config F2FS_FS_LZO bool "LZO compression support" depends on F2FS_FS_COMPRESSION default y help Support LZO compress algorithm, if unsure, say Y. config F2FS_FS_LZORLE bool "LZO-RLE compression support" depends on F2FS_FS_LZO default y help Support LZO-RLE compress algorithm, if unsure, say Y. config F2FS_FS_LZ4 bool "LZ4 compression support" depends on F2FS_FS_COMPRESSION default y help Support LZ4 compress algorithm, if unsure, say Y. config F2FS_FS_LZ4HC bool "LZ4HC compression support" depends on F2FS_FS_LZ4 default y help Support LZ4HC compress algorithm, LZ4HC has compatible on-disk layout with LZ4, if unsure, say Y. config F2FS_FS_ZSTD bool "ZSTD compression support" depends on F2FS_FS_COMPRESSION default y help Support ZSTD compress algorithm, if unsure, say Y. config F2FS_IOSTAT bool "F2FS IO statistics information" depends on F2FS_FS default y help Support getting IO statistics through sysfs and printing out periodic IO statistics tracepoint events. You have to turn on "iostat_enable" sysfs node to enable this feature. PK ! �Z=�� � f2fs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_F2FS_FS) += f2fs.o f2fs-y := dir.o file.o inode.o namei.o hash.o super.o inline.o f2fs-y += checkpoint.o gc.o data.o node.o segment.o recovery.o f2fs-y += shrinker.o extent_cache.o sysfs.o f2fs-$(CONFIG_F2FS_STAT_FS) += debug.o f2fs-$(CONFIG_F2FS_FS_XATTR) += xattr.o f2fs-$(CONFIG_F2FS_FS_POSIX_ACL) += acl.o f2fs-$(CONFIG_FS_VERITY) += verity.o f2fs-$(CONFIG_F2FS_FS_COMPRESSION) += compress.o f2fs-$(CONFIG_F2FS_IOSTAT) += iostat.o PK ! �k�q` ` quota/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Quota configuration # config QUOTA bool "Quota support" select QUOTACTL select SRCU help If you say Y here, you will be able to set per user limits for disk usage (also called disk quotas). Currently, it works for the ext2, ext3, ext4, jfs, ocfs2 and reiserfs file systems. Note that gfs2 and xfs use their own quota system. Ext3, ext4 and reiserfs also support journaled quotas for which you don't need to run quotacheck(8) after an unclean shutdown. For further details, read the Quota mini-HOWTO, available from <https://www.tldp.org/docs.html#howto>, or the documentation provided with the quota tools. Probably the quota support is only useful for multi user systems. If unsure, say N. config QUOTA_NETLINK_INTERFACE bool "Report quota messages through netlink interface" depends on QUOTACTL && NET help If you say Y here, quota warnings (about exceeding softlimit, reaching hardlimit, etc.) will be reported through netlink interface. If unsure, say Y. config PRINT_QUOTA_WARNING bool "Print quota warnings to console (OBSOLETE)" depends on QUOTA default y help If you say Y here, quota warnings (about exceeding softlimit, reaching hardlimit, etc.) will be printed to the process' controlling terminal. Note that this behavior is currently deprecated and may go away in future. Please use notification via netlink socket instead. config QUOTA_DEBUG bool "Additional quota sanity checks" depends on QUOTA default n help If you say Y here, quota subsystem will perform some additional sanity checks of quota internal structures. If unsure, say N. # Generic support for tree structured quota files. Selected when needed. config QUOTA_TREE tristate config QFMT_V1 tristate "Old quota format support" depends on QUOTA help This quota format was (is) used by kernels earlier than 2.4.22. If you have quota working and you don't want to convert to new quota format say Y here. config QFMT_V2 tristate "Quota format vfsv0 and vfsv1 support" depends on QUOTA select QUOTA_TREE help This config option enables kernel support for vfsv0 and vfsv1 quota formats. Both these formats support 32-bit UIDs/GIDs and vfsv1 format also supports 64-bit inode and block quota limits. If you need this functionality say Y here. config QUOTACTL bool default n PK ! 3� quota/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_QUOTA) += dquot.o obj-$(CONFIG_QFMT_V1) += quota_v1.o obj-$(CONFIG_QFMT_V2) += quota_v2.o obj-$(CONFIG_QUOTA_TREE) += quota_tree.o obj-$(CONFIG_QUOTACTL) += quota.o kqid.o obj-$(CONFIG_QUOTA_NETLINK_INTERFACE) += netlink.o PK ! 3Q�m m debugfs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only debugfs-objs := inode.o file.o obj-$(CONFIG_DEBUG_FS) += debugfs.o PK ! ��Z�l �l nls/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Native language support configuration # menuconfig NLS tristate "Native language support" help The base Native Language Support. A number of filesystems depend on it (e.g. FAT, JOLIET, NT, BEOS filesystems), as well as the ability of some filesystems to use native languages (NCP, SMB). If unsure, say Y. To compile this code as a module, choose M here: the module will be called nls_base. if NLS config NLS_DEFAULT string "Default NLS Option" default "iso8859-1" help The default NLS used when mounting file system. Note, that this is the NLS used by your console, not the NLS used by a specific file system (if different) to store data (filenames) on a disk. Currently, the valid values are: big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861, cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936, cp949, cp950, cp1251, cp1255, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3, iso8859-4, iso8859-5, iso8859-6, iso8859-7, iso8859-8, iso8859-9, iso8859-13, iso8859-14, iso8859-15, koi8-r, koi8-ru, koi8-u, sjis, tis-620, macroman, utf8. If you specify a wrong value, it will use the built-in NLS; compatible with iso8859-1. If unsure, specify it as "iso8859-1". config NLS_CODEPAGE_437 tristate "Codepage 437 (United States, Canada)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage that is used in the United States and parts of Canada. This is recommended. config NLS_CODEPAGE_737 tristate "Codepage 737 (Greek)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage that is used for Greek. If unsure, say N. config NLS_CODEPAGE_775 tristate "Codepage 775 (Baltic Rim)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage that is used for the Baltic Rim Languages (Latvian and Lithuanian). If unsure, say N. config NLS_CODEPAGE_850 tristate "Codepage 850 (Europe)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage that is used for much of Europe -- United Kingdom, Germany, Spain, Italy, and [add more countries here]. It has some characters useful to many European languages that are not part of the US codepage 437. If unsure, say Y. config NLS_CODEPAGE_852 tristate "Codepage 852 (Central/Eastern Europe)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Latin 2 codepage used by DOS for much of Central and Eastern Europe. It has all the required characters for these languages: Albanian, Croatian, Czech, English, Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin transcription), Slovak, Slovenian, and Sorbian. config NLS_CODEPAGE_855 tristate "Codepage 855 (Cyrillic)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Cyrillic. config NLS_CODEPAGE_857 tristate "Codepage 857 (Turkish)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Turkish. config NLS_CODEPAGE_860 tristate "Codepage 860 (Portuguese)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Portuguese. config NLS_CODEPAGE_861 tristate "Codepage 861 (Icelandic)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Icelandic. config NLS_CODEPAGE_862 tristate "Codepage 862 (Hebrew)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Hebrew. config NLS_CODEPAGE_863 tristate "Codepage 863 (Canadian French)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Canadian French. config NLS_CODEPAGE_864 tristate "Codepage 864 (Arabic)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Arabic. config NLS_CODEPAGE_865 tristate "Codepage 865 (Norwegian, Danish)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for the Nordic European countries. config NLS_CODEPAGE_866 tristate "Codepage 866 (Cyrillic/Russian)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Cyrillic/Russian. config NLS_CODEPAGE_869 tristate "Codepage 869 (Greek)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Greek. config NLS_CODEPAGE_936 tristate "Simplified Chinese charset (CP936, GB2312)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Simplified Chinese(GBK). config NLS_CODEPAGE_950 tristate "Traditional Chinese charset (Big5)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Traditional Chinese(Big5). config NLS_CODEPAGE_932 tristate "Japanese charsets (Shift-JIS, EUC-JP)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Shift-JIS or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or NLS Default value during kernel configuration, instead of 'cp932'. config NLS_CODEPAGE_949 tristate "Korean charset (CP949, EUC-KR)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for UHC. config NLS_CODEPAGE_874 tristate "Thai charset (CP874, TIS-620)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Thai. config NLS_ISO8859_8 tristate "Hebrew charsets (ISO-8859-8, CP1255)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for ISO8859-8, the Hebrew character set. config NLS_CODEPAGE_1250 tristate "Windows CP1250 (Slavic/Central European Languages)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CDROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Windows CP-1250 character set, which works for most Latin-written Slavic and Central European languages: Czech, German, Hungarian, Polish, Rumanian, Croatian, Slovak, Slovene. config NLS_CODEPAGE_1251 tristate "Windows CP1251 (Bulgarian, Belarusian)" help The Microsoft FAT file system family can deal with filenames in native language character sets. These character sets are stored in so-called DOS codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on DOS/Windows partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the DOS codepage for Russian and Bulgarian and Belarusian. config NLS_ASCII tristate "ASCII (United States)" help An ASCII NLS module is needed if you want to override the DEFAULT NLS with this very basic charset and don't want any non-ASCII characters to be translated. config NLS_ISO8859_1 tristate "NLS ISO 8859-1 (Latin 1; Western European Languages)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 1 character set, which covers most West European languages such as Albanian, Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German, Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish, and Swedish. It is also the default for the US. If unsure, say Y. config NLS_ISO8859_2 tristate "NLS ISO 8859-2 (Latin 2; Slavic/Central European Languages)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 2 character set, which works for most Latin-written Slavic and Central European languages: Czech, German, Hungarian, Polish, Rumanian, Croatian, Slovak, Slovene. config NLS_ISO8859_3 tristate "NLS ISO 8859-3 (Latin 3; Esperanto, Galician, Maltese, Turkish)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 3 character set, which is popular with authors of Esperanto, Galician, Maltese, and Turkish. config NLS_ISO8859_4 tristate "NLS ISO 8859-4 (Latin 4; old Baltic charset)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 4 character set which introduces letters for Estonian, Latvian, and Lithuanian. It is an incomplete predecessor of Latin 7. config NLS_ISO8859_5 tristate "NLS ISO 8859-5 (Cyrillic)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for ISO8859-5, a Cyrillic character set with which you can type Bulgarian, Belarusian, Macedonian, Russian, Serbian, and Ukrainian. Note that the charset KOI8-R is preferred in Russia. config NLS_ISO8859_6 tristate "NLS ISO 8859-6 (Arabic)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for ISO8859-6, the Arabic character set. config NLS_ISO8859_7 tristate "NLS ISO 8859-7 (Modern Greek)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for ISO8859-7, the Modern Greek character set. config NLS_ISO8859_9 tristate "NLS ISO 8859-9 (Latin 5; Turkish)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 5 character set, and it replaces the rarely needed Icelandic letters in Latin 1 with the Turkish ones. Useful in Turkey. config NLS_ISO8859_13 tristate "NLS ISO 8859-13 (Latin 7; Baltic)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 7 character set, which supports modern Baltic languages including Latvian and Lithuanian. config NLS_ISO8859_14 tristate "NLS ISO 8859-14 (Latin 8; Celtic)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 8 character set, which adds the last accented vowels for Welsh (aka Cymraeg) (and Manx Gaelic) that were missing in Latin 1. <http://linux.speech.cymru.org/> has further information. config NLS_ISO8859_15 tristate "NLS ISO 8859-15 (Latin 9; Western European Languages with Euro)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the Latin 9 character set, which covers most West European languages such as Albanian, Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish, French, German, Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish, and Swedish. Latin 9 is an update to Latin 1 (ISO 8859-1) that removes a handful of rarely used characters and instead adds support for Estonian, corrects the support for French and Finnish, and adds the new Euro character. If unsure, say Y. config NLS_KOI8_R tristate "NLS KOI8-R (Russian)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the preferred Russian character set. config NLS_KOI8_U tristate "NLS KOI8-U/RU (Ukrainian, Belarusian)" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the preferred Ukrainian (koi8-u) and Belarusian (koi8-ru) character sets. config NLS_MAC_ROMAN tristate "Codepage macroman" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for much of Europe -- United Kingdom, Germany, Spain, Italy, and [add more countries here]. If unsure, say Y. config NLS_MAC_CELTIC tristate "Codepage macceltic" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for Celtic. If unsure, say Y. config NLS_MAC_CENTEURO tristate "Codepage maccenteuro" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for Central Europe. If unsure, say Y. config NLS_MAC_CROATIAN tristate "Codepage maccroatian" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for Croatian. If unsure, say Y. config NLS_MAC_CYRILLIC tristate "Codepage maccyrillic" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for Cyrillic. If unsure, say Y. config NLS_MAC_GAELIC tristate "Codepage macgaelic" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for Gaelic. If unsure, say Y. config NLS_MAC_GREEK tristate "Codepage macgreek" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for Greek. If unsure, say Y. config NLS_MAC_ICELAND tristate "Codepage maciceland" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for Iceland. If unsure, say Y. config NLS_MAC_INUIT tristate "Codepage macinuit" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for Inuit. If unsure, say Y. config NLS_MAC_ROMANIAN tristate "Codepage macromanian" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for Romanian. If unsure, say Y. config NLS_MAC_TURKISH tristate "Codepage macturkish" help The Apple HFS file system family can deal with filenames in native language character sets. These character sets are stored in so-called MAC codepages. You need to include the appropriate codepage if you want to be able to read/write these filenames on Mac partitions correctly. This does apply to the filenames only, not to the file contents. You can include several codepages; say Y here if you want to include the Mac codepage that is used for Turkish. If unsure, say Y. config NLS_UTF8 tristate "NLS UTF-8" help If you want to display filenames with native language characters from the Microsoft FAT file system family or from JOLIET CD-ROMs correctly on the screen, you need to include the appropriate input/output character sets. Say Y here for the UTF-8 encoding of the Unicode/ISO9646 universal character set. endif # NLS PK ! �q(r r nls/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for native language support # obj-$(CONFIG_NLS) += nls_base.o obj-$(CONFIG_NLS_CODEPAGE_437) += nls_cp437.o obj-$(CONFIG_NLS_CODEPAGE_737) += nls_cp737.o obj-$(CONFIG_NLS_CODEPAGE_775) += nls_cp775.o obj-$(CONFIG_NLS_CODEPAGE_850) += nls_cp850.o obj-$(CONFIG_NLS_CODEPAGE_852) += nls_cp852.o obj-$(CONFIG_NLS_CODEPAGE_855) += nls_cp855.o obj-$(CONFIG_NLS_CODEPAGE_857) += nls_cp857.o obj-$(CONFIG_NLS_CODEPAGE_860) += nls_cp860.o obj-$(CONFIG_NLS_CODEPAGE_861) += nls_cp861.o obj-$(CONFIG_NLS_CODEPAGE_862) += nls_cp862.o obj-$(CONFIG_NLS_CODEPAGE_863) += nls_cp863.o obj-$(CONFIG_NLS_CODEPAGE_864) += nls_cp864.o obj-$(CONFIG_NLS_CODEPAGE_865) += nls_cp865.o obj-$(CONFIG_NLS_CODEPAGE_866) += nls_cp866.o obj-$(CONFIG_NLS_CODEPAGE_869) += nls_cp869.o obj-$(CONFIG_NLS_CODEPAGE_874) += nls_cp874.o obj-$(CONFIG_NLS_CODEPAGE_932) += nls_cp932.o nls_euc-jp.o obj-$(CONFIG_NLS_CODEPAGE_936) += nls_cp936.o obj-$(CONFIG_NLS_CODEPAGE_949) += nls_cp949.o obj-$(CONFIG_NLS_CODEPAGE_950) += nls_cp950.o obj-$(CONFIG_NLS_CODEPAGE_1250) += nls_cp1250.o obj-$(CONFIG_NLS_CODEPAGE_1251) += nls_cp1251.o obj-$(CONFIG_NLS_ASCII) += nls_ascii.o obj-$(CONFIG_NLS_ISO8859_1) += nls_iso8859-1.o obj-$(CONFIG_NLS_ISO8859_2) += nls_iso8859-2.o obj-$(CONFIG_NLS_ISO8859_3) += nls_iso8859-3.o obj-$(CONFIG_NLS_ISO8859_4) += nls_iso8859-4.o obj-$(CONFIG_NLS_ISO8859_5) += nls_iso8859-5.o obj-$(CONFIG_NLS_ISO8859_6) += nls_iso8859-6.o obj-$(CONFIG_NLS_ISO8859_7) += nls_iso8859-7.o obj-$(CONFIG_NLS_ISO8859_8) += nls_cp1255.o obj-$(CONFIG_NLS_ISO8859_9) += nls_iso8859-9.o obj-$(CONFIG_NLS_ISO8859_13) += nls_iso8859-13.o obj-$(CONFIG_NLS_ISO8859_14) += nls_iso8859-14.o obj-$(CONFIG_NLS_ISO8859_15) += nls_iso8859-15.o obj-$(CONFIG_NLS_KOI8_R) += nls_koi8-r.o obj-$(CONFIG_NLS_KOI8_U) += nls_koi8-u.o nls_koi8-ru.o obj-$(CONFIG_NLS_UTF8) += nls_utf8.o obj-$(CONFIG_NLS_MAC_CELTIC) += mac-celtic.o obj-$(CONFIG_NLS_MAC_CENTEURO) += mac-centeuro.o obj-$(CONFIG_NLS_MAC_CROATIAN) += mac-croatian.o obj-$(CONFIG_NLS_MAC_CYRILLIC) += mac-cyrillic.o obj-$(CONFIG_NLS_MAC_GAELIC) += mac-gaelic.o obj-$(CONFIG_NLS_MAC_GREEK) += mac-greek.o obj-$(CONFIG_NLS_MAC_ICELAND) += mac-iceland.o obj-$(CONFIG_NLS_MAC_INUIT) += mac-inuit.o obj-$(CONFIG_NLS_MAC_ROMANIAN) += mac-romanian.o obj-$(CONFIG_NLS_MAC_ROMAN) += mac-roman.o obj-$(CONFIG_NLS_MAC_TURKISH) += mac-turkish.o PK ! �~3�_ _ nfsd/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NFSD tristate "NFS server support" depends on INET depends on FILE_LOCKING depends on FSNOTIFY select CRC32 select LOCKD select SUNRPC select EXPORTFS select NFS_ACL_SUPPORT if NFSD_V2_ACL select NFS_ACL_SUPPORT if NFSD_V3_ACL depends on MULTIUSER help Choose Y here if you want to allow other computers to access files residing on this system using Sun's Network File System protocol. To compile the NFS server support as a module, choose M here: the module will be called nfsd. You may choose to use a user-space NFS server instead, in which case you can choose N here. To export local file systems using NFS, you also need to install user space programs which can be found in the Linux nfs-utils package, available from http://linux-nfs.org/. More detail about the Linux NFS server implementation is available via the exports(5) man page. Below you can choose which versions of the NFS protocol are available to clients mounting the NFS server on this system. Support for NFS version 3 (RFC 1813) is always available when CONFIG_NFSD is selected. If unsure, say N. config NFSD_V2 bool "NFS server support for NFS version 2 (DEPRECATED)" depends on NFSD default n help NFSv2 (RFC 1094) was the first publicly-released version of NFS. Unless you are hosting ancient (1990's era) NFS clients, you don't need this. If unsure, say N. config NFSD_V2_ACL bool "NFS server support for the NFSv2 ACL protocol extension" depends on NFSD_V2 config NFSD_V3_ACL bool "NFS server support for the NFSv3 ACL protocol extension" depends on NFSD help Solaris NFS servers support an auxiliary NFSv3 ACL protocol that never became an official part of the NFS version 3 protocol. This protocol extension allows applications on NFS clients to manipulate POSIX Access Control Lists on files residing on NFS servers. NFS servers enforce POSIX ACLs on local files whether this protocol is available or not. This option enables support in your system's NFS server for the NFSv3 ACL protocol extension allowing NFS clients to manipulate POSIX ACLs on files exported by your system's NFS server. NFS clients which support the Solaris NFSv3 ACL protocol can then access and modify ACLs on your NFS server. To store ACLs on your NFS server, you also need to enable ACL- related CONFIG options for your local file systems of choice. If unsure, say N. config NFSD_V4 bool "NFS server support for NFS version 4" depends on NFSD && PROC_FS select FS_POSIX_ACL select SUNRPC_GSS select CRYPTO select CRYPTO_MD5 select CRYPTO_SHA256 select GRACE_PERIOD select NFS_V4_2_SSC_HELPER if NFS_V4_2 help This option enables support in your system's NFS server for version 4 of the NFS protocol (RFC 3530). To export files using NFSv4, you need to install additional user space programs which can be found in the Linux nfs-utils package, available from http://linux-nfs.org/. If unsure, say N. config NFSD_PNFS bool config NFSD_BLOCKLAYOUT bool "NFSv4.1 server support for pNFS block layouts" depends on NFSD_V4 && BLOCK select NFSD_PNFS select EXPORTFS_BLOCK_OPS help This option enables support for the exporting pNFS block layouts in the kernel's NFS server. The pNFS block layout enables NFS clients to directly perform I/O to block devices accessible to both the server and the clients. See RFC 5663 for more details. If unsure, say N. config NFSD_SCSILAYOUT bool "NFSv4.1 server support for pNFS SCSI layouts" depends on NFSD_V4 && BLOCK select NFSD_PNFS select EXPORTFS_BLOCK_OPS select SCSI_COMMON help This option enables support for the exporting pNFS SCSI layouts in the kernel's NFS server. The pNFS SCSI layout enables NFS clients to directly perform I/O to SCSI devices accessible to both the server and the clients. See draft-ietf-nfsv4-scsi-layout for more details. If unsure, say N. config NFSD_FLEXFILELAYOUT bool "NFSv4.1 server support for pNFS Flex File layouts" depends on NFSD_V4 select NFSD_PNFS help This option enables support for the exporting pNFS Flex File layouts in the kernel's NFS server. The pNFS Flex File layout enables NFS clients to directly perform I/O to NFSv3 devices accessible to both the server and the clients. See draft-ietf-nfsv4-flex-files for more details. Warning, this server implements the bare minimum functionality to be a flex file server - it is for testing the client, not for use in production. If unsure, say N. config NFSD_V4_2_INTER_SSC bool "NFSv4.2 inter server to server COPY" depends on NFSD_V4 && NFS_V4_2 help This option enables support for NFSv4.2 inter server to server copy where the destination server calls the NFSv4.2 client to read the data to copy from the source server. If unsure, say N. config NFSD_V4_SECURITY_LABEL bool "Provide Security Label support for NFSv4 server" depends on NFSD_V4 && SECURITY help Say Y here if you want enable fine-grained security label attribute support for NFS version 4. Security labels allow security modules like SELinux and Smack to label files to facilitate enforcement of their policies. Without this an NFSv4 mount will have the same label on each file. If you do not wish to enable fine-grained security labels SELinux or Smack policies on NFSv4 files, say N. PK ! ���t t nfsd/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux nfs server # ccflags-y += -I$(src) # needed for trace events obj-$(CONFIG_NFSD) += nfsd.o # this one should be compiled first, as the tracing macros can easily blow up nfsd-y += trace.o nfsd-y += nfssvc.o nfsctl.o nfsfh.o vfs.o \ export.o auth.o lockd.o nfscache.o \ stats.o filecache.o nfs3proc.o nfs3xdr.o nfsd-$(CONFIG_NFSD_V2) += nfsproc.o nfsxdr.o nfsd-$(CONFIG_NFSD_V2_ACL) += nfs2acl.o nfsd-$(CONFIG_NFSD_V3_ACL) += nfs3acl.o nfsd-$(CONFIG_NFSD_V4) += nfs4proc.o nfs4xdr.o nfs4state.o nfs4idmap.o \ nfs4acl.o nfs4callback.o nfs4recover.o nfsd-$(CONFIG_NFSD_PNFS) += nfs4layouts.o nfsd-$(CONFIG_NFSD_BLOCKLAYOUT) += blocklayout.o blocklayoutxdr.o nfsd-$(CONFIG_NFSD_SCSILAYOUT) += blocklayout.o blocklayoutxdr.o nfsd-$(CONFIG_NFSD_FLEXFILELAYOUT) += flexfilelayout.o flexfilelayoutxdr.o PK ! �k��, , Kconfig.binfmtnu �[��� # SPDX-License-Identifier: GPL-2.0-only menu "Executable file formats" config BINFMT_ELF bool "Kernel support for ELF binaries" depends on MMU select ELFCORE default y help ELF (Executable and Linkable Format) is a format for libraries and executables used across different architectures and operating systems. Saying Y here will enable your kernel to run ELF binaries and enlarge it by about 13 KB. ELF support under Linux has now all but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC) because it is portable (this does *not* mean that you will be able to run executables from different architectures or operating systems however) and makes building run-time libraries very easy. Many new executables are distributed solely in ELF format. You definitely want to say Y here. Information about ELF is contained in the ELF HOWTO available from <http://www.tldp.org/docs.html#howto>. If you find that after upgrading from Linux kernel 1.2 and saying Y here, you still can't run any ELF binaries (they just crash), then you'll have to install the newest ELF runtime libraries, including ld.so (check the file <file:Documentation/Changes> for location and latest version). config COMPAT_BINFMT_ELF def_bool y depends on COMPAT && BINFMT_ELF select ELFCORE config ARCH_BINFMT_ELF_STATE bool config ARCH_HAVE_ELF_PROT bool config ARCH_USE_GNU_PROPERTY bool config BINFMT_ELF_FDPIC bool "Kernel support for FDPIC ELF binaries" default y if !BINFMT_ELF depends on (ARM || (SUPERH && !MMU)) select ELFCORE help ELF FDPIC binaries are based on ELF, but allow the individual load segments of a binary to be located in memory independently of each other. This makes this format ideal for use in environments where no MMU is available as it still permits text segments to be shared, even if data segments are not. It is also possible to run FDPIC ELF binaries on MMU linux also. config ELFCORE bool help This option enables kernel/elfcore.o. config CORE_DUMP_DEFAULT_ELF_HEADERS bool "Write ELF core dumps with partial segments" default y depends on BINFMT_ELF && ELF_CORE help ELF core dump files describe each memory mapping of the crashed process, and can contain or omit the memory contents of each one. The contents of an unmodified text mapping are omitted by default. For an unmodified text mapping of an ELF object, including just the first page of the file in a core dump makes it possible to identify the build ID bits in the file, without paying the i/o cost and disk space to dump all the text. However, versions of GDB before 6.7 are confused by ELF core dump files in this format. The core dump behavior can be controlled per process using the /proc/PID/coredump_filter pseudo-file; this setting is inherited. See Documentation/filesystems/proc.rst for details. This config option changes the default setting of coredump_filter seen at boot time. If unsure, say Y. config BINFMT_SCRIPT tristate "Kernel support for scripts starting with #!" default y help Say Y here if you want to execute interpreted scripts starting with #! followed by the path to an interpreter. You can build this support as a module; however, until that module gets loaded, you cannot run scripts. Thus, if you want to load this module from an initramfs, the portion of the initramfs before loading this module must consist of compiled binaries only. Most systems will not boot if you say M or N here. If unsure, say Y. config ARCH_HAS_BINFMT_FLAT bool config BINFMT_FLAT bool "Kernel support for flat binaries" depends on ARCH_HAS_BINFMT_FLAT help Support uClinux FLAT format binaries. config BINFMT_FLAT_ARGVP_ENVP_ON_STACK bool config BINFMT_FLAT_OLD_ALWAYS_RAM bool config BINFMT_FLAT_NO_DATA_START_OFFSET bool config BINFMT_FLAT_OLD bool "Enable support for very old legacy flat binaries" depends on BINFMT_FLAT help Support decade old uClinux FLAT format binaries. Unless you know you have some of those say N here. config BINFMT_ZFLAT bool "Enable ZFLAT support" depends on BINFMT_FLAT select ZLIB_INFLATE help Support FLAT format compressed binaries config BINFMT_SHARED_FLAT bool "Enable shared FLAT support" depends on BINFMT_FLAT help Support FLAT shared libraries config HAVE_AOUT def_bool n config BINFMT_AOUT tristate "Kernel support for a.out and ECOFF binaries" depends on HAVE_AOUT help A.out (Assembler.OUTput) is a set of formats for libraries and executables used in the earliest versions of UNIX. Linux used the a.out formats QMAGIC and ZMAGIC until they were replaced with the ELF format. The conversion to ELF started in 1995. This option is primarily provided for historical interest and for the benefit of those who need to run binaries from that era. Most people should answer N here. If you think you may have occasional use for this format, enable module support above and answer M here to compile this support as a module called binfmt_aout. If any crucial components of your system (such as /sbin/init or /lib/ld.so) are still in a.out format, you will have to say Y here. config OSF4_COMPAT bool "OSF/1 v4 readv/writev compatibility" depends on ALPHA && BINFMT_AOUT help Say Y if you are using OSF/1 binaries (like Netscape and Acrobat) with v4 shared libraries freely available from Compaq. If you're going to use shared libraries from Tru64 version 5.0 or later, say N. config BINFMT_MISC tristate "Kernel support for MISC binaries" help If you say Y here, it will be possible to plug wrapper-driven binary formats into the kernel. You will like this especially when you use programs that need an interpreter to run like Java, Python, .NET or Emacs-Lisp. It's also useful if you often run DOS executables under the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from <http://www.tldp.org/docs.html#howto>). Once you have registered such a binary class with the kernel, you can start one of those programs simply by typing in its name at a shell prompt; Linux will automatically feed it to the correct interpreter. You can do other nice things, too. Read the file <file:Documentation/admin-guide/binfmt-misc.rst> to learn how to use this feature, <file:Documentation/admin-guide/java.rst> for information about how to include Java support. and <file:Documentation/admin-guide/mono.rst> for information about how to include Mono-based .NET support. To use binfmt_misc, you will need to mount it: mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc You may say M here for module support and later load the module when you have use for it; the module is called binfmt_misc. If you don't know what to answer at this point, say Y. config COREDUMP bool "Enable core dump support" if EXPERT default y help This option enables support for performing core dumps. You almost certainly want to say Y here. Not necessary on systems that never need debugging or only ever run flawless code. endmenu PK ! A��� � notify/inotify/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config INOTIFY_USER bool "Inotify support for userspace" select FSNOTIFY default y help Say Y here to enable inotify support for userspace, including the associated system calls. Inotify allows monitoring of both files and directories via a single open fd. Events are read from the file descriptor, which is also select()- and poll()-able. Inotify fixes numerous shortcomings in dnotify and introduces several new features including multiple file events, one-shot support, and unmount notification. For more information, see <file:Documentation/filesystems/inotify.rst> If unsure, say Y. PK ! v���h h notify/inotify/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_INOTIFY_USER) += inotify_fsnotify.o inotify_user.o PK ! �H��� � notify/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config FSNOTIFY def_bool n select SRCU source "fs/notify/dnotify/Kconfig" source "fs/notify/inotify/Kconfig" source "fs/notify/fanotify/Kconfig" PK ! �54� � notify/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_FSNOTIFY) += fsnotify.o notification.o group.o mark.o \ fdinfo.o obj-y += dnotify/ obj-y += inotify/ obj-y += fanotify/ PK ! ��� � notify/fanotify/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config FANOTIFY bool "Filesystem wide access notification" select FSNOTIFY select EXPORTFS default n help Say Y here to enable fanotify support. fanotify is a file access notification system which differs from inotify in that it sends an open file descriptor to the userspace listener along with the event. If unsure, say Y. config FANOTIFY_ACCESS_PERMISSIONS bool "fanotify permissions checking" depends on FANOTIFY depends on SECURITY default n help Say Y here is you want fanotify listeners to be able to make permissions decisions concerning filesystem events. This is used by some fanotify listeners which need to scan files before allowing the system access to use those files. This is used by some anti-malware vendors and by some hierarchical storage management systems. If unsure, say N. PK ! H*M^ ^ notify/fanotify/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_FANOTIFY) += fanotify.o fanotify_user.o PK ! .�E2c c notify/dnotify/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config DNOTIFY bool "Dnotify support" select FSNOTIFY default y help Dnotify is a directory-based per-fd file change notification system that uses signals to communicate events to user-space. There exist superior alternatives, but some applications may still rely on dnotify. If unsure, say Y. PK ! �Y@�L L notify/dnotify/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_DNOTIFY) += dnotify.o PK ! i� S. . qnx4/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config QNX4FS_FS tristate "QNX4 file system support (read only)" depends on BLOCK help This is the file system used by the real-time operating systems QNX 4 and QNX 6 (the latter is also called QNX RTP). Further information is available at <http://www.qnx.com/>. Say Y if you intend to mount QNX hard disks or floppies. To compile this file system support as a module, choose M here: the module will be called qnx4. If you don't know whether you need it, then you don't need it: answer N. PK ! ש�� � qnx4/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux qnx4-filesystem routines. # obj-$(CONFIG_QNX4FS_FS) += qnx4.o qnx4-objs := inode.o dir.o namei.o bitmap.o PK ! v � efs/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config EFS_FS tristate "EFS file system support (read only)" depends on BLOCK help EFS is an older file system used for non-ISO9660 CD-ROMs and hard disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer uses the XFS file system for hard disk partitions however). This implementation only offers read-only access. If you don't know what all this is about, it's safe to say N. For more information about EFS see its home page at <http://aeschi.ch.eu.org/efs/>. To compile the EFS file system support as a module, choose M here: the module will be called efs. PK ! 4K�.� � efs/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the linux efs-filesystem routines. # obj-$(CONFIG_EFS_FS) += efs.o efs-objs := super.o inode.o namei.o dir.o file.o symlink.o PK ! Zal�( ( ext4/sda/fc_infonu ��6�$ fc stats: 0 commits 0 ineligible 0 numblks 0us avg_commit_time Ineligible reasons: "Extended attributes changed": 0 "Cross rename": 0 "Journal flag changed": 0 "Insufficient memory": 0 "Swap boot": 0 "Resize": 0 "Dir renamed": 0 "Falloc range op": 0 "Data journalling": 0 "Encrypted filename": 0 PK ! ��Hu4 4 ext4/sda/optionsnu ��6�$ rw bsddf nogrpid block_validity dioread_nolock nodiscard delalloc nowarn_on_error nojournal_checksum barrier auto_da_alloc user_xattr acl noquota resuid=0 resgid=0 errors=remount-ro commit=5 min_batch_time=0 max_batch_time=15000 stripe=0 data=ordered inode_readahead_blks=32 init_itable=10 max_dir_size_kb=0 PK ! ��U_ _ ext4/sda/mb_statsnu ��6�$ mballoc: mb stats collection turned off. To enable, please write "1" to sysfs file mb_stats. PK ! � �'�W �W ext4/sda/mb_groupsnu ��6�$ #group: free frags first [ 2^0 2^1 2^2 2^3 2^4 2^5 2^6 2^7 2^8 2^9 2^10 2^11 2^12 2^13 ] #0 : 6507 111 11162 [ 99 50 25 18 15 12 9 16 5 3 0 0 0 0 ] #1 : 14362 231 764 [ 202 150 119 105 94 85 44 21 11 0 0 0 0 0 ] #2 : 3582 241 228 [ 204 115 61 55 20 11 6 1 1 0 1 0 0 0 ] #3 : 6828 95 504 [ 72 64 67 61 39 24 20 15 5 0 0 0 0 0 ] #4 : 10083 103 45 [ 69 51 50 66 38 14 11 8 9 4 0 1 0 0 ] #5 : 12914 193 504 [ 120 107 107 111 98 43 36 27 6 2 0 0 0 0 ] #6 : 10591 149 208 [ 87 94 93 83 80 44 27 12 13 0 0 0 0 0 ] #7 : 9034 129 546 [ 86 86 68 59 56 33 19 10 6 2 1 0 0 0 ] #8 : 11042 135 101 [ 84 77 85 62 89 43 20 14 16 0 0 0 0 0 ] #9 : 11973 185 501 [ 133 108 82 78 105 57 20 28 9 0 0 0 0 0 ] #10 : 1431 49 88 [ 33 23 20 11 8 5 2 2 2 0 0 0 0 0 ] #11 : 7066 158 24 [ 86 72 65 42 38 8 8 14 10 1 0 0 0 0 ] #12 : 6323 150 0 [ 113 91 65 59 37 31 16 3 5 2 0 0 0 0 ] #13 : 4135 210 2144 [ 145 137 103 85 56 6 6 5 2 0 0 0 0 0 ] #14 : 10543 165 0 [ 143 90 57 55 47 25 19 9 6 2 1 1 0 0 ] #15 : 8760 104 1120 [ 60 66 58 54 44 39 17 12 1 2 2 0 0 0 ] #16 : 13838 123 8167 [ 98 48 37 29 31 21 19 11 9 6 4 0 0 0 ] #17 : 4862 129 16442 [ 100 81 70 44 26 19 14 8 2 1 0 0 0 0 ] #18 : 12932 524 256 [ 450 285 196 193 147 84 41 11 2 0 0 0 0 0 ] #19 : 2627 178 24 [ 107 90 81 82 37 6 1 0 2 0 0 0 0 0 ] #20 : 3407 195 58 [ 125 115 109 117 39 3 3 0 3 0 0 0 0 0 ] #21 : 3718 68 112 [ 46 34 35 23 29 14 5 0 2 1 1 0 0 0 ] #22 : 9969 168 17 [ 127 109 104 89 71 20 11 11 8 3 1 0 0 0 ] #23 : 7704 126 59 [ 100 80 65 68 67 36 15 11 4 2 0 0 0 0 ] #24 : 13381 73 0 [ 55 33 21 17 19 18 12 9 8 10 3 0 0 0 ] #25 : 4477 96 640 [ 71 63 54 40 48 25 10 10 1 0 0 0 0 0 ] #26 : 8927 166 48 [ 111 80 62 51 32 12 11 18 12 2 0 0 0 0 ] #27 : 15 1 2269 [ 1 1 1 1 0 0 0 0 0 0 0 0 0 0 ] #28 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #29 : 5659 191 0 [ 125 105 103 82 44 5 5 6 5 2 0 0 0 0 ] #30 : 1064 60 352 [ 34 35 36 34 12 5 1 1 0 0 0 0 0 0 ] #31 : 2134 183 568 [ 106 100 89 100 38 0 1 0 0 0 0 0 0 0 ] #32 : 4425 14 9000 [ 13 8 7 10 10 7 7 5 5 3 0 0 0 0 ] #33 : 8941 173 2 [ 147 97 76 59 31 27 27 21 8 0 0 0 0 0 ] #34 : 5298 161 56 [ 108 99 118 59 33 14 10 9 5 0 0 0 0 0 ] #35 : 282 20 3099 [ 14 10 10 12 5 1 0 0 0 0 0 0 0 0 ] #36 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #37 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #38 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #39 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #40 : 210 21 851 [ 18 18 21 5 0 1 0 0 0 0 0 0 0 0 ] #41 : 242 13 64 [ 8 5 6 5 2 2 1 0 0 0 0 0 0 0 ] #42 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #43 : 1 1 3643 [ 1 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #44 : 98 3 3925 [ 2 2 3 2 0 2 0 0 0 0 0 0 0 0 ] #45 : 428 28 698 [ 24 18 20 14 5 3 0 0 0 0 0 0 0 0 ] #46 : 892 48 1696 [ 20 20 28 22 22 6 0 0 0 0 0 0 0 0 ] #47 : 268 12 1172 [ 6 7 8 3 2 1 0 1 0 0 0 0 0 0 ] #48 : 8877 19 16384 [ 13 14 11 9 7 9 8 9 6 2 4 0 0 0 ] #49 : 326 67 620 [ 58 24 23 8 4 0 0 0 0 0 0 0 0 0 ] #50 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #51 : 4632 90 2661 [ 76 54 48 36 32 8 8 7 5 1 0 0 0 0 ] #52 : 2727 101 3055 [ 75 54 46 51 44 9 1 1 3 0 0 0 0 0 ] #53 : 4086 123 2560 [ 108 71 65 47 46 29 14 5 0 0 0 0 0 0 ] #54 : 4561 64 1328 [ 43 35 54 41 16 8 9 4 3 1 1 0 0 0 ] #55 : 6632 103 1552 [ 64 54 47 62 53 20 11 4 4 2 1 0 0 0 ] #56 : 1838 131 2063 [ 96 85 85 90 32 0 0 0 0 0 0 0 0 0 ] #57 : 6112 160 1939 [ 98 97 77 67 51 28 25 7 3 0 0 0 0 0 ] #58 : 2488 176 2850 [ 170 75 52 27 15 13 5 2 2 0 0 0 0 0 ] #59 : 696 75 3067 [ 66 41 23 9 2 5 3 0 0 0 0 0 0 0 ] #60 : 704 12 826 [ 8 8 8 7 7 7 0 0 1 0 0 0 0 0 ] #61 : 9089 36 0 [ 31 27 23 18 20 18 11 8 4 2 2 1 0 0 ] #62 : 350 12 0 [ 8 11 4 6 2 3 2 0 0 0 0 0 0 0 ] #63 : 8155 67 24 [ 37 39 34 44 32 30 25 19 6 1 0 0 0 0 ] #64 : 3434 9 15616 [ 4 5 5 1 4 4 2 6 5 2 0 0 0 0 ] #65 : 294 102 1092 [ 102 36 14 6 1 0 0 0 0 0 0 0 0 0 ] #66 : 2829 125 383 [ 121 38 10 12 8 2 2 3 3 0 1 0 0 0 ] #67 : 104 7 17 [ 6 5 6 4 2 0 0 0 0 0 0 0 0 0 ] #68 : 225 8 2174 [ 7 5 2 3 1 1 2 0 0 0 0 0 0 0 ] #69 : 220 15 499 [ 12 10 9 9 5 0 0 0 0 0 0 0 0 0 ] #70 : 880 28 96 [ 18 15 24 12 6 9 4 0 0 0 0 0 0 0 ] #71 : 270 24 19 [ 16 19 12 15 3 0 0 0 0 0 0 0 0 0 ] #72 : 171 11 761 [ 5 5 11 6 0 0 1 0 0 0 0 0 0 0 ] #73 : 241 9 72 [ 3 3 4 5 5 1 1 0 0 0 0 0 0 0 ] #74 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #75 : 300 11 0 [ 8 6 6 8 4 0 2 0 0 0 0 0 0 0 ] #76 : 96 12 88 [ 6 7 5 7 0 0 0 0 0 0 0 0 0 0 ] #77 : 195 15 120 [ 9 9 6 8 3 1 0 0 0 0 0 0 0 0 ] #78 : 414 34 149 [ 14 18 21 19 2 1 1 0 0 0 0 0 0 0 ] #79 : 185 14 503 [ 7 9 6 7 5 0 0 0 0 0 0 0 0 0 ] #80 : 755 4 15243 [ 1 1 2 1 0 1 1 3 1 0 0 0 0 0 ] #81 : 45 4 1162 [ 5 2 1 2 1 0 0 0 0 0 0 0 0 0 ] #82 : 1123 28 180 [ 21 21 17 14 9 5 5 0 1 0 0 0 0 0 ] #83 : 103 4 198 [ 3 4 1 3 2 1 0 0 0 0 0 0 0 0 ] #84 : 558 52 93 [ 50 20 7 9 5 1 0 0 1 0 0 0 0 0 ] #85 : 106 14 120 [ 14 12 5 6 0 0 0 0 0 0 0 0 0 0 ] #86 : 256 23 1027 [ 24 8 8 7 6 1 0 0 0 0 0 0 0 0 ] #87 : 185 31 0 [ 27 17 11 4 3 0 0 0 0 0 0 0 0 0 ] #88 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #89 : 207 11 508 [ 5 5 6 7 3 0 1 0 0 0 0 0 0 0 ] #90 : 166 19 1371 [ 18 10 12 8 1 0 0 0 0 0 0 0 0 0 ] #91 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #92 : 220 19 232 [ 8 18 12 12 2 0 0 0 0 0 0 0 0 0 ] #93 : 200 11 416 [ 6 9 8 4 5 1 0 0 0 0 0 0 0 0 ] #94 : 76 9 64 [ 2 7 9 3 0 0 0 0 0 0 0 0 0 0 ] #95 : 483 60 576 [ 47 24 21 26 6 0 0 0 0 0 0 0 0 0 ] #96 : 2597 10 9079 [ 9 6 4 4 4 5 4 4 2 0 1 0 0 0 ] #97 : 234 7 1681 [ 4 3 6 7 1 2 1 0 0 0 0 0 0 0 ] #98 : 348 18 791 [ 14 9 9 11 4 2 1 0 0 0 0 0 0 0 ] #99 : 116 8 3136 [ 4 6 3 7 2 0 0 0 0 0 0 0 0 0 ] #100 : 2040 41 2303 [ 34 29 23 24 14 11 9 4 0 0 0 0 0 0 ] #101 : 629 34 2153 [ 13 16 22 18 16 3 0 0 0 0 0 0 0 0 ] #102 : 3270 70 4216 [ 30 32 42 46 21 14 9 6 2 0 0 0 0 0 ] #103 : 113 4 1909 [ 3 3 2 2 1 0 1 0 0 0 0 0 0 0 ] #104 : 2038 37 92 [ 22 18 17 17 9 7 2 2 2 1 0 0 0 0 ] #105 : 4684 33 27 [ 20 22 21 17 15 14 6 6 4 1 1 0 0 0 ] #106 : 14421 276 25 [ 185 106 102 124 29 34 23 19 4 4 2 1 0 0 ] #107 : 9466 149 19 [ 106 80 72 86 46 8 5 8 11 0 1 1 0 0 ] #108 : 6351 162 50 [ 115 94 86 85 34 10 11 9 5 0 1 0 0 0 ] #109 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #110 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #111 : 2073 6 1024 [ 1 4 4 2 3 4 1 2 2 2 0 0 0 0 ] #112 : 18541 8 8191 [ 5 6 7 4 6 6 4 4 4 4 6 2 1 0 ] #113 : 4118 103 8318 [ 90 80 57 55 16 6 3 8 4 1 0 0 0 0 ] #114 : 176 10 8952 [ 8 4 2 5 1 1 1 0 0 0 0 0 0 0 ] #115 : 1764 93 35 [ 56 50 48 55 33 14 0 0 0 0 0 0 0 0 ] #116 : 14749 80 0 [ 63 53 41 46 40 43 38 21 13 5 1 0 0 0 ] #117 : 7673 88 2048 [ 61 38 30 35 32 17 11 10 2 3 2 0 0 0 ] #118 : 3450 36 958 [ 30 18 20 15 21 13 8 1 3 0 1 0 0 0 ] #119 : 1741 74 4208 [ 43 53 48 43 34 16 0 0 0 0 0 0 0 0 ] #120 : 4259 116 51 [ 73 69 68 64 42 5 2 0 1 0 0 1 0 0 ] #121 : 7665 111 181 [ 67 61 73 74 32 8 15 12 9 2 0 0 0 0 ] #122 : 5957 144 41 [ 95 85 67 86 50 15 2 8 3 1 1 0 0 0 ] #123 : 6333 173 169 [ 103 109 87 104 52 5 2 5 4 2 1 0 0 0 ] #124 : 4113 35 224 [ 21 24 19 20 22 14 11 2 2 1 1 0 0 0 ] #125 : 5295 84 778 [ 49 47 48 40 24 31 9 7 3 2 0 0 0 0 ] #126 : 3863 77 72 [ 65 31 28 27 21 12 4 5 3 0 1 0 0 0 ] #127 : 14491 186 64 [ 101 107 152 144 28 26 22 20 24 2 0 0 0 0 ] #128 : 17345 5 8160 [ 3 3 4 3 5 6 6 2 2 1 3 2 0 1 ] #129 : 5390 96 21 [ 48 57 53 59 40 14 6 8 4 0 1 0 0 0 ] #130 : 6074 98 2048 [ 56 49 48 50 37 16 16 11 7 0 0 0 0 0 ] #131 : 8393 57 0 [ 17 24 30 38 28 13 12 7 3 1 4 0 0 0 ] #132 : 14989 121 0 [ 75 61 64 63 63 29 21 14 9 5 2 1 0 0 ] #133 : 3228 21 1536 [ 6 7 4 5 5 0 8 10 3 1 0 0 0 0 ] #134 : 4332 93 82 [ 48 56 59 68 38 15 10 9 2 0 0 0 0 0 ] #135 : 10499 87 896 [ 39 48 49 51 26 14 5 11 12 4 2 0 0 0 ] #136 : 8780 159 2096 [ 146 89 58 40 30 14 11 5 2 2 2 1 0 0 ] #137 : 3744 98 36 [ 74 33 21 28 20 13 10 1 1 1 1 0 0 0 ] #138 : 7215 115 0 [ 83 74 64 57 42 39 30 17 1 0 0 0 0 0 ] #139 : 4409 81 2048 [ 67 31 20 17 4 7 3 6 3 0 0 1 0 0 ] #140 : 5153 88 256 [ 73 58 51 39 34 26 14 5 2 0 1 0 0 0 ] #141 : 8778 61 32 [ 26 30 33 32 29 13 16 8 7 7 0 0 0 0 ] #142 : 3778 38 4703 [ 28 29 25 23 23 13 11 5 5 0 0 0 0 0 ] #143 : 7481 102 2560 [ 79 75 49 50 40 22 9 11 5 2 1 0 0 0 ] #144 : 19565 5 8160 [ 3 5 4 6 6 6 2 3 5 4 3 2 2 0 ] #145 : 11224 59 0 [ 44 28 39 29 27 22 12 7 5 3 1 2 0 0 ] #146 : 10548 70 0 [ 46 43 42 41 32 26 20 13 12 5 0 0 0 0 ] #147 : 9567 67 251 [ 49 53 49 46 39 27 13 15 14 2 0 0 0 0 ] #148 : 11475 116 53 [ 89 65 58 56 25 16 11 6 4 8 3 0 0 0 ] #149 : 12981 111 0 [ 85 62 59 41 39 30 16 9 7 7 3 0 0 0 ] #150 : 3157 10 184 [ 5 4 4 9 5 5 2 5 8 0 0 0 0 0 ] #151 : 4412 44 0 [ 28 16 12 8 7 7 7 11 4 0 1 0 0 0 ] #152 : 7615 85 0 [ 71 40 36 29 15 4 9 6 9 2 0 1 0 0 ] #153 : 9785 18 256 [ 5 4 3 4 4 6 8 6 6 1 2 2 0 0 ] #154 : 6763 115 420 [ 105 41 22 15 10 10 10 11 9 1 1 0 0 0 ] #155 : 11402 114 1024 [ 56 51 63 60 41 12 10 13 10 3 3 0 0 0 ] #156 : 10591 57 0 [ 49 41 37 35 33 25 22 11 5 7 1 0 0 0 ] #157 : 647 7 15952 [ 3 2 0 4 4 3 1 1 1 0 0 0 0 0 ] #158 : 7056 92 512 [ 68 50 34 26 19 11 12 14 7 1 1 0 0 0 ] #159 : 7812 64 245 [ 40 34 26 28 27 25 16 16 10 1 0 0 0 0 ] #160 : 10184 7 10207 [ 4 4 3 6 6 5 4 5 3 4 4 1 0 0 ] #161 : 7444 89 1187 [ 50 55 59 59 47 16 13 11 6 3 0 0 0 0 ] #162 : 6295 165 2048 [ 179 100 47 36 28 14 5 7 7 1 1 0 0 0 ] #163 : 8267 174 256 [ 89 101 86 72 79 31 21 15 6 0 0 0 0 0 ] #164 : 11904 130 0 [ 96 74 59 54 37 31 23 12 5 4 1 1 0 0 ] #165 : 2327 72 1119 [ 39 42 41 49 21 9 6 1 2 0 0 0 0 0 ] #166 : 9811 75 2121 [ 49 51 47 44 44 19 10 14 7 1 1 1 0 0 ] #167 : 6757 154 289 [ 103 105 91 76 56 27 24 9 4 0 0 0 0 0 ] #168 : 9700 158 0 [ 94 73 81 82 42 12 10 9 4 3 3 0 0 0 ] #169 : 5358 140 41 [ 92 89 82 105 33 4 1 1 2 1 2 0 0 0 ] #170 : 7296 125 2300 [ 76 64 67 75 55 5 5 4 5 0 3 0 0 0 ] #171 : 4099 24 0 [ 19 16 12 10 9 10 12 3 5 2 0 0 0 0 ] #172 : 1896 41 0 [ 34 21 19 8 7 9 8 4 1 0 0 0 0 0 ] #173 : 4967 56 6080 [ 31 30 31 28 29 23 16 6 2 0 1 0 0 0 ] #174 : 12112 29 3072 [ 8 6 7 8 6 8 12 13 12 4 2 1 0 0 ] #175 : 4663 7 3456 [ 1 3 2 1 0 1 2 1 1 2 3 0 0 0 ] #176 : 19418 6 9259 [ 6 4 5 5 5 2 6 5 3 4 3 4 1 0 ] #177 : 5930 60 1533 [ 46 42 30 30 18 13 16 9 4 1 1 0 0 0 ] #178 : 6904 93 426 [ 66 53 55 48 39 16 10 2 2 1 1 1 0 0 ] #179 : 4765 79 208 [ 73 42 34 35 22 16 16 6 4 1 0 0 0 0 ] #180 : 2796 59 6478 [ 32 30 28 32 28 9 3 5 3 0 0 0 0 0 ] #181 : 7036 41 1536 [ 26 23 19 27 13 14 10 4 3 4 2 0 0 0 ] #182 : 4767 74 392 [ 41 45 45 53 26 11 7 4 7 1 0 0 0 0 ] #183 : 7080 59 2048 [ 44 34 30 26 29 23 13 10 5 2 1 0 0 0 ] #184 : 6895 12 0 [ 5 5 4 4 5 3 6 5 6 8 0 0 0 0 ] #185 : 1415 53 127 [ 31 30 37 29 21 3 4 2 0 0 0 0 0 0 ] #186 : 7342 65 2304 [ 50 40 35 38 23 10 9 7 6 4 1 0 0 0 ] #187 : 6678 107 256 [ 66 58 62 69 40 12 9 10 9 1 0 0 0 0 ] #188 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #189 : 10 1 16374 [ 0 1 0 1 0 0 0 0 0 0 0 0 0 0 ] #190 : 0 0 32768 [ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ] #191 : 599 23 10386 [ 17 13 15 12 9 0 0 0 1 0 0 0 0 0 ] #192 : 14760 9 3379 [ 10 7 4 6 3 5 6 6 6 3 4 1 1 0 ] #193 : 126 6 9656 [ 4 3 3 1 2 2 0 0 0 0 0 0 0 0 ] #194 : 378 27 3056 [ 18 14 19 18 7 0 0 0 0 0 0 0 0 0 ] #195 : 6910 72 8192 [ 40 39 30 36 17 5 3 13 8 2 1 0 0 0 ] PK ! �ۤp� � ext4/sda/es_shrinker_infonu ��6�$ stats: 2423 objects 2420 reclaimable objects 7220644/5453375 cache hits/misses 570 inodes on list average: 36 us scan time 83 shrunk objects maximum: 9365 inode (1489 objects, 1489 reclaimable) 3253 us max scan time PK ! 1�� � ext4/sda/mb_structs_summarynu ��6�$ optimize_scan: 1 max_free_order_lists: list_order_0_groups: 1 list_order_1_groups: 0 list_order_2_groups: 0 list_order_3_groups: 5 list_order_4_groups: 14 list_order_5_groups: 13 list_order_6_groups: 15 list_order_7_groups: 5 list_order_8_groups: 33 list_order_9_groups: 29 list_order_10_groups: 45 list_order_11_groups: 17 list_order_12_groups: 4 list_order_13_groups: 1 fragment_size_tree: tree_min: 1 tree_max: 3913 tree_nodes: 182 PK ! ���zy y jbd2/sda-8/infonu ��6�$ 8493 transactions (8173 requested), each up to 4096 blocks average: 0ms waiting for transaction 0ms request delay 1244ms running transaction 0ms transaction was being locked 0ms flushing data (in ordered mode) 0ms logging transaction 693us average transaction commit time 35 handles per transaction 4 blocks per transaction 6 logged blocks per transaction PK ! 9��6T T romfs/Kconfignu �[��� PK ! ���� � � romfs/Makefilenu �[��� PK ! W�״ � � devpts/Makefilenu �[��� PK ! �� � � jbd2/Kconfignu �[��� PK ! i�=Z� � � jbd2/Makefilenu �[��� PK ! F�w�8 8 � xfs/Kconfignu �[��� PK ! j�b * xfs/Makefilenu �[��� PK ! ��n� � T9 afs/Kconfignu �[��� PK ! �mf�u u _> afs/Makefilenu �[��� PK ! pEc�} } A lockd/Makefilenu �[��� PK ! ��~)� � �B ceph/Kconfignu �[��� PK ! oy+�t t �H ceph/Makefilenu �[��� PK ! �!��� � �J fat/Kconfignu �[��� PK ! �@��R R �^ fat/Makefilenu �[��� PK ! ��Y?! ?! 8` pstore/Kconfignu �[��� PK ! � � �� pstore/Makefilenu �[��� PK ! Jz�+t t �� ntfs3/Kconfignu �[��� PK ! �� � � b� ntfs3/Makefilenu �[��� PK ! tpd+ + I� zonefs/Kconfignu �[��� PK ! �J Hv v �� zonefs/Makefilenu �[��� PK ! "\�Ac c g� cramfs/Kconfignu �[��� PK ! ��-�� � � cramfs/Makefilenu �[��� PK ! �g�m� � � freevxfs/Kconfignu �[��� PK ! ��(� � � freevxfs/Makefilenu �[��� PK ! \� �� � 4� configfs/Kconfignu �[��� PK ! �t�e� � [� configfs/Makefilenu �[��� PK ! ��H�u u `� crypto/Kconfignu �[��� PK ! �!- O O � crypto/Makefilenu �[��� PK ! w��� � �� affs/Kconfignu �[��� PK ! ��N�� � ů affs/Makefilenu �[��� PK ! �1�� � ubifs/Kconfignu �[��� PK ! ��U� � )� ubifs/Makefilenu �[��� PK ! ��<A� � K� 9p/Kconfignu �[��� PK ! �H�� ]� 9p/Makefilenu �[��� PK ! W���� � �� udf/Kconfignu �[��� PK ! 8bi� �� udf/Makefilenu �[��� PK ! �r�� � �� overlayfs/Kconfignu �[��� PK ! �� � � �� overlayfs/Makefilenu �[��� PK ! {ڿ�� � �� ocfs2/dlm/Makefilenu �[��� PK ! J\�w w �� ocfs2/dlmfs/Makefilenu �[��� PK ! ��� � �� ocfs2/cluster/Makefilenu �[��� PK ! ��X�� � �� ocfs2/Kconfignu �[��� PK ! P�� �� ocfs2/Makefilenu �[��� PK ! Y���} } � verity/Kconfignu �[��� PK ! g2>�� � � verity/Makefilenu �[��� PK ! ��� J J �� aufs/Kconfignu �[��� PK ! r +�C C � aufs/Makefilenu �[��� PK ! 7�?K� � nfs/flexfilelayout/Makefilenu �[��� PK ! ���� � 4 nfs/blocklayout/Makefilenu �[��� PK ! 6gؓ� � Y nfs/Kconfignu �[��� PK ! �9�$9 9 ]7 nfs/Makefilenu �[��� PK ! �� � �< nfs/filelayout/Makefilenu �[��� PK ! X7`je e �= tracefs/Makefilenu �[��� PK ! w� �> ntfs/Kconfignu �[��� PK ! �=��� � �K ntfs/Makefilenu �[��� PK ! �K K �M ecryptfs/Kconfignu �[��� PK ! �XZ/ / tQ ecryptfs/Makefilenu �[��� PK ! bJT=o o �R erofs/Kconfignu �[��� PK ! kߤ� � �\ erofs/Makefilenu �[��� PK ! ̓e3� � �] btrfs/Kconfignu �[��� PK ! ߳u�� � �k btrfs/Makefilenu �[��� PK ! J(�u u �s kernfs/Kconfignu �[��� PK ! f�)d� � 4t kernfs/Makefilenu �[��� PK ! �<=� � �t hugetlbfs/Makefilenu �[��� PK ! �z��T T �u squashfs/Kconfignu �[��� PK ! bav�{ { k� squashfs/Makefilenu �[��� PK ! �)b_� � '� fscache/Kconfignu �[��� PK ! ��]< < #� fscache/Makefilenu �[��� PK ! ��� � �� exportfs/Makefilenu �[��� PK ! �ϳ�� � �� sysv/Kconfignu �[��� PK ! �ŀ@� � �� sysv/Makefilenu �[��� PK ! ��� �� ufs/Kconfignu �[��� PK ! jZ � ufs/Makefilenu �[��� PK ! ��� � @� ksmbd/Kconfignu �[��� PK ! �~� � k� ksmbd/Makefilenu �[��� PK ! _���O O =� netfs/Kconfignu �[��� PK ! <*m m � netfs/Makefilenu �[��� PK ! � .� � t� cachefiles/Kconfignu �[��� PK ! �}|� � �� cachefiles/Makefilenu �[��� PK ! 2&�� � �� autofs/Kconfignu �[��� PK ! �_V� � %� autofs/Makefilenu �[��� PK ! v� 9� coda/Kconfignu �[��� PK ! r�>0� � �� coda/Makefilenu �[��� PK ! ���� � F� orangefs/Kconfignu �[��� PK ! �Dk�d d j� orangefs/Makefilenu �[��� PK ! &�� � dlm/Kconfignu �[��� PK ! �$��z z [� dlm/Makefilenu �[��� PK ! "N�)b b � proc/Kconfignu �[��� PK ! �c�ͥ � �� proc/Makefilenu �[��� PK ! �&>� �� nfs_common/Makefilenu �[��� PK ! es� � �� hpfs/Kconfignu �[��� PK ! M��j� � �� hpfs/Makefilenu �[��� PK ! Ph)�� � � befs/Kconfignu �[��� PK ! ���� � � befs/Makefilenu �[��� PK ! ��\�| | ?� gfs2/Kconfignu �[��� PK ! �HW W �� gfs2/Makefilenu �[��� PK ! K�1�� � � reiserfs/Kconfignu �[��� PK ! ���ڽ � � reiserfs/Makefilenu �[��� PK ! ��'E= = � adfs/Kconfignu �[��� PK ! Wɏ� � - adfs/Makefilenu �[��� PK ! 5ѫ<� � / ramfs/Makefilenu �[��� PK ! DC�_ _ 9 iomap/Makefilenu �[��� PK ! ��5�� � � hostfs/Makefilenu �[��� PK ! � <n � ext4/Kconfignu �[��� PK ! }���� � $* ext4/Makefilenu �[��� PK ! �l5u u )- vboxsf/Kconfignu �[��� PK ! �Ɏ|� � �. vboxsf/Makefilenu �[��� PK ! ��[^� � �/ efivarfs/Kconfignu �[��� PK ! �x�� � v1 efivarfs/Makefilenu �[��� PK ! �&|' ' ]2 hfsplus/Kconfignu �[��� PK ! �nm m �4 hfsplus/Makefilenu �[��� PK ! �۩u p6 sysfs/Kconfignu �[��� PK ! )�T� � �: sysfs/Makefilenu �[��� PK ! �|�� � �; jfs/Kconfignu �[��� PK ! �oR� � �A jfs/Makefilenu �[��� PK ! �%�m� � �C exfat/Kconfignu �[��� PK ! ,�� � G exfat/Makefilenu �[��� PK ! H� TD D $H omfs/Kconfignu �[��� PK ! ^�+�r r �J omfs/Makefilenu �[��� PK ! |�!�A A SK minix/Kconfignu �[��� PK ! OG�� � �O minix/Makefilenu �[��� PK ! 0y�5� � �P smbfs_common/Makefilenu �[��� PK ! ���e e �Q qnx6/Kconfignu �[��� PK ! ��m;� � �U qnx6/Makefilenu �[��� PK ! �٪ư � �V bfs/Kconfignu �[��� PK ! �e (� � �Z bfs/Makefilenu �[��� PK ! �WWr� � ^[ hfs/Kconfignu �[��� PK ! �%# # {] hfs/Makefilenu �[��� PK ! �F�� � �^ cifs/Kconfignu �[��� PK ! E���H H �} cifs/Makefilenu �[��� PK ! ��t5� � Q� isofs/Kconfignu �[��� PK ! �X�3 3 �� isofs/Makefilenu �[��� PK ! �i#�( �( �� Kconfignu �[��� PK ! ��8�1 1 !� Makefilenu �[��� PK ! H 0� � �� ext2/Kconfignu �[��� PK ! >��z z �� ext2/Makefilenu �[��� PK ! �S<� � f� nilfs2/Kconfignu �[��� PK ! � �� I� nilfs2/Makefilenu �[��� PK ! ����q q �� fuse/Kconfignu �[��� PK ! {�� @ @ P� fuse/Makefilenu �[��� PK ! �EĻ2 2 �� jffs2/Kconfignu �[��� PK ! ��+ <� jffs2/Makefilenu �[��� PK ! �^NwQ Q �� unicode/Kconfignu �[��� PK ! :Y!. . � unicode/Makefilenu �[��� PK ! �8� � �� openpromfs/Makefilenu �[��� PK ! ٶj�: : ~� f2fs/Kconfignu �[��� PK ! �Z=�� � � f2fs/Makefilenu �[��� PK ! �k�q` ` quota/Kconfignu �[��� PK ! 3� � quota/Makefilenu �[��� PK ! 3Q�m m debugfs/Makefilenu �[��� PK ! ��Z�l �l � nls/Kconfignu �[��� PK ! �q(r r �� nls/Makefilenu �[��� PK ! �~3�_ _ k� nfsd/Kconfignu �[��� PK ! ���t t � nfsd/Makefilenu �[��� PK ! �k��, , �� Kconfig.binfmtnu �[��� PK ! A��� � !� notify/inotify/Kconfignu �[��� PK ! v���h h �� notify/inotify/Makefilenu �[��� PK ! �H��� � �� notify/Kconfignu �[��� PK ! �54� � �� notify/Makefilenu �[��� PK ! ��� � �� notify/fanotify/Kconfignu �[��� PK ! H*M^ ^ e� notify/fanotify/Makefilenu �[��� PK ! .�E2c c � notify/dnotify/Kconfignu �[��� PK ! �Y@�L L �� notify/dnotify/Makefilenu �[��� PK ! i� S. . G� qnx4/Kconfignu �[��� PK ! ש�� � �� qnx4/Makefilenu �[��� PK ! v � �� efs/Kconfignu �[��� PK ! 4K�.� � W� efs/Makefilenu �[��� PK ! Zal�( ( L� ext4/sda/fc_infonu ��6�$ PK ! ��Hu4 4 �� ext4/sda/optionsnu ��6�$ PK ! ��U_ _ (� ext4/sda/mb_statsnu ��6�$ PK ! � �'�W �W �� ext4/sda/mb_groupsnu ��6�$ PK ! �ۤp� � �6 ext4/sda/es_shrinker_infonu ��6�$ PK ! 1�� � �7 ext4/sda/mb_structs_summarynu ��6�$ PK ! ���zy y : jbd2/sda-8/infonu ��6�$ PK � � V5 �;
| ver. 1.1 | |
.
| PHP 8.4.18 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0.02 |
proxy
|
phpinfo
|
ÐаÑтройка