Файловый менеджер - Редактировать - /var/www/html/lib.zip
Ðазад
PK ! BGyX� � Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Copyright (C) 2004, 2007-2010, 2011-2012 Synopsys, Inc. (www.synopsys.com) # lib-y := strchr-700.o strcpy-700.o strlen.o memcmp.o lib-$(CONFIG_ISA_ARCOMPACT) += memcpy-700.o memset.o strcmp.o lib-$(CONFIG_ISA_ARCV2) += memset-archs.o strcmp-archs.o ifdef CONFIG_ARC_USE_UNALIGNED_MEM_ACCESS lib-$(CONFIG_ISA_ARCV2) +=memcpy-archs-unaligned.o else lib-$(CONFIG_ISA_ARCV2) +=memcpy-archs.o endif PK ! lͺ+�@ �@ Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Library configuration # config BINARY_PRINTF def_bool n menu "Library routines" config RAID6_PQ tristate config RAID6_PQ_BENCHMARK bool "Automatically choose fastest RAID6 PQ functions" depends on RAID6_PQ default y help Benchmark all available RAID6 PQ functions on init and choose the fastest one. config LINEAR_RANGES tristate config PACKING bool "Generic bitfield packing and unpacking" default n help This option provides the packing() helper function, which permits converting bitfields between a CPU-usable representation and a memory representation that can have any combination of these quirks: - Is little endian (bytes are reversed within a 32-bit group) - The least-significant 32-bit word comes first (within a 64-bit group) - The most significant bit of a byte is at its right (bit 0 of a register description is numerically 2^7). Drivers may use these helpers to match the bit indices as described in the data sheets of the peripherals they are in control of. When in doubt, say N. config BITREVERSE tristate config HAVE_ARCH_BITREVERSE bool default n help This option enables the use of hardware bit-reversal instructions on architectures which support such operations. config ARCH_HAS_STRNCPY_FROM_USER bool config ARCH_HAS_STRNLEN_USER bool config GENERIC_STRNCPY_FROM_USER def_bool !ARCH_HAS_STRNCPY_FROM_USER config GENERIC_STRNLEN_USER def_bool !ARCH_HAS_STRNLEN_USER config GENERIC_NET_UTILS bool config GENERIC_FIND_FIRST_BIT bool source "lib/math/Kconfig" config NO_GENERIC_PCI_IOPORT_MAP bool config GENERIC_PCI_IOMAP bool config GENERIC_IOMAP bool select GENERIC_PCI_IOMAP config STMP_DEVICE bool config ARCH_USE_CMPXCHG_LOCKREF bool config ARCH_HAS_FAST_MULTIPLIER bool config ARCH_USE_SYM_ANNOTATIONS bool config INDIRECT_PIO bool "Access I/O in non-MMIO mode" depends on ARM64 help On some platforms where no separate I/O space exists, there are I/O hosts which can not be accessed in MMIO mode. Using the logical PIO mechanism, the host-local I/O resource can be mapped into system logic PIO space shared with MMIO hosts, such as PCI/PCIe, then the system can access the I/O devices with the mapped-logic PIO through I/O accessors. This way has relatively little I/O performance cost. Please make sure your devices really need this configure item enabled. When in doubt, say N. config INDIRECT_IOMEM bool help This is selected by other options/architectures to provide the emulated iomem accessors. config INDIRECT_IOMEM_FALLBACK bool depends on INDIRECT_IOMEM help If INDIRECT_IOMEM is selected, this enables falling back to plain mmio accesses when the IO memory address is not a registered emulated region. source "lib/crypto/Kconfig" config LIB_MEMNEQ bool config CRC_CCITT tristate "CRC-CCITT functions" help This option is provided for the case where no in-kernel-tree modules require CRC-CCITT functions, but a module built outside the kernel tree does. Such modules that use library CRC-CCITT functions require M here. config CRC16 tristate "CRC16 functions" help This option is provided for the case where no in-kernel-tree modules require CRC16 functions, but a module built outside the kernel tree does. Such modules that use library CRC16 functions require M here. config CRC_T10DIF tristate "CRC calculation for the T10 Data Integrity Field" select CRYPTO select CRYPTO_CRCT10DIF help This option is only needed if a module that's not in the kernel tree needs to calculate CRC checks for use with the SCSI data integrity subsystem. config CRC_ITU_T tristate "CRC ITU-T V.41 functions" help This option is provided for the case where no in-kernel-tree modules require CRC ITU-T V.41 functions, but a module built outside the kernel tree does. Such modules that use library CRC ITU-T V.41 functions require M here. config CRC32 tristate "CRC32/CRC32c functions" default y select BITREVERSE help This option is provided for the case where no in-kernel-tree modules require CRC32/CRC32c functions, but a module built outside the kernel tree does. Such modules that use library CRC32/CRC32c functions require M here. config CRC32_SELFTEST tristate "CRC32 perform self test on init" depends on CRC32 help This option enables the CRC32 library functions to perform a self test on initialization. The self test computes crc32_le and crc32_be over byte strings with random alignment and length and computes the total elapsed time and number of bytes processed. choice prompt "CRC32 implementation" depends on CRC32 default CRC32_SLICEBY8 help This option allows a kernel builder to override the default choice of CRC32 algorithm. Choose the default ("slice by 8") unless you know that you need one of the others. config CRC32_SLICEBY8 bool "Slice by 8 bytes" help Calculate checksum 8 bytes at a time with a clever slicing algorithm. This is the fastest algorithm, but comes with a 8KiB lookup table. Most modern processors have enough cache to hold this table without thrashing the cache. This is the default implementation choice. Choose this one unless you have a good reason not to. config CRC32_SLICEBY4 bool "Slice by 4 bytes" help Calculate checksum 4 bytes at a time with a clever slicing algorithm. This is a bit slower than slice by 8, but has a smaller 4KiB lookup table. Only choose this option if you know what you are doing. config CRC32_SARWATE bool "Sarwate's Algorithm (one byte at a time)" help Calculate checksum a byte at a time using Sarwate's algorithm. This is not particularly fast, but has a small 256 byte lookup table. Only choose this option if you know what you are doing. config CRC32_BIT bool "Classic Algorithm (one bit at a time)" help Calculate checksum one bit at a time. This is VERY slow, but has no lookup table. This is provided as a debugging option. Only choose this option if you are debugging crc32. endchoice config CRC64 tristate "CRC64 functions" help This option is provided for the case where no in-kernel-tree modules require CRC64 functions, but a module built outside the kernel tree does. Such modules that use library CRC64 functions require M here. config CRC4 tristate "CRC4 functions" help This option is provided for the case where no in-kernel-tree modules require CRC4 functions, but a module built outside the kernel tree does. Such modules that use library CRC4 functions require M here. config CRC7 tristate "CRC7 functions" help This option is provided for the case where no in-kernel-tree modules require CRC7 functions, but a module built outside the kernel tree does. Such modules that use library CRC7 functions require M here. config LIBCRC32C tristate "CRC32c (Castagnoli, et al) Cyclic Redundancy-Check" select CRYPTO select CRYPTO_CRC32C help This option is provided for the case where no in-kernel-tree modules require CRC32c functions, but a module built outside the kernel tree does. Such modules that use library CRC32c functions require M here. See Castagnoli93. Module will be libcrc32c. config CRC8 tristate "CRC8 function" help This option provides CRC8 function. Drivers may select this when they need to do cyclic redundancy check according CRC8 algorithm. Module will be called crc8. config XXHASH tristate config AUDIT_GENERIC bool depends on AUDIT && !AUDIT_ARCH default y config AUDIT_ARCH_COMPAT_GENERIC bool default n config AUDIT_COMPAT_GENERIC bool depends on AUDIT_GENERIC && AUDIT_ARCH_COMPAT_GENERIC && COMPAT default y config RANDOM32_SELFTEST bool "PRNG perform self test on init" help This option enables the 32 bit PRNG library functions to perform a self test on initialization. # # compression support is select'ed if needed # config 842_COMPRESS select CRC32 tristate config 842_DECOMPRESS select CRC32 tristate config ZLIB_INFLATE tristate config ZLIB_DEFLATE tristate select BITREVERSE config ZLIB_DFLTCC def_bool y depends on S390 prompt "Enable s390x DEFLATE CONVERSION CALL support for kernel zlib" help Enable s390x hardware support for zlib in the kernel. config LZO_COMPRESS tristate config LZO_DECOMPRESS tristate config LZ4_COMPRESS tristate config LZ4HC_COMPRESS tristate config LZ4_DECOMPRESS tristate config ZSTD_COMPRESS select XXHASH tristate config ZSTD_DECOMPRESS select XXHASH tristate source "lib/xz/Kconfig" # # These all provide a common interface (hence the apparent duplication with # ZLIB_INFLATE; DECOMPRESS_GZIP is just a wrapper.) # config DECOMPRESS_GZIP select ZLIB_INFLATE tristate config DECOMPRESS_BZIP2 tristate config DECOMPRESS_LZMA tristate config DECOMPRESS_XZ select XZ_DEC tristate config DECOMPRESS_LZO select LZO_DECOMPRESS tristate config DECOMPRESS_LZ4 select LZ4_DECOMPRESS tristate config DECOMPRESS_ZSTD select ZSTD_DECOMPRESS tristate # # Generic allocator support is selected if needed # config GENERIC_ALLOCATOR bool # # reed solomon support is select'ed if needed # config REED_SOLOMON tristate config REED_SOLOMON_ENC8 bool config REED_SOLOMON_DEC8 bool config REED_SOLOMON_ENC16 bool config REED_SOLOMON_DEC16 bool # # BCH support is selected if needed # config BCH tristate config BCH_CONST_PARAMS bool help Drivers may select this option to force specific constant values for parameters 'm' (Galois field order) and 't' (error correction capability). Those specific values must be set by declaring default values for symbols BCH_CONST_M and BCH_CONST_T. Doing so will enable extra compiler optimizations, improving encoding and decoding performance up to 2x for usual (m,t) values (typically such that m*t < 200). When this option is selected, the BCH library supports only a single (m,t) configuration. This is mainly useful for NAND flash board drivers requiring known, fixed BCH parameters. config BCH_CONST_M int range 5 15 help Constant value for Galois field order 'm'. If 'k' is the number of data bits to protect, 'm' should be chosen such that (k + m*t) <= 2**m - 1. Drivers should declare a default value for this symbol if they select option BCH_CONST_PARAMS. config BCH_CONST_T int help Constant value for error correction capability in bits 't'. Drivers should declare a default value for this symbol if they select option BCH_CONST_PARAMS. # # Textsearch support is select'ed if needed # config TEXTSEARCH bool config TEXTSEARCH_KMP tristate config TEXTSEARCH_BM tristate config TEXTSEARCH_FSM tristate config BTREE bool config INTERVAL_TREE bool help Simple, embeddable, interval-tree. Can find the start of an overlapping range in log(n) time and then iterate over all overlapping nodes. The algorithm is implemented as an augmented rbtree. See: Documentation/core-api/rbtree.rst for more information. config XARRAY_MULTI bool help Support entries which occupy multiple consecutive indices in the XArray. config ASSOCIATIVE_ARRAY bool help Generic associative array. Can be searched and iterated over whilst it is being modified. It is also reasonably quick to search and modify. The algorithms are non-recursive, and the trees are highly capacious. See: Documentation/core-api/assoc_array.rst for more information. config HAS_IOMEM bool depends on !NO_IOMEM default y config HAS_IOPORT_MAP bool depends on HAS_IOMEM && !NO_IOPORT_MAP default y source "kernel/dma/Kconfig" config SGL_ALLOC bool default n config IOMMU_HELPER bool config CHECK_SIGNATURE bool config CPUMASK_OFFSTACK bool "Force CPU masks off stack" if DEBUG_PER_CPU_MAPS help Use dynamic allocation for cpumask_var_t, instead of putting them on the stack. This is a bit more expensive, but avoids stack overflow. config CPU_RMAP bool depends on SMP config DQL bool config GLOB bool # This actually supports modular compilation, but the module overhead # is ridiculous for the amount of code involved. Until an out-of-tree # driver asks for it, we'll just link it directly it into the kernel # when required. Since we're ignoring out-of-tree users, there's also # no need bother prompting for a manual decision: # prompt "glob_match() function" help This option provides a glob_match function for performing simple text pattern matching. It originated in the ATA code to blacklist particular drive models, but other device drivers may need similar functionality. All drivers in the Linux kernel tree that require this function should automatically select this option. Say N unless you are compiling an out-of tree driver which tells you that it depends on this. config GLOB_SELFTEST tristate "glob self-test on init" depends on GLOB help This option enables a simple self-test of the glob_match function on startup. It is primarily useful for people working on the code to ensure they haven't introduced any regressions. It only adds a little bit of code and slows kernel boot (or module load) by a small amount, so you're welcome to play with it, but you probably don't need it. # # Netlink attribute parsing support is select'ed if needed # config NLATTR bool # # Generic 64-bit atomic support is selected if needed # config GENERIC_ATOMIC64 bool config LRU_CACHE tristate config CLZ_TAB bool config IRQ_POLL bool "IRQ polling library" help Helper library to poll interrupt mitigation using polling. config MPILIB tristate select CLZ_TAB help Multiprecision maths library from GnuPG. It is used to implement RSA digital signature verification, which is used by IMA/EVM digital signature extension. config SIGNATURE tristate depends on KEYS select CRYPTO select CRYPTO_SHA1 select MPILIB help Digital signature verification. Currently only RSA is supported. Implementation is done using GnuPG MPI library config DIMLIB bool help Dynamic Interrupt Moderation library. Implements an algorithm for dynamically changing CQ moderation values according to run time performance. # # libfdt files, only selected if needed. # config LIBFDT bool config OID_REGISTRY tristate help Enable fast lookup object identifier registry. config UCS2_STRING tristate # # generic vdso # source "lib/vdso/Kconfig" source "lib/fonts/Kconfig" config SG_SPLIT def_bool n help Provides a helper to split scatterlists into chunks, each chunk being a scatterlist. This should be selected by a driver or an API which whishes to split a scatterlist amongst multiple DMA channels. config SG_POOL def_bool n help Provides a helper to allocate chained scatterlists. This should be selected by a driver or an API which whishes to allocate chained scatterlist. # # sg chaining option # config ARCH_NO_SG_CHAIN def_bool n config ARCH_HAS_PMEM_API bool config MEMREGION bool config ARCH_HAS_MEMREMAP_COMPAT_ALIGN bool # use memcpy to implement user copies for nommu architectures config UACCESS_MEMCPY bool config ARCH_HAS_UACCESS_FLUSHCACHE bool # arch has a concept of a recoverable synchronous exception due to a # memory-read error like x86 machine-check or ARM data-abort, and # implements copy_mc_to_{user,kernel} to abort and report # 'bytes-transferred' if that exception fires when accessing the source # buffer. config ARCH_HAS_COPY_MC bool # Temporary. Goes away when all archs are cleaned up config ARCH_STACKWALK bool config STACKDEPOT bool select STACKTRACE config STACK_HASH_ORDER int "stack depot hash size (12 => 4KB, 20 => 1024KB)" range 12 20 default 20 depends on STACKDEPOT help Select the hash size as a power of 2 for the stackdepot hash table. Choose a lower value to reduce the memory impact. config SBITMAP bool config PARMAN tristate "parman" if COMPILE_TEST config OBJAGG tristate "objagg" if COMPILE_TEST endmenu config GENERIC_IOREMAP bool config GENERIC_LIB_ASHLDI3 bool config GENERIC_LIB_ASHRDI3 bool config GENERIC_LIB_LSHRDI3 bool config GENERIC_LIB_MULDI3 bool config GENERIC_LIB_CMPDI2 bool config GENERIC_LIB_UCMPDI2 bool config GENERIC_LIB_DEVMEM_IS_ALLOWED bool config PLDMFW bool select CRC32 default n config ASN1_ENCODER tristate PK ! ����� � subcmd/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 include ../../scripts/Makefile.include include ../../scripts/utilities.mak # QUIET_CLEAN ifeq ($(srctree),) srctree := $(patsubst %/,%,$(dir $(CURDIR))) srctree := $(patsubst %/,%,$(dir $(srctree))) srctree := $(patsubst %/,%,$(dir $(srctree))) #$(info Determined 'srctree' to be $(srctree)) endif CC ?= $(CROSS_COMPILE)gcc LD ?= $(CROSS_COMPILE)ld AR ?= $(CROSS_COMPILE)ar RM = rm -f MAKEFLAGS += --no-print-directory LIBFILE = $(OUTPUT)libsubcmd.a CFLAGS := -ggdb3 -Wall -Wextra -std=gnu99 -fPIC ifeq ($(DEBUG),0) ifeq ($(feature-fortify-source), 1) CFLAGS += -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 endif endif ifeq ($(DEBUG),1) CFLAGS += -O0 else ifeq ($(CC_NO_CLANG), 0) CFLAGS += -O3 else CFLAGS += -O6 endif # Treat warnings as errors unless directed not to ifneq ($(WERROR),0) CFLAGS += -Werror endif CFLAGS += -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE CFLAGS += -I$(srctree)/tools/include/ CFLAGS += $(EXTRA_WARNINGS) $(EXTRA_CFLAGS) SUBCMD_IN := $(OUTPUT)libsubcmd-in.o all: export srctree OUTPUT CC LD CFLAGS V include $(srctree)/tools/build/Makefile.include all: fixdep $(LIBFILE) $(SUBCMD_IN): FORCE @$(MAKE) $(build)=libsubcmd $(LIBFILE): $(SUBCMD_IN) $(QUIET_AR)$(RM) $@ && $(AR) rcs $@ $(SUBCMD_IN) clean: $(call QUIET_CLEAN, libsubcmd) $(RM) $(LIBFILE); \ find $(if $(OUTPUT),$(OUTPUT),.) -name \*.o -or -name \*.o.cmd -or -name \*.o.d | xargs $(RM) FORCE: .PHONY: clean FORCE PK ! ��@$ @$ bpf/Makefilenu �[��� # SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause) # Most of this file is copied from tools/lib/traceevent/Makefile RM ?= rm srctree = $(abs_srctree) VERSION_SCRIPT := libbpf.map LIBBPF_VERSION := $(shell \ grep -oE '^LIBBPF_([0-9.]+)' $(VERSION_SCRIPT) | \ sort -rV | head -n1 | cut -d'_' -f2) LIBBPF_MAJOR_VERSION := $(firstword $(subst ., ,$(LIBBPF_VERSION))) MAKEFLAGS += --no-print-directory # This will work when bpf is built in tools env. where srctree # isn't set and when invoked from selftests build, where srctree # is a ".". building_out_of_srctree is undefined for in srctree # builds ifndef building_out_of_srctree srctree := $(patsubst %/,%,$(dir $(CURDIR))) srctree := $(patsubst %/,%,$(dir $(srctree))) srctree := $(patsubst %/,%,$(dir $(srctree))) #$(info Determined 'srctree' to be $(srctree)) endif INSTALL = install # Use DESTDIR for installing into a different root directory. # This is useful for building a package. The program will be # installed in this directory as if it was the root directory. # Then the build tool can move it later. DESTDIR ?= DESTDIR_SQ = '$(subst ','\'',$(DESTDIR))' include $(srctree)/tools/scripts/Makefile.arch ifeq ($(LP64), 1) libdir_relative = lib64 else libdir_relative = lib endif prefix ?= /usr/local libdir = $(prefix)/$(libdir_relative) man_dir = $(prefix)/share/man man_dir_SQ = '$(subst ','\'',$(man_dir))' export man_dir man_dir_SQ INSTALL export DESTDIR DESTDIR_SQ include $(srctree)/tools/scripts/Makefile.include # copy a bit from Linux kbuild ifeq ("$(origin V)", "command line") VERBOSE = $(V) endif ifndef VERBOSE VERBOSE = 0 endif INCLUDES = -I. -I$(srctree)/tools/include -I$(srctree)/tools/include/uapi export prefix libdir src obj # Shell quotes libdir_SQ = $(subst ','\'',$(libdir)) libdir_relative_SQ = $(subst ','\'',$(libdir_relative)) OBJ = $@ N = LIB_TARGET = libbpf.a libbpf.so.$(LIBBPF_VERSION) LIB_FILE = libbpf.a libbpf.so* PC_FILE = libbpf.pc # Set compile option CFLAGS ifdef EXTRA_CFLAGS CFLAGS := $(EXTRA_CFLAGS) else CFLAGS := -g -O2 endif # Append required CFLAGS override CFLAGS += $(EXTRA_WARNINGS) -Wno-switch-enum override CFLAGS += -Werror -Wall override CFLAGS += $(INCLUDES) override CFLAGS += -fvisibility=hidden override CFLAGS += -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 # flags specific for shared library SHLIB_FLAGS := -DSHARED -fPIC ifeq ($(VERBOSE),1) Q = else Q = @ endif # Disable command line variables (CFLAGS) override from top # level Makefile (perf), otherwise build Makefile will get # the same command line setup. MAKEOVERRIDES= all: export srctree OUTPUT CC LD CFLAGS V include $(srctree)/tools/build/Makefile.include SHARED_OBJDIR := $(OUTPUT)sharedobjs/ STATIC_OBJDIR := $(OUTPUT)staticobjs/ BPF_IN_SHARED := $(SHARED_OBJDIR)libbpf-in.o BPF_IN_STATIC := $(STATIC_OBJDIR)libbpf-in.o BPF_HELPER_DEFS := $(OUTPUT)bpf_helper_defs.h LIB_TARGET := $(addprefix $(OUTPUT),$(LIB_TARGET)) LIB_FILE := $(addprefix $(OUTPUT),$(LIB_FILE)) PC_FILE := $(addprefix $(OUTPUT),$(PC_FILE)) TAGS_PROG := $(if $(shell which etags 2>/dev/null),etags,ctags) GLOBAL_SYM_COUNT = $(shell readelf -s --wide $(BPF_IN_SHARED) | \ cut -d "@" -f1 | sed 's/_v[0-9]_[0-9]_[0-9].*//' | \ sed 's/\[.*\]//' | \ awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}' | \ sort -u | wc -l) VERSIONED_SYM_COUNT = $(shell readelf --dyn-syms --wide $(OUTPUT)libbpf.so | \ sed 's/\[.*\]//' | \ awk '/GLOBAL/ && /DEFAULT/ && !/UND|ABS/ {print $$NF}' | \ grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | sort -u | wc -l) CMD_TARGETS = $(LIB_TARGET) $(PC_FILE) all: fixdep $(Q)$(MAKE) all_cmd all_cmd: $(CMD_TARGETS) check $(BPF_IN_SHARED): force $(BPF_HELPER_DEFS) @(test -f ../../include/uapi/linux/bpf.h -a -f ../../../include/uapi/linux/bpf.h && ( \ (diff -B ../../include/uapi/linux/bpf.h ../../../include/uapi/linux/bpf.h >/dev/null) || \ echo "Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from latest version at 'include/uapi/linux/bpf.h'" >&2 )) || true @(test -f ../../include/uapi/linux/bpf_common.h -a -f ../../../include/uapi/linux/bpf_common.h && ( \ (diff -B ../../include/uapi/linux/bpf_common.h ../../../include/uapi/linux/bpf_common.h >/dev/null) || \ echo "Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf_common.h' differs from latest version at 'include/uapi/linux/bpf_common.h'" >&2 )) || true @(test -f ../../include/uapi/linux/netlink.h -a -f ../../../include/uapi/linux/netlink.h && ( \ (diff -B ../../include/uapi/linux/netlink.h ../../../include/uapi/linux/netlink.h >/dev/null) || \ echo "Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h'" >&2 )) || true @(test -f ../../include/uapi/linux/if_link.h -a -f ../../../include/uapi/linux/if_link.h && ( \ (diff -B ../../include/uapi/linux/if_link.h ../../../include/uapi/linux/if_link.h >/dev/null) || \ echo "Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h'" >&2 )) || true @(test -f ../../include/uapi/linux/if_xdp.h -a -f ../../../include/uapi/linux/if_xdp.h && ( \ (diff -B ../../include/uapi/linux/if_xdp.h ../../../include/uapi/linux/if_xdp.h >/dev/null) || \ echo "Warning: Kernel ABI header at 'tools/include/uapi/linux/if_xdp.h' differs from latest version at 'include/uapi/linux/if_xdp.h'" >&2 )) || true $(Q)$(MAKE) $(build)=libbpf OUTPUT=$(SHARED_OBJDIR) CFLAGS="$(CFLAGS) $(SHLIB_FLAGS)" $(BPF_IN_STATIC): force $(BPF_HELPER_DEFS) $(Q)$(MAKE) $(build)=libbpf OUTPUT=$(STATIC_OBJDIR) $(BPF_HELPER_DEFS): $(srctree)/tools/include/uapi/linux/bpf.h $(QUIET_GEN)$(srctree)/scripts/bpf_doc.py --header \ --file $(srctree)/tools/include/uapi/linux/bpf.h > $(BPF_HELPER_DEFS) $(OUTPUT)libbpf.so: $(OUTPUT)libbpf.so.$(LIBBPF_VERSION) $(OUTPUT)libbpf.so.$(LIBBPF_VERSION): $(BPF_IN_SHARED) $(VERSION_SCRIPT) $(QUIET_LINK)$(CC) $(LDFLAGS) \ --shared -Wl,-soname,libbpf.so.$(LIBBPF_MAJOR_VERSION) \ -Wl,--version-script=$(VERSION_SCRIPT) $< -lelf -lz -o $@ @ln -sf $(@F) $(OUTPUT)libbpf.so @ln -sf $(@F) $(OUTPUT)libbpf.so.$(LIBBPF_MAJOR_VERSION) $(OUTPUT)libbpf.a: $(BPF_IN_STATIC) $(QUIET_LINK)$(RM) -f $@; $(AR) rcs $@ $^ $(OUTPUT)libbpf.pc: $(QUIET_GEN)sed -e "s|@PREFIX@|$(prefix)|" \ -e "s|@LIBDIR@|$(libdir_SQ)|" \ -e "s|@VERSION@|$(LIBBPF_VERSION)|" \ < libbpf.pc.template > $@ check: check_abi check_abi: $(OUTPUT)libbpf.so $(VERSION_SCRIPT) @if [ "$(GLOBAL_SYM_COUNT)" != "$(VERSIONED_SYM_COUNT)" ]; then \ echo "Warning: Num of global symbols in $(BPF_IN_SHARED)" \ "($(GLOBAL_SYM_COUNT)) does NOT match with num of" \ "versioned symbols in $^ ($(VERSIONED_SYM_COUNT))." \ "Please make sure all LIBBPF_API symbols are" \ "versioned in $(VERSION_SCRIPT)." >&2; \ readelf -s --wide $(BPF_IN_SHARED) | \ cut -d "@" -f1 | sed 's/_v[0-9]_[0-9]_[0-9].*//' | \ sed 's/\[.*\]//' | \ awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \ sort -u > $(OUTPUT)libbpf_global_syms.tmp; \ readelf --dyn-syms --wide $(OUTPUT)libbpf.so | \ sed 's/\[.*\]//' | \ awk '/GLOBAL/ && /DEFAULT/ && !/UND|ABS/ {print $$NF}'| \ grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | \ sort -u > $(OUTPUT)libbpf_versioned_syms.tmp; \ diff -u $(OUTPUT)libbpf_global_syms.tmp \ $(OUTPUT)libbpf_versioned_syms.tmp; \ rm $(OUTPUT)libbpf_global_syms.tmp \ $(OUTPUT)libbpf_versioned_syms.tmp; \ exit 1; \ fi define do_install_mkdir if [ ! -d '$(DESTDIR_SQ)$1' ]; then \ $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$1'; \ fi endef define do_install if [ ! -d '$(DESTDIR_SQ)$2' ]; then \ $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$2'; \ fi; \ $(INSTALL) $(if $3,-m $3,) $1 '$(DESTDIR_SQ)$2' endef install_lib: all_cmd $(call QUIET_INSTALL, $(LIB_TARGET)) \ $(call do_install_mkdir,$(libdir_SQ)); \ cp -fpR $(LIB_FILE) $(DESTDIR)$(libdir_SQ) INSTALL_HEADERS = bpf.h libbpf.h btf.h libbpf_common.h libbpf_legacy.h xsk.h \ bpf_helpers.h $(BPF_HELPER_DEFS) bpf_tracing.h \ bpf_endian.h bpf_core_read.h skel_internal.h install_headers: $(BPF_HELPER_DEFS) $(call QUIET_INSTALL, headers) \ $(foreach hdr,$(INSTALL_HEADERS), \ $(call do_install,$(hdr),$(prefix)/include/bpf,644);) install_pkgconfig: $(PC_FILE) $(call QUIET_INSTALL, $(PC_FILE)) \ $(call do_install,$(PC_FILE),$(libdir_SQ)/pkgconfig,644) install: install_lib install_pkgconfig install_headers clean: $(call QUIET_CLEAN, libbpf) $(RM) -rf $(CMD_TARGETS) \ *~ .*.d .*.cmd LIBBPF-CFLAGS $(BPF_HELPER_DEFS) \ $(SHARED_OBJDIR) $(STATIC_OBJDIR) \ $(addprefix $(OUTPUT), \ *.o *.a *.so *.so.$(LIBBPF_MAJOR_VERSION) *.pc) PHONY += force cscope tags force: cscope: ls *.c *.h > cscope.files cscope -b -q -I $(srctree)/include -f cscope.out tags: $(RM) -f TAGS tags ls *.c *.h | xargs $(TAGS_PROG) -a # Declare the contents of the .PHONY variable as phony. We keep that # information in a variable so we can use it in if_changed and friends. .PHONY: $(PHONY) # Delete partially updated (corrupted) files on error .DELETE_ON_ERROR: PK ! D �_� � lockdep/run_tests.shnu ȯ�� #! /bin/bash # SPDX-License-Identifier: GPL-2.0 if ! make >/dev/null; then echo "Building liblockdep failed." echo "FAILED!" exit 1 fi find tests -name '*.c' | sort | while read -r i; do testname=$(basename "$i" .c) echo -ne "$testname... " if gcc -o "tests/$testname" -pthread "$i" liblockdep.a -Iinclude -D__USE_LIBLOCKDEP && timeout 1 "tests/$testname" 2>&1 | /bin/bash "tests/${testname}.sh"; then echo "PASSED!" else echo "FAILED!" fi rm -f "tests/$testname" done find tests -name '*.c' | sort | while read -r i; do testname=$(basename "$i" .c) echo -ne "(PRELOAD) $testname... " if gcc -o "tests/$testname" -pthread -Iinclude "$i" && timeout 1 ./lockdep "tests/$testname" 2>&1 | /bin/bash "tests/${testname}.sh"; then echo "PASSED!" else echo "FAILED!" fi rm -f "tests/$testname" done find tests -name '*.c' | sort | while read -r i; do testname=$(basename "$i" .c) echo -ne "(PRELOAD + Valgrind) $testname... " if gcc -o "tests/$testname" -pthread -Iinclude "$i" && { timeout 10 valgrind --read-var-info=yes ./lockdep "./tests/$testname" >& "tests/${testname}.vg.out"; true; } && /bin/bash "tests/${testname}.sh" < "tests/${testname}.vg.out" && ! grep -Eq '(^==[0-9]*== (Invalid |Uninitialised ))|Mismatched free|Source and destination overlap| UME ' "tests/${testname}.vg.out"; then echo "PASSED!" else echo "FAILED!" fi rm -f "tests/$testname" done PK ! h?A�w w lockdep/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # file format version FILE_VERSION = 1 LIBLOCKDEP_VERSION=$(shell make --no-print-directory -sC ../../.. kernelversion) # Makefiles suck: This macro sets a default value of $(2) for the # variable named by $(1), unless the variable has been set by # environment or command line. This is necessary for CC and AR # because make sets default values, so the simpler ?= approach # won't work as expected. define allow-override $(if $(or $(findstring environment,$(origin $(1))),\ $(findstring command line,$(origin $(1)))),,\ $(eval $(1) = $(2))) endef # Allow setting CC and AR and LD, or setting CROSS_COMPILE as a prefix. $(call allow-override,CC,$(CROSS_COMPILE)gcc) $(call allow-override,AR,$(CROSS_COMPILE)ar) $(call allow-override,LD,$(CROSS_COMPILE)ld) INSTALL = install # Use DESTDIR for installing into a different root directory. # This is useful for building a package. The program will be # installed in this directory as if it was the root directory. # Then the build tool can move it later. DESTDIR ?= DESTDIR_SQ = '$(subst ','\'',$(DESTDIR))' prefix ?= /usr/local libdir_relative = lib libdir = $(prefix)/$(libdir_relative) bindir_relative = bin bindir = $(prefix)/$(bindir_relative) export DESTDIR DESTDIR_SQ INSTALL MAKEFLAGS += --no-print-directory include ../../scripts/Makefile.include # copy a bit from Linux kbuild ifeq ("$(origin V)", "command line") VERBOSE = $(V) endif ifndef VERBOSE VERBOSE = 0 endif ifeq ($(srctree),) srctree := $(patsubst %/,%,$(dir $(CURDIR))) srctree := $(patsubst %/,%,$(dir $(srctree))) srctree := $(patsubst %/,%,$(dir $(srctree))) #$(info Determined 'srctree' to be $(srctree)) endif # Shell quotes libdir_SQ = $(subst ','\'',$(libdir)) bindir_SQ = $(subst ','\'',$(bindir)) LIB_IN := $(OUTPUT)liblockdep-in.o BIN_FILE = lockdep LIB_FILE = $(OUTPUT)liblockdep.a $(OUTPUT)liblockdep.so.$(LIBLOCKDEP_VERSION) CONFIG_INCLUDES = CONFIG_LIBS = CONFIG_FLAGS = OBJ = $@ N = export Q VERBOSE INCLUDES = -I. -I./uinclude -I./include -I../../include $(CONFIG_INCLUDES) # Set compile option CFLAGS if not set elsewhere CFLAGS ?= -g -DCONFIG_LOCKDEP -DCONFIG_STACKTRACE -DCONFIG_PROVE_LOCKING -DBITS_PER_LONG=__WORDSIZE -DLIBLOCKDEP_VERSION='"$(LIBLOCKDEP_VERSION)"' -rdynamic -O0 -g CFLAGS += -fPIC CFLAGS += -Wall override CFLAGS += $(CONFIG_FLAGS) $(INCLUDES) $(PLUGIN_DIR_SQ) ifeq ($(VERBOSE),1) Q = print_shared_lib_compile = print_install = else Q = @ print_shared_lib_compile = echo ' LD '$(OBJ); print_static_lib_build = echo ' LD '$(OBJ); print_install = echo ' INSTALL '$1' to $(DESTDIR_SQ)$2'; endif all: export srctree OUTPUT CC LD CFLAGS V include $(srctree)/tools/build/Makefile.include do_compile_shared_library = \ ($(print_shared_lib_compile) \ $(CC) $(LDFLAGS) --shared $^ -o $@ -lpthread -ldl -Wl,-soname='$(@F)';$(shell ln -sf $(@F) $(@D)/liblockdep.so)) do_build_static_lib = \ ($(print_static_lib_build) \ $(RM) $@; $(AR) rcs $@ $^) CMD_TARGETS = $(LIB_FILE) TARGETS = $(CMD_TARGETS) all: fixdep all_cmd all_cmd: $(CMD_TARGETS) $(LIB_IN): force $(Q)$(MAKE) $(build)=liblockdep $(OUTPUT)liblockdep.so.$(LIBLOCKDEP_VERSION): $(LIB_IN) $(Q)$(do_compile_shared_library) $(OUTPUT)liblockdep.a: $(LIB_IN) $(Q)$(do_build_static_lib) tags: force $(RM) tags find . -name '*.[ch]' | xargs ctags --extra=+f --c-kinds=+px \ --regex-c++='/_PE\(([^,)]*).*/TEP_ERRNO__\1/' TAGS: force $(RM) TAGS find . -name '*.[ch]' | xargs etags \ --regex='/_PE(\([^,)]*\).*/TEP_ERRNO__\1/' define do_install $(print_install) \ if [ ! -d '$(DESTDIR_SQ)$2' ]; then \ $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$2'; \ fi; \ $(INSTALL) $1 '$(DESTDIR_SQ)$2' endef install_lib: all_cmd $(Q)$(call do_install,$(LIB_FILE),$(libdir_SQ)) $(Q)$(call do_install,$(BIN_FILE),$(bindir_SQ)) install: install_lib clean: $(RM) $(OUTPUT)*.o *~ $(TARGETS) $(OUTPUT)*.a $(OUTPUT)*liblockdep*.so* $(VERSION_FILES) $(OUTPUT).*.d $(OUTPUT).*.cmd $(RM) tags TAGS PHONY += force force: # Declare the contents of the .PHONY variable as phony. We keep that # information in a variable so we can use it in if_changed and friends. .PHONY: $(PHONY) PK ! ���C C lockdep/tests/WW.shnu �[��� #!/bin/bash grep -q 'WARNING: possible recursive locking detected' PK ! P��dM M lockdep/tests/ABBA.shnu �[��� #!/bin/bash grep -q 'WARNING: possible circular locking dependency detected' PK ! P��dM M lockdep/tests/ABBA_2threads.shnu �[��� #!/bin/bash grep -q 'WARNING: possible circular locking dependency detected' PK ! ���C C lockdep/tests/AA.shnu �[��� #!/bin/bash grep -q 'WARNING: possible recursive locking detected' PK ! P��dM M lockdep/tests/ABCABC.shnu �[��� #!/bin/bash grep -q 'WARNING: possible circular locking dependency detected' PK ! P��dM M lockdep/tests/ABBCCDDA.shnu �[��� #!/bin/bash grep -q 'WARNING: possible circular locking dependency detected' PK ! P��dM M lockdep/tests/ABBCCA.shnu �[��� #!/bin/bash grep -q 'WARNING: possible circular locking dependency detected' PK ! ��o~; ; lockdep/tests/unlock_balance.shnu �[��� #!/bin/bash grep -q 'WARNING: bad unlock balance detected' PK ! ���C C lockdep/tests/ABA.shnu �[��� #!/bin/bash grep -q 'WARNING: possible recursive locking detected' PK ! P��dM M lockdep/tests/ABCDBCDA.shnu �[��� #!/bin/bash grep -q 'WARNING: possible circular locking dependency detected' PK ! P��dM M lockdep/tests/ABCDBDDA.shnu �[��� #!/bin/bash grep -q 'WARNING: possible circular locking dependency detected' PK ! �� ot t perf/Makefilenu �[��� # SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause) # Most of this file is copied from tools/lib/bpf/Makefile LIBPERF_VERSION = 0 LIBPERF_PATCHLEVEL = 0 LIBPERF_EXTRAVERSION = 1 MAKEFLAGS += --no-print-directory ifeq ($(srctree),) srctree := $(patsubst %/,%,$(dir $(CURDIR))) srctree := $(patsubst %/,%,$(dir $(srctree))) srctree := $(patsubst %/,%,$(dir $(srctree))) #$(info Determined 'srctree' to be $(srctree)) endif INSTALL = install # Use DESTDIR for installing into a different root directory. # This is useful for building a package. The program will be # installed in this directory as if it was the root directory. # Then the build tool can move it later. DESTDIR ?= DESTDIR_SQ = '$(subst ','\'',$(DESTDIR))' include $(srctree)/tools/scripts/Makefile.include include $(srctree)/tools/scripts/Makefile.arch ifeq ($(LP64), 1) libdir_relative = lib64 else libdir_relative = lib endif prefix ?= libdir = $(prefix)/$(libdir_relative) # Shell quotes libdir_SQ = $(subst ','\'',$(libdir)) libdir_relative_SQ = $(subst ','\'',$(libdir_relative)) ifeq ("$(origin V)", "command line") VERBOSE = $(V) endif ifndef VERBOSE VERBOSE = 0 endif ifeq ($(VERBOSE),1) Q = else Q = @ endif TEST_ARGS := $(if $(V),-v) # Set compile option CFLAGS ifdef EXTRA_CFLAGS CFLAGS := $(EXTRA_CFLAGS) else CFLAGS := -g -Wall endif INCLUDES = \ -I$(srctree)/tools/lib/perf/include \ -I$(srctree)/tools/lib/ \ -I$(srctree)/tools/include \ -I$(srctree)/tools/arch/$(SRCARCH)/include/ \ -I$(srctree)/tools/arch/$(SRCARCH)/include/uapi \ -I$(srctree)/tools/include/uapi # Append required CFLAGS override CFLAGS += $(EXTRA_WARNINGS) override CFLAGS += -Werror -Wall override CFLAGS += -fPIC override CFLAGS += $(INCLUDES) override CFLAGS += -fvisibility=hidden all: export srctree OUTPUT CC LD CFLAGS V export DESTDIR DESTDIR_SQ include $(srctree)/tools/build/Makefile.include VERSION_SCRIPT := libperf.map PATCHLEVEL = $(LIBPERF_PATCHLEVEL) EXTRAVERSION = $(LIBPERF_EXTRAVERSION) VERSION = $(LIBPERF_VERSION).$(LIBPERF_PATCHLEVEL).$(LIBPERF_EXTRAVERSION) LIBPERF_SO := $(OUTPUT)libperf.so.$(VERSION) LIBPERF_A := $(OUTPUT)libperf.a LIBPERF_IN := $(OUTPUT)libperf-in.o LIBPERF_PC := $(OUTPUT)libperf.pc LIBPERF_ALL := $(LIBPERF_A) $(OUTPUT)libperf.so* LIB_DIR := $(srctree)/tools/lib/api/ ifneq ($(OUTPUT),) ifneq ($(subdir),) API_PATH=$(OUTPUT)/../lib/api/ else API_PATH=$(OUTPUT) endif else API_PATH=$(LIB_DIR) endif LIBAPI = $(API_PATH)libapi.a export LIBAPI $(LIBAPI): FORCE $(Q)$(MAKE) -C $(LIB_DIR) O=$(OUTPUT) $(OUTPUT)libapi.a $(LIBAPI)-clean: $(call QUIET_CLEAN, libapi) $(Q)$(MAKE) -C $(LIB_DIR) O=$(OUTPUT) clean >/dev/null $(LIBPERF_IN): FORCE $(Q)$(MAKE) $(build)=libperf $(LIBPERF_A): $(LIBPERF_IN) $(QUIET_AR)$(RM) $@ && $(AR) rcs $@ $(LIBPERF_IN) $(LIBPERF_SO): $(LIBPERF_IN) $(LIBAPI) $(QUIET_LINK)$(CC) --shared -Wl,-soname,libperf.so \ -Wl,--version-script=$(VERSION_SCRIPT) $^ -o $@ @ln -sf $(@F) $(OUTPUT)libperf.so @ln -sf $(@F) $(OUTPUT)libperf.so.$(LIBPERF_VERSION) libs: $(LIBPERF_A) $(LIBPERF_SO) $(LIBPERF_PC) all: fixdep $(Q)$(MAKE) libs clean: $(LIBAPI)-clean $(call QUIET_CLEAN, libperf) $(RM) $(LIBPERF_A) \ *.o *~ *.a *.so *.so.$(VERSION) *.so.$(LIBPERF_VERSION) .*.d .*.cmd tests/*.o LIBPERF-CFLAGS $(LIBPERF_PC) \ $(TESTS_STATIC) $(TESTS_SHARED) TESTS_IN = tests-in.o TESTS_STATIC = $(OUTPUT)tests-static TESTS_SHARED = $(OUTPUT)tests-shared $(TESTS_IN): FORCE $(Q)$(MAKE) $(build)=tests $(TESTS_STATIC): $(TESTS_IN) $(LIBPERF_A) $(LIBAPI) $(QUIET_LINK)$(CC) -o $@ $^ $(TESTS_SHARED): $(TESTS_IN) $(LIBAPI) $(QUIET_LINK)$(CC) -o $@ -L$(if $(OUTPUT),$(OUTPUT),.) $^ -lperf make-tests: libs $(TESTS_SHARED) $(TESTS_STATIC) tests: make-tests @echo "running static:" @./$(TESTS_STATIC) $(TEST_ARGS) @echo "running dynamic:" @LD_LIBRARY_PATH=. ./$(TESTS_SHARED) $(TEST_ARGS) $(LIBPERF_PC): $(QUIET_GEN)sed -e "s|@PREFIX@|$(prefix)|" \ -e "s|@LIBDIR@|$(libdir_SQ)|" \ -e "s|@VERSION@|$(VERSION)|" \ < libperf.pc.template > $@ define do_install_mkdir if [ ! -d '$(DESTDIR_SQ)$1' ]; then \ $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$1'; \ fi endef define do_install if [ ! -d '$(DESTDIR_SQ)$2' ]; then \ $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$2'; \ fi; \ $(INSTALL) $1 $(if $3,-m $3,) '$(DESTDIR_SQ)$2' endef install_lib: libs $(call QUIET_INSTALL, $(LIBPERF_ALL)) \ $(call do_install_mkdir,$(libdir_SQ)); \ cp -fpR $(LIBPERF_ALL) $(DESTDIR)$(libdir_SQ) install_headers: $(call QUIET_INSTALL, headers) \ $(call do_install,include/perf/core.h,$(prefix)/include/perf,644); \ $(call do_install,include/perf/cpumap.h,$(prefix)/include/perf,644); \ $(call do_install,include/perf/threadmap.h,$(prefix)/include/perf,644); \ $(call do_install,include/perf/evlist.h,$(prefix)/include/perf,644); \ $(call do_install,include/perf/evsel.h,$(prefix)/include/perf,644); \ $(call do_install,include/perf/event.h,$(prefix)/include/perf,644); \ $(call do_install,include/perf/mmap.h,$(prefix)/include/perf,644); install_pkgconfig: $(LIBPERF_PC) $(call QUIET_INSTALL, $(LIBPERF_PC)) \ $(call do_install,$(LIBPERF_PC),$(libdir_SQ)/pkgconfig,644) install_doc: $(Q)$(MAKE) -C Documentation install-man install-html install-examples install: install_lib install_headers install_pkgconfig install_doc FORCE: .PHONY: all install clean tests FORCE PK ! �D�� � perf/Documentation/Makefilenu �[��� # SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause) # Most of this file is copied from tools/perf/Documentation/Makefile include ../../../scripts/Makefile.include include ../../../scripts/utilities.mak MAN3_TXT = libperf.txt MAN7_TXT = libperf-counting.txt libperf-sampling.txt MAN_EX = examples/*.c MAN_TXT = $(MAN3_TXT) $(MAN7_TXT) _MAN_XML = $(patsubst %.txt,%.xml,$(MAN_TXT)) _MAN_HTML = $(patsubst %.txt,%.html,$(MAN_TXT)) _MAN_3 = $(patsubst %.txt,%.3,$(MAN3_TXT)) _MAN_7 = $(patsubst %.txt,%.7,$(MAN7_TXT)) MAN_XML = $(addprefix $(OUTPUT),$(_MAN_XML)) MAN_HTML = $(addprefix $(OUTPUT),$(_MAN_HTML)) MAN_3 = $(addprefix $(OUTPUT),$(_MAN_3)) MAN_7 = $(addprefix $(OUTPUT),$(_MAN_7)) MAN_X = $(MAN_3) $(MAN_7) # Make the path relative to DESTDIR, not prefix ifndef DESTDIR prefix ?=$(HOME) endif mandir ?= $(prefix)/share/man man3dir = $(mandir)/man3 man7dir = $(mandir)/man7 docdir ?= $(prefix)/share/doc/libperf htmldir = $(docdir)/html exdir = $(docdir)/examples ASCIIDOC = asciidoc ASCIIDOC_EXTRA = --unsafe -f asciidoc.conf ASCIIDOC_HTML = xhtml11 MANPAGE_XSL = manpage-normal.xsl XMLTO_EXTRA = XMLTO =xmlto INSTALL ?= install RM ?= rm -f # For asciidoc ... # -7.1.2, no extra settings are needed. # 8.0-, set ASCIIDOC8. # # For docbook-xsl ... # -1.68.1, set ASCIIDOC_NO_ROFF? (based on changelog from 1.73.0) # 1.69.0, no extra settings are needed? # 1.69.1-1.71.0, set DOCBOOK_SUPPRESS_SP? # 1.71.1, no extra settings are needed? # 1.72.0, set DOCBOOK_XSL_172. # 1.73.0-, set ASCIIDOC_NO_ROFF # If you had been using DOCBOOK_XSL_172 in an attempt to get rid # of 'the ".ft C" problem' in your generated manpages, and you # instead ended up with weird characters around callouts, try # using ASCIIDOC_NO_ROFF instead (it works fine with ASCIIDOC8). ifdef ASCIIDOC8 ASCIIDOC_EXTRA += -a asciidoc7compatible endif ifdef DOCBOOK_XSL_172 ASCIIDOC_EXTRA += -a libperf-asciidoc-no-roff MANPAGE_XSL = manpage-1.72.xsl else ifdef ASCIIDOC_NO_ROFF # docbook-xsl after 1.72 needs the regular XSL, but will not # pass-thru raw roff codes from asciidoc.conf, so turn them off. ASCIIDOC_EXTRA += -a libperf-asciidoc-no-roff endif endif ifdef MAN_BOLD_LITERAL XMLTO_EXTRA += -m manpage-bold-literal.xsl endif ifdef DOCBOOK_SUPPRESS_SP XMLTO_EXTRA += -m manpage-suppress-sp.xsl endif DESTDIR ?= DESTDIR_SQ = '$(subst ','\'',$(DESTDIR))' export DESTDIR DESTDIR_SQ # Please note that there is a minor bug in asciidoc. # The version after 6.0.3 _will_ include the patch found here: # http://marc.theaimsgroup.com/?l=libtraceevent&m=111558757202243&w=2 # # Until that version is released you may have to apply the patch # yourself - yes, all 6 characters of it! QUIET_SUBDIR0 = +$(MAKE) -C # space to separate -C and subdir QUIET_SUBDIR1 = ifneq ($(findstring $(MAKEFLAGS),w),w) PRINT_DIR = --no-print-directory else # "make -w" NO_SUBDIR = : endif ifneq ($(findstring $(MAKEFLAGS),s),s) ifneq ($(V),1) QUIET_ASCIIDOC = @echo ' ASCIIDOC '$@; QUIET_XMLTO = @echo ' XMLTO '$@; endif endif all: $(MAN_X) $(MAN_HTML) $(MAN_HTML) $(MAN_X): asciidoc.conf install-man: all $(call QUIET_INSTALL, man) \ $(INSTALL) -d -m 755 $(DESTDIR)$(man3dir); \ $(INSTALL) -m 644 $(MAN_3) $(DESTDIR)$(man3dir); \ $(INSTALL) -d -m 755 $(DESTDIR)$(man7dir); \ $(INSTALL) -m 644 $(MAN_7) $(DESTDIR)$(man7dir); install-html: $(call QUIET_INSTALL, html) \ $(INSTALL) -d -m 755 $(DESTDIR)$(htmldir); \ $(INSTALL) -m 644 $(MAN_HTML) $(DESTDIR)$(htmldir); \ install-examples: $(call QUIET_INSTALL, examples) \ $(INSTALL) -d -m 755 $(DESTDIR)$(exdir); \ $(INSTALL) -m 644 $(MAN_EX) $(DESTDIR)$(exdir); \ CLEAN_FILES = \ $(MAN_XML) $(addsuffix +,$(MAN_XML)) \ $(MAN_HTML) $(addsuffix +,$(MAN_HTML)) \ $(MAN_X) clean: $(call QUIET_CLEAN, Documentation) $(RM) $(CLEAN_FILES) $(MAN_3): $(OUTPUT)%.3: %.xml $(QUIET_XMLTO)$(XMLTO) -o $(OUTPUT). -m $(MANPAGE_XSL) $(XMLTO_EXTRA) man $< $(MAN_7): $(OUTPUT)%.7: %.xml $(QUIET_XMLTO)$(XMLTO) -o $(OUTPUT). -m $(MANPAGE_XSL) $(XMLTO_EXTRA) man $< $(MAN_XML): $(OUTPUT)%.xml: %.txt $(QUIET_ASCIIDOC)$(ASCIIDOC) -b docbook -d manpage \ $(ASCIIDOC_EXTRA) -alibperf_version=$(EVENT_PARSE_VERSION) -o $@+ $< && \ mv $@+ $@ $(MAN_HTML): $(OUTPUT)%.html: %.txt $(QUIET_ASCIIDOC)$(ASCIIDOC) -b $(ASCIIDOC_HTML) -d manpage \ $(ASCIIDOC_EXTRA) -aperf_version=$(EVENT_PARSE_VERSION) -o $@+ $< && \ mv $@+ $@ PK ! �ى � api/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 include ../../scripts/Makefile.include include ../../scripts/utilities.mak # QUIET_CLEAN ifeq ($(srctree),) srctree := $(patsubst %/,%,$(dir $(CURDIR))) srctree := $(patsubst %/,%,$(dir $(srctree))) srctree := $(patsubst %/,%,$(dir $(srctree))) #$(info Determined 'srctree' to be $(srctree)) endif CC ?= $(CROSS_COMPILE)gcc AR ?= $(CROSS_COMPILE)ar LD ?= $(CROSS_COMPILE)ld MAKEFLAGS += --no-print-directory LIBFILE = $(OUTPUT)libapi.a CFLAGS := $(EXTRA_WARNINGS) $(EXTRA_CFLAGS) CFLAGS += -ggdb3 -Wall -Wextra -std=gnu99 -U_FORTIFY_SOURCE -fPIC ifeq ($(DEBUG),0) ifeq ($(CC_NO_CLANG), 0) CFLAGS += -O3 else CFLAGS += -O6 endif endif ifeq ($(DEBUG),0) CFLAGS += -D_FORTIFY_SOURCE endif # Treat warnings as errors unless directed not to ifneq ($(WERROR),0) CFLAGS += -Werror endif CFLAGS += -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 CFLAGS += -I$(srctree)/tools/lib/api CFLAGS += -I$(srctree)/tools/include RM = rm -f API_IN := $(OUTPUT)libapi-in.o all: export srctree OUTPUT CC LD CFLAGS V include $(srctree)/tools/build/Makefile.include all: fixdep $(LIBFILE) $(API_IN): FORCE @$(MAKE) $(build)=libapi $(LIBFILE): $(API_IN) $(QUIET_AR)$(RM) $@ && $(AR) rcs $@ $(API_IN) clean: $(call QUIET_CLEAN, libapi) $(RM) $(LIBFILE); \ find $(if $(OUTPUT),$(OUTPUT),.) -name \*.o -or -name \*.o.cmd -or -name \*.o.d | xargs $(RM) FORCE: .PHONY: clean FORCE PK ! g�2�> > traceevent/plugins/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 #MAKEFLAGS += --no-print-directory # Makefiles suck: This macro sets a default value of $(2) for the # variable named by $(1), unless the variable has been set by # environment or command line. This is necessary for CC and AR # because make sets default values, so the simpler ?= approach # won't work as expected. define allow-override $(if $(or $(findstring environment,$(origin $(1))),\ $(findstring command line,$(origin $(1)))),,\ $(eval $(1) = $(2))) endef # Allow setting CC and AR, or setting CROSS_COMPILE as a prefix. $(call allow-override,CC,$(CROSS_COMPILE)gcc) $(call allow-override,AR,$(CROSS_COMPILE)ar) $(call allow-override,NM,$(CROSS_COMPILE)nm) $(call allow-override,PKG_CONFIG,pkg-config) EXT = -std=gnu99 INSTALL = install # Use DESTDIR for installing into a different root directory. # This is useful for building a package. The program will be # installed in this directory as if it was the root directory. # Then the build tool can move it later. DESTDIR ?= DESTDIR_SQ = '$(subst ','\'',$(DESTDIR))' LP64 := $(shell echo __LP64__ | ${CC} ${CFLAGS} -E -x c - | tail -n 1) ifeq ($(LP64), 1) libdir_relative_tmp = lib64 else libdir_relative_tmp = lib endif libdir_relative ?= $(libdir_relative_tmp) prefix ?= /usr/local libdir = $(prefix)/$(libdir_relative) set_plugin_dir := 1 # Set plugin_dir to preffered global plugin location # If we install under $HOME directory we go under # $(HOME)/.local/lib/traceevent/plugins # # We dont set PLUGIN_DIR in case we install under $HOME # directory, because by default the code looks under: # $(HOME)/.local/lib/traceevent/plugins by default. # ifeq ($(plugin_dir),) ifeq ($(prefix),$(HOME)) override plugin_dir = $(HOME)/.local/lib/traceevent/plugins set_plugin_dir := 0 else override plugin_dir = $(libdir)/traceevent/plugins endif endif ifeq ($(set_plugin_dir),1) PLUGIN_DIR = -DPLUGIN_DIR="$(plugin_dir)" PLUGIN_DIR_SQ = '$(subst ','\'',$(PLUGIN_DIR))' endif include ../../../scripts/Makefile.include # copy a bit from Linux kbuild ifeq ("$(origin V)", "command line") VERBOSE = $(V) endif ifndef VERBOSE VERBOSE = 0 endif ifeq ($(srctree),) srctree := $(patsubst %/,%,$(dir $(CURDIR))) srctree := $(patsubst %/,%,$(dir $(srctree))) srctree := $(patsubst %/,%,$(dir $(srctree))) srctree := $(patsubst %/,%,$(dir $(srctree))) #$(info Determined 'srctree' to be $(srctree)) endif export prefix libdir src obj # Shell quotes plugin_dir_SQ = $(subst ','\'',$(plugin_dir)) CONFIG_INCLUDES = CONFIG_LIBS = CONFIG_FLAGS = OBJ = $@ N = INCLUDES = -I. -I.. -I $(srctree)/tools/include $(CONFIG_INCLUDES) # Set compile option CFLAGS ifdef EXTRA_CFLAGS CFLAGS := $(EXTRA_CFLAGS) else CFLAGS := -g -Wall endif # Append required CFLAGS override CFLAGS += -fPIC override CFLAGS += $(CONFIG_FLAGS) $(INCLUDES) $(PLUGIN_DIR_SQ) override CFLAGS += $(udis86-flags) -D_GNU_SOURCE ifeq ($(VERBOSE),1) Q = else Q = @ endif # Disable command line variables (CFLAGS) override from top # level Makefile (perf), otherwise build Makefile will get # the same command line setup. MAKEOVERRIDES= export srctree OUTPUT CC LD CFLAGS V build := -f $(srctree)/tools/build/Makefile.build dir=. obj DYNAMIC_LIST_FILE := $(OUTPUT)libtraceevent-dynamic-list PLUGINS = plugin_jbd2.so PLUGINS += plugin_hrtimer.so PLUGINS += plugin_kmem.so PLUGINS += plugin_kvm.so PLUGINS += plugin_mac80211.so PLUGINS += plugin_sched_switch.so PLUGINS += plugin_function.so PLUGINS += plugin_futex.so PLUGINS += plugin_xen.so PLUGINS += plugin_scsi.so PLUGINS += plugin_cfg80211.so PLUGINS += plugin_tlb.so PLUGINS := $(addprefix $(OUTPUT),$(PLUGINS)) PLUGINS_IN := $(PLUGINS:.so=-in.o) plugins: $(PLUGINS) $(DYNAMIC_LIST_FILE) __plugin_obj = $(notdir $@) plugin_obj = $(__plugin_obj:-in.o=) $(PLUGINS_IN): force $(Q)$(MAKE) $(build)=$(plugin_obj) $(OUTPUT)libtraceevent-dynamic-list: $(PLUGINS) $(QUIET_GEN)$(call do_generate_dynamic_list_file, $(PLUGINS), $@) $(OUTPUT)%.so: $(OUTPUT)%-in.o $(QUIET_LINK)$(CC) $(CFLAGS) -shared $(LDFLAGS) -nostartfiles -o $@ $^ define update_dir (echo $1 > $@.tmp; \ if [ -r $@ ] && cmp -s $@ $@.tmp; then \ rm -f $@.tmp; \ else \ echo ' UPDATE $@'; \ mv -f $@.tmp $@; \ fi); endef tags: force $(RM) tags find . -name '*.[ch]' | xargs ctags --extra=+f --c-kinds=+px \ --regex-c++='/_PE\(([^,)]*).*/TEP_ERRNO__\1/' TAGS: force $(RM) TAGS find . -name '*.[ch]' | xargs etags \ --regex='/_PE(\([^,)]*\).*/TEP_ERRNO__\1/' define do_install_mkdir if [ ! -d '$(DESTDIR_SQ)$1' ]; then \ $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$1'; \ fi endef define do_install $(call do_install_mkdir,$2); \ $(INSTALL) $(if $3,-m $3,) $1 '$(DESTDIR_SQ)$2' endef define do_install_plugins for plugin in $1; do \ $(call do_install,$$plugin,$(plugin_dir_SQ)); \ done endef define do_generate_dynamic_list_file symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \ xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\ if [ "$$symbol_type" = "U W" ];then \ (echo '{'; \ $(NM) -u -D $1 | awk 'NF>1 {sub("@.*", "", $$2); print "\t"$$2";"}' | sort -u;\ echo '};'; \ ) > $2; \ else \ (echo Either missing one of [$1] or bad version of $(NM)) 1>&2;\ fi endef install: $(PLUGINS) $(call QUIET_INSTALL, trace_plugins) \ $(call do_install_plugins, $(PLUGINS)) clean: $(call QUIET_CLEAN, trace_plugins) \ $(RM) *.o *~ $(TARGETS) *.a *.so $(VERSION_FILES) .*.d .*.cmd; \ $(RM) $(OUTPUT)libtraceevent-dynamic-list \ $(RM) TRACEEVENT-CFLAGS tags TAGS; PHONY += force plugins force: # Declare the contents of the .PHONY variable as phony. We keep that # information in a variable so we can use it in if_changed and friends. .PHONY: $(PHONY) PK ! �pը[ [ traceevent/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # trace-cmd version EP_VERSION = 1 EP_PATCHLEVEL = 1 EP_EXTRAVERSION = 0 # file format version FILE_VERSION = 6 MAKEFLAGS += --no-print-directory # Makefiles suck: This macro sets a default value of $(2) for the # variable named by $(1), unless the variable has been set by # environment or command line. This is necessary for CC and AR # because make sets default values, so the simpler ?= approach # won't work as expected. define allow-override $(if $(or $(findstring environment,$(origin $(1))),\ $(findstring command line,$(origin $(1)))),,\ $(eval $(1) = $(2))) endef # Allow setting CC and AR, or setting CROSS_COMPILE as a prefix. $(call allow-override,CC,$(CROSS_COMPILE)gcc) $(call allow-override,AR,$(CROSS_COMPILE)ar) $(call allow-override,NM,$(CROSS_COMPILE)nm) $(call allow-override,PKG_CONFIG,pkg-config) EXT = -std=gnu99 INSTALL = install # Use DESTDIR for installing into a different root directory. # This is useful for building a package. The program will be # installed in this directory as if it was the root directory. # Then the build tool can move it later. DESTDIR ?= DESTDIR_SQ = '$(subst ','\'',$(DESTDIR))' LP64 := $(shell echo __LP64__ | ${CC} ${CFLAGS} -E -x c - | tail -n 1) ifeq ($(LP64), 1) libdir_relative_temp = lib64 else libdir_relative_temp = lib endif libdir_relative ?= $(libdir_relative_temp) prefix ?= /usr/local libdir = $(prefix)/$(libdir_relative) man_dir = $(prefix)/share/man man_dir_SQ = '$(subst ','\'',$(man_dir))' pkgconfig_dir ?= $(word 1,$(shell $(PKG_CONFIG) \ --variable pc_path pkg-config | tr ":" " ")) includedir_relative = traceevent includedir = $(prefix)/include/$(includedir_relative) includedir_SQ = '$(subst ','\'',$(includedir))' export man_dir man_dir_SQ INSTALL export DESTDIR DESTDIR_SQ export EVENT_PARSE_VERSION include ../../scripts/Makefile.include # copy a bit from Linux kbuild ifeq ("$(origin V)", "command line") VERBOSE = $(V) endif ifndef VERBOSE VERBOSE = 0 endif ifeq ($(srctree),) srctree := $(patsubst %/,%,$(dir $(CURDIR))) srctree := $(patsubst %/,%,$(dir $(srctree))) srctree := $(patsubst %/,%,$(dir $(srctree))) #$(info Determined 'srctree' to be $(srctree)) endif export prefix libdir src obj # Shell quotes libdir_SQ = $(subst ','\'',$(libdir)) libdir_relative_SQ = $(subst ','\'',$(libdir_relative)) CONFIG_INCLUDES = CONFIG_LIBS = CONFIG_FLAGS = VERSION = $(EP_VERSION) PATCHLEVEL = $(EP_PATCHLEVEL) EXTRAVERSION = $(EP_EXTRAVERSION) OBJ = $@ N = EVENT_PARSE_VERSION = $(EP_VERSION).$(EP_PATCHLEVEL).$(EP_EXTRAVERSION) LIB_TARGET = libtraceevent.a libtraceevent.so.$(EVENT_PARSE_VERSION) LIB_INSTALL = libtraceevent.a libtraceevent.so* LIB_INSTALL := $(addprefix $(OUTPUT),$(LIB_INSTALL)) INCLUDES = -I. -I $(srctree)/tools/include $(CONFIG_INCLUDES) # Set compile option CFLAGS ifdef EXTRA_CFLAGS CFLAGS := $(EXTRA_CFLAGS) else CFLAGS := -g -Wall endif # Append required CFLAGS override CFLAGS += -fPIC override CFLAGS += $(CONFIG_FLAGS) $(INCLUDES) $(PLUGIN_DIR_SQ) override CFLAGS += $(udis86-flags) -D_GNU_SOURCE ifeq ($(VERBOSE),1) Q = else Q = @ endif # Disable command line variables (CFLAGS) override from top # level Makefile (perf), otherwise build Makefile will get # the same command line setup. MAKEOVERRIDES= export srctree OUTPUT CC LD CFLAGS V build := -f $(srctree)/tools/build/Makefile.build dir=. obj TE_IN := $(OUTPUT)libtraceevent-in.o LIB_TARGET := $(addprefix $(OUTPUT),$(LIB_TARGET)) CMD_TARGETS = $(LIB_TARGET) TARGETS = $(CMD_TARGETS) all: all_cmd plugins all_cmd: $(CMD_TARGETS) $(TE_IN): force $(Q)$(MAKE) $(build)=libtraceevent $(OUTPUT)libtraceevent.so.$(EVENT_PARSE_VERSION): $(TE_IN) $(QUIET_LINK)$(CC) --shared $(LDFLAGS) $^ -Wl,-soname,libtraceevent.so.$(EP_VERSION) -o $@ @ln -sf $(@F) $(OUTPUT)libtraceevent.so @ln -sf $(@F) $(OUTPUT)libtraceevent.so.$(EP_VERSION) $(OUTPUT)libtraceevent.a: $(TE_IN) $(QUIET_LINK)$(RM) $@; $(AR) rcs $@ $^ $(OUTPUT)%.so: $(OUTPUT)%-in.o $(QUIET_LINK)$(CC) $(CFLAGS) -shared $(LDFLAGS) -nostartfiles -o $@ $^ define make_version.h (echo '/* This file is automatically generated. Do not modify. */'; \ echo \#define VERSION_CODE $(shell \ expr $(VERSION) \* 256 + $(PATCHLEVEL)); \ echo '#define EXTRAVERSION ' $(EXTRAVERSION); \ echo '#define VERSION_STRING "'$(VERSION).$(PATCHLEVEL).$(EXTRAVERSION)'"'; \ echo '#define FILE_VERSION '$(FILE_VERSION); \ ) > $1 endef define update_version.h ($(call make_version.h, $@.tmp); \ if [ -r $@ ] && cmp -s $@ $@.tmp; then \ rm -f $@.tmp; \ else \ echo ' UPDATE $@'; \ mv -f $@.tmp $@; \ fi); endef ep_version.h: force $(Q)$(N)$(call update_version.h) VERSION_FILES = ep_version.h define update_dir (echo $1 > $@.tmp; \ if [ -r $@ ] && cmp -s $@ $@.tmp; then \ rm -f $@.tmp; \ else \ echo ' UPDATE $@'; \ mv -f $@.tmp $@; \ fi); endef tags: force $(RM) tags find . -name '*.[ch]' | xargs ctags --extra=+f --c-kinds=+px \ --regex-c++='/_PE\(([^,)]*).*/TEP_ERRNO__\1/' TAGS: force $(RM) TAGS find . -name '*.[ch]' | xargs etags \ --regex='/_PE(\([^,)]*\).*/TEP_ERRNO__\1/' define do_install_mkdir if [ ! -d '$(DESTDIR_SQ)$1' ]; then \ $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$1'; \ fi endef define do_install $(call do_install_mkdir,$2); \ $(INSTALL) $(if $3,-m $3,) $1 '$(DESTDIR_SQ)$2' endef PKG_CONFIG_SOURCE_FILE = libtraceevent.pc PKG_CONFIG_FILE := $(addprefix $(OUTPUT),$(PKG_CONFIG_SOURCE_FILE)) define do_install_pkgconfig_file if [ -n "${pkgconfig_dir}" ]; then \ cp -f ${PKG_CONFIG_SOURCE_FILE}.template ${PKG_CONFIG_FILE}; \ sed -i "s|INSTALL_PREFIX|${1}|g" ${PKG_CONFIG_FILE}; \ sed -i "s|LIB_VERSION|${EVENT_PARSE_VERSION}|g" ${PKG_CONFIG_FILE}; \ sed -i "s|LIB_DIR|${libdir}|g" ${PKG_CONFIG_FILE}; \ sed -i "s|HEADER_DIR|$(includedir)|g" ${PKG_CONFIG_FILE}; \ $(call do_install,$(PKG_CONFIG_FILE),$(pkgconfig_dir),644); \ else \ (echo Failed to locate pkg-config directory) 1>&2; \ fi endef install_lib: all_cmd install_plugins install_headers install_pkgconfig $(call QUIET_INSTALL, $(LIB_TARGET)) \ $(call do_install_mkdir,$(libdir_SQ)); \ cp -fpR $(LIB_INSTALL) $(DESTDIR)$(libdir_SQ) install_pkgconfig: $(call QUIET_INSTALL, $(PKG_CONFIG_FILE)) \ $(call do_install_pkgconfig_file,$(prefix)) install_headers: $(call QUIET_INSTALL, headers) \ $(call do_install,event-parse.h,$(includedir_SQ),644); \ $(call do_install,event-utils.h,$(includedir_SQ),644); \ $(call do_install,trace-seq.h,$(includedir_SQ),644); \ $(call do_install,kbuffer.h,$(includedir_SQ),644) install: install_lib clean: clean_plugins $(call QUIET_CLEAN, libtraceevent) \ $(RM) *.o *~ $(TARGETS) *.a *.so $(VERSION_FILES) .*.d .*.cmd; \ $(RM) TRACEEVENT-CFLAGS tags TAGS; \ $(RM) $(PKG_CONFIG_FILE) PHONY += doc doc: $(call descend,Documentation) PHONY += doc-clean doc-clean: $(call descend,Documentation,clean) PHONY += doc-install doc-install: $(call descend,Documentation,install) PHONY += doc-uninstall doc-uninstall: $(call descend,Documentation,uninstall) PHONY += help help: @echo 'Possible targets:' @echo'' @echo ' all - default, compile the library and the'\ 'plugins' @echo ' plugins - compile the plugins' @echo ' install - install the library, the plugins,'\ 'the header and pkgconfig files' @echo ' clean - clean the library and the plugins object files' @echo ' doc - compile the documentation files - man'\ 'and html pages, in the Documentation directory' @echo ' doc-clean - clean the documentation files' @echo ' doc-install - install the man pages' @echo ' doc-uninstall - uninstall the man pages' @echo'' PHONY += plugins plugins: $(call descend,plugins) PHONY += install_plugins install_plugins: $(call descend,plugins,install) PHONY += clean_plugins clean_plugins: $(call descend,plugins,clean) force: # Declare the contents of the .PHONY variable as phony. We keep that # information in a variable so we can use it in if_changed and friends. .PHONY: $(PHONY) PK ! w��j� � ! traceevent/Documentation/Makefilenu �[��� include ../../../scripts/Makefile.include include ../../../scripts/utilities.mak # This Makefile and manpage XSL files were taken from tools/perf/Documentation # and modified for libtraceevent. MAN3_TXT= \ $(wildcard libtraceevent-*.txt) \ libtraceevent.txt MAN_TXT = $(MAN3_TXT) _MAN_XML=$(patsubst %.txt,%.xml,$(MAN_TXT)) _MAN_HTML=$(patsubst %.txt,%.html,$(MAN_TXT)) _DOC_MAN3=$(patsubst %.txt,%.3,$(MAN3_TXT)) MAN_XML=$(addprefix $(OUTPUT),$(_MAN_XML)) MAN_HTML=$(addprefix $(OUTPUT),$(_MAN_HTML)) DOC_MAN3=$(addprefix $(OUTPUT),$(_DOC_MAN3)) # Make the path relative to DESTDIR, not prefix ifndef DESTDIR prefix?=$(HOME) endif bindir?=$(prefix)/bin htmldir?=$(prefix)/share/doc/libtraceevent-doc pdfdir?=$(prefix)/share/doc/libtraceevent-doc mandir?=$(prefix)/share/man man3dir=$(mandir)/man3 ASCIIDOC=asciidoc ASCIIDOC_EXTRA = --unsafe -f asciidoc.conf ASCIIDOC_HTML = xhtml11 MANPAGE_XSL = manpage-normal.xsl XMLTO_EXTRA = INSTALL?=install RM ?= rm -f ifdef USE_ASCIIDOCTOR ASCIIDOC = asciidoctor ASCIIDOC_EXTRA = -a compat-mode ASCIIDOC_EXTRA += -I. -rasciidoctor-extensions ASCIIDOC_EXTRA += -a mansource="libtraceevent" -a manmanual="libtraceevent Manual" ASCIIDOC_HTML = xhtml5 endif XMLTO=xmlto _tmp_tool_path := $(call get-executable,$(ASCIIDOC)) ifeq ($(_tmp_tool_path),) missing_tools = $(ASCIIDOC) endif ifndef USE_ASCIIDOCTOR _tmp_tool_path := $(call get-executable,$(XMLTO)) ifeq ($(_tmp_tool_path),) missing_tools += $(XMLTO) endif endif # # For asciidoc ... # -7.1.2, no extra settings are needed. # 8.0-, set ASCIIDOC8. # # # For docbook-xsl ... # -1.68.1, set ASCIIDOC_NO_ROFF? (based on changelog from 1.73.0) # 1.69.0, no extra settings are needed? # 1.69.1-1.71.0, set DOCBOOK_SUPPRESS_SP? # 1.71.1, no extra settings are needed? # 1.72.0, set DOCBOOK_XSL_172. # 1.73.0-, set ASCIIDOC_NO_ROFF # # # If you had been using DOCBOOK_XSL_172 in an attempt to get rid # of 'the ".ft C" problem' in your generated manpages, and you # instead ended up with weird characters around callouts, try # using ASCIIDOC_NO_ROFF instead (it works fine with ASCIIDOC8). # ifdef ASCIIDOC8 ASCIIDOC_EXTRA += -a asciidoc7compatible endif ifdef DOCBOOK_XSL_172 ASCIIDOC_EXTRA += -a libtraceevent-asciidoc-no-roff MANPAGE_XSL = manpage-1.72.xsl else ifdef ASCIIDOC_NO_ROFF # docbook-xsl after 1.72 needs the regular XSL, but will not # pass-thru raw roff codes from asciidoc.conf, so turn them off. ASCIIDOC_EXTRA += -a libtraceevent-asciidoc-no-roff endif endif ifdef MAN_BOLD_LITERAL XMLTO_EXTRA += -m manpage-bold-literal.xsl endif ifdef DOCBOOK_SUPPRESS_SP XMLTO_EXTRA += -m manpage-suppress-sp.xsl endif SHELL_PATH ?= $(SHELL) # Shell quote; SHELL_PATH_SQ = $(subst ','\'',$(SHELL_PATH)) DESTDIR ?= DESTDIR_SQ = '$(subst ','\'',$(DESTDIR))' export DESTDIR DESTDIR_SQ # # Please note that there is a minor bug in asciidoc. # The version after 6.0.3 _will_ include the patch found here: # http://marc.theaimsgroup.com/?l=libtraceevent&m=111558757202243&w=2 # # Until that version is released you may have to apply the patch # yourself - yes, all 6 characters of it! # QUIET_SUBDIR0 = +$(MAKE) -C # space to separate -C and subdir QUIET_SUBDIR1 = ifneq ($(findstring $(MAKEFLAGS),w),w) PRINT_DIR = --no-print-directory else # "make -w" NO_SUBDIR = : endif ifneq ($(findstring $(MAKEFLAGS),s),s) ifneq ($(V),1) QUIET_ASCIIDOC = @echo ' ASCIIDOC '$@; QUIET_XMLTO = @echo ' XMLTO '$@; QUIET_SUBDIR0 = +@subdir= QUIET_SUBDIR1 = ;$(NO_SUBDIR) \ echo ' SUBDIR ' $$subdir; \ $(MAKE) $(PRINT_DIR) -C $$subdir export V endif endif all: html man man: man3 man3: $(DOC_MAN3) html: $(MAN_HTML) $(MAN_HTML) $(DOC_MAN3): asciidoc.conf install: install-man check-man-tools: ifdef missing_tools $(error "You need to install $(missing_tools) for man pages") endif do-install-man: man $(call QUIET_INSTALL, Documentation-man) \ $(INSTALL) -d -m 755 $(DESTDIR)$(man3dir); \ $(INSTALL) -m 644 $(DOC_MAN3) $(DESTDIR)$(man3dir); install-man: check-man-tools man do-install-man uninstall: uninstall-man uninstall-man: $(call QUIET_UNINST, Documentation-man) \ $(Q)$(RM) $(addprefix $(DESTDIR)$(man3dir)/,$(DOC_MAN3)) ifdef missing_tools DO_INSTALL_MAN = $(warning Please install $(missing_tools) to have the man pages installed) else DO_INSTALL_MAN = do-install-man endif CLEAN_FILES = \ $(MAN_XML) $(addsuffix +,$(MAN_XML)) \ $(MAN_HTML) $(addsuffix +,$(MAN_HTML)) \ $(DOC_MAN3) *.3 clean: $(call QUIET_CLEAN, Documentation) $(RM) $(CLEAN_FILES) ifdef USE_ASCIIDOCTOR $(OUTPUT)%.3 : $(OUTPUT)%.txt $(QUIET_ASCIIDOC)$(RM) $@+ $@ && \ $(ASCIIDOC) -b manpage -d manpage \ $(ASCIIDOC_EXTRA) -alibtraceevent_version=$(EVENT_PARSE_VERSION) -o $@+ $< && \ mv $@+ $@ endif $(OUTPUT)%.3 : $(OUTPUT)%.xml $(QUIET_XMLTO)$(RM) $@ && \ $(XMLTO) -o $(OUTPUT). -m $(MANPAGE_XSL) $(XMLTO_EXTRA) man $< $(OUTPUT)%.xml : %.txt $(QUIET_ASCIIDOC)$(RM) $@+ $@ && \ $(ASCIIDOC) -b docbook -d manpage \ $(ASCIIDOC_EXTRA) -alibtraceevent_version=$(EVENT_PARSE_VERSION) -o $@+ $< && \ mv $@+ $@ $(MAN_HTML): $(OUTPUT)%.html : %.txt $(QUIET_ASCIIDOC)$(RM) $@+ $@ && \ $(ASCIIDOC) -b $(ASCIIDOC_HTML) -d manpage \ $(ASCIIDOC_EXTRA) -aperf_version=$(EVENT_PARSE_VERSION) -o $@+ $< && \ mv $@+ $@ PK ! �f�8 8 expoline/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-y += expoline.o PK ! '��| | zstd/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_ZSTD_COMPRESS) += zstd_compress.o obj-$(CONFIG_ZSTD_DECOMPRESS) += zstd_decompress.o ccflags-y += -O3 zstd_compress-y := fse_compress.o huf_compress.o compress.o \ entropy_common.o fse_decompress.o zstd_common.o zstd_decompress-y := huf_decompress.o decompress.o \ entropy_common.o fse_decompress.o zstd_common.o PK ! ��� Kconfig.kasannu �[��� # SPDX-License-Identifier: GPL-2.0-only # This config refers to the generic KASAN mode. config HAVE_ARCH_KASAN bool config HAVE_ARCH_KASAN_SW_TAGS bool config HAVE_ARCH_KASAN_HW_TAGS bool config HAVE_ARCH_KASAN_VMALLOC bool config ARCH_DISABLE_KASAN_INLINE bool help An architecture might not support inline instrumentation. When this option is selected, inline and stack instrumentation are disabled. config CC_HAS_KASAN_GENERIC def_bool $(cc-option, -fsanitize=kernel-address) config CC_HAS_KASAN_SW_TAGS def_bool $(cc-option, -fsanitize=kernel-hwaddress) # This option is only required for software KASAN modes. # Old GCC versions don't have proper support for no_sanitize_address. # See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89124 for details. config CC_HAS_WORKING_NOSANITIZE_ADDRESS def_bool !CC_IS_GCC || GCC_VERSION >= 80300 menuconfig KASAN bool "KASAN: runtime memory debugger" depends on (((HAVE_ARCH_KASAN && CC_HAS_KASAN_GENERIC) || \ (HAVE_ARCH_KASAN_SW_TAGS && CC_HAS_KASAN_SW_TAGS)) && \ CC_HAS_WORKING_NOSANITIZE_ADDRESS) || \ HAVE_ARCH_KASAN_HW_TAGS depends on (SLUB && SYSFS) || (SLAB && !DEBUG_SLAB) select STACKDEPOT help Enables KASAN (KernelAddressSANitizer) - runtime memory debugger, designed to find out-of-bounds accesses and use-after-free bugs. See Documentation/dev-tools/kasan.rst for details. if KASAN choice prompt "KASAN mode" default KASAN_GENERIC help KASAN has three modes: 1. generic KASAN (similar to userspace ASan, x86_64/arm64/xtensa, enabled with CONFIG_KASAN_GENERIC), 2. software tag-based KASAN (arm64 only, based on software memory tagging (similar to userspace HWASan), enabled with CONFIG_KASAN_SW_TAGS), and 3. hardware tag-based KASAN (arm64 only, based on hardware memory tagging, enabled with CONFIG_KASAN_HW_TAGS). All KASAN modes are strictly debugging features. For better error reports enable CONFIG_STACKTRACE. config KASAN_GENERIC bool "Generic mode" depends on HAVE_ARCH_KASAN && CC_HAS_KASAN_GENERIC depends on CC_HAS_WORKING_NOSANITIZE_ADDRESS select SLUB_DEBUG if SLUB select CONSTRUCTORS help Enables generic KASAN mode. This mode is supported in both GCC and Clang. With GCC it requires version 8.3.0 or later. Any supported Clang version is compatible, but detection of out-of-bounds accesses for global variables is supported only since Clang 11. This mode consumes about 1/8th of available memory at kernel start and introduces an overhead of ~x1.5 for the rest of the allocations. The performance slowdown is ~x3. Currently CONFIG_KASAN_GENERIC doesn't work with CONFIG_DEBUG_SLAB (the resulting kernel does not boot). config KASAN_SW_TAGS bool "Software tag-based mode" depends on HAVE_ARCH_KASAN_SW_TAGS && CC_HAS_KASAN_SW_TAGS depends on CC_HAS_WORKING_NOSANITIZE_ADDRESS select SLUB_DEBUG if SLUB select CONSTRUCTORS help Enables software tag-based KASAN mode. This mode require software memory tagging support in the form of HWASan-like compiler instrumentation. Currently this mode is only implemented for arm64 CPUs and relies on Top Byte Ignore. This mode requires Clang. This mode consumes about 1/16th of available memory at kernel start and introduces an overhead of ~20% for the rest of the allocations. This mode may potentially introduce problems relating to pointer casting and comparison, as it embeds tags into the top byte of each pointer. Currently CONFIG_KASAN_SW_TAGS doesn't work with CONFIG_DEBUG_SLAB (the resulting kernel does not boot). config KASAN_HW_TAGS bool "Hardware tag-based mode" depends on HAVE_ARCH_KASAN_HW_TAGS depends on SLUB help Enables hardware tag-based KASAN mode. This mode requires hardware memory tagging support, and can be used by any architecture that provides it. Currently this mode is only implemented for arm64 CPUs starting from ARMv8.5 and relies on Memory Tagging Extension and Top Byte Ignore. endchoice choice prompt "Instrumentation type" depends on KASAN_GENERIC || KASAN_SW_TAGS default KASAN_OUTLINE config KASAN_OUTLINE bool "Outline instrumentation" help Before every memory access compiler insert function call __asan_load*/__asan_store*. These functions performs check of shadow memory. This is slower than inline instrumentation, however it doesn't bloat size of kernel's .text section so much as inline does. config KASAN_INLINE bool "Inline instrumentation" depends on !ARCH_DISABLE_KASAN_INLINE help Compiler directly inserts code checking shadow memory before memory accesses. This is faster than outline (in some workloads it gives about x2 boost over outline instrumentation), but make kernel's .text size much bigger. endchoice config KASAN_STACK bool "Enable stack instrumentation (unsafe)" if CC_IS_CLANG && !COMPILE_TEST depends on KASAN_GENERIC || KASAN_SW_TAGS depends on !ARCH_DISABLE_KASAN_INLINE default y if CC_IS_GCC help The LLVM stack address sanitizer has a know problem that causes excessive stack usage in a lot of functions, see https://bugs.llvm.org/show_bug.cgi?id=38809 Disabling asan-stack makes it safe to run kernels build with clang-8 with KASAN enabled, though it loses some of the functionality. This feature is always disabled when compile-testing with clang to avoid cluttering the output in stack overflow warnings, but clang users can still enable it for builds without CONFIG_COMPILE_TEST. On gcc it is assumed to always be safe to use and enabled by default. If the architecture disables inline instrumentation, stack instrumentation is also disabled as it adds inline-style instrumentation that is run unconditionally. config KASAN_TAGS_IDENTIFY bool "Enable memory corruption identification" depends on KASAN_SW_TAGS || KASAN_HW_TAGS help This option enables best-effort identification of bug type (use-after-free or out-of-bounds) at the cost of increased memory consumption. config KASAN_VMALLOC bool "Back mappings in vmalloc space with real shadow memory" depends on KASAN_GENERIC && HAVE_ARCH_KASAN_VMALLOC help By default, the shadow region for vmalloc space is the read-only zero page. This means that KASAN cannot detect errors involving vmalloc space. Enabling this option will hook in to vmap/vmalloc and back those mappings with real shadow memory allocated on demand. This allows for KASAN to detect more sorts of errors (and to support vmapped stacks), but at the cost of higher memory usage. config KASAN_KUNIT_TEST tristate "KUnit-compatible tests of KASAN bug detection capabilities" if !KUNIT_ALL_TESTS depends on KASAN && KUNIT default KUNIT_ALL_TESTS help This is a KUnit test suite doing various nasty things like out of bounds and use after free accesses. It is useful for testing kernel debugging features like KASAN. For more information on KUnit and unit tests in general, please refer to the KUnit documentation in Documentation/dev-tools/kunit. config KASAN_MODULE_TEST tristate "KUnit-incompatible tests of KASAN bug detection capabilities" depends on m && KASAN && !KASAN_HW_TAGS help This is a part of the KASAN test suite that is incompatible with KUnit. Currently includes tests that do bad copy_from/to_user accesses. endif # KASAN PK ! �@@� kunit/Kconfignu �[��� # # KUnit base configuration # menuconfig KUNIT tristate "KUnit - Enable support for unit tests" select GLOB if KUNIT=y help Enables support for kernel unit tests (KUnit), a lightweight unit testing and mocking framework for the Linux kernel. These tests are able to be run locally on a developer's workstation without a VM or special hardware when using UML. Can also be used on most other architectures. For more information, please see Documentation/dev-tools/kunit/. if KUNIT config KUNIT_DEBUGFS bool "KUnit - Enable /sys/kernel/debug/kunit debugfs representation" if !KUNIT_ALL_TESTS default KUNIT_ALL_TESTS help Enable debugfs representation for kunit. Currently this consists of /sys/kernel/debug/kunit/<test_suite>/results files for each test suite, which allow users to see results of the last test suite run that occurred. config KUNIT_TEST tristate "KUnit test for KUnit" if !KUNIT_ALL_TESTS default KUNIT_ALL_TESTS help Enables the unit tests for the KUnit test framework. These tests test the KUnit test framework itself; the tests are both written using KUnit and test KUnit. This option should only be enabled for testing purposes by developers interested in testing that KUnit works as expected. config KUNIT_EXAMPLE_TEST tristate "Example test for KUnit" if !KUNIT_ALL_TESTS default KUNIT_ALL_TESTS help Enables an example unit test that illustrates some of the basic features of KUnit. This test only exists to help new users understand what KUnit is and how it is used. Please refer to the example test itself, lib/kunit/example-test.c, for more information. This option is intended for curious hackers who would like to understand how to use KUnit for kernel development. config KUNIT_ALL_TESTS tristate "All KUnit tests with satisfied dependencies" help Enables all KUnit tests, if they can be enabled. KUnit tests run during boot and output the results to the debug log in TAP format (http://testanything.org/). Only useful for kernel devs running the KUnit test harness, and not intended 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. endif # KUNIT PK ! t�!� � kunit/Makefilenu �[��� obj-$(CONFIG_KUNIT) += kunit.o kunit-objs += test.o \ string-stream.o \ assert.o \ try-catch.o \ executor.o ifeq ($(CONFIG_KUNIT_DEBUGFS),y) kunit-objs += debugfs.o endif obj-$(CONFIG_KUNIT_TEST) += kunit-test.o # string-stream-test compiles built-in only. ifeq ($(CONFIG_KUNIT_TEST),y) obj-$(CONFIG_KUNIT_TEST) += string-stream-test.o endif obj-$(CONFIG_KUNIT_EXAMPLE_TEST) += kunit-example-test.o PK ! �u�% % zlib_dfltcc/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # This is a modified version of zlib, which does all memory # allocation ahead of time. # # This is the code for s390 zlib hardware support. # obj-$(CONFIG_ZLIB_DFLTCC) += zlib_dfltcc.o zlib_dfltcc-objs := dfltcc.o dfltcc_deflate.o dfltcc_inflate.o PK ! ����p p crypto/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0 menu "Crypto library routines" config CRYPTO_LIB_AES tristate config CRYPTO_LIB_ARC4 tristate config CRYPTO_ARCH_HAVE_LIB_BLAKE2S bool help Declares whether the architecture provides an arch-specific accelerated implementation of the Blake2s library interface, either builtin or as a module. config CRYPTO_LIB_BLAKE2S_GENERIC def_bool !CRYPTO_ARCH_HAVE_LIB_BLAKE2S help This symbol can be depended upon by arch implementations of the Blake2s library interface that require the generic code as a fallback, e.g., for SIMD implementations. If no arch specific implementation is enabled, this implementation serves the users of CRYPTO_LIB_BLAKE2S. config CRYPTO_ARCH_HAVE_LIB_CHACHA tristate help Declares whether the architecture provides an arch-specific accelerated implementation of the ChaCha library interface, either builtin or as a module. config CRYPTO_LIB_CHACHA_GENERIC tristate help This symbol can be depended upon by arch implementations of the ChaCha library interface that require the generic code as a fallback, e.g., for SIMD implementations. If no arch specific implementation is enabled, this implementation serves the users of CRYPTO_LIB_CHACHA. config CRYPTO_LIB_CHACHA tristate "ChaCha library interface" depends on CRYPTO depends on CRYPTO_ARCH_HAVE_LIB_CHACHA || !CRYPTO_ARCH_HAVE_LIB_CHACHA select CRYPTO_LIB_CHACHA_GENERIC if CRYPTO_ARCH_HAVE_LIB_CHACHA=n help Enable the ChaCha library interface. This interface may be fulfilled by either the generic implementation or an arch-specific one, if one is available and enabled. config CRYPTO_ARCH_HAVE_LIB_CURVE25519 tristate help Declares whether the architecture provides an arch-specific accelerated implementation of the Curve25519 library interface, either builtin or as a module. config CRYPTO_LIB_CURVE25519_GENERIC tristate help This symbol can be depended upon by arch implementations of the Curve25519 library interface that require the generic code as a fallback, e.g., for SIMD implementations. If no arch specific implementation is enabled, this implementation serves the users of CRYPTO_LIB_CURVE25519. config CRYPTO_LIB_CURVE25519 tristate "Curve25519 scalar multiplication library" depends on CRYPTO_ARCH_HAVE_LIB_CURVE25519 || !CRYPTO_ARCH_HAVE_LIB_CURVE25519 select CRYPTO_LIB_CURVE25519_GENERIC if CRYPTO_ARCH_HAVE_LIB_CURVE25519=n select LIB_MEMNEQ help Enable the Curve25519 library interface. This interface may be fulfilled by either the generic implementation or an arch-specific one, if one is available and enabled. config CRYPTO_LIB_DES tristate config CRYPTO_LIB_POLY1305_RSIZE int default 2 if MIPS default 11 if X86_64 default 9 if ARM || ARM64 default 1 config CRYPTO_ARCH_HAVE_LIB_POLY1305 tristate help Declares whether the architecture provides an arch-specific accelerated implementation of the Poly1305 library interface, either builtin or as a module. config CRYPTO_LIB_POLY1305_GENERIC tristate help This symbol can be depended upon by arch implementations of the Poly1305 library interface that require the generic code as a fallback, e.g., for SIMD implementations. If no arch specific implementation is enabled, this implementation serves the users of CRYPTO_LIB_POLY1305. config CRYPTO_LIB_POLY1305 tristate "Poly1305 library interface" depends on CRYPTO_ARCH_HAVE_LIB_POLY1305 || !CRYPTO_ARCH_HAVE_LIB_POLY1305 select CRYPTO_LIB_POLY1305_GENERIC if CRYPTO_ARCH_HAVE_LIB_POLY1305=n help Enable the Poly1305 library interface. This interface may be fulfilled by either the generic implementation or an arch-specific one, if one is available and enabled. config CRYPTO_LIB_CHACHA20POLY1305 tristate "ChaCha20-Poly1305 AEAD support (8-byte nonce library version)" depends on CRYPTO_ARCH_HAVE_LIB_CHACHA || !CRYPTO_ARCH_HAVE_LIB_CHACHA depends on CRYPTO_ARCH_HAVE_LIB_POLY1305 || !CRYPTO_ARCH_HAVE_LIB_POLY1305 depends on CRYPTO select CRYPTO_LIB_CHACHA select CRYPTO_LIB_POLY1305 select CRYPTO_ALGAPI config CRYPTO_LIB_SHA256 tristate config CRYPTO_LIB_SM4 tristate endmenu PK ! :�o@� � crypto/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # chacha is used by the /dev/random driver which is always builtin obj-y += chacha.o obj-$(CONFIG_CRYPTO_LIB_CHACHA_GENERIC) += libchacha.o obj-$(CONFIG_CRYPTO_LIB_AES) += libaes.o libaes-y := aes.o obj-$(CONFIG_CRYPTO_LIB_ARC4) += libarc4.o libarc4-y := arc4.o # blake2s is used by the /dev/random driver which is always builtin obj-y += libblake2s.o libblake2s-y := blake2s.o libblake2s-$(CONFIG_CRYPTO_LIB_BLAKE2S_GENERIC) += blake2s-generic.o obj-$(CONFIG_CRYPTO_LIB_CHACHA20POLY1305) += libchacha20poly1305.o libchacha20poly1305-y += chacha20poly1305.o obj-$(CONFIG_CRYPTO_LIB_CURVE25519_GENERIC) += libcurve25519-generic.o libcurve25519-generic-y := curve25519-fiat32.o libcurve25519-generic-$(CONFIG_ARCH_SUPPORTS_INT128) := curve25519-hacl64.o libcurve25519-generic-y += curve25519-generic.o # clang versions prior to 18 may blow out the stack with KASAN ifeq ($(CONFIG_CC_IS_CLANG)_$(call clang-min-version, 180000),y_) KASAN_SANITIZE_curve25519-hacl64.o := n endif obj-$(CONFIG_CRYPTO_LIB_CURVE25519) += libcurve25519.o libcurve25519-y += curve25519.o obj-$(CONFIG_CRYPTO_LIB_DES) += libdes.o libdes-y := des.o obj-$(CONFIG_CRYPTO_LIB_POLY1305_GENERIC) += libpoly1305.o libpoly1305-y := poly1305-donna32.o libpoly1305-$(CONFIG_ARCH_SUPPORTS_INT128) := poly1305-donna64.o libpoly1305-y += poly1305.o obj-$(CONFIG_CRYPTO_LIB_SHA256) += libsha256.o libsha256-y := sha256.o obj-$(CONFIG_CRYPTO_LIB_SM4) += libsm4.o libsm4-y := sm4.o ifneq ($(CONFIG_CRYPTO_MANAGER_DISABLE_TESTS),y) libblake2s-y += blake2s-selftest.o libchacha20poly1305-y += chacha20poly1305-selftest.o libcurve25519-y += curve25519-selftest.o endif PK ! �>�~�% �% Kconfig.kcsannu �[��� # SPDX-License-Identifier: GPL-2.0-only config HAVE_ARCH_KCSAN bool config HAVE_KCSAN_COMPILER def_bool (CC_IS_CLANG && $(cc-option,-fsanitize=thread -mllvm -tsan-distinguish-volatile=1)) || \ (CC_IS_GCC && $(cc-option,-fsanitize=thread --param tsan-distinguish-volatile=1)) help For the list of compilers that support KCSAN, please see <file:Documentation/dev-tools/kcsan.rst>. config KCSAN_KCOV_BROKEN def_bool KCOV && CC_HAS_SANCOV_TRACE_PC depends on CC_IS_CLANG depends on !$(cc-option,-Werror=unused-command-line-argument -fsanitize=thread -fsanitize-coverage=trace-pc) help Some versions of clang support either KCSAN and KCOV but not the combination of the two. See https://bugs.llvm.org/show_bug.cgi?id=45831 for the status in newer releases. menuconfig KCSAN bool "KCSAN: dynamic data race detector" depends on HAVE_ARCH_KCSAN && HAVE_KCSAN_COMPILER depends on DEBUG_KERNEL && !KASAN depends on !KCSAN_KCOV_BROKEN select STACKTRACE help The Kernel Concurrency Sanitizer (KCSAN) is a dynamic data-race detector that relies on compile-time instrumentation. KCSAN uses a watchpoint-based sampling approach to detect races. While KCSAN's primary purpose is to detect data races, it also provides assertions to check data access constraints. These assertions can expose bugs that do not manifest as data races. See <file:Documentation/dev-tools/kcsan.rst> for more details. if KCSAN config CC_HAS_TSAN_COMPOUND_READ_BEFORE_WRITE def_bool (CC_IS_CLANG && $(cc-option,-fsanitize=thread -mllvm -tsan-compound-read-before-write=1)) || \ (CC_IS_GCC && $(cc-option,-fsanitize=thread --param tsan-compound-read-before-write=1)) help The compiler instruments plain compound read-write operations differently (++, --, +=, -=, |=, &=, etc.), which allows KCSAN to distinguish them from other plain accesses. This is currently supported by Clang 12 or later. config KCSAN_VERBOSE bool "Show verbose reports with more information about system state" depends on PROVE_LOCKING help If enabled, reports show more information about the system state that may help better analyze and debug races. This includes held locks and IRQ trace events. While this option should generally be benign, we call into more external functions on report generation; if a race report is generated from any one of them, system stability may suffer due to deadlocks or recursion. If in doubt, say N. config KCSAN_SELFTEST bool "Perform short selftests on boot" default y help Run KCSAN selftests on boot. On test failure, causes the kernel to panic. Recommended to be enabled, ensuring critical functionality works as intended. config KCSAN_KUNIT_TEST tristate "KCSAN test for integrated runtime behaviour" if !KUNIT_ALL_TESTS default KUNIT_ALL_TESTS depends on TRACEPOINTS && KUNIT select TORTURE_TEST help KCSAN test focusing on behaviour of the integrated runtime. Tests various race scenarios, and verifies the reports generated to console. Makes use of KUnit for test organization, and the Torture framework for test thread control. Each test case may run at least up to KCSAN_REPORT_ONCE_IN_MS milliseconds. Test run duration may be optimized by building the kernel and KCSAN test with KCSAN_REPORT_ONCE_IN_MS set to a lower than default value. Say Y here if you want the test to be built into the kernel and run during boot; say M if you want the test to build as a module; say N if you are unsure. config KCSAN_EARLY_ENABLE bool "Early enable during boot" default y help If KCSAN should be enabled globally as soon as possible. KCSAN can later be enabled/disabled via debugfs. config KCSAN_NUM_WATCHPOINTS int "Number of available watchpoints" default 64 help Total number of available watchpoints. An address range maps into a specific watchpoint slot as specified in kernel/kcsan/encoding.h. Although larger number of watchpoints may not be usable due to limited number of CPUs, a larger value helps to improve performance due to reducing cache-line contention. The chosen default is a conservative value; we should almost never observe "no_capacity" events (see /sys/kernel/debug/kcsan). config KCSAN_UDELAY_TASK int "Delay in microseconds (for tasks)" default 80 help For tasks, the microsecond delay after setting up a watchpoint. config KCSAN_UDELAY_INTERRUPT int "Delay in microseconds (for interrupts)" default 20 help For interrupts, the microsecond delay after setting up a watchpoint. Interrupts have tighter latency requirements, and their delay should be lower than for tasks. config KCSAN_DELAY_RANDOMIZE bool "Randomize above delays" default y help If delays should be randomized, where the maximum is KCSAN_UDELAY_*. If false, the chosen delays are always the KCSAN_UDELAY_* values as defined above. config KCSAN_SKIP_WATCH int "Skip instructions before setting up watchpoint" default 4000 help The number of per-CPU memory operations to skip, before another watchpoint is set up, i.e. one in KCSAN_WATCH_SKIP per-CPU memory operations are used to set up a watchpoint. A smaller value results in more aggressive race detection, whereas a larger value improves system performance at the cost of missing some races. config KCSAN_SKIP_WATCH_RANDOMIZE bool "Randomize watchpoint instruction skip count" default y help If instruction skip count should be randomized, where the maximum is KCSAN_WATCH_SKIP. If false, the chosen value is always KCSAN_WATCH_SKIP. config KCSAN_INTERRUPT_WATCHER bool "Interruptible watchers" if !KCSAN_STRICT default KCSAN_STRICT help If enabled, a task that set up a watchpoint may be interrupted while delayed. This option will allow KCSAN to detect races between interrupted tasks and other threads of execution on the same CPU. Currently disabled by default, because not all safe per-CPU access primitives and patterns may be accounted for, and therefore could result in false positives. config KCSAN_REPORT_ONCE_IN_MS int "Duration in milliseconds, in which any given race is only reported once" default 3000 help Any given race is only reported once in the defined time window. Different races may still generate reports within a duration that is smaller than the duration defined here. This allows rate limiting reporting to avoid flooding the console with reports. Setting this to 0 disables rate limiting. # The main purpose of the below options is to control reported data races, and # are not expected to be switched frequently by non-testers or at runtime. # The defaults are chosen to be conservative, and can miss certain bugs. config KCSAN_REPORT_RACE_UNKNOWN_ORIGIN bool "Report races of unknown origin" default y help If KCSAN should report races where only one access is known, and the conflicting access is of unknown origin. This type of race is reported if it was only possible to infer a race due to a data value change while an access is being delayed on a watchpoint. config KCSAN_STRICT bool "Strict data-race checking" help KCSAN will report data races with the strictest possible rules, which closely aligns with the rules defined by the Linux-kernel memory consistency model (LKMM). config KCSAN_REPORT_VALUE_CHANGE_ONLY bool "Only report races where watcher observed a data value change" default y depends on !KCSAN_STRICT help If enabled and a conflicting write is observed via a watchpoint, but the data value of the memory location was observed to remain unchanged, do not report the data race. config KCSAN_ASSUME_PLAIN_WRITES_ATOMIC bool "Assume that plain aligned writes up to word size are atomic" default y depends on !KCSAN_STRICT help Assume that plain aligned writes up to word size are atomic by default, and also not subject to other unsafe compiler optimizations resulting in data races. This will cause KCSAN to not report data races due to conflicts where the only plain accesses are aligned writes up to word size: conflicts between marked reads and plain aligned writes up to word size will not be reported as data races; notice that data races between two conflicting plain aligned writes will also not be reported. config KCSAN_IGNORE_ATOMICS bool "Do not instrument marked atomic accesses" depends on !KCSAN_STRICT help Never instrument marked atomic accesses. This option can be used for additional filtering. Conflicting marked atomic reads and plain writes will never be reported as a data race, however, will cause plain reads and marked writes to result in "unknown origin" reports. If combined with CONFIG_KCSAN_REPORT_RACE_UNKNOWN_ORIGIN=n, data races where at least one access is marked atomic will never be reported. Similar to KCSAN_ASSUME_PLAIN_WRITES_ATOMIC, but including unaligned accesses, conflicting marked atomic reads and plain writes will not be reported as data races; however, unlike that option, data races due to two conflicting plain writes will be reported (aligned and unaligned, if CONFIG_KCSAN_ASSUME_PLAIN_WRITES_ATOMIC=n). config KCSAN_PERMISSIVE bool "Enable all additional permissive rules" depends on KCSAN_REPORT_VALUE_CHANGE_ONLY help Enable additional permissive rules to ignore certain classes of data races (also see kernel/kcsan/permissive.h). None of the permissive rules imply that such data races are generally safe, but can be used to further reduce reported data races due to data-racy patterns common across the kernel. endif # KCSAN PK ! L��� � vdso/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0 config HAVE_GENERIC_VDSO bool if HAVE_GENERIC_VDSO config GENERIC_GETTIMEOFDAY bool help This is a generic implementation of gettimeofday vdso. Each architecture that enables this feature has to provide the fallback implementation. config GENERIC_VDSO_32 bool depends on GENERIC_GETTIMEOFDAY && !64BIT help This config option helps to avoid possible performance issues in 32 bit only architectures. config GENERIC_COMPAT_VDSO bool help This config option enables the compat VDSO layer. config GENERIC_VDSO_TIME_NS bool help Selected by architectures which support time namespaces in the VDSO endif PK ! A��| | vdso/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 GENERIC_VDSO_MK_PATH := $(abspath $(lastword $(MAKEFILE_LIST))) GENERIC_VDSO_DIR := $(dir $(GENERIC_VDSO_MK_PATH)) c-gettimeofday-$(CONFIG_GENERIC_GETTIMEOFDAY) := $(addprefix $(GENERIC_VDSO_DIR), gettimeofday.c) # This cmd checks that the vdso library does not contain absolute relocation # It has to be called after the linking of the vdso library and requires it # as a parameter. # # $(ARCH_REL_TYPE_ABS) is defined in the arch specific makefile and corresponds # to the absolute relocation types printed by "objdump -R" and accepted by the # dynamic linker. ifndef ARCH_REL_TYPE_ABS $(error ARCH_REL_TYPE_ABS is not set) endif quiet_cmd_vdso_check = VDSOCHK $@ cmd_vdso_check = if $(OBJDUMP) -R $@ | grep -E -h "$(ARCH_REL_TYPE_ABS)"; \ then (echo >&2 "$@: dynamic relocations are not supported"; \ rm -f $@; /bin/false); fi PK ! #{�sL L Kconfig.kgdbnu �[��� # SPDX-License-Identifier: GPL-2.0-only config HAVE_ARCH_KGDB bool # set if architecture has the its kgdb_arch_handle_qxfer_pkt # function to enable gdb stub to address XML packet sent from GDB. config HAVE_ARCH_KGDB_QXFER_PKT bool menuconfig KGDB bool "KGDB: kernel debugger" depends on HAVE_ARCH_KGDB depends on DEBUG_KERNEL help If you say Y here, it will be possible to remotely debug the kernel using gdb. It is recommended but not required, that you also turn on the kernel config option CONFIG_FRAME_POINTER to aid in producing more reliable stack backtraces in the external debugger. Documentation of kernel debugger is available at http://kgdb.sourceforge.net as well as in Documentation/dev-tools/kgdb.rst. If unsure, say N. if KGDB config KGDB_HONOUR_BLOCKLIST bool "KGDB: use kprobe blocklist to prohibit unsafe breakpoints" depends on HAVE_KPROBES depends on MODULES select KPROBES default y help If set to Y the debug core will use the kprobe blocklist to identify symbols where it is unsafe to set breakpoints. In particular this disallows instrumentation of functions called during debug trap handling and thus makes it very difficult to inadvertently provoke recursive trap handling. If unsure, say Y. config KGDB_SERIAL_CONSOLE tristate "KGDB: use kgdb over the serial console" select CONSOLE_POLL select MAGIC_SYSRQ depends on TTY && HW_CONSOLE default y help Share a serial console with kgdb. Sysrq-g must be used to break in initially. config KGDB_TESTS bool "KGDB: internal test suite" default n help This is a kgdb I/O module specifically designed to test kgdb's internal functions. This kgdb I/O module is intended to for the development of new kgdb stubs as well as regression testing the kgdb internals. See the drivers/misc/kgdbts.c for the details about the tests. The most basic of this I/O module is to boot a kernel boot arguments "kgdbwait kgdbts=V1F100" config KGDB_TESTS_ON_BOOT bool "KGDB: Run tests on boot" depends on KGDB_TESTS default n help Run the kgdb tests on boot up automatically without the need to pass in a kernel parameter config KGDB_TESTS_BOOT_STRING string "KGDB: which internal kgdb tests to run" depends on KGDB_TESTS_ON_BOOT default "V1F100" help This is the command string to send the kgdb test suite on boot. See the drivers/misc/kgdbts.c for detailed information about other strings you could use beyond the default of V1F100. config KGDB_LOW_LEVEL_TRAP bool "KGDB: Allow debugging with traps in notifiers" depends on X86 || MIPS default n help This will add an extra call back to kgdb for the breakpoint exception handler which will allow kgdb to step through a notify handler. config KGDB_KDB bool "KGDB_KDB: include kdb frontend for kgdb" default n help KDB frontend for kernel config KDB_DEFAULT_ENABLE hex "KDB: Select kdb command functions to be enabled by default" depends on KGDB_KDB default 0x1 help Specifiers which kdb commands are enabled by default. This may be set to 1 or 0 to enable all commands or disable almost all commands. Alternatively the following bitmask applies: 0x0002 - allow arbitrary reads from memory and symbol lookup 0x0004 - allow arbitrary writes to memory 0x0008 - allow current register state to be inspected 0x0010 - allow current register state to be modified 0x0020 - allow passive inspection (backtrace, process list, lsmod) 0x0040 - allow flow control management (breakpoint, single step) 0x0080 - enable signalling of processes 0x0100 - allow machine to be rebooted The config option merely sets the default at boot time. Both issuing 'echo X > /sys/module/kdb/parameters/cmd_enable' or setting with kdb.cmd_enable=X kernel command line option will override the default settings. config KDB_KEYBOARD bool "KGDB_KDB: keyboard as input device" depends on VT && KGDB_KDB default n help KDB can use a PS/2 type keyboard for an input device config KDB_CONTINUE_CATASTROPHIC int "KDB: continue after catastrophic errors" depends on KGDB_KDB default "0" help This integer controls the behaviour of kdb when the kernel gets a catastrophic error, i.e. for a panic or oops. When KDB is active and a catastrophic error occurs, nothing extra will happen until you type 'go'. CONFIG_KDB_CONTINUE_CATASTROPHIC == 0 (default). The first time you type 'go', you will be warned by kdb. The secend time you type 'go', KDB tries to continue. No guarantees that the kernel is still usable in this situation. CONFIG_KDB_CONTINUE_CATASTROPHIC == 1. KDB tries to continue. No guarantees that the kernel is still usable in this situation. CONFIG_KDB_CONTINUE_CATASTROPHIC == 2. KDB forces a reboot. If you are not sure, say 0. config ARCH_HAS_EARLY_DEBUG bool default n help If an architecture can definitely handle entering the debugger when early_param's are parsed then it select this config. Otherwise, if "kgdbwait" is passed on the kernel command line it won't actually be processed until dbg_late_init() just after the call to kgdb_arch_late() is made. NOTE: Even if this isn't selected by an architecture we will still try to register kgdb to handle breakpoints and crashes when early_param's are parsed, we just won't act on the "kgdbwait" parameter until dbg_late_init(). If you get a crash and try to drop into kgdb somewhere between these two places you might or might not end up being able to use kgdb depending on exactly how far along the architecture has initted. endif # KGDB PK ! 6�� C C Kconfig.kfencenu �[��� # SPDX-License-Identifier: GPL-2.0-only config HAVE_ARCH_KFENCE bool menuconfig KFENCE bool "KFENCE: low-overhead sampling-based memory safety error detector" depends on HAVE_ARCH_KFENCE && (SLAB || SLUB) select STACKTRACE select IRQ_WORK help KFENCE is a low-overhead sampling-based detector of heap out-of-bounds access, use-after-free, and invalid-free errors. KFENCE is designed to have negligible cost to permit enabling it in production environments. See <file:Documentation/dev-tools/kfence.rst> for more details. Note that, KFENCE is not a substitute for explicit testing with tools such as KASAN. KFENCE can detect a subset of bugs that KASAN can detect, albeit at very different performance profiles. If you can afford to use KASAN, continue using KASAN, for example in test environments. If your kernel targets production use, and cannot enable KASAN due to its cost, consider using KFENCE. if KFENCE config KFENCE_SAMPLE_INTERVAL int "Default sample interval in milliseconds" default 100 help The KFENCE sample interval determines the frequency with which heap allocations will be guarded by KFENCE. May be overridden via boot parameter "kfence.sample_interval". Set this to 0 to disable KFENCE by default, in which case only setting "kfence.sample_interval" to a non-zero value enables KFENCE. config KFENCE_NUM_OBJECTS int "Number of guarded objects available" range 1 65535 default 255 help The number of guarded objects available. For each KFENCE object, 2 pages are required; with one containing the object and two adjacent ones used as guard pages. config KFENCE_DEFERRABLE bool "Use a deferrable timer to trigger allocations" help Use a deferrable timer to trigger allocations. This avoids forcing CPU wake-ups if the system is idle, at the risk of a less predictable sample interval. Warning: The KUnit test suite fails with this option enabled - due to the unpredictability of the sample interval! Say N if you are unsure. config KFENCE_STATIC_KEYS bool "Use static keys to set up allocations" if EXPERT depends on JUMP_LABEL help Use static keys (static branches) to set up KFENCE allocations. This option is only recommended when using very large sample intervals, or performance has carefully been evaluated with this option. Using static keys comes with trade-offs that need to be carefully evaluated given target workloads and system architectures. Notably, enabling and disabling static keys invoke IPI broadcasts, the latency and impact of which is much harder to predict than a dynamic branch. Say N if you are unsure. config KFENCE_STRESS_TEST_FAULTS int "Stress testing of fault handling and error reporting" if EXPERT default 0 help The inverse probability with which to randomly protect KFENCE object pages, resulting in spurious use-after-frees. The main purpose of this option is to stress test KFENCE with concurrent error reports and allocations/frees. A value of 0 disables stress testing logic. Only for KFENCE testing; set to 0 if you are not a KFENCE developer. config KFENCE_KUNIT_TEST tristate "KFENCE integration test suite" if !KUNIT_ALL_TESTS default KUNIT_ALL_TESTS depends on TRACEPOINTS && KUNIT help Test suite for KFENCE, testing various error detection scenarios with various allocation types, and checking that reports are correctly output to console. Say Y here if you want the test to be built into the kernel and run during boot; say M if you want the test to build as a module; say N if you are unsure. endif # KFENCE PK ! h�RI I pldmfw/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_PLDMFW) += pldmfw.o PK ! J("� mpi/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # MPI multiprecision maths library (from gpg) # obj-$(CONFIG_MPILIB) = mpi.o mpi-y = \ generic_mpih-lshift.o \ generic_mpih-mul1.o \ generic_mpih-mul2.o \ generic_mpih-mul3.o \ generic_mpih-rshift.o \ generic_mpih-sub1.o \ generic_mpih-add1.o \ ec.o \ mpicoder.o \ mpi-add.o \ mpi-bit.o \ mpi-cmp.o \ mpi-sub-ui.o \ mpi-div.o \ mpi-inv.o \ mpi-mod.o \ mpi-mul.o \ mpih-cmp.o \ mpih-div.o \ mpih-mul.o \ mpi-pow.o \ mpiutil.o PK ! y�~j� � math/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config CORDIC tristate "CORDIC algorithm" help This option provides an implementation of the CORDIC algorithm; calculations are in fixed point. Module will be called cordic. config PRIME_NUMBERS tristate "Simple prime number generator for testing" help This option provides a simple prime number generator for test modules. If unsure, say N. config RATIONAL tristate PK ! �j�pB B math/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-y += div64.o gcd.o lcm.o int_pow.o int_sqrt.o reciprocal_div.o obj-$(CONFIG_CORDIC) += cordic.o obj-$(CONFIG_PRIME_NUMBERS) += prime_numbers.o obj-$(CONFIG_RATIONAL) += rational.o obj-$(CONFIG_TEST_DIV64) += test_div64.o obj-$(CONFIG_RATIONAL_KUNIT_TEST) += rational-test.o PK ! "��F� � raid6/test/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # This is a simple Makefile to test some of the RAID-6 code # from userspace. # pound := \# CC = gcc OPTFLAGS = -O2 # Adjust as desired CFLAGS = -I.. -I ../../../include -g $(OPTFLAGS) LD = ld AWK = awk -f AR = ar RANLIB = ranlib OBJS = int1.o int2.o int4.o int8.o int16.o int32.o recov.o algos.o tables.o ARCH := $(shell uname -m 2>/dev/null | sed -e /s/i.86/i386/) ifeq ($(ARCH),i386) CFLAGS += -DCONFIG_X86_32 IS_X86 = yes endif ifeq ($(ARCH),x86_64) CFLAGS += -DCONFIG_X86_64 IS_X86 = yes endif ifeq ($(ARCH),arm) CFLAGS += -I../../../arch/arm/include -mfpu=neon HAS_NEON = yes endif ifeq ($(ARCH),aarch64) CFLAGS += -I../../../arch/arm64/include HAS_NEON = yes endif ifeq ($(IS_X86),yes) OBJS += mmx.o sse1.o sse2.o avx2.o recov_ssse3.o recov_avx2.o avx512.o recov_avx512.o CFLAGS += -DCONFIG_X86 CFLAGS += $(shell echo "vpmovm2b %k1, %zmm5" | \ gcc -c -x assembler - >/dev/null 2>&1 && \ rm ./-.o && echo -DCONFIG_AS_AVX512=1) else ifeq ($(HAS_NEON),yes) OBJS += neon.o neon1.o neon2.o neon4.o neon8.o recov_neon.o recov_neon_inner.o CFLAGS += -DCONFIG_KERNEL_MODE_NEON=1 else HAS_ALTIVEC := $(shell printf '$(pound)include <altivec.h>\nvector int a;\n' |\ gcc -c -x c - >/dev/null && rm ./-.o && echo yes) ifeq ($(HAS_ALTIVEC),yes) CFLAGS += -I../../../arch/powerpc/include CFLAGS += -DCONFIG_ALTIVEC OBJS += altivec1.o altivec2.o altivec4.o altivec8.o \ vpermxor1.o vpermxor2.o vpermxor4.o vpermxor8.o endif endif .c.o: $(CC) $(CFLAGS) -c -o $@ $< %.c: ../%.c cp -f $< $@ %.uc: ../%.uc cp -f $< $@ all: raid6.a raid6test raid6.a: $(OBJS) rm -f $@ $(AR) cq $@ $^ $(RANLIB) $@ raid6test: test.c raid6.a $(CC) $(CFLAGS) -o raid6test $^ neon1.c: neon.uc ../unroll.awk $(AWK) ../unroll.awk -vN=1 < neon.uc > $@ neon2.c: neon.uc ../unroll.awk $(AWK) ../unroll.awk -vN=2 < neon.uc > $@ neon4.c: neon.uc ../unroll.awk $(AWK) ../unroll.awk -vN=4 < neon.uc > $@ neon8.c: neon.uc ../unroll.awk $(AWK) ../unroll.awk -vN=8 < neon.uc > $@ altivec1.c: altivec.uc ../unroll.awk $(AWK) ../unroll.awk -vN=1 < altivec.uc > $@ altivec2.c: altivec.uc ../unroll.awk $(AWK) ../unroll.awk -vN=2 < altivec.uc > $@ altivec4.c: altivec.uc ../unroll.awk $(AWK) ../unroll.awk -vN=4 < altivec.uc > $@ altivec8.c: altivec.uc ../unroll.awk $(AWK) ../unroll.awk -vN=8 < altivec.uc > $@ vpermxor1.c: vpermxor.uc ../unroll.awk $(AWK) ../unroll.awk -vN=1 < vpermxor.uc > $@ vpermxor2.c: vpermxor.uc ../unroll.awk $(AWK) ../unroll.awk -vN=2 < vpermxor.uc > $@ vpermxor4.c: vpermxor.uc ../unroll.awk $(AWK) ../unroll.awk -vN=4 < vpermxor.uc > $@ vpermxor8.c: vpermxor.uc ../unroll.awk $(AWK) ../unroll.awk -vN=8 < vpermxor.uc > $@ int1.c: int.uc ../unroll.awk $(AWK) ../unroll.awk -vN=1 < int.uc > $@ int2.c: int.uc ../unroll.awk $(AWK) ../unroll.awk -vN=2 < int.uc > $@ int4.c: int.uc ../unroll.awk $(AWK) ../unroll.awk -vN=4 < int.uc > $@ int8.c: int.uc ../unroll.awk $(AWK) ../unroll.awk -vN=8 < int.uc > $@ int16.c: int.uc ../unroll.awk $(AWK) ../unroll.awk -vN=16 < int.uc > $@ int32.c: int.uc ../unroll.awk $(AWK) ../unroll.awk -vN=32 < int.uc > $@ tables.c: mktables ./mktables > tables.c clean: rm -f *.o *.a mktables mktables.c *.uc int*.c altivec*.c vpermxor*.c neon*.c tables.c raid6test spotless: clean rm -f *~ PK ! Z�s� � raid6/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_RAID6_PQ) += raid6_pq.o raid6_pq-y += algos.o recov.o tables.o int1.o int2.o int4.o \ int8.o int16.o int32.o raid6_pq-$(CONFIG_X86) += recov_ssse3.o recov_avx2.o mmx.o sse1.o sse2.o avx2.o avx512.o recov_avx512.o raid6_pq-$(CONFIG_ALTIVEC) += altivec1.o altivec2.o altivec4.o altivec8.o \ vpermxor1.o vpermxor2.o vpermxor4.o vpermxor8.o raid6_pq-$(CONFIG_KERNEL_MODE_NEON) += neon.o neon1.o neon2.o neon4.o neon8.o recov_neon.o recov_neon_inner.o raid6_pq-$(CONFIG_S390) += s390vx8.o recov_s390xc.o hostprogs += mktables ifeq ($(CONFIG_ALTIVEC),y) altivec_flags := -maltivec $(call cc-option,-mabi=altivec) ifdef CONFIG_CC_IS_CLANG # clang ppc port does not yet support -maltivec when -msoft-float is # enabled. A future release of clang will resolve this # https://bugs.llvm.org/show_bug.cgi?id=31177 CFLAGS_REMOVE_altivec1.o += -msoft-float CFLAGS_REMOVE_altivec2.o += -msoft-float CFLAGS_REMOVE_altivec4.o += -msoft-float CFLAGS_REMOVE_altivec8.o += -msoft-float CFLAGS_REMOVE_vpermxor1.o += -msoft-float CFLAGS_REMOVE_vpermxor2.o += -msoft-float CFLAGS_REMOVE_vpermxor4.o += -msoft-float CFLAGS_REMOVE_vpermxor8.o += -msoft-float endif endif # The GCC option -ffreestanding is required in order to compile code containing # ARM/NEON intrinsics in a non C99-compliant environment (such as the kernel) ifeq ($(CONFIG_KERNEL_MODE_NEON),y) NEON_FLAGS := -ffreestanding ifeq ($(ARCH),arm) NEON_FLAGS += -march=armv7-a -mfloat-abi=softfp -mfpu=neon endif CFLAGS_recov_neon_inner.o += $(NEON_FLAGS) ifeq ($(ARCH),arm64) CFLAGS_REMOVE_recov_neon_inner.o += -mgeneral-regs-only CFLAGS_REMOVE_neon1.o += -mgeneral-regs-only CFLAGS_REMOVE_neon2.o += -mgeneral-regs-only CFLAGS_REMOVE_neon4.o += -mgeneral-regs-only CFLAGS_REMOVE_neon8.o += -mgeneral-regs-only endif endif quiet_cmd_unroll = UNROLL $@ cmd_unroll = $(AWK) -v N=$* -f $(srctree)/$(src)/unroll.awk < $< > $@ targets += int1.c int2.c int4.c int8.c int16.c int32.c $(obj)/int%.c: $(src)/int.uc $(src)/unroll.awk FORCE $(call if_changed,unroll) CFLAGS_altivec1.o += $(altivec_flags) CFLAGS_altivec2.o += $(altivec_flags) CFLAGS_altivec4.o += $(altivec_flags) CFLAGS_altivec8.o += $(altivec_flags) targets += altivec1.c altivec2.c altivec4.c altivec8.c $(obj)/altivec%.c: $(src)/altivec.uc $(src)/unroll.awk FORCE $(call if_changed,unroll) CFLAGS_vpermxor1.o += $(altivec_flags) CFLAGS_vpermxor2.o += $(altivec_flags) CFLAGS_vpermxor4.o += $(altivec_flags) CFLAGS_vpermxor8.o += $(altivec_flags) targets += vpermxor1.c vpermxor2.c vpermxor4.c vpermxor8.c $(obj)/vpermxor%.c: $(src)/vpermxor.uc $(src)/unroll.awk FORCE $(call if_changed,unroll) CFLAGS_neon1.o += $(NEON_FLAGS) CFLAGS_neon2.o += $(NEON_FLAGS) CFLAGS_neon4.o += $(NEON_FLAGS) CFLAGS_neon8.o += $(NEON_FLAGS) targets += neon1.c neon2.c neon4.c neon8.c $(obj)/neon%.c: $(src)/neon.uc $(src)/unroll.awk FORCE $(call if_changed,unroll) targets += s390vx8.c $(obj)/s390vx%.c: $(src)/s390vx.uc $(src)/unroll.awk FORCE $(call if_changed,unroll) quiet_cmd_mktable = TABLE $@ cmd_mktable = $(obj)/mktables > $@ targets += tables.c $(obj)/tables.c: $(obj)/mktables FORCE $(call if_changed,mktable) PK ! 3�XE~Z ~Z Kconfig.debugnu �[��� # SPDX-License-Identifier: GPL-2.0-only menu "Kernel hacking" menu "printk and dmesg options" config PRINTK_TIME bool "Show timing information on printks" depends on PRINTK help Selecting this option causes time stamps of the printk() messages to be added to the output of the syslog() system call and at the console. The timestamp is always recorded internally, and exported to /dev/kmsg. This flag just specifies if the timestamp should be included, not that the timestamp is recorded. The behavior is also controlled by the kernel command line parameter printk.time=1. See Documentation/admin-guide/kernel-parameters.rst config PRINTK_CALLER bool "Show caller information on printks" depends on PRINTK help Selecting this option causes printk() to add a caller "thread id" (if in task context) or a caller "processor id" (if not in task context) to every message. This option is intended for environments where multiple threads concurrently call printk() for many times, for it is difficult to interpret without knowing where these lines (or sometimes individual line which was divided into multiple lines due to race) came from. Since toggling after boot makes the code racy, currently there is no option to enable/disable at the kernel command line parameter or sysfs interface. config STACKTRACE_BUILD_ID bool "Show build ID information in stacktraces" depends on PRINTK help Selecting this option adds build ID information for symbols in stacktraces printed with the printk format '%p[SR]b'. This option is intended for distros where debuginfo is not easily accessible but can be downloaded given the build ID of the vmlinux or kernel module where the function is located. config CONSOLE_LOGLEVEL_DEFAULT int "Default console loglevel (1-15)" range 1 15 default "7" help Default loglevel to determine what will be printed on the console. Setting a default here is equivalent to passing in loglevel=<x> in the kernel bootargs. loglevel=<x> continues to override whatever value is specified here as well. Note: This does not affect the log level of un-prefixed printk() usage in the kernel. That is controlled by the MESSAGE_LOGLEVEL_DEFAULT option. config CONSOLE_LOGLEVEL_QUIET int "quiet console loglevel (1-15)" range 1 15 default "4" help loglevel to use when "quiet" is passed on the kernel commandline. When "quiet" is passed on the kernel commandline this loglevel will be used as the loglevel. IOW passing "quiet" will be the equivalent of passing "loglevel=<CONSOLE_LOGLEVEL_QUIET>" config MESSAGE_LOGLEVEL_DEFAULT int "Default message log level (1-7)" range 1 7 default "4" help Default log level for printk statements with no specified priority. This was hard-coded to KERN_WARNING since at least 2.6.10 but folks that are auditing their logs closely may want to set it to a lower priority. Note: This does not affect what message level gets printed on the console by default. To change that, use loglevel=<x> in the kernel bootargs, or pick a different CONSOLE_LOGLEVEL_DEFAULT configuration value. config BOOT_PRINTK_DELAY bool "Delay each boot printk message by N milliseconds" depends on DEBUG_KERNEL && PRINTK && GENERIC_CALIBRATE_DELAY help This build option allows you to read kernel boot messages by inserting a short delay after each one. The delay is specified in milliseconds on the kernel command line, using "boot_delay=N". It is likely that you would also need to use "lpj=M" to preset the "loops per jiffie" value. See a previous boot log for the "lpj" value to use for your system, and then set "lpj=M" before setting "boot_delay=N". NOTE: Using this option may adversely affect SMP systems. I.e., processors other than the first one may not boot up. BOOT_PRINTK_DELAY also may cause LOCKUP_DETECTOR to detect what it believes to be lockup conditions. config DYNAMIC_DEBUG bool "Enable dynamic printk() support" default n depends on PRINTK depends on (DEBUG_FS || PROC_FS) select DYNAMIC_DEBUG_CORE help Compiles debug level messages into the kernel, which would not otherwise be available at runtime. These messages can then be enabled/disabled based on various levels of scope - per source file, function, module, format string, and line number. This mechanism implicitly compiles in all pr_debug() and dev_dbg() calls, which enlarges the kernel text size by about 2%. If a source file is compiled with DEBUG flag set, any pr_debug() calls in it are enabled by default, but can be disabled at runtime as below. Note that DEBUG flag is turned on by many CONFIG_*DEBUG* options. Usage: Dynamic debugging is controlled via the 'dynamic_debug/control' file, which is contained in the 'debugfs' filesystem or procfs. Thus, the debugfs or procfs filesystem must first be mounted before making use of this feature. We refer the control file as: <debugfs>/dynamic_debug/control. This file contains a list of the debug statements that can be enabled. The format for each line of the file is: filename:lineno [module]function flags format filename : source file of the debug statement lineno : line number of the debug statement module : module that contains the debug statement function : function that contains the debug statement flags : '=p' means the line is turned 'on' for printing format : the format used for the debug statement From a live system: nullarbor:~ # cat <debugfs>/dynamic_debug/control # filename:lineno [module]function flags format fs/aio.c:222 [aio]__put_ioctx =_ "__put_ioctx:\040freeing\040%p\012" fs/aio.c:248 [aio]ioctx_alloc =_ "ENOMEM:\040nr_events\040too\040high\012" fs/aio.c:1770 [aio]sys_io_cancel =_ "calling\040cancel\012" Example usage: // enable the message at line 1603 of file svcsock.c nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' > <debugfs>/dynamic_debug/control // enable all the messages in file svcsock.c nullarbor:~ # echo -n 'file svcsock.c +p' > <debugfs>/dynamic_debug/control // enable all the messages in the NFS server module nullarbor:~ # echo -n 'module nfsd +p' > <debugfs>/dynamic_debug/control // enable all 12 messages in the function svc_process() nullarbor:~ # echo -n 'func svc_process +p' > <debugfs>/dynamic_debug/control // disable all 12 messages in the function svc_process() nullarbor:~ # echo -n 'func svc_process -p' > <debugfs>/dynamic_debug/control See Documentation/admin-guide/dynamic-debug-howto.rst for additional information. config DYNAMIC_DEBUG_CORE bool "Enable core function of dynamic debug support" depends on PRINTK depends on (DEBUG_FS || PROC_FS) help Enable core functional support of dynamic debug. It is useful when you want to tie dynamic debug to your kernel modules with DYNAMIC_DEBUG_MODULE defined for each of them, especially for the case of embedded system where the kernel image size is sensitive for people. config SYMBOLIC_ERRNAME bool "Support symbolic error names in printf" default y if PRINTK help If you say Y here, the kernel's printf implementation will be able to print symbolic error names such as ENOSPC instead of the number 28. It makes the kernel image slightly larger (about 3KB), but can make the kernel logs easier to read. config DEBUG_BUGVERBOSE bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT depends on BUG && (GENERIC_BUG || HAVE_DEBUG_BUGVERBOSE) default y help Say Y here to make BUG() panics output the file name and line number of the BUG call as well as the EIP and oops trace. This aids debugging but costs about 70-100K of memory. endmenu # "printk and dmesg options" # Clang is known to generate .{s,u}leb128 with symbol deltas with DWARF5, which # some targets may not support: https://sourceware.org/bugzilla/show_bug.cgi?id=27215 config AS_HAS_NON_CONST_LEB128 def_bool $(as-instr,.uleb128 .Lexpr_end4 - .Lexpr_start3\n.Lexpr_start3:\n.Lexpr_end4:) menu "Compile-time checks and compiler options" config DEBUG_INFO bool "Compile the kernel with debug info" depends on DEBUG_KERNEL && !COMPILE_TEST help If you say Y here the resulting kernel image will include debugging info resulting in a larger kernel image. This adds debug symbols to the kernel and modules (gcc -g), and is needed if you intend to use kernel crashdump or binary object tools like crash, kgdb, LKCD, gdb, etc on the kernel. Say Y here only if you plan to debug the kernel. If unsure, say N. if DEBUG_INFO config DEBUG_INFO_REDUCED bool "Reduce debugging information" help If you say Y here gcc is instructed to generate less debugging information for structure types. This means that tools that need full debugging information (like kgdb or systemtap) won't be happy. But if you merely need debugging information to resolve line numbers there is no loss. Advantage is that build directory object sizes shrink dramatically over a full DEBUG_INFO build and compile times are reduced too. Only works with newer gcc versions. config DEBUG_INFO_COMPRESSED bool "Compressed debugging information" depends on $(cc-option,-gz=zlib) depends on $(ld-option,--compress-debug-sections=zlib) help Compress the debug information using zlib. Requires GCC 5.0+ or Clang 5.0+, binutils 2.26+, and zlib. Users of dpkg-deb via scripts/package/builddeb may find an increase in size of their debug .deb packages with this config set, due to the debug info being compressed with zlib, then the object files being recompressed with a different compression scheme. But this is still preferable to setting $KDEB_COMPRESS to "none" which would be even larger. config DEBUG_INFO_SPLIT bool "Produce split debuginfo in .dwo files" depends on $(cc-option,-gsplit-dwarf) help Generate debug info into separate .dwo files. This significantly reduces the build directory size for builds with DEBUG_INFO, because it stores the information only once on disk in .dwo files instead of multiple times in object files and executables. In addition the debug information is also compressed. Requires recent gcc (4.7+) and recent gdb/binutils. Any tool that packages or reads debug information would need to know about the .dwo files and include them. Incompatible with older versions of ccache. choice prompt "DWARF version" help Which version of DWARF debug info to emit. config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT bool "Rely on the toolchain's implicit default DWARF version" depends on !CC_IS_CLANG || AS_IS_LLVM || CLANG_VERSION < 140000 || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) help The implicit default version of DWARF debug info produced by a toolchain changes over time. This can break consumers of the debug info that haven't upgraded to support newer revisions, and prevent testing newer versions, but those should be less common scenarios. If unsure, say Y. config DEBUG_INFO_DWARF4 bool "Generate DWARF Version 4 debuginfo" help Generate DWARF v4 debug info. This requires gcc 4.5+ and gdb 7.0+. If you have consumers of DWARF debug info that are not ready for newer revisions of DWARF, you may wish to choose this or have your config select this. config DEBUG_INFO_DWARF5 bool "Generate DWARF Version 5 debuginfo" depends on !CC_IS_CLANG || AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502 && AS_HAS_NON_CONST_LEB128) depends on !DEBUG_INFO_BTF || PAHOLE_VERSION >= 121 help Generate DWARF v5 debug info. Requires binutils 2.35.2, gcc 5.0+ (gcc 5.0+ accepts the -gdwarf-5 flag but only had partial support for some draft features until 7.0), and gdb 8.0+. Changes to the structure of debug info in Version 5 allow for around 15-18% savings in resulting image and debug info section sizes as compared to DWARF Version 4. DWARF Version 5 standardizes previous extensions such as accelerators for symbol indexing and the format for fission (.dwo/.dwp) files. Users may not want to select this config if they rely on tooling that has not yet been updated to support DWARF Version 5. endchoice # "DWARF version" config DEBUG_INFO_BTF bool "Generate BTF type information" depends on !DEBUG_INFO_SPLIT && !DEBUG_INFO_REDUCED depends on !GCC_PLUGIN_RANDSTRUCT || COMPILE_TEST help Generate deduplicated BTF type information from DWARF debug info. Turning this on expects presence of pahole tool, which will convert DWARF type info into equivalent deduplicated BTF type info. config PAHOLE_HAS_SPLIT_BTF def_bool PAHOLE_VERSION >= 119 config DEBUG_INFO_BTF_MODULES bool "Generate BTF type information for kernel modules" default y depends on DEBUG_INFO_BTF && MODULES && PAHOLE_HAS_SPLIT_BTF help Generate compact split BTF type information for kernel modules. config GDB_SCRIPTS bool "Provide GDB scripts for kernel debugging" help This creates the required links to GDB helper scripts in the build directory. If you load vmlinux into gdb, the helper scripts will be automatically imported by gdb as well, and additional functions are available to analyze a Linux kernel instance. See Documentation/dev-tools/gdb-kernel-debugging.rst for further details. endif # DEBUG_INFO config FRAME_WARN int "Warn for stack frames larger than" range 0 8192 default 2048 if GCC_PLUGIN_LATENT_ENTROPY default 2048 if PARISC default 1536 if (!64BIT && XTENSA) default 1280 if KASAN && !64BIT default 1024 if !64BIT default 2048 if 64BIT help Tell gcc to warn at build time for stack frames larger than this. Setting this too low will cause a lot of warnings. Setting it to 0 disables the warning. config STRIP_ASM_SYMS bool "Strip assembler-generated symbols during link" default n help Strip internal assembler-generated symbols during a link (symbols that look like '.Lxxx') so they don't pollute the output of get_wchan() and suchlike. config READABLE_ASM bool "Generate readable assembler code" depends on DEBUG_KERNEL depends on CC_IS_GCC help Disable some compiler optimizations that tend to generate human unreadable assembler output. This may make the kernel slightly slower, but it helps to keep kernel developers who have to stare a lot at assembler listings sane. config HEADERS_INSTALL bool "Install uapi headers to usr/include" depends on !UML help This option will install uapi headers (headers exported to user-space) into the usr/include directory for use during the kernel build. This is unneeded for building the kernel itself, but needed for some user-space program samples. It is also needed by some features such as uapi header sanity checks. config DEBUG_SECTION_MISMATCH bool "Enable full Section mismatch analysis" depends on CC_IS_GCC help The section mismatch analysis checks if there are illegal references from one section to another section. During linktime or runtime, some sections are dropped; any use of code/data previously in these sections would most likely result in an oops. In the code, functions and variables are annotated with __init,, etc. (see the full list in include/linux/init.h), which results in the code/data being placed in specific sections. The section mismatch analysis is always performed after a full kernel build, and enabling this option causes the following additional step to occur: - Add the option -fno-inline-functions-called-once to gcc commands. When inlining a function annotated with __init in a non-init function, we would lose the section information and thus the analysis would not catch the illegal reference. This option tells gcc to inline less (but it does result in a larger kernel). config SECTION_MISMATCH_WARN_ONLY bool "Make section mismatch errors non-fatal" default y help If you say N here, the build process will fail if there are any section mismatch, instead of just throwing warnings. If unsure, say Y. config DEBUG_FORCE_FUNCTION_ALIGN_64B bool "Force all function address 64B aligned" depends on EXPERT && (X86_64 || ARM64 || PPC32 || PPC64 || ARC) select FUNCTION_ALIGNMENT_64B help There are cases that a commit from one domain changes the function address alignment of other domains, and cause magic performance bump (regression or improvement). Enable this option will help to verify if the bump is caused by function alignment changes, while it will slightly increase the kernel size and affect icache usage. It is mainly for debug and performance tuning use. # # Select this config option from the architecture Kconfig, if it # is preferred to always offer frame pointers as a config # option on the architecture (regardless of KERNEL_DEBUG): # config ARCH_WANT_FRAME_POINTERS bool config FRAME_POINTER bool "Compile the kernel with frame pointers" depends on DEBUG_KERNEL && (M68K || UML || SUPERH) || ARCH_WANT_FRAME_POINTERS default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS help If you say Y here the resulting kernel image will be slightly larger and slower, but it gives very useful debugging information in case of kernel bugs. (precise oopses/stacktraces/warnings) config STACK_VALIDATION bool "Compile-time stack metadata validation" depends on HAVE_STACK_VALIDATION default n help Add compile-time checks to validate stack metadata, including frame pointers (if CONFIG_FRAME_POINTER is enabled). This helps ensure that runtime stack traces are more reliable. This is also a prerequisite for generation of ORC unwind data, which is needed for CONFIG_UNWINDER_ORC. For more information, see tools/objtool/Documentation/stack-validation.txt. config VMLINUX_VALIDATION bool depends on STACK_VALIDATION && DEBUG_ENTRY && !PARAVIRT default y config VMLINUX_MAP bool "Generate vmlinux.map file when linking" depends on EXPERT help Selecting this option will pass "-Map=vmlinux.map" to ld when linking vmlinux. That file can be useful for verifying and debugging magic section games, and for seeing which pieces of code get eliminated with CONFIG_LD_DEAD_CODE_DATA_ELIMINATION. config DEBUG_FORCE_WEAK_PER_CPU bool "Force weak per-cpu definitions" depends on DEBUG_KERNEL help s390 and alpha require percpu variables in modules to be defined weak to work around addressing range issue which puts the following two restrictions on percpu variable definitions. 1. percpu symbols must be unique whether static or not 2. percpu variables can't be defined inside a function To ensure that generic code follows the above rules, this option forces all percpu variables to be defined as weak. endmenu # "Compiler options" menu "Generic Kernel Debugging Instruments" config MAGIC_SYSRQ bool "Magic SysRq key" depends on !UML help If you say Y here, you will have some control over the system even if the system crashes for example during kernel debugging (e.g., you will be able to flush the buffer cache to disk, reboot the system immediately or dump some status information). This is accomplished by pressing various keys while holding SysRq (Alt+PrintScreen). It also works on a serial console (on PC hardware at least), if you send a BREAK and then within 5 seconds a command keypress. The keys are documented in <file:Documentation/admin-guide/sysrq.rst>. Don't say Y unless you really know what this hack does. config MAGIC_SYSRQ_DEFAULT_ENABLE hex "Enable magic SysRq key functions by default" depends on MAGIC_SYSRQ default 0x1 help Specifies which SysRq key functions are enabled by default. This may be set to 1 or 0 to enable or disable them all, or to a bitmask as described in Documentation/admin-guide/sysrq.rst. config MAGIC_SYSRQ_SERIAL bool "Enable magic SysRq key over serial" depends on MAGIC_SYSRQ default y help Many embedded boards have a disconnected TTL level serial which can generate some garbage that can lead to spurious false sysrq detects. This option allows you to decide whether you want to enable the magic SysRq key. config MAGIC_SYSRQ_SERIAL_SEQUENCE string "Char sequence that enables magic SysRq over serial" depends on MAGIC_SYSRQ_SERIAL default "" help Specifies a sequence of characters that can follow BREAK to enable SysRq on a serial console. If unsure, leave an empty string and the option will not be enabled. config DEBUG_FS bool "Debug Filesystem" help debugfs is a virtual file system that kernel developers use to put debugging files into. Enable this option to be able to read and write to these files. For detailed documentation on the debugfs API, see Documentation/filesystems/. If unsure, say N. choice prompt "Debugfs default access" depends on DEBUG_FS default DEBUG_FS_ALLOW_ALL help This selects the default access restrictions for debugfs. It can be overridden with kernel command line option debugfs=[on,no-mount,off]. The restrictions apply for API access and filesystem registration. config DEBUG_FS_ALLOW_ALL bool "Access normal" help No restrictions apply. Both API and filesystem registration is on. This is the normal default operation. config DEBUG_FS_DISALLOW_MOUNT bool "Do not register debugfs as filesystem" help The API is open but filesystem is not loaded. Clients can still do their work and read with debug tools that do not need debugfs filesystem. config DEBUG_FS_ALLOW_NONE bool "No access" help Access is off. Clients get -PERM when trying to create nodes in debugfs tree and debugfs is not registered as a filesystem. Client can then back-off or continue without debugfs access. endchoice source "lib/Kconfig.kgdb" source "lib/Kconfig.ubsan" source "lib/Kconfig.kcsan" endmenu config DEBUG_KERNEL bool "Kernel debugging" help Say Y here if you are developing drivers or trying to debug and identify kernel problems. config DEBUG_MISC bool "Miscellaneous debug code" default DEBUG_KERNEL depends on DEBUG_KERNEL help Say Y here if you need to enable miscellaneous debug code that should be under a more specific debug option but isn't. menu "Memory Debugging" source "mm/Kconfig.debug" config DEBUG_OBJECTS bool "Debug object operations" depends on DEBUG_KERNEL help If you say Y here, additional code will be inserted into the kernel to track the life time of various objects and validate the operations on those objects. config DEBUG_OBJECTS_SELFTEST bool "Debug objects selftest" depends on DEBUG_OBJECTS help This enables the selftest of the object debug code. config DEBUG_OBJECTS_FREE bool "Debug objects in freed memory" depends on DEBUG_OBJECTS help This enables checks whether a k/v free operation frees an area which contains an object which has not been deactivated properly. This can make kmalloc/kfree-intensive workloads much slower. config DEBUG_OBJECTS_TIMERS bool "Debug timer objects" depends on DEBUG_OBJECTS help If you say Y here, additional code will be inserted into the timer routines to track the life time of timer objects and validate the timer operations. config DEBUG_OBJECTS_WORK bool "Debug work objects" depends on DEBUG_OBJECTS help If you say Y here, additional code will be inserted into the work queue routines to track the life time of work objects and validate the work operations. config DEBUG_OBJECTS_RCU_HEAD bool "Debug RCU callbacks objects" depends on DEBUG_OBJECTS help Enable this to turn on debugging of RCU list heads (call_rcu() usage). config DEBUG_OBJECTS_PERCPU_COUNTER bool "Debug percpu counter objects" depends on DEBUG_OBJECTS help If you say Y here, additional code will be inserted into the percpu counter routines to track the life time of percpu counter objects and validate the percpu counter operations. config DEBUG_OBJECTS_ENABLE_DEFAULT int "debug_objects bootup default value (0-1)" range 0 1 default "1" depends on DEBUG_OBJECTS help Debug objects boot parameter default value config DEBUG_SLAB bool "Debug slab memory allocations" depends on DEBUG_KERNEL && SLAB help Say Y here to have the kernel do limited verification on memory allocation as well as poisoning memory on free to catch use of freed memory. This can make kmalloc/kfree-intensive workloads much slower. config SLUB_DEBUG_ON bool "SLUB debugging on by default" depends on SLUB && SLUB_DEBUG default n help Boot with debugging on by default. SLUB boots by default with the runtime debug capabilities switched off. Enabling this is equivalent to specifying the "slub_debug" parameter on boot. There is no support for more fine grained debug control like possible with slub_debug=xxx. SLUB debugging may be switched off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying "slub_debug=-". config SLUB_STATS default n bool "Enable SLUB performance statistics" depends on SLUB && SYSFS help SLUB statistics are useful to debug SLUBs allocation behavior in order find ways to optimize the allocator. This should never be enabled for production use since keeping statistics slows down the allocator by a few percentage points. The slabinfo command supports the determination of the most active slabs to figure out which slabs are relevant to a particular load. Try running: slabinfo -DA config HAVE_DEBUG_KMEMLEAK bool config DEBUG_KMEMLEAK bool "Kernel memory leak detector" depends on DEBUG_KERNEL && HAVE_DEBUG_KMEMLEAK select DEBUG_FS select STACKTRACE if STACKTRACE_SUPPORT select KALLSYMS select CRC32 help Say Y here if you want to enable the memory leak detector. The memory allocation/freeing is traced in a way similar to the Boehm's conservative garbage collector, the difference being that the orphan objects are not freed but only shown in /sys/kernel/debug/kmemleak. Enabling this feature will introduce an overhead to memory allocations. See Documentation/dev-tools/kmemleak.rst for more details. Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances of finding leaks due to the slab objects poisoning. In order to access the kmemleak file, debugfs needs to be mounted (usually at /sys/kernel/debug). config DEBUG_KMEMLEAK_MEM_POOL_SIZE int "Kmemleak memory pool size" depends on DEBUG_KMEMLEAK range 200 1000000 default 16000 help Kmemleak must track all the memory allocations to avoid reporting false positives. Since memory may be allocated or freed before kmemleak is fully initialised, use a static pool of metadata objects to track such callbacks. After kmemleak is fully initialised, this memory pool acts as an emergency one if slab allocations fail. config DEBUG_KMEMLEAK_TEST tristate "Simple test for the kernel memory leak detector" depends on DEBUG_KMEMLEAK && m help This option enables a module that explicitly leaks memory. If unsure, say N. config DEBUG_KMEMLEAK_DEFAULT_OFF bool "Default kmemleak to off" depends on DEBUG_KMEMLEAK help Say Y here to disable kmemleak by default. It can then be enabled on the command line via kmemleak=on. config DEBUG_KMEMLEAK_AUTO_SCAN bool "Enable kmemleak auto scan thread on boot up" default y depends on DEBUG_KMEMLEAK help Depending on the cpu, kmemleak scan may be cpu intensive and can stall user tasks at times. This option enables/disables automatic kmemleak scan at boot up. Say N here to disable kmemleak auto scan thread to stop automatic scanning. Disabling this option disables automatic reporting of memory leaks. If unsure, say Y. config DEBUG_STACK_USAGE bool "Stack utilization instrumentation" depends on DEBUG_KERNEL && !IA64 help Enables the display of the minimum amount of free stack which each task has ever had available in the sysrq-T and sysrq-P debug output. This option will slow down process creation somewhat. config SCHED_STACK_END_CHECK bool "Detect stack corruption on calls to schedule()" depends on DEBUG_KERNEL default n help This option checks for a stack overrun on calls to schedule(). If the stack end location is found to be over written always panic as the content of the corrupted region can no longer be trusted. This is to ensure no erroneous behaviour occurs which could result in data corruption or a sporadic crash at a later stage once the region is examined. The runtime overhead introduced is minimal. config ARCH_HAS_DEBUG_VM_PGTABLE bool help An architecture should select this when it can successfully build and run DEBUG_VM_PGTABLE. config DEBUG_VM bool "Debug VM" depends on DEBUG_KERNEL help Enable this to turn on extended checks in the virtual-memory system that may impact performance. If unsure, say N. config DEBUG_VM_VMACACHE bool "Debug VMA caching" depends on DEBUG_VM help Enable this to turn on VMA caching debug information. Doing so can cause significant overhead, so only enable it in non-production environments. If unsure, say N. config DEBUG_VM_RB bool "Debug VM red-black trees" depends on DEBUG_VM help Enable VM red-black tree debugging information and extra validations. If unsure, say N. config DEBUG_VM_PGFLAGS bool "Debug page-flags operations" depends on DEBUG_VM help Enables extra validation on page flags operations. If unsure, say N. config DEBUG_VM_PGTABLE bool "Debug arch page table for semantics compliance" depends on MMU depends on ARCH_HAS_DEBUG_VM_PGTABLE default y if DEBUG_VM help This option provides a debug method which can be used to test architecture page table helper functions on various platforms in verifying if they comply with expected generic MM semantics. This will help architecture code in making sure that any changes or new additions of these helpers still conform to expected semantics of the generic MM. Platforms will have to opt in for this through ARCH_HAS_DEBUG_VM_PGTABLE. If unsure, say N. config ARCH_HAS_DEBUG_VIRTUAL bool config DEBUG_VIRTUAL bool "Debug VM translations" depends on DEBUG_KERNEL && ARCH_HAS_DEBUG_VIRTUAL help Enable some costly sanity checks in virtual to page code. This can catch mistakes with virt_to_page() and friends. If unsure, say N. config DEBUG_NOMMU_REGIONS bool "Debug the global anon/private NOMMU mapping region tree" depends on DEBUG_KERNEL && !MMU help This option causes the global tree of anonymous and private mapping regions to be regularly checked for invalid topology. config DEBUG_MEMORY_INIT bool "Debug memory initialisation" if EXPERT default !EXPERT help Enable this for additional checks during memory initialisation. The sanity checks verify aspects of the VM such as the memory model and other information provided by the architecture. Verbose information will be printed at KERN_DEBUG loglevel depending on the mminit_loglevel= command-line option. If unsure, say Y config MEMORY_NOTIFIER_ERROR_INJECT tristate "Memory hotplug notifier error injection module" depends on MEMORY_HOTPLUG_SPARSE && NOTIFIER_ERROR_INJECTION help This option provides the ability to inject artificial errors to memory hotplug notifier chain callbacks. It is controlled through debugfs interface under /sys/kernel/debug/notifier-error-inject/memory If the notifier call chain should be failed with some events notified, write the error code to "actions/<notifier event>/error". Example: Inject memory hotplug offline error (-12 == -ENOMEM) # cd /sys/kernel/debug/notifier-error-inject/memory # echo -12 > actions/MEM_GOING_OFFLINE/error # echo offline > /sys/devices/system/memory/memoryXXX/state bash: echo: write error: Cannot allocate memory To compile this code as a module, choose M here: the module will be called memory-notifier-error-inject. If unsure, say N. config DEBUG_PER_CPU_MAPS bool "Debug access to per_cpu maps" depends on DEBUG_KERNEL depends on SMP help Say Y to verify that the per_cpu map being accessed has been set up. This adds a fair amount of code to kernel memory and decreases performance. Say N if unsure. config DEBUG_KMAP_LOCAL bool "Debug kmap_local temporary mappings" depends on DEBUG_KERNEL && KMAP_LOCAL help This option enables additional error checking for the kmap_local infrastructure. Disable for production use. config ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP bool config DEBUG_KMAP_LOCAL_FORCE_MAP bool "Enforce kmap_local temporary mappings" depends on DEBUG_KERNEL && ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP select KMAP_LOCAL select DEBUG_KMAP_LOCAL help This option enforces temporary mappings through the kmap_local mechanism for non-highmem pages and on non-highmem systems. Disable this for production systems! config DEBUG_HIGHMEM bool "Highmem debugging" depends on DEBUG_KERNEL && HIGHMEM select DEBUG_KMAP_LOCAL_FORCE_MAP if ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP select DEBUG_KMAP_LOCAL help This option enables additional error checking for high memory systems. Disable for production systems. config HAVE_DEBUG_STACKOVERFLOW bool config DEBUG_STACKOVERFLOW bool "Check for stack overflows" depends on DEBUG_KERNEL && HAVE_DEBUG_STACKOVERFLOW help Say Y here if you want to check for overflows of kernel, IRQ and exception stacks (if your architecture uses them). This option will show detailed messages if free stack space drops below a certain limit. These kinds of bugs usually occur when call-chains in the kernel get too deep, especially when interrupts are involved. Use this in cases where you see apparently random memory corruption, especially if it appears in 'struct thread_info' If in doubt, say "N". source "lib/Kconfig.kasan" source "lib/Kconfig.kfence" endmenu # "Memory Debugging" config DEBUG_SHIRQ bool "Debug shared IRQ handlers" depends on DEBUG_KERNEL help Enable this to generate a spurious interrupt just before a shared interrupt handler is deregistered (generating one when registering is currently disabled). Drivers need to handle this correctly. Some don't and need to be caught. menu "Debug Oops, Lockups and Hangs" config PANIC_ON_OOPS bool "Panic on Oops" help Say Y here to enable the kernel to panic when it oopses. This has the same effect as setting oops=panic on the kernel command line. This feature is useful to ensure that the kernel does not do anything erroneous after an oops which could result in data corruption or other issues. Say N if unsure. config PANIC_ON_OOPS_VALUE int range 0 1 default 0 if !PANIC_ON_OOPS default 1 if PANIC_ON_OOPS config PANIC_TIMEOUT int "panic timeout" default 0 help Set the timeout value (in seconds) until a reboot occurs when the kernel panics. If n = 0, then we wait forever. A timeout value n > 0 will wait n seconds before rebooting, while a timeout value n < 0 will reboot immediately. config LOCKUP_DETECTOR bool config SOFTLOCKUP_DETECTOR bool "Detect Soft Lockups" depends on DEBUG_KERNEL && !S390 select LOCKUP_DETECTOR help Say Y here to enable the kernel to act as a watchdog to detect soft lockups. Softlockups are bugs that cause the kernel to loop in kernel mode for more than 20 seconds, without giving other tasks a chance to run. The current stack trace is displayed upon detection and the system will stay locked up. config BOOTPARAM_SOFTLOCKUP_PANIC bool "Panic (Reboot) On Soft Lockups" depends on SOFTLOCKUP_DETECTOR help Say Y here to enable the kernel to panic on "soft lockups", which are bugs that cause the kernel to loop in kernel mode for more than 20 seconds (configurable using the watchdog_thresh sysctl), without giving other tasks a chance to run. The panic can be used in combination with panic_timeout, to cause the system to reboot automatically after a lockup has been detected. This feature is useful for high-availability systems that have uptime guarantees and where a lockup must be resolved ASAP. Say N if unsure. config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE int depends on SOFTLOCKUP_DETECTOR range 0 1 default 0 if !BOOTPARAM_SOFTLOCKUP_PANIC default 1 if BOOTPARAM_SOFTLOCKUP_PANIC config HARDLOCKUP_DETECTOR_PERF bool select SOFTLOCKUP_DETECTOR # # Enables a timestamp based low pass filter to compensate for perf based # hard lockup detection which runs too fast due to turbo modes. # config HARDLOCKUP_CHECK_TIMESTAMP bool # # arch/ can define HAVE_HARDLOCKUP_DETECTOR_ARCH to provide their own hard # lockup detector rather than the perf based detector. # config HARDLOCKUP_DETECTOR bool "Detect Hard Lockups" depends on DEBUG_KERNEL && !S390 depends on HAVE_HARDLOCKUP_DETECTOR_PERF || HAVE_HARDLOCKUP_DETECTOR_ARCH select LOCKUP_DETECTOR select HARDLOCKUP_DETECTOR_PERF if HAVE_HARDLOCKUP_DETECTOR_PERF help Say Y here to enable the kernel to act as a watchdog to detect hard lockups. Hardlockups are bugs that cause the CPU to loop in kernel mode for more than 10 seconds, without letting other interrupts have a chance to run. The current stack trace is displayed upon detection and the system will stay locked up. config BOOTPARAM_HARDLOCKUP_PANIC bool "Panic (Reboot) On Hard Lockups" depends on HARDLOCKUP_DETECTOR help Say Y here to enable the kernel to panic on "hard lockups", which are bugs that cause the kernel to loop in kernel mode with interrupts disabled for more than 10 seconds (configurable using the watchdog_thresh sysctl). Say N if unsure. config BOOTPARAM_HARDLOCKUP_PANIC_VALUE int depends on HARDLOCKUP_DETECTOR range 0 1 default 0 if !BOOTPARAM_HARDLOCKUP_PANIC default 1 if BOOTPARAM_HARDLOCKUP_PANIC config DETECT_HUNG_TASK bool "Detect Hung Tasks" depends on DEBUG_KERNEL default SOFTLOCKUP_DETECTOR help Say Y here to enable the kernel to detect "hung tasks", which are bugs that cause the task to be stuck in uninterruptible "D" state indefinitely. When a hung task is detected, the kernel will print the current stack trace (which you should report), but the task will stay in uninterruptible state. If lockdep is enabled then all held locks will also be reported. This feature has negligible overhead. config DEFAULT_HUNG_TASK_TIMEOUT int "Default timeout for hung task detection (in seconds)" depends on DETECT_HUNG_TASK default 120 help This option controls the default timeout (in seconds) used to determine when a task has become non-responsive and should be considered hung. It can be adjusted at runtime via the kernel.hung_task_timeout_secs sysctl or by writing a value to /proc/sys/kernel/hung_task_timeout_secs. A timeout of 0 disables the check. The default is two minutes. Keeping the default should be fine in most cases. config BOOTPARAM_HUNG_TASK_PANIC bool "Panic (Reboot) On Hung Tasks" depends on DETECT_HUNG_TASK help Say Y here to enable the kernel to panic on "hung tasks", which are bugs that cause the kernel to leave a task stuck in uninterruptible "D" state. The panic can be used in combination with panic_timeout, to cause the system to reboot automatically after a hung task has been detected. This feature is useful for high-availability systems that have uptime guarantees and where a hung tasks must be resolved ASAP. Say N if unsure. config BOOTPARAM_HUNG_TASK_PANIC_VALUE int depends on DETECT_HUNG_TASK range 0 1 default 0 if !BOOTPARAM_HUNG_TASK_PANIC default 1 if BOOTPARAM_HUNG_TASK_PANIC config WQ_WATCHDOG bool "Detect Workqueue Stalls" depends on DEBUG_KERNEL help Say Y here to enable stall detection on workqueues. If a worker pool doesn't make forward progress on a pending work item for over a given amount of time, 30s by default, a warning message is printed along with dump of workqueue state. This can be configured through kernel parameter "workqueue.watchdog_thresh" and its sysfs counterpart. config TEST_LOCKUP tristate "Test module to generate lockups" depends on m help This builds the "test_lockup" module that helps to make sure that watchdogs and lockup detectors are working properly. Depending on module parameters it could emulate soft or hard lockup, "hung task", or locking arbitrary lock for a long time. Also it could generate series of lockups with cooling-down periods. If unsure, say N. endmenu # "Debug lockups and hangs" menu "Scheduler Debugging" config SCHED_DEBUG bool "Collect scheduler debugging info" depends on DEBUG_KERNEL && PROC_FS default y help If you say Y here, the /proc/sched_debug file will be provided that can help debug the scheduler. The runtime overhead of this option is minimal. config SCHED_INFO bool default n config SCHEDSTATS bool "Collect scheduler statistics" depends on DEBUG_KERNEL && PROC_FS select SCHED_INFO help If you say Y here, additional code will be inserted into the scheduler and related routines to collect statistics about scheduler behavior and provide them in /proc/schedstat. These stats may be useful for both tuning and debugging the scheduler If you aren't debugging the scheduler or trying to tune a specific application, you can say N to avoid the very slight overhead this adds. endmenu config DEBUG_TIMEKEEPING bool "Enable extra timekeeping sanity checking" help This option will enable additional timekeeping sanity checks which may be helpful when diagnosing issues where timekeeping problems are suspected. This may include checks in the timekeeping hotpaths, so this option may have a (very small) performance impact to some workloads. If unsure, say N. config DEBUG_PREEMPT bool "Debug preemptible kernel" depends on DEBUG_KERNEL && PREEMPTION && TRACE_IRQFLAGS_SUPPORT help If you say Y here then the kernel will use a debug variant of the commonly used smp_processor_id() function and will print warnings if kernel code uses it in a preemption-unsafe way. Also, the kernel will detect preemption count underflows. This option has potential to introduce high runtime overhead, depending on workload as it triggers debugging routines for each this_cpu operation. It should only be used for debugging purposes. menu "Lock Debugging (spinlocks, mutexes, etc...)" config LOCK_DEBUGGING_SUPPORT bool depends on TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT default y config PROVE_LOCKING bool "Lock debugging: prove locking correctness" depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT select LOCKDEP select DEBUG_SPINLOCK select DEBUG_MUTEXES if !PREEMPT_RT select DEBUG_RT_MUTEXES if RT_MUTEXES select DEBUG_RWSEMS select DEBUG_WW_MUTEX_SLOWPATH select DEBUG_LOCK_ALLOC select PREEMPT_COUNT if !ARCH_NO_PREEMPT select TRACE_IRQFLAGS default n help This feature enables the kernel to prove that all locking that occurs in the kernel runtime is mathematically correct: that under no circumstance could an arbitrary (and not yet triggered) combination of observed locking sequences (on an arbitrary number of CPUs, running an arbitrary number of tasks and interrupt contexts) cause a deadlock. In short, this feature enables the kernel to report locking related deadlocks before they actually occur. The proof does not depend on how hard and complex a deadlock scenario would be to trigger: how many participant CPUs, tasks and irq-contexts would be needed for it to trigger. The proof also does not depend on timing: if a race and a resulting deadlock is possible theoretically (no matter how unlikely the race scenario is), it will be proven so and will immediately be reported by the kernel (once the event is observed that makes the deadlock theoretically possible). If a deadlock is impossible (i.e. the locking rules, as observed by the kernel, are mathematically correct), the kernel reports nothing. NOTE: this feature can also be enabled for rwlocks, mutexes and rwsems - in which case all dependencies between these different locking variants are observed and mapped too, and the proof of observed correctness is also maintained for an arbitrary combination of these separate locking variants. For more details, see Documentation/locking/lockdep-design.rst. config PROVE_RAW_LOCK_NESTING bool "Enable raw_spinlock - spinlock nesting checks" depends on PROVE_LOCKING default n help Enable the raw_spinlock vs. spinlock nesting checks which ensure that the lock nesting rules for PREEMPT_RT enabled kernels are not violated. NOTE: There are known nesting problems. So if you enable this option expect lockdep splats until these problems have been fully addressed which is work in progress. This config switch allows to identify and analyze these problems. It will be removed and the check permanently enabled once the main issues have been fixed. If unsure, select N. config LOCK_STAT bool "Lock usage statistics" depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT select LOCKDEP select DEBUG_SPINLOCK select DEBUG_MUTEXES if !PREEMPT_RT select DEBUG_RT_MUTEXES if RT_MUTEXES select DEBUG_LOCK_ALLOC default n help This feature enables tracking lock contention points For more details, see Documentation/locking/lockstat.rst This also enables lock events required by "perf lock", subcommand of perf. If you want to use "perf lock", you also need to turn on CONFIG_EVENT_TRACING. CONFIG_LOCK_STAT defines "contended" and "acquired" lock events. (CONFIG_LOCKDEP defines "acquire" and "release" events.) config DEBUG_RT_MUTEXES bool "RT Mutex debugging, deadlock detection" depends on DEBUG_KERNEL && RT_MUTEXES help This allows rt mutex semantics violations and rt mutex related deadlocks (lockups) to be detected and reported automatically. config DEBUG_SPINLOCK bool "Spinlock and rw-lock debugging: basic checks" depends on DEBUG_KERNEL select UNINLINE_SPIN_UNLOCK help Say Y here and build SMP to catch missing spinlock initialization and certain other kinds of spinlock errors commonly made. This is best used in conjunction with the NMI watchdog so that spinlock deadlocks are also debuggable. config DEBUG_MUTEXES bool "Mutex debugging: basic checks" depends on DEBUG_KERNEL && !PREEMPT_RT help This feature allows mutex semantics violations to be detected and reported. config DEBUG_WW_MUTEX_SLOWPATH bool "Wait/wound mutex debugging: Slowpath testing" depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT select DEBUG_LOCK_ALLOC select DEBUG_SPINLOCK select DEBUG_MUTEXES if !PREEMPT_RT select DEBUG_RT_MUTEXES if PREEMPT_RT help This feature enables slowpath testing for w/w mutex users by injecting additional -EDEADLK wound/backoff cases. Together with the full mutex checks enabled with (CONFIG_PROVE_LOCKING) this will test all possible w/w mutex interface abuse with the exception of simply not acquiring all the required locks. Note that this feature can introduce significant overhead, so it really should not be enabled in a production or distro kernel, even a debug kernel. If you are a driver writer, enable it. If you are a distro, do not. config DEBUG_RWSEMS bool "RW Semaphore debugging: basic checks" depends on DEBUG_KERNEL help This debugging feature allows mismatched rw semaphore locks and unlocks to be detected and reported. config DEBUG_LOCK_ALLOC bool "Lock debugging: detect incorrect freeing of live locks" depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT select DEBUG_SPINLOCK select DEBUG_MUTEXES if !PREEMPT_RT select DEBUG_RT_MUTEXES if RT_MUTEXES select LOCKDEP help This feature will check whether any held lock (spinlock, rwlock, mutex or rwsem) is incorrectly freed by the kernel, via any of the memory-freeing routines (kfree(), kmem_cache_free(), free_pages(), vfree(), etc.), whether a live lock is incorrectly reinitialized via spin_lock_init()/mutex_init()/etc., or whether there is any lock held during task exit. config LOCKDEP bool depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT select STACKTRACE select KALLSYMS select KALLSYMS_ALL config LOCKDEP_SMALL bool config LOCKDEP_BITS int "Bitsize for MAX_LOCKDEP_ENTRIES" depends on LOCKDEP && !LOCKDEP_SMALL range 10 24 default 15 help Try increasing this value if you hit "BUG: MAX_LOCKDEP_ENTRIES too low!" message. config LOCKDEP_CHAINS_BITS int "Bitsize for MAX_LOCKDEP_CHAINS" depends on LOCKDEP && !LOCKDEP_SMALL range 10 30 default 16 help Try increasing this value if you hit "BUG: MAX_LOCKDEP_CHAINS too low!" message. config LOCKDEP_STACK_TRACE_BITS int "Bitsize for MAX_STACK_TRACE_ENTRIES" depends on LOCKDEP && !LOCKDEP_SMALL range 10 26 default 19 help Try increasing this value if you hit "BUG: MAX_STACK_TRACE_ENTRIES too low!" message. config LOCKDEP_STACK_TRACE_HASH_BITS int "Bitsize for STACK_TRACE_HASH_SIZE" depends on LOCKDEP && !LOCKDEP_SMALL range 10 26 default 14 help Try increasing this value if you need large MAX_STACK_TRACE_ENTRIES. config LOCKDEP_CIRCULAR_QUEUE_BITS int "Bitsize for elements in circular_queue struct" depends on LOCKDEP range 10 26 default 12 help Try increasing this value if you hit "lockdep bfs error:-1" warning due to __cq_enqueue() failure. config DEBUG_LOCKDEP bool "Lock dependency engine debugging" depends on DEBUG_KERNEL && LOCKDEP select DEBUG_IRQFLAGS help If you say Y here, the lock dependency engine will do additional runtime checks to debug itself, at the price of more runtime overhead. config DEBUG_ATOMIC_SLEEP bool "Sleep inside atomic section checking" select PREEMPT_COUNT depends on DEBUG_KERNEL depends on !ARCH_NO_PREEMPT help If you say Y here, various routines which may sleep will become very noisy if they are called inside atomic sections: when a spinlock is held, inside an rcu read side critical section, inside preempt disabled sections, inside an interrupt, etc... config DEBUG_LOCKING_API_SELFTESTS bool "Locking API boot-time self-tests" depends on DEBUG_KERNEL help Say Y here if you want the kernel to run a short self-test during bootup. The self-test checks whether common types of locking bugs are detected by debugging mechanisms or not. (if you disable lock debugging then those bugs won't be detected of course.) The following locking APIs are covered: spinlocks, rwlocks, mutexes and rwsems. config LOCK_TORTURE_TEST tristate "torture tests for locking" depends on DEBUG_KERNEL select TORTURE_TEST help This option provides a kernel module that runs torture tests on kernel locking primitives. The kernel module may be built after the fact on the running kernel to be tested, if desired. Say Y here if you want kernel locking-primitive torture tests to be built into the kernel. Say M if you want these torture tests to build as a module. Say N if you are unsure. config WW_MUTEX_SELFTEST tristate "Wait/wound mutex selftests" help This option provides a kernel module that runs tests on the on the struct ww_mutex locking API. It is recommended to enable DEBUG_WW_MUTEX_SLOWPATH in conjunction with this test harness. Say M if you want these self tests to build as a module. Say N if you are unsure. config SCF_TORTURE_TEST tristate "torture tests for smp_call_function*()" depends on DEBUG_KERNEL select TORTURE_TEST help This option provides a kernel module that runs torture tests on the smp_call_function() family of primitives. The kernel module may be built after the fact on the running kernel to be tested, if desired. config CSD_LOCK_WAIT_DEBUG bool "Debugging for csd_lock_wait(), called from smp_call_function*()" depends on DEBUG_KERNEL depends on 64BIT default n help This option enables debug prints when CPUs are slow to respond to the smp_call_function*() IPI wrappers. These debug prints include the IPI handler function currently executing (if any) and relevant stack traces. endmenu # lock debugging config TRACE_IRQFLAGS depends on TRACE_IRQFLAGS_SUPPORT bool help Enables hooks to interrupt enabling and disabling for either tracing or lock debugging. config TRACE_IRQFLAGS_NMI def_bool y depends on TRACE_IRQFLAGS depends on TRACE_IRQFLAGS_NMI_SUPPORT config DEBUG_IRQFLAGS bool "Debug IRQ flag manipulation" help Enables checks for potentially unsafe enabling or disabling of interrupts, such as calling raw_local_irq_restore() when interrupts are enabled. config STACKTRACE bool "Stack backtrace support" depends on STACKTRACE_SUPPORT help This option causes the kernel to create a /proc/pid/stack for every process, showing its current stack trace. It is also used by various kernel debugging features that require stack trace generation. config WARN_ALL_UNSEEDED_RANDOM bool "Warn for all uses of unseeded randomness" default n help Some parts of the kernel contain bugs relating to their use of cryptographically secure random numbers before it's actually possible to generate those numbers securely. This setting ensures that these flaws don't go unnoticed, by enabling a message, should this ever occur. This will allow people with obscure setups to know when things are going wrong, so that they might contact developers about fixing it. Unfortunately, on some models of some architectures getting a fully seeded CRNG is extremely difficult, and so this can result in dmesg getting spammed for a surprisingly long time. This is really bad from a security perspective, and so architecture maintainers really need to do what they can to get the CRNG seeded sooner after the system is booted. However, since users cannot do anything actionable to address this, by default this option is disabled. Say Y here if you want to receive warnings for all uses of unseeded randomness. This will be of use primarily for those developers interested in improving the security of Linux kernels running on their architecture (or subarchitecture). config DEBUG_KOBJECT bool "kobject debugging" depends on DEBUG_KERNEL help If you say Y here, some extra kobject debugging messages will be sent to the syslog. config DEBUG_KOBJECT_RELEASE bool "kobject release debugging" depends on DEBUG_OBJECTS_TIMERS help kobjects are reference counted objects. This means that their last reference count put is not predictable, and the kobject can live on past the point at which a driver decides to drop it's initial reference to the kobject gained on allocation. An example of this would be a struct device which has just been unregistered. However, some buggy drivers assume that after such an operation, the memory backing the kobject can be immediately freed. This goes completely against the principles of a refcounted object. If you say Y here, the kernel will delay the release of kobjects on the last reference count to improve the visibility of this kind of kobject release bug. config HAVE_DEBUG_BUGVERBOSE bool menu "Debug kernel data structures" config DEBUG_LIST bool "Debug linked list manipulation" depends on DEBUG_KERNEL || BUG_ON_DATA_CORRUPTION help Enable this to turn on extended checks in the linked-list walking routines. If unsure, say N. config DEBUG_PLIST bool "Debug priority linked list manipulation" depends on DEBUG_KERNEL help Enable this to turn on extended checks in the priority-ordered linked-list (plist) walking routines. This checks the entire list multiple times during each manipulation. If unsure, say N. config DEBUG_SG bool "Debug SG table operations" depends on DEBUG_KERNEL help Enable this to turn on checks on scatter-gather tables. This can help find problems with drivers that do not properly initialize their sg tables. If unsure, say N. config DEBUG_NOTIFIERS bool "Debug notifier call chains" depends on DEBUG_KERNEL help Enable this to turn on sanity checking for notifier call chains. This is most useful for kernel developers to make sure that modules properly unregister themselves from notifier chains. This is a relatively cheap check but if you care about maximum performance, say N. config BUG_ON_DATA_CORRUPTION bool "Trigger a BUG when data corruption is detected" select DEBUG_LIST help Select this option if the kernel should BUG when it encounters data corruption in kernel memory structures when they get checked for validity. If unsure, say N. endmenu config DEBUG_CREDENTIALS bool "Debug credential management" depends on DEBUG_KERNEL help Enable this to turn on some debug checking for credential management. The additional code keeps track of the number of pointers from task_structs to any given cred struct, and checks to see that this number never exceeds the usage count of the cred struct. Furthermore, if SELinux is enabled, this also checks that the security pointer in the cred struct is never seen to be invalid. If unsure, say N. source "kernel/rcu/Kconfig.debug" config DEBUG_WQ_FORCE_RR_CPU bool "Force round-robin CPU selection for unbound work items" depends on DEBUG_KERNEL default n help Workqueue used to implicitly guarantee that work items queued without explicit CPU specified are put on the local CPU. This guarantee is no longer true and while local CPU is still preferred work items may be put on foreign CPUs. Kernel parameter "workqueue.debug_force_rr_cpu" is added to force round-robin CPU selection to flush out usages which depend on the now broken guarantee. This config option enables the debug feature by default. When enabled, memory and cache locality will be impacted. config CPU_HOTPLUG_STATE_CONTROL bool "Enable CPU hotplug state control" depends on DEBUG_KERNEL depends on HOTPLUG_CPU default n help Allows to write steps between "offline" and "online" to the CPUs sysfs target file so states can be stepped granular. This is a debug option for now as the hotplug machinery cannot be stopped and restarted at arbitrary points yet. Say N if your are unsure. config LATENCYTOP bool "Latency measuring infrastructure" depends on DEBUG_KERNEL depends on STACKTRACE_SUPPORT depends on PROC_FS depends on FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86 select KALLSYMS select KALLSYMS_ALL select STACKTRACE select SCHEDSTATS help Enable this option if you want to use the LatencyTOP tool to find out which userspace is blocking on what kernel operations. source "kernel/trace/Kconfig" config PROVIDE_OHCI1394_DMA_INIT bool "Remote debugging over FireWire early on boot" depends on PCI && X86 help If you want to debug problems which hang or crash the kernel early on boot and the crashing machine has a FireWire port, you can use this feature to remotely access the memory of the crashed machine over FireWire. This employs remote DMA as part of the OHCI1394 specification which is now the standard for FireWire controllers. With remote DMA, you can monitor the printk buffer remotely using firescope and access all memory below 4GB using fireproxy from gdb. Even controlling a kernel debugger is possible using remote DMA. Usage: If ohci1394_dma=early is used as boot parameter, it will initialize all OHCI1394 controllers which are found in the PCI config space. As all changes to the FireWire bus such as enabling and disabling devices cause a bus reset and thereby disable remote DMA for all devices, be sure to have the cable plugged and FireWire enabled on the debugging host before booting the debug target for debugging. This code (~1k) is freed after boot. By then, the firewire stack in charge of the OHCI-1394 controllers should be used instead. See Documentation/core-api/debugging-via-ohci1394.rst for more information. source "samples/Kconfig" config ARCH_HAS_DEVMEM_IS_ALLOWED bool config STRICT_DEVMEM bool "Filter access to /dev/mem" depends on MMU && DEVMEM depends on ARCH_HAS_DEVMEM_IS_ALLOWED || GENERIC_LIB_DEVMEM_IS_ALLOWED default y if PPC || X86 || ARM64 help If this option is disabled, you allow userspace (root) access to all of memory, including kernel and userspace memory. Accidental access to this is obviously disastrous, but specific access can be used by people debugging the kernel. Note that with PAT support enabled, even in this case there are restrictions on /dev/mem use due to the cache aliasing requirements. If this option is switched on, and IO_STRICT_DEVMEM=n, the /dev/mem file only allows userspace access to PCI space and the BIOS code and data regions. This is sufficient for dosemu and X and all common users of /dev/mem. If in doubt, say Y. config IO_STRICT_DEVMEM bool "Filter I/O access to /dev/mem" depends on STRICT_DEVMEM help If this option is disabled, you allow userspace (root) access to all io-memory regardless of whether a driver is actively using that range. Accidental access to this is obviously disastrous, but specific access can be used by people debugging kernel drivers. If this option is switched on, the /dev/mem file only allows userspace access to *idle* io-memory ranges (see /proc/iomem) This may break traditional users of /dev/mem (dosemu, legacy X, etc...) if the driver using a given range cannot be disabled. If in doubt, say Y. menu "$(SRCARCH) Debugging" source "arch/$(SRCARCH)/Kconfig.debug" endmenu menu "Kernel Testing and Coverage" source "lib/kunit/Kconfig" config NOTIFIER_ERROR_INJECTION tristate "Notifier error injection" depends on DEBUG_KERNEL select DEBUG_FS help This option provides the ability to inject artificial errors to specified notifier chain callbacks. It is useful to test the error handling of notifier call chain failures. Say N if unsure. config PM_NOTIFIER_ERROR_INJECT tristate "PM notifier error injection module" depends on PM && NOTIFIER_ERROR_INJECTION default m if PM_DEBUG help This option provides the ability to inject artificial errors to PM notifier chain callbacks. It is controlled through debugfs interface /sys/kernel/debug/notifier-error-inject/pm If the notifier call chain should be failed with some events notified, write the error code to "actions/<notifier event>/error". Example: Inject PM suspend error (-12 = -ENOMEM) # cd /sys/kernel/debug/notifier-error-inject/pm/ # echo -12 > actions/PM_SUSPEND_PREPARE/error # echo mem > /sys/power/state bash: echo: write error: Cannot allocate memory To compile this code as a module, choose M here: the module will be called pm-notifier-error-inject. If unsure, say N. config OF_RECONFIG_NOTIFIER_ERROR_INJECT tristate "OF reconfig notifier error injection module" depends on OF_DYNAMIC && NOTIFIER_ERROR_INJECTION help This option provides the ability to inject artificial errors to OF reconfig notifier chain callbacks. It is controlled through debugfs interface under /sys/kernel/debug/notifier-error-inject/OF-reconfig/ If the notifier call chain should be failed with some events notified, write the error code to "actions/<notifier event>/error". To compile this code as a module, choose M here: the module will be called of-reconfig-notifier-error-inject. If unsure, say N. config NETDEV_NOTIFIER_ERROR_INJECT tristate "Netdev notifier error injection module" depends on NET && NOTIFIER_ERROR_INJECTION help This option provides the ability to inject artificial errors to netdevice notifier chain callbacks. It is controlled through debugfs interface /sys/kernel/debug/notifier-error-inject/netdev If the notifier call chain should be failed with some events notified, write the error code to "actions/<notifier event>/error". Example: Inject netdevice mtu change error (-22 = -EINVAL) # cd /sys/kernel/debug/notifier-error-inject/netdev # echo -22 > actions/NETDEV_CHANGEMTU/error # ip link set eth0 mtu 1024 RTNETLINK answers: Invalid argument To compile this code as a module, choose M here: the module will be called netdev-notifier-error-inject. If unsure, say N. config FUNCTION_ERROR_INJECTION bool "Fault-injections of functions" depends on HAVE_FUNCTION_ERROR_INJECTION && KPROBES help Add fault injections into various functions that are annotated with ALLOW_ERROR_INJECTION() in the kernel. BPF may also modify the return value of theses functions. This is useful to test error paths of code. If unsure, say N config FAULT_INJECTION bool "Fault-injection framework" depends on DEBUG_KERNEL help Provide fault-injection framework. For more details, see Documentation/fault-injection/. config FAILSLAB bool "Fault-injection capability for kmalloc" depends on FAULT_INJECTION depends on SLAB || SLUB help Provide fault-injection capability for kmalloc. config FAIL_PAGE_ALLOC bool "Fault-injection capability for alloc_pages()" depends on FAULT_INJECTION help Provide fault-injection capability for alloc_pages(). config FAULT_INJECTION_USERCOPY bool "Fault injection capability for usercopy functions" depends on FAULT_INJECTION help Provides fault-injection capability to inject failures in usercopy functions (copy_from_user(), get_user(), ...). config FAIL_MAKE_REQUEST bool "Fault-injection capability for disk IO" depends on FAULT_INJECTION && BLOCK help Provide fault-injection capability for disk IO. config FAIL_IO_TIMEOUT bool "Fault-injection capability for faking disk interrupts" depends on FAULT_INJECTION && BLOCK help Provide fault-injection capability on end IO handling. This will make the block layer "forget" an interrupt as configured, thus exercising the error handling. Only works with drivers that use the generic timeout handling, for others it won't do anything. config FAIL_FUTEX bool "Fault-injection capability for futexes" select DEBUG_FS depends on FAULT_INJECTION && FUTEX help Provide fault-injection capability for futexes. config FAULT_INJECTION_DEBUG_FS bool "Debugfs entries for fault-injection capabilities" depends on FAULT_INJECTION && SYSFS && DEBUG_FS help Enable configuration of fault-injection capabilities via debugfs. config FAIL_FUNCTION bool "Fault-injection capability for functions" depends on FAULT_INJECTION_DEBUG_FS && FUNCTION_ERROR_INJECTION help Provide function-based fault-injection capability. This will allow you to override a specific function with a return with given return value. As a result, function caller will see an error value and have to handle it. This is useful to test the error handling in various subsystems. config FAIL_MMC_REQUEST bool "Fault-injection capability for MMC IO" depends on FAULT_INJECTION_DEBUG_FS && MMC help Provide fault-injection capability for MMC IO. This will make the mmc core return data errors. This is useful to test the error handling in the mmc block device and to test how the mmc host driver handles retries from the block device. config FAIL_SUNRPC bool "Fault-injection capability for SunRPC" depends on FAULT_INJECTION_DEBUG_FS && SUNRPC_DEBUG help Provide fault-injection capability for SunRPC and its consumers. config FAULT_INJECTION_STACKTRACE_FILTER bool "stacktrace filter for fault-injection capabilities" depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT depends on !X86_64 select STACKTRACE depends on FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86 help Provide stacktrace filter for fault-injection capabilities config ARCH_HAS_KCOV bool help An architecture should select this when it can successfully build and run with CONFIG_KCOV. This typically requires disabling instrumentation for some early boot code. config CC_HAS_SANCOV_TRACE_PC def_bool $(cc-option,-fsanitize-coverage=trace-pc) config KCOV bool "Code coverage for fuzzing" depends on ARCH_HAS_KCOV depends on CC_HAS_SANCOV_TRACE_PC || GCC_PLUGINS select DEBUG_FS select GCC_PLUGIN_SANCOV if !CC_HAS_SANCOV_TRACE_PC help KCOV exposes kernel code coverage information in a form suitable for coverage-guided fuzzing (randomized testing). If RANDOMIZE_BASE is enabled, PC values will not be stable across different machines and across reboots. If you need stable PC values, disable RANDOMIZE_BASE. For more details, see Documentation/dev-tools/kcov.rst. config KCOV_ENABLE_COMPARISONS bool "Enable comparison operands collection by KCOV" depends on KCOV depends on $(cc-option,-fsanitize-coverage=trace-cmp) help KCOV also exposes operands of every comparison in the instrumented code along with operand sizes and PCs of the comparison instructions. These operands can be used by fuzzing engines to improve the quality of fuzzing coverage. config KCOV_INSTRUMENT_ALL bool "Instrument all code by default" depends on KCOV default y help If you are doing generic system call fuzzing (like e.g. syzkaller), then you will want to instrument the whole kernel and you should say y here. If you are doing more targeted fuzzing (like e.g. filesystem fuzzing with AFL) then you will want to enable coverage for more specific subsets of files, and should say n here. config KCOV_IRQ_AREA_SIZE hex "Size of interrupt coverage collection area in words" depends on KCOV default 0x40000 help KCOV uses preallocated per-cpu areas to collect coverage from soft interrupts. This specifies the size of those areas in the number of unsigned long words. menuconfig RUNTIME_TESTING_MENU bool "Runtime Testing" def_bool y if RUNTIME_TESTING_MENU config LKDTM tristate "Linux Kernel Dump Test Tool Module" depends on DEBUG_FS help This module enables testing of the different dumping mechanisms by inducing system failures at predefined crash points. If you don't need it: say N Choose M here to compile this code as a module. The module will be called lkdtm. Documentation on how to use the module can be found in Documentation/fault-injection/provoke-crashes.rst config TEST_LIST_SORT tristate "Linked list sorting test" if !KUNIT_ALL_TESTS depends on KUNIT default KUNIT_ALL_TESTS help Enable this to turn on 'list_sort()' function test. This test is executed only once during system boot (so affects only boot time), or at module load time. If unsure, say N. config TEST_MIN_HEAP tristate "Min heap test" depends on DEBUG_KERNEL || m help Enable this to turn on min heap function tests. This test is executed only once during system boot (so affects only boot time), or at module load time. If unsure, say N. config TEST_SORT tristate "Array-based sort test" if !KUNIT_ALL_TESTS depends on KUNIT default KUNIT_ALL_TESTS help This option enables the self-test function of 'sort()' at boot, or at module load time. If unsure, say N. config TEST_DIV64 tristate "64bit/32bit division and modulo test" depends on DEBUG_KERNEL || m help Enable this to turn on 'do_div()' function test. This test is executed only once during system boot (so affects only boot time), or at module load time. If unsure, say N. config KPROBES_SANITY_TEST bool "Kprobes sanity tests" depends on DEBUG_KERNEL depends on KPROBES help This option provides for testing basic kprobes functionality on boot. Samples of kprobe and kretprobe are inserted and verified for functionality. Say N if you are unsure. config BACKTRACE_SELF_TEST tristate "Self test for the backtrace code" depends on DEBUG_KERNEL help This option provides a kernel module that can be used to test the kernel stack backtrace code. This option is not useful for distributions or general kernels, but only for kernel developers working on architecture code. Note that if you want to also test saved backtraces, you will have to enable STACKTRACE as well. Say N if you are unsure. config RBTREE_TEST tristate "Red-Black tree test" depends on DEBUG_KERNEL help A benchmark measuring the performance of the rbtree library. Also includes rbtree invariant checks. config REED_SOLOMON_TEST tristate "Reed-Solomon library test" depends on DEBUG_KERNEL || m select REED_SOLOMON select REED_SOLOMON_ENC16 select REED_SOLOMON_DEC16 help This option enables the self-test function of rslib at boot, or at module load time. If unsure, say N. config INTERVAL_TREE_TEST tristate "Interval tree test" depends on DEBUG_KERNEL select INTERVAL_TREE help A benchmark measuring the performance of the interval tree library config PERCPU_TEST tristate "Per cpu operations test" depends on m && DEBUG_KERNEL help Enable this option to build test module which validates per-cpu operations. If unsure, say N. config ATOMIC64_SELFTEST tristate "Perform an atomic64_t self-test" help Enable this option to test the atomic64_t functions at boot or at module load time. If unsure, say N. config ASYNC_RAID6_TEST tristate "Self test for hardware accelerated raid6 recovery" depends on ASYNC_RAID6_RECOV select ASYNC_MEMCPY help This is a one-shot self test that permutes through the recovery of all the possible two disk failure scenarios for a N-disk array. Recovery is performed with the asynchronous raid6 recovery routines, and will optionally use an offload engine if one is available. If unsure, say N. config TEST_HEXDUMP tristate "Test functions located in the hexdump module at runtime" config STRING_SELFTEST tristate "Test string functions at runtime" config TEST_STRING_HELPERS tristate "Test functions located in the string_helpers module at runtime" config TEST_STRSCPY tristate "Test strscpy*() family of functions at runtime" config TEST_KSTRTOX tristate "Test kstrto*() family of functions at runtime" config TEST_PRINTF tristate "Test printf() family of functions at runtime" config TEST_SCANF tristate "Test scanf() family of functions at runtime" config TEST_BITMAP tristate "Test bitmap_*() family of functions at runtime" help Enable this option to test the bitmap functions at boot. If unsure, say N. config TEST_UUID tristate "Test functions located in the uuid module at runtime" config TEST_XARRAY tristate "Test the XArray code at runtime" config TEST_OVERFLOW tristate "Test check_*_overflow() functions at runtime" config TEST_RHASHTABLE tristate "Perform selftest on resizable hash table" help Enable this option to test the rhashtable functions at boot. If unsure, say N. config TEST_HASH tristate "Perform selftest on hash functions" help Enable this option to test the kernel's integer (<linux/hash.h>), string (<linux/stringhash.h>), and siphash (<linux/siphash.h>) hash functions on boot (or module load). This is intended to help people writing architecture-specific optimized versions. If unsure, say N. config TEST_IDA tristate "Perform selftest on IDA functions" config TEST_PARMAN tristate "Perform selftest on priority array manager" depends on PARMAN help Enable this option to test priority array manager on boot (or module load). If unsure, say N. config TEST_IRQ_TIMINGS bool "IRQ timings selftest" depends on IRQ_TIMINGS help Enable this option to test the irq timings code on boot. If unsure, say N. config TEST_LKM tristate "Test module loading with 'hello world' module" depends on m help This builds the "test_module" module that emits "Hello, world" on printk when loaded. It is designed to be used for basic evaluation of the module loading subsystem (for example when validating module verification). It lacks any extra dependencies, and will not normally be loaded by the system unless explicitly requested by name. If unsure, say N. config TEST_BITOPS tristate "Test module for compilation of bitops operations" depends on m help This builds the "test_bitops" module that is much like the TEST_LKM module except that it does a basic exercise of the set/clear_bit macros and get_count_order/long to make sure there are no compiler warnings from C=1 sparse checker or -Wextra compilations. It has no dependencies and doesn't run or load unless explicitly requested by name. for example: modprobe test_bitops. If unsure, say N. config TEST_VMALLOC tristate "Test module for stress/performance analysis of vmalloc allocator" default n depends on MMU depends on m help This builds the "test_vmalloc" module that should be used for stress and performance analysis. So, any new change for vmalloc subsystem can be evaluated from performance and stability point of view. If unsure, say N. config TEST_USER_COPY tristate "Test user/kernel boundary protections" depends on m help This builds the "test_user_copy" module that runs sanity checks on the copy_to/from_user infrastructure, making sure basic user/kernel boundary testing is working. If it fails to load, a regression has been detected in the user/kernel memory boundary protections. If unsure, say N. config TEST_BPF tristate "Test BPF filter functionality" depends on m && NET help This builds the "test_bpf" module that runs various test vectors against the BPF interpreter or BPF JIT compiler depending on the current setting. This is in particular useful for BPF JIT compiler development, but also to run regression tests against changes in the interpreter code. It also enables test stubs for eBPF maps and verifier used by user space verifier testsuite. If unsure, say N. config TEST_BLACKHOLE_DEV tristate "Test blackhole netdev functionality" depends on m && NET help This builds the "test_blackhole_dev" module that validates the data path through this blackhole netdev. If unsure, say N. config FIND_BIT_BENCHMARK tristate "Test find_bit functions" help This builds the "test_find_bit" module that measure find_*_bit() functions performance. If unsure, say N. config TEST_FIRMWARE tristate "Test firmware loading via userspace interface" depends on FW_LOADER help This builds the "test_firmware" module that creates a userspace interface for testing firmware loading. This can be used to control the triggering of firmware loading without needing an actual firmware-using device. The contents can be rechecked by userspace. If unsure, say N. config TEST_SYSCTL tristate "sysctl test driver" depends on PROC_SYSCTL help This builds the "test_sysctl" module. This driver enables to test the proc sysctl interfaces available to drivers safely without affecting production knobs which might alter system functionality. If unsure, say N. config BITFIELD_KUNIT tristate "KUnit test bitfield functions at runtime" depends on KUNIT help Enable this option to test the bitfield functions at boot. KUnit tests run during boot and output the results to the debug log in TAP format (http://testanything.org/). Only useful for kernel devs running the KUnit test harness, and not intended 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. config RESOURCE_KUNIT_TEST tristate "KUnit test for resource API" depends on KUNIT help This builds the resource API unit test. Tests the logic of API provided by resource.c and ioport.h. 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. config SYSCTL_KUNIT_TEST tristate "KUnit test for sysctl" if !KUNIT_ALL_TESTS depends on KUNIT default KUNIT_ALL_TESTS help This builds the proc sysctl unit test, which runs on boot. Tests the API contract and implementation correctness of sysctl. 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. config LIST_KUNIT_TEST tristate "KUnit Test for Kernel Linked-list structures" if !KUNIT_ALL_TESTS depends on KUNIT default KUNIT_ALL_TESTS help This builds the linked list KUnit test suite. It tests that the API and basic functionality of the list_head type and associated macros. 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 the KUnit test harness, and not intended 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. config LINEAR_RANGES_TEST tristate "KUnit test for linear_ranges" depends on KUNIT select LINEAR_RANGES help This builds the linear_ranges unit test, which runs on boot. Tests the linear_ranges logic correctness. 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. config CMDLINE_KUNIT_TEST tristate "KUnit test for cmdline API" depends on KUNIT help This builds the cmdline API unit test. Tests the logic of API provided by cmdline.c. 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. config BITS_TEST tristate "KUnit test for bits.h" depends on KUNIT help This builds the bits unit test. Tests the logic of macros defined in bits.h. 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. config SLUB_KUNIT_TEST tristate "KUnit test for SLUB cache error detection" if !KUNIT_ALL_TESTS depends on SLUB_DEBUG && KUNIT default KUNIT_ALL_TESTS help This builds SLUB allocator unit test. Tests SLUB cache debugging functionality. 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. config RATIONAL_KUNIT_TEST tristate "KUnit test for rational.c" if !KUNIT_ALL_TESTS depends on KUNIT && RATIONAL default KUNIT_ALL_TESTS help This builds the rational math unit test. 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. config TEST_UDELAY tristate "udelay test driver" help This builds the "udelay_test" module that helps to make sure that udelay() is working properly. If unsure, say N. config TEST_STATIC_KEYS tristate "Test static keys" depends on m help Test the static key interfaces. If unsure, say N. config TEST_KMOD tristate "kmod stress tester" depends on m depends on NETDEVICES && NET_CORE && INET # for TUN depends on BLOCK select TEST_LKM select XFS_FS select TUN select BTRFS_FS help Test the kernel's module loading mechanism: kmod. kmod implements support to load modules using the Linux kernel's usermode helper. This test provides a series of tests against kmod. Although technically you can either build test_kmod as a module or into the kernel we disallow building it into the kernel since it stress tests request_module() and this will very likely cause some issues by taking over precious threads available from other module load requests, ultimately this could be fatal. To run tests run: tools/testing/selftests/kmod/kmod.sh --help If unsure, say N. config TEST_DEBUG_VIRTUAL tristate "Test CONFIG_DEBUG_VIRTUAL feature" depends on DEBUG_VIRTUAL help Test the kernel's ability to detect incorrect calls to virt_to_phys() done against the non-linear part of the kernel's virtual address map. If unsure, say N. config TEST_MEMCAT_P tristate "Test memcat_p() helper function" help Test the memcat_p() helper for correctly merging two pointer arrays together. If unsure, say N. config TEST_LIVEPATCH tristate "Test livepatching" default n depends on DYNAMIC_DEBUG depends on LIVEPATCH depends on m help Test kernel livepatching features for correctness. The tests will load test modules that will be livepatched in various scenarios. To run all the livepatching tests: make -C tools/testing/selftests TARGETS=livepatch run_tests Alternatively, individual tests may be invoked: tools/testing/selftests/livepatch/test-callbacks.sh tools/testing/selftests/livepatch/test-livepatch.sh tools/testing/selftests/livepatch/test-shadow-vars.sh If unsure, say N. config TEST_OBJAGG tristate "Perform selftest on object aggreration manager" default n depends on OBJAGG help Enable this option to test object aggregation manager on boot (or module load). config TEST_STACKINIT tristate "Test level of stack variable initialization" help Test if the kernel is zero-initializing stack variables and padding. Coverage is controlled by compiler flags, CONFIG_GCC_PLUGIN_STRUCTLEAK, CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF, or CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL. If unsure, say N. config TEST_MEMINIT tristate "Test heap/page initialization" help Test if the kernel is zero-initializing heap and page allocations. This can be useful to test init_on_alloc and init_on_free features. If unsure, say N. config TEST_HMM tristate "Test HMM (Heterogeneous Memory Management)" depends on TRANSPARENT_HUGEPAGE depends on DEVICE_PRIVATE select HMM_MIRROR select MMU_NOTIFIER help This is a pseudo device driver solely for testing HMM. Say M here if you want to build the HMM test module. Doing so will allow you to run tools/testing/selftest/vm/hmm-tests. If unsure, say N. config TEST_FREE_PAGES tristate "Test freeing pages" help Test that a memory leak does not occur due to a race between freeing a block of pages and a speculative page reference. Loading this module is safe if your kernel has the bug fixed. If the bug is not fixed, it will leak gigabytes of memory and probably OOM your system. config TEST_FPU tristate "Test floating point operations in kernel space" depends on X86 && !KCOV_INSTRUMENT_ALL help Enable this option to add /sys/kernel/debug/selftest_helpers/test_fpu which will trigger a sequence of floating point operations. This is used for self-testing floating point control register setting in kernel_fpu_begin(). If unsure, say N. config TEST_CLOCKSOURCE_WATCHDOG tristate "Test clocksource watchdog in kernel space" depends on CLOCKSOURCE_WATCHDOG help Enable this option to create a kernel module that will trigger a test of the clocksource watchdog. This module may be loaded via modprobe or insmod in which case it will run upon being loaded, or it may be built in, in which case it will run shortly after boot. If unsure, say N. endif # RUNTIME_TESTING_MENU config ARCH_USE_MEMTEST bool help An architecture should select this when it uses early_memtest() during boot process. config MEMTEST bool "Memtest" depends on ARCH_USE_MEMTEST help This option adds a kernel parameter 'memtest', which allows memtest to be set and executed. memtest=0, mean disabled; -- default memtest=1, mean do 1 test pattern; ... memtest=17, mean do 17 test patterns. If you are unsure how to answer this question, answer N. config HYPERV_TESTING bool "Microsoft Hyper-V driver testing" default n depends on HYPERV && DEBUG_FS help Select this option to enable Hyper-V vmbus testing. endmenu # "Kernel Testing and Coverage" source "Documentation/Kconfig" endmenu # Kernel hacking PK ! �)@�H H fonts/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Font configuration # config FONT_SUPPORT tristate if FONT_SUPPORT config FONTS bool "Select compiled-in fonts" depends on FRAMEBUFFER_CONSOLE || STI_CONSOLE help Say Y here if you would like to use fonts other than the default your frame buffer console usually use. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about foreign fonts. If unsure, say N (the default choices are safe). config FONT_8x8 bool "VGA 8x8 font" if FONTS depends on FRAMEBUFFER_CONSOLE || STI_CONSOLE default y if !SPARC && !FONTS help This is the "high resolution" font for the VGA frame buffer (the one provided by the text console 80x50 (and higher) modes). Note that this is a poor quality font. The VGA 8x16 font is quite a lot more readable. Given the resolution provided by the frame buffer device, answer N here is safe. config FONT_8x16 bool "VGA 8x16 font" if FONTS default y if !SPARC && !FONTS help This is the "high resolution" font for the VGA frame buffer (the one provided by the VGA text console 80x25 mode. If unsure, say Y. config FONT_6x11 bool "Mac console 6x11 font (not supported by all drivers)" if FONTS depends on FRAMEBUFFER_CONSOLE || STI_CONSOLE default y if !SPARC && !FONTS && MAC help Small console font with Macintosh-style high-half glyphs. Some Mac framebuffer drivers don't support this one at all. config FONT_7x14 bool "console 7x14 font (not supported by all drivers)" if FONTS depends on FRAMEBUFFER_CONSOLE help Console font with characters just a bit smaller than the default. If the standard 8x16 font is a little too big for you, say Y. Otherwise, say N. config FONT_PEARL_8x8 bool "Pearl (old m68k) console 8x8 font" if FONTS depends on FRAMEBUFFER_CONSOLE default y if !SPARC && !FONTS && AMIGA help Small console font with PC-style control-character and high-half glyphs. config FONT_ACORN_8x8 bool "Acorn console 8x8 font" if FONTS depends on FRAMEBUFFER_CONSOLE default y if !SPARC && !FONTS && ARM && ARCH_ACORN help Small console font with PC-style control characters and high-half glyphs. config FONT_MINI_4x6 bool "Mini 4x6 font" depends on !SPARC && FONTS config FONT_6x10 bool "Medium-size 6x10 font" depends on !SPARC && FONTS help Medium-size console font. Suitable for framebuffer consoles on embedded devices with a 320x240 screen, to get a reasonable number of characters (53x24) that are still at a readable size. config FONT_10x18 bool "console 10x18 font (not supported by all drivers)" if FONTS depends on FRAMEBUFFER_CONSOLE help This is a high resolution console font for machines with very big letters. It fits between the sun 12x22 and the normal 8x16 font. If other fonts are too big or too small for you, say Y, otherwise say N. config FONT_SUN8x16 bool "Sparc console 8x16 font" depends on FRAMEBUFFER_CONSOLE && (!SPARC && FONTS || SPARC) help This is the high resolution console font for Sun machines. Say Y. config FONT_SUN12x22 bool "Sparc console 12x22 font (not supported by all drivers)" depends on FRAMEBUFFER_CONSOLE && (!SPARC && FONTS || SPARC) help This is the high resolution console font for Sun machines with very big letters (like the letters used in the SPARC PROM). If the standard font is unreadable for you, say Y, otherwise say N. config FONT_TER16x32 bool "Terminus 16x32 font (not supported by all drivers)" depends on FRAMEBUFFER_CONSOLE && (!SPARC && FONTS || SPARC) help Terminus Font is a clean, fixed width bitmap font, designed for long (8 and more hours per day) work with computers. This is the high resolution, large version for use with HiDPI screens. If the standard font is unreadable for you, say Y, otherwise say N. config FONT_6x8 bool "OLED 6x8 font" if FONTS depends on FRAMEBUFFER_CONSOLE help This font is useful for small displays (OLED). config FONT_AUTOSELECT def_bool y depends on !FONT_8x8 depends on !FONT_6x11 depends on !FONT_7x14 depends on !FONT_PEARL_8x8 depends on !FONT_ACORN_8x8 depends on !FONT_MINI_4x6 depends on !FONT_6x10 depends on !FONT_SUN8x16 depends on !FONT_SUN12x22 depends on !FONT_10x18 depends on !FONT_TER16x32 depends on !FONT_6x8 select FONT_8x16 endif # FONT_SUPPORT PK ! �?7 7 fonts/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Font handling font-objs := fonts.o font-objs-$(CONFIG_FONT_SUN8x16) += font_sun8x16.o font-objs-$(CONFIG_FONT_SUN12x22) += font_sun12x22.o font-objs-$(CONFIG_FONT_8x8) += font_8x8.o font-objs-$(CONFIG_FONT_8x16) += font_8x16.o font-objs-$(CONFIG_FONT_6x11) += font_6x11.o font-objs-$(CONFIG_FONT_7x14) += font_7x14.o font-objs-$(CONFIG_FONT_10x18) += font_10x18.o font-objs-$(CONFIG_FONT_PEARL_8x8) += font_pearl_8x8.o font-objs-$(CONFIG_FONT_ACORN_8x8) += font_acorn_8x8.o font-objs-$(CONFIG_FONT_MINI_4x6) += font_mini_4x6.o font-objs-$(CONFIG_FONT_6x10) += font_6x10.o font-objs-$(CONFIG_FONT_TER16x32) += font_ter16x32.o font-objs-$(CONFIG_FONT_6x8) += font_6x8.o font-objs += $(font-objs-y) obj-$(CONFIG_FONT_SUPPORT) += font.o PK ! �">� � Kconfig.ubsannu �[��� # SPDX-License-Identifier: GPL-2.0-only config ARCH_HAS_UBSAN_SANITIZE_ALL bool menuconfig UBSAN bool "Undefined behaviour sanity checker" help This option enables the Undefined Behaviour sanity checker. Compile-time instrumentation is used to detect various undefined behaviours at runtime. For more details, see: Documentation/dev-tools/ubsan.rst if UBSAN config UBSAN_TRAP bool "On Sanitizer warnings, abort the running kernel code" depends on !COMPILE_TEST depends on $(cc-option, -fsanitize-undefined-trap-on-error) help Building kernels with Sanitizer features enabled tends to grow the kernel size by around 5%, due to adding all the debugging text on failure paths. To avoid this, Sanitizer instrumentation can just issue a trap. This reduces the kernel size overhead but turns all warnings (including potentially harmless conditions) into full exceptions that abort the running kernel code (regardless of context, locks held, etc), which may destabilize the system. For some system builders this is an acceptable trade-off. config UBSAN_KCOV_BROKEN def_bool KCOV && CC_HAS_SANCOV_TRACE_PC depends on CC_IS_CLANG depends on !$(cc-option,-Werror=unused-command-line-argument -fsanitize=bounds -fsanitize-coverage=trace-pc) help Some versions of clang support either UBSAN or KCOV but not the combination of the two. See https://bugs.llvm.org/show_bug.cgi?id=45831 for the status in newer releases. config CC_HAS_UBSAN_BOUNDS def_bool $(cc-option,-fsanitize=bounds) config CC_HAS_UBSAN_ARRAY_BOUNDS def_bool $(cc-option,-fsanitize=array-bounds) config UBSAN_BOUNDS bool "Perform array index bounds checking" default UBSAN depends on !UBSAN_KCOV_BROKEN depends on CC_HAS_UBSAN_ARRAY_BOUNDS || CC_HAS_UBSAN_BOUNDS help This option enables detection of directly indexed out of bounds array accesses, where the array size is known at compile time. Note that this does not protect array overflows via bad calls to the {str,mem}*cpy() family of functions (that is addressed by CONFIG_FORTIFY_SOURCE). config UBSAN_ONLY_BOUNDS def_bool CC_HAS_UBSAN_BOUNDS && !CC_HAS_UBSAN_ARRAY_BOUNDS depends on UBSAN_BOUNDS help This is a weird case: Clang's -fsanitize=bounds includes -fsanitize=local-bounds, but it's trapping-only, so for Clang, we must use -fsanitize=array-bounds when we want traditional array bounds checking enabled. For GCC, we want -fsanitize=bounds. config UBSAN_ARRAY_BOUNDS def_bool CC_HAS_UBSAN_ARRAY_BOUNDS depends on UBSAN_BOUNDS config UBSAN_LOCAL_BOUNDS bool "Perform array local bounds checking" depends on UBSAN_TRAP depends on !UBSAN_KCOV_BROKEN depends on $(cc-option,-fsanitize=local-bounds) help This option enables -fsanitize=local-bounds which traps when an exception/error is detected. Therefore, it may only be enabled with CONFIG_UBSAN_TRAP. Enabling this option detects errors due to accesses through a pointer that is derived from an object of a statically-known size, where an added offset (which may not be known statically) is out-of-bounds. config UBSAN_SHIFT bool "Perform checking for bit-shift overflows" default UBSAN depends on $(cc-option,-fsanitize=shift) help This option enables -fsanitize=shift which checks for bit-shift operations that overflow to the left or go switch to negative for signed types. config UBSAN_DIV_ZERO bool "Perform checking for integer divide-by-zero" depends on $(cc-option,-fsanitize=integer-divide-by-zero) help This option enables -fsanitize=integer-divide-by-zero which checks for integer division by zero. This is effectively redundant with the kernel's existing exception handling, though it can provide greater debugging information under CONFIG_UBSAN_REPORT_FULL. config UBSAN_UNREACHABLE bool "Perform checking for unreachable code" # objtool already handles unreachable checking and gets angry about # seeing UBSan instrumentation located in unreachable places. depends on !STACK_VALIDATION depends on $(cc-option,-fsanitize=unreachable) help This option enables -fsanitize=unreachable which checks for control flow reaching an expected-to-be-unreachable position. config UBSAN_BOOL bool "Perform checking for non-boolean values used as boolean" default UBSAN depends on $(cc-option,-fsanitize=bool) help This option enables -fsanitize=bool which checks for boolean values being loaded that are neither 0 nor 1. config UBSAN_ENUM bool "Perform checking for out of bounds enum values" default UBSAN depends on $(cc-option,-fsanitize=enum) help This option enables -fsanitize=enum which checks for values being loaded into an enum that are outside the range of given values for the given enum. config UBSAN_ALIGNMENT bool "Perform checking for misaligned pointer usage" default !HAVE_EFFICIENT_UNALIGNED_ACCESS depends on !UBSAN_TRAP && !COMPILE_TEST depends on $(cc-option,-fsanitize=alignment) help This option enables the check of unaligned memory accesses. Enabling this option on architectures that support unaligned accesses may produce a lot of false positives. config UBSAN_SANITIZE_ALL bool "Enable instrumentation for the entire kernel" depends on ARCH_HAS_UBSAN_SANITIZE_ALL default y help This option activates instrumentation for the entire kernel. If you don't enable this option, you have to explicitly specify UBSAN_SANITIZE := y for the files/directories you want to check for UB. Enabling this option will get kernel image size increased significantly. config TEST_UBSAN tristate "Module for testing for undefined behavior detection" depends on m help This is a test module for UBSAN. It triggers various undefined behavior, and detect it. endif # if UBSAN PK ! �5�! xz/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config XZ_DEC tristate "XZ decompression support" select CRC32 help LZMA2 compression algorithm and BCJ filters are supported using the .xz file format as the container. For integrity checking, CRC32 is supported. See Documentation/staging/xz.rst for more information. if XZ_DEC config XZ_DEC_X86 bool "x86 BCJ filter decoder" if EXPERT default y select XZ_DEC_BCJ config XZ_DEC_POWERPC bool "PowerPC BCJ filter decoder" if EXPERT default y select XZ_DEC_BCJ config XZ_DEC_IA64 bool "IA-64 BCJ filter decoder" if EXPERT default y select XZ_DEC_BCJ config XZ_DEC_ARM bool "ARM BCJ filter decoder" if EXPERT default y select XZ_DEC_BCJ config XZ_DEC_ARMTHUMB bool "ARM-Thumb BCJ filter decoder" if EXPERT default y select XZ_DEC_BCJ config XZ_DEC_SPARC bool "SPARC BCJ filter decoder" if EXPERT default y select XZ_DEC_BCJ endif config XZ_DEC_BCJ bool default n config XZ_DEC_TEST tristate "XZ decompressor tester" default n depends on XZ_DEC help This allows passing .xz files to the in-kernel XZ decoder via a character special file. It calculates CRC32 of the decompressed data and writes diagnostics to the system log. Unless you are developing the XZ decoder, you don't need this and should say N. PK ! G8%� � xz/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_XZ_DEC) += xz_dec.o xz_dec-y := xz_dec_syms.o xz_dec_stream.o xz_dec_lzma2.o xz_dec-$(CONFIG_XZ_DEC_BCJ) += xz_dec_bcj.o obj-$(CONFIG_XZ_DEC_TEST) += xz_dec_test.o PK ! �� � reed_solomon/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # This is a modified version of reed solomon lib, # obj-$(CONFIG_REED_SOLOMON) += reed_solomon.o obj-$(CONFIG_REED_SOLOMON_TEST) += test_rslib.o PK ! ��V�� � lz4/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only ccflags-y += -O3 obj-$(CONFIG_LZ4_COMPRESS) += lz4_compress.o obj-$(CONFIG_LZ4HC_COMPRESS) += lz4hc_compress.o obj-$(CONFIG_LZ4_DECOMPRESS) += lz4_decompress.o PK ! �^�W W zlib_inflate/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # This is a modified version of zlib, which does all memory # allocation ahead of time. # # This is only the decompression, see zlib_deflate for the # the compression # # Decompression needs to be serialized for each memory # allocation. # # (The upsides of the simplification is that you can't get in # any nasty situations wrt memory management, and that the # uncompression can be done without blocking on allocation). # obj-$(CONFIG_ZLIB_INFLATE) += zlib_inflate.o zlib_inflate-objs := inffast.o inflate.o infutil.o \ inftrees.o inflate_syms.o PK ! �r��< < zlib_deflate/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # This is a modified version of zlib, which does all memory # allocation ahead of time. # # This is the compression code, see zlib_inflate for the # decompression code. # obj-$(CONFIG_ZLIB_DEFLATE) += zlib_deflate.o zlib_deflate-objs := deflate.o deftree.o deflate_syms.o PK ! 5�b�s s dim/Makefilenu �[��� # # DIM Dynamic Interrupt Moderation library # obj-$(CONFIG_DIMLIB) += dim.o dim-y := dim.o net_dim.o rdma_dim.o PK ! ���� � lzo/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only lzo_compress-objs := lzo1x_compress.o lzo1x_compress_safe.o lzo_decompress-objs := lzo1x_decompress_safe.o obj-$(CONFIG_LZO_COMPRESS) += lzo_compress.o obj-$(CONFIG_LZO_DECOMPRESS) += lzo_decompress.o PK ! �O� � � livepatch/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for livepatch test code. obj-$(CONFIG_TEST_LIVEPATCH) += test_klp_atomic_replace.o \ test_klp_callbacks_demo.o \ test_klp_callbacks_demo2.o \ test_klp_callbacks_busy.o \ test_klp_callbacks_mod.o \ test_klp_livepatch.o \ test_klp_shadow_vars.o \ test_klp_state.o \ test_klp_state2.o \ test_klp_state3.o PK ! ?H�� � 842/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_842_COMPRESS) += 842_compress.o obj-$(CONFIG_842_DECOMPRESS) += 842_decompress.o PK ! �= �. �. ts_fsm.konu �[��� ELF >