ID Workflow Result Correct Bug Created Started Finished Revision
163d2864 assessment-security DenialOfService: βœ… Exploitable: βœ… FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ KASAN: slab-use-after-free Write in xlog_cil_push_work 2026/09/19 00:00 2026/09/19 00:00 2026/09/19 00:53 853b104b
Agent: prod-syz-agent-2
External Bug ID: ---

Inputs:
BaseBranch master
BaseCommit RC
BaseRepository git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
BugTitle KASAN: slab-use-after-free Write in xlog_cil_push_work
CrashLogID 6620679828406272
CrashReportID 4608367122710528
KernelCommit 238650ef6c7c7cca08e032527329424c9fbd70e5
KernelConfig
Show (273947 bytes)
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 syzkaller Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77)"
CONFIG_GCC_VERSION=0
CONFIG_CC_IS_CLANG=y
CONFIG_CLANG_VERSION=220108
CONFIG_AS_IS_LLVM=y
CONFIG_AS_VERSION=220108
CONFIG_LD_VERSION=0
CONFIG_LD_IS_LLD=y
CONFIG_LLD_VERSION=220108
CONFIG_RUSTC_VERSION=109600
CONFIG_RUST_IS_AVAILABLE=y
CONFIG_RUSTC_LLVM_VERSION=220102
CONFIG_RUSTC_LLVM_MAJOR_VERSION=22
CONFIG_RUSTC_CLANG_LLVM_COMPATIBLE=y
CONFIG_CC_CAN_LINK=y
CONFIG_CC_HAS_ASM_GOTO_OUTPUT=y
CONFIG_CC_HAS_ASM_GOTO_TIED_OUTPUT=y
CONFIG_TOOLS_SUPPORT_RELR=y
CONFIG_CC_HAS_ASM_INLINE=y
CONFIG_CC_HAS_ASSUME=y
CONFIG_CC_HAS_NO_PROFILE_FN_ATTR=y
CONFIG_CC_HAS_COUNTED_BY=y
CONFIG_CC_HAS_COUNTED_BY_PTR=y
CONFIG_CC_HAS_ALLOC_TOKEN=y
CONFIG_CC_HAS_MULTIDIMENSIONAL_NONSTRING=y
CONFIG_LD_CAN_USE_KEEP_IN_OVERLAY=y
CONFIG_RUSTC_HAS_SPAN_FILE=y
CONFIG_RUSTC_HAS_UNNECESSARY_TRANSMUTES=y
CONFIG_RUSTC_HAS_FILE_WITH_NUL=y
CONFIG_RUSTC_HAS_FILE_AS_C_STR=y
CONFIG_PAHOLE_VERSION=130
CONFIG_CONSTRUCTORS=y
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_TABLE_SORT=y
CONFIG_THREAD_INFO_IN_TASK=y

#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not set
# CONFIG_WERROR is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_BUILD_SALT=""
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
CONFIG_HAVE_KERNEL_ZSTD=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
# CONFIG_KERNEL_ZSTD is not set
CONFIG_DEFAULT_INIT=""
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_WATCH_QUEUE=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_GENERIC_IRQ_MIGRATION=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR=y
CONFIG_GENERIC_IRQ_RESERVATION_MODE=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
# CONFIG_GENERIC_IRQ_DEBUGFS is not set
# end of IRQ subsystem

CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_INIT=y
CONFIG_ARCH_WANTS_CLOCKSOURCE_READ_INLINE=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST_IDLE=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CLOCKEVENTS_COUPLED=y
CONFIG_GENERIC_CLOCKEVENTS_COUPLED_INLINE=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_HRTIMER_REARM_DEFERRED=y
CONFIG_HAVE_POSIX_CPU_TIMERS_TASK_WORK=y
CONFIG_POSIX_CPU_TIMERS_TASK_WORK=y
CONFIG_CONTEXT_TRACKING=y
CONFIG_CONTEXT_TRACKING_IDLE=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not set
CONFIG_CONTEXT_TRACKING_USER=y
# CONFIG_CONTEXT_TRACKING_USER_FORCE is not set
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_POSIX_AUX_CLOCKS=y
# end of Timers subsystem

CONFIG_BPF=y
CONFIG_HAVE_EBPF_JIT=y
CONFIG_ARCH_WANT_DEFAULT_BPF_JIT=y

#
# BPF subsystem
#
CONFIG_BPF_SYSCALL=y
CONFIG_BPF_JIT=y
CONFIG_BPF_JIT_ALWAYS_ON=y
CONFIG_BPF_JIT_DEFAULT_ON=y
# CONFIG_BPF_UNPRIV_DEFAULT_OFF is not set
CONFIG_BPF_PRELOAD=y
CONFIG_BPF_PRELOAD_UMD=y
CONFIG_BPF_LSM=y
# end of BPF subsystem

CONFIG_PREEMPT_BUILD=y
CONFIG_ARCH_HAS_PREEMPT_LAZY=y
CONFIG_PREEMPT=y
# CONFIG_PREEMPT_LAZY is not set
CONFIG_PREEMPT_RT=y
# CONFIG_PREEMPT_RT_NEEDS_BH_LOCK is not set
CONFIG_PREEMPT_COUNT=y
CONFIG_HAS_SEPARATE_PREEMPT_RESCHED_BITS=y
CONFIG_PREEMPTION=y
CONFIG_PREEMPT_DYNAMIC=y
CONFIG_SCHED_CORE=y

#
# CPU/Task time and stats accounting
#
CONFIG_VIRT_CPU_ACCOUNTING=y
# CONFIG_TICK_CPU_ACCOUNTING is not set
CONFIG_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_SCHED_AVG_IRQ=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_PSI=y
# CONFIG_PSI_DEFAULT_DISABLED is not set
# end of CPU/Task time and stats accounting

CONFIG_CPU_ISOLATION=y

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
CONFIG_PREEMPT_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_TREE_SRCU=y
CONFIG_TASKS_RCU_GENERIC=y
CONFIG_NEED_TASKS_RCU=y
CONFIG_TASKS_RCU=y
CONFIG_TASKS_TRACE_RCU=y
CONFIG_RCU_STALL_COMMON=y
CONFIG_RCU_NEED_SEGCBLIST=y
# CONFIG_RCU_BOOST is not set
# end of RCU Subsystem

CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_IKHEADERS is not set
CONFIG_LOG_BUF_SHIFT=18
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
# CONFIG_PRINTK_INDEX is not set
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y

#
# Scheduler features
#
# CONFIG_UCLAMP_TASK is not set
# end of Scheduler features

CONFIG_ARCH_HAS_PTE_PROTNONE=y
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y
CONFIG_CC_HAS_INT128=y
CONFIG_CC_IMPLICIT_FALLTHROUGH="-Wimplicit-fallthrough"
CONFIG_CC_MS_EXTENSIONS="-fms-extensions"
CONFIG_GCC10_NO_ARRAY_BOUNDS=y
CONFIG_GCC_NO_STRINGOP_OVERFLOW=y
CONFIG_ARCH_SUPPORTS_INT128=y
CONFIG_SCHED_CACHE=y
CONFIG_SLAB_OBJ_EXT=y
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
# CONFIG_CGROUP_FAVOR_DYNMODS is not set
CONFIG_MEMCG=y
CONFIG_MEMCG_V1=y
CONFIG_BLK_CGROUP=y
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_GROUP_SCHED_WEIGHT=y
CONFIG_GROUP_SCHED_BANDWIDTH=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_CFS_BANDWIDTH=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_SCHED_MM_CID=y
CONFIG_CGROUP_PIDS=y
CONFIG_CGROUP_RDMA=y
# CONFIG_CGROUP_DMEM is not set
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_HUGETLB=y
CONFIG_CPUSETS=y
# CONFIG_CPUSETS_V1 is not set
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
# CONFIG_CGROUP_BPF is not set
CONFIG_CGROUP_MISC=y
CONFIG_CGROUP_DEBUG=y
CONFIG_SOCK_CGROUP_DATA=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_TIME_NS=y
CONFIG_TIME_NS_VDSO=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_CHECKPOINT_RESTORE=y
# CONFIG_SCHED_AUTOGROUP is not set
CONFIG_RELAY=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_RD_LZ4=y
CONFIG_RD_ZSTD=y
# CONFIG_BOOT_CONFIG is not set
CONFIG_ARCH_SUPPORTS_CMDLINE_FROM_BOOTCONFIG=y
CONFIG_CMDLINE_LOG_WRAP_IDEAL_LEN=1021
CONFIG_INITRAMFS_PRESERVE_MTIME=y
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_LD_ORPHAN_WARN=y
CONFIG_LD_ORPHAN_WARN_LEVEL="warn"
CONFIG_HAVE_UID16=y
CONFIG_SYSCTL_EXCEPTION_TRACE=y
CONFIG_SYSFS_SYSCALL=y
CONFIG_HAVE_PCSPKR_PLATFORM=y
CONFIG_EXPERT=y
CONFIG_UID16=y
CONFIG_MULTIUSER=y
CONFIG_SGETMASK_SYSCALL=y
CONFIG_FHANDLE=y
CONFIG_POSIX_TIMERS=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
# CONFIG_BASE_SMALL is not set
CONFIG_FUTEX=y
CONFIG_FUTEX_PI=y
CONFIG_FUTEX_PRIVATE_HASH=y
CONFIG_FUTEX_MPOL=y
CONFIG_HAVE_FUTEX_ROBUST_UNLOCK=y
CONFIG_FUTEX_ROBUST_UNLOCK=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_IO_URING=y
CONFIG_IO_URING_MOCK_FILE=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_MEMBARRIER=y
CONFIG_KCMP=y
CONFIG_RSEQ=y
CONFIG_RSEQ_SLICE_EXTENSION=y
# CONFIG_RSEQ_STATS is not set
# CONFIG_RSEQ_DEBUG_DEFAULT_ENABLE is not set
CONFIG_CACHESTAT_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_SELFTEST is not set
CONFIG_KALLSYMS_ALL=y
CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y
CONFIG_ARCH_SUPPORTS_MSEAL_SYSTEM_MAPPINGS=y
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_GUEST_PERF_EVENTS=y
CONFIG_PERF_GUEST_MEDIATED_PMU=y

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
# end of Kernel Performance Events And Counters

CONFIG_SYSTEM_DATA_VERIFICATION=y
CONFIG_PROFILING=y
# CONFIG_RUST is not set
CONFIG_TRACEPOINTS=y

#
# Kexec and crash features
#
CONFIG_CRASH_RESERVE=y
CONFIG_VMCORE_INFO=y
CONFIG_KEXEC_CORE=y
CONFIG_KEXEC=y
# CONFIG_KEXEC_FILE is not set
# CONFIG_KEXEC_JUMP is not set
CONFIG_CRASH_DUMP=y
CONFIG_CRASH_HOTPLUG=y
CONFIG_CRASH_MAX_MEMORY_RANGES=8192
# end of Kexec and crash features

#
# Live Update and Kexec HandOver
#
# CONFIG_KEXEC_HANDOVER is not set
# end of Live Update and Kexec HandOver
# end of General setup

CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_MMU=y
CONFIG_ARCH_MMAP_RND_BITS_MIN=28
CONFIG_ARCH_MMAP_RND_BITS_MAX=32
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_CSUM=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_AUDIT_ARCH=y
CONFIG_KASAN_SHADOW_OFFSET=0xdffffc0000000000
CONFIG_HAVE_INTEL_TXT=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_PGTABLE_LEVELS=5

#
# Processor type and features
#
CONFIG_SMP=y
CONFIG_X86_X2APIC=y
# CONFIG_X86_POSTED_MSI is not set
CONFIG_X86_MPPARSE=y
# CONFIG_X86_CPU_RESCTRL is not set
CONFIG_X86_FRED=y
CONFIG_X86_EXTENDED_PLATFORM=y
# CONFIG_X86_NUMACHIP is not set
# CONFIG_X86_VSMP is not set
# CONFIG_X86_INTEL_MID is not set
# CONFIG_X86_GOLDFISH is not set
# CONFIG_X86_INTEL_LPSS is not set
# CONFIG_X86_AMD_PLATFORM_DEVICE is not set
CONFIG_IOSF_MBI=y
# CONFIG_IOSF_MBI_DEBUG is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
CONFIG_SCHED_OMIT_FRAME_POINTER=y
CONFIG_HYPERVISOR_GUEST=y
CONFIG_PARAVIRT=y
CONFIG_PARAVIRT_SPINLOCKS=y
CONFIG_X86_HV_CALLBACK_VECTOR=y
# CONFIG_XEN is not set
CONFIG_KVM_GUEST=y
CONFIG_ARCH_CPUIDLE_HALTPOLL=y
CONFIG_PVH=y
# CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_JAILHOUSE_GUEST is not set
# CONFIG_ACRN_GUEST is not set
# CONFIG_BHYVE_GUEST is not set
CONFIG_CC_HAS_MARCH_NATIVE=y
# CONFIG_X86_NATIVE_CPU is not set
CONFIG_X86_INTERNODE_CACHE_SHIFT=6
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_TSC=y
CONFIG_X86_HAVE_PAE=y
CONFIG_X86_CX8=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_IA32_FEAT_CTL=y
CONFIG_X86_VMX_FEATURE_NAMES=y
CONFIG_PROCESSOR_SELECT=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
# CONFIG_CPU_SUP_HYGON is not set
# CONFIG_CPU_SUP_CENTAUR is not set
# CONFIG_CPU_SUP_ZHAOXIN is not set
CONFIG_BROADCAST_TLB_FLUSH=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
# CONFIG_GART_IOMMU is not set
CONFIG_BOOT_VESA_SUPPORT=y
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS_RANGE_BEGIN=2
CONFIG_NR_CPUS_RANGE_END=512
CONFIG_NR_CPUS_DEFAULT=64
CONFIG_NR_CPUS=8
CONFIG_SCHED_MC_PRIO=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_ACPI_MADT_WAKEUP=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCELOG_LEGACY is not set
CONFIG_X86_MCE_INTEL=y
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set

#
# Performance monitoring
#
CONFIG_PERF_EVENTS_INTEL_UNCORE=y
CONFIG_PERF_EVENTS_INTEL_RAPL=y
CONFIG_PERF_EVENTS_INTEL_CSTATE=y
# CONFIG_PERF_EVENTS_AMD_POWER is not set
CONFIG_PERF_EVENTS_AMD_UNCORE=y
# CONFIG_PERF_EVENTS_AMD_BRS is not set
# end of Performance monitoring

CONFIG_X86_16BIT=y
CONFIG_X86_ESPFIX64=y
CONFIG_X86_VSYSCALL_EMULATION=y
CONFIG_X86_IOPL_IOPERM=y
CONFIG_MICROCODE=y
# CONFIG_MICROCODE_LATE_LOADING is not set
# CONFIG_MICROCODE_DBG is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_X86_DIRECT_GBPAGES=y
# CONFIG_X86_CPA_STATISTICS is not set
CONFIG_NUMA=y
CONFIG_AMD_NUMA=y
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SHIFT=6
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
# CONFIG_ARCH_MEMORY_PROBE is not set
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
# CONFIG_X86_PMEM_LEGACY is not set
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_MTRR=y
# CONFIG_MTRR_SANITIZER is not set
CONFIG_X86_PAT=y
CONFIG_X86_UMIP=y
CONFIG_CC_HAS_IBT=y
CONFIG_X86_CET=y
CONFIG_X86_KERNEL_IBT=y
CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS=y
CONFIG_ARCH_PKEY_BITS=4
# CONFIG_X86_INTEL_TSX_MODE_OFF is not set
CONFIG_X86_INTEL_TSX_MODE_ON=y
# CONFIG_X86_INTEL_TSX_MODE_AUTO is not set
CONFIG_X86_SGX=y
CONFIG_X86_USER_SHADOW_STACK=y
# CONFIG_INTEL_TDX_HOST is not set
# CONFIG_EFI is not set
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
CONFIG_SCHED_HRTICK=y
CONFIG_ARCH_SUPPORTS_KEXEC=y
CONFIG_ARCH_SUPPORTS_KEXEC_FILE=y
CONFIG_ARCH_SUPPORTS_KEXEC_PURGATORY=y
CONFIG_ARCH_SUPPORTS_KEXEC_SIG=y
CONFIG_ARCH_SUPPORTS_KEXEC_SIG_FORCE=y
CONFIG_ARCH_SUPPORTS_KEXEC_BZIMAGE_VERIFY_SIG=y
CONFIG_ARCH_SUPPORTS_KEXEC_JUMP=y
CONFIG_ARCH_SUPPORTS_KEXEC_HANDOVER=y
CONFIG_ARCH_SUPPORTS_CRASH_DUMP=y
CONFIG_ARCH_DEFAULT_CRASH_DUMP=y
CONFIG_ARCH_SUPPORTS_CRASH_HOTPLUG=y
CONFIG_ARCH_HAS_GENERIC_CRASHKERNEL_RESERVATION=y
CONFIG_PHYSICAL_START=0x1000000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x200000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
CONFIG_LEGACY_VSYSCALL_XONLY=y
# CONFIG_LEGACY_VSYSCALL_NONE is not set
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE="earlyprintk=serial net.ifnames=0 sysctl.kernel.hung_task_all_cpu_backtrace=1 ima_policy=tcb nf-conntrack-ftp.ports=20000 nf-conntrack-tftp.ports=20000 nf-conntrack-sip.ports=20000 nf-conntrack-irc.ports=20000 nf-conntrack-sane.ports=20000 binder.debug_mask=0 rcupdate.rcu_expedited=1 rcupdate.rcu_cpu_stall_cputime=1 no_hash_pointers page_owner=on sysctl.vm.nr_hugepages=4 sysctl.vm.nr_overcommit_hugepages=4 secretmem.enable=1 sysctl.max_rcu_stall_to_panic=1 msr.allow_writes=off coredump_filter=0xffff root=/dev/sda console=ttyS0 vsyscall=native numa=fake=2 kvm-intel.nested=1 spec_store_bypass_disable=prctl nopcid vivid.n_devs=64 vivid.multiplanar=1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2 netrom.nr_ndevs=32 rose.rose_ndevs=32 smp.csd_lock_timeout=100000 watchdog_thresh=55 workqueue.watchdog_thresh=140 sysctl.net.core.netdev_unregister_timeout_secs=140 dummy_hcd.num=32 max_loop=32 nbds_max=32 comedi.comedi_num_legacy_minors=4 panic_on_warn=1"
# CONFIG_CMDLINE_OVERRIDE is not set
CONFIG_MODIFY_LDT_SYSCALL=y
# CONFIG_STRICT_SIGALTSTACK_SIZE is not set
CONFIG_HAVE_LIVEPATCH=y
CONFIG_HAVE_KLP_BUILD=y
CONFIG_X86_BUS_LOCK_DETECT=y
# end of Processor type and features

CONFIG_CC_HAS_SLS=y
CONFIG_CC_HAS_RETURN_THUNK=y
CONFIG_CC_HAS_ENTRY_PADDING=y
CONFIG_CC_HAS_KCFI_ARITY=y
CONFIG_FUNCTION_PADDING_CFI=11
CONFIG_FUNCTION_PADDING_BYTES=16
CONFIG_CALL_PADDING=y
CONFIG_HAVE_CALL_THUNKS=y
CONFIG_CALL_THUNKS=y
CONFIG_CPU_MITIGATIONS=y
CONFIG_MITIGATION_PAGE_TABLE_ISOLATION=y
CONFIG_MITIGATION_RETPOLINE=y
CONFIG_MITIGATION_RETHUNK=y
CONFIG_MITIGATION_UNRET_ENTRY=y
CONFIG_MITIGATION_CALL_DEPTH_TRACKING=y
# CONFIG_CALL_THUNKS_DEBUG is not set
CONFIG_MITIGATION_IBPB_ENTRY=y
CONFIG_MITIGATION_IBRS_ENTRY=y
CONFIG_MITIGATION_SRSO=y
# CONFIG_MITIGATION_SLS is not set
CONFIG_MITIGATION_GDS=y
CONFIG_MITIGATION_RFDS=y
CONFIG_MITIGATION_SPECTRE_BHI=y
CONFIG_MITIGATION_MDS=y
CONFIG_MITIGATION_TAA=y
CONFIG_MITIGATION_MMIO_STALE_DATA=y
CONFIG_MITIGATION_L1TF=y
CONFIG_MITIGATION_RETBLEED=y
CONFIG_MITIGATION_SPECTRE_V1=y
CONFIG_MITIGATION_SPECTRE_V2=y
CONFIG_MITIGATION_SRBDS=y
CONFIG_MITIGATION_SSB=y
CONFIG_MITIGATION_ITS=y
CONFIG_MITIGATION_TSA=y
# CONFIG_MITIGATION_VMSCAPE is not set
CONFIG_ARCH_HAS_ADD_PAGES=y

#
# Power management and ACPI options
#
CONFIG_ARCH_HIBERNATION_HEADER=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_SUSPEND_SKIP_SYNC is not set
CONFIG_HIBERNATE_CALLBACKS=y
CONFIG_HIBERNATION=y
CONFIG_HIBERNATION_SNAPSHOT_DEV=y
CONFIG_HIBERNATION_COMP_LZO=y
# CONFIG_HIBERNATION_COMP_LZ4 is not set
CONFIG_HIBERNATION_DEF_COMP="lzo"
CONFIG_PM_STD_PARTITION=""
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_USERSPACE_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
# CONFIG_PM_QOS_CPU_SYSTEM_WAKEUP is not set
CONFIG_PM=y
CONFIG_PM_DEBUG=y
# CONFIG_PM_ADVANCED_DEBUG is not set
# CONFIG_PM_TEST_SUSPEND is not set
CONFIG_PM_SLEEP_DEBUG=y
# CONFIG_DPM_WATCHDOG is not set
CONFIG_PM_TRACE=y
CONFIG_PM_TRACE_RTC=y
CONFIG_PM_CLK=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
# CONFIG_ENERGY_MODEL is not set
CONFIG_ARCH_SUPPORTS_ACPI=y
CONFIG_ACPI=y
CONFIG_ACPI_LEGACY_TABLES_LOOKUP=y
CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=y
CONFIG_ACPI_SYSTEM_POWER_STATES_SUPPORT=y
CONFIG_ACPI_THERMAL_LIB=y
# CONFIG_ACPI_DEBUGGER is not set
CONFIG_ACPI_SPCR_TABLE=y
# CONFIG_ACPI_FPDT is not set
CONFIG_ACPI_LPIT=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y
CONFIG_ACPI_EC=y
# CONFIG_ACPI_EC_DEBUGFS is not set
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_VIDEO=y
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_TAD is not set
CONFIG_ACPI_DOCK=y
CONFIG_ACPI_CPU_FREQ_PSS=y
CONFIG_ACPI_PROCESSOR_CSTATE=y
CONFIG_ACPI_PROCESSOR_IDLE=y
CONFIG_ACPI_CPPC_LIB=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_PLATFORM_PROFILE=y
CONFIG_ARCH_HAS_ACPI_TABLE_UPGRADE=y
CONFIG_ACPI_TABLE_UPGRADE=y
CONFIG_ACPI_DEBUG=y
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_HOTPLUG_MEMORY is not set
CONFIG_ACPI_HOTPLUG_IOAPIC=y
# CONFIG_ACPI_SBS is not set
# CONFIG_ACPI_HED is not set
# CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not set
CONFIG_ACPI_NHLT=y
CONFIG_ACPI_NFIT=y
# CONFIG_NFIT_SECURITY_DEBUG is not set
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_HMAT is not set
CONFIG_HAVE_ACPI_APEI=y
CONFIG_HAVE_ACPI_APEI_NMI=y
# CONFIG_ACPI_APEI is not set
# CONFIG_ACPI_DPTF is not set
# CONFIG_ACPI_EXTLOG is not set
# CONFIG_ACPI_CONFIGFS is not set
# CONFIG_ACPI_PFRUT is not set
CONFIG_ACPI_PCC=y
# CONFIG_ACPI_FFH is not set
CONFIG_ACPI_MRRM=y
CONFIG_PMIC_OPREGION=y
CONFIG_BXT_WC_PMIC_OPREGION=y
# CONFIG_CHT_WC_PMIC_OPREGION is not set
CONFIG_X86_PM_TIMER=y

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_GOV_ATTR_SET=y
CONFIG_CPU_FREQ_GOV_COMMON=y
# CONFIG_CPU_FREQ_STAT is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
# CONFIG_CPU_FREQ_GOV_POWERSAVE is not set
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y

#
# CPU frequency scaling drivers
#
# CONFIG_CPUFREQ_DT is not set
# CONFIG_CPUFREQ_DT_PLATDEV is not set
CONFIG_X86_INTEL_PSTATE=y
# CONFIG_X86_PCC_CPUFREQ is not set
CONFIG_X86_AMD_PSTATE=y
CONFIG_X86_AMD_PSTATE_DEFAULT_MODE=3
# CONFIG_X86_AMD_PSTATE_UT is not set
CONFIG_X86_ACPI_CPUFREQ=y
CONFIG_X86_ACPI_CPUFREQ_CPB=y
# CONFIG_X86_POWERNOW_K8 is not set
# CONFIG_X86_AMD_FREQ_SENSITIVITY is not set
# CONFIG_X86_SPEEDSTEP_CENTRINO is not set
# CONFIG_X86_P4_CLOCKMOD is not set

#
# shared options
#
CONFIG_CPUFREQ_ARCH_CUR_FREQ=y
# end of CPU Frequency scaling

#
# CPU Idle
#
CONFIG_CPU_IDLE=y
# CONFIG_CPU_IDLE_GOV_LADDER is not set
CONFIG_CPU_IDLE_GOV_MENU=y
# CONFIG_CPU_IDLE_GOV_TEO is not set
CONFIG_CPU_IDLE_GOV_HALTPOLL=y
CONFIG_HALTPOLL_CPUIDLE=y
# end of CPU Idle

CONFIG_INTEL_IDLE=y
# end of Power management and ACPI options

#
# Bus options (PCI etc.)
#
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_MMCONF_FAM10H=y
CONFIG_ISA_BUS=y
CONFIG_ISA_DMA_API=y
CONFIG_AMD_NB=y
CONFIG_AMD_NODE=y
# end of Bus options (PCI etc.)

#
# Binary Emulations
#
CONFIG_IA32_EMULATION=y
# CONFIG_IA32_EMULATION_DEFAULT_DISABLED is not set
CONFIG_COMPAT_32=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
# end of Binary Emulations

CONFIG_KVM_COMMON=y
CONFIG_HAVE_KVM_PFNCACHE=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_HAVE_KVM_IRQ_ROUTING=y
CONFIG_HAVE_KVM_DIRTY_RING=y
CONFIG_HAVE_KVM_DIRTY_RING_TSO=y
CONFIG_HAVE_KVM_DIRTY_RING_ACQ_REL=y
CONFIG_KVM_MMIO=y
CONFIG_KVM_ASYNC_PF=y
CONFIG_HAVE_KVM_MSI=y
CONFIG_HAVE_KVM_READONLY_MEM=y
CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT=y
CONFIG_KVM_VFIO=y
CONFIG_KVM_GENERIC_DIRTYLOG_READ_PROTECT=y
CONFIG_KVM_GENERIC_PRE_FAULT_MEMORY=y
CONFIG_KVM_COMPAT=y
CONFIG_HAVE_KVM_IRQ_BYPASS=y
CONFIG_HAVE_KVM_NO_POLL=y
CONFIG_VIRT_XFER_TO_GUEST_WORK=y
CONFIG_HAVE_KVM_PM_NOTIFIER=y
CONFIG_KVM_GENERIC_HARDWARE_ENABLING=y
CONFIG_KVM_ELIDE_TLB_FLUSH_IF_YOUNG=y
CONFIG_KVM_MMU_LOCKLESS_AGING=y
CONFIG_KVM_GENERIC_MEMORY_ATTRIBUTES=y
CONFIG_KVM_GUEST_MEMFD=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM_X86=y
CONFIG_KVM=y
CONFIG_KVM_SW_PROTECTED_VM=y
CONFIG_KVM_INTEL=y
# CONFIG_KVM_INTEL_PROVE_VE is not set
CONFIG_X86_SGX_KVM=y
CONFIG_KVM_AMD=y
CONFIG_KVM_IOAPIC=y
CONFIG_KVM_SMM=y
CONFIG_KVM_HYPERV=y
CONFIG_KVM_XEN=y
CONFIG_KVM_PROVE_MMU=y
CONFIG_KVM_MAX_NR_VCPUS=1024
CONFIG_X86_REQUIRED_FEATURE_ALWAYS=y
CONFIG_X86_REQUIRED_FEATURE_NOPL=y
CONFIG_X86_REQUIRED_FEATURE_CX8=y
CONFIG_X86_REQUIRED_FEATURE_CMOV=y
CONFIG_X86_REQUIRED_FEATURE_CPUID=y
CONFIG_X86_REQUIRED_FEATURE_FPU=y
CONFIG_X86_REQUIRED_FEATURE_PAE=y
CONFIG_X86_REQUIRED_FEATURE_PSE=y
CONFIG_X86_REQUIRED_FEATURE_PGE=y
CONFIG_X86_REQUIRED_FEATURE_MSR=y
CONFIG_X86_REQUIRED_FEATURE_FXSR=y
CONFIG_X86_REQUIRED_FEATURE_XMM=y
CONFIG_X86_REQUIRED_FEATURE_XMM2=y
CONFIG_X86_REQUIRED_FEATURE_LM=y
CONFIG_X86_DISABLED_FEATURE_VME=y
CONFIG_X86_DISABLED_FEATURE_K6_MTRR=y
CONFIG_X86_DISABLED_FEATURE_CYRIX_ARR=y
CONFIG_X86_DISABLED_FEATURE_CENTAUR_MCR=y
CONFIG_X86_DISABLED_FEATURE_LAM=y
CONFIG_X86_DISABLED_FEATURE_XENPV=y
CONFIG_X86_DISABLED_FEATURE_TDX_GUEST=y
CONFIG_X86_DISABLED_FEATURE_SEV_SNP=y
CONFIG_AS_WRUSS=y
CONFIG_ARCH_CONFIGURES_CPU_MITIGATIONS=y

#
# General architecture-dependent options
#
CONFIG_HOTPLUG_SMT=y
CONFIG_ARCH_SUPPORTS_SCHED_SMT=y
CONFIG_ARCH_SUPPORTS_SCHED_CLUSTER=y
CONFIG_ARCH_SUPPORTS_SCHED_MC=y
CONFIG_SCHED_SMT=y
CONFIG_SCHED_CLUSTER=y
CONFIG_SCHED_MC=y
CONFIG_HOTPLUG_CORE_SYNC=y
CONFIG_HOTPLUG_CORE_SYNC_DEAD=y
CONFIG_HOTPLUG_CORE_SYNC_FULL=y
CONFIG_HOTPLUG_SPLIT_STARTUP=y
CONFIG_HOTPLUG_PARALLEL=y
CONFIG_GENERIC_IRQ_ENTRY=y
CONFIG_GENERIC_SYSCALL=y
CONFIG_GENERIC_ENTRY=y
CONFIG_ARCH_SUPPORTS_SYSCALL_USER_DISPATCH=y
CONFIG_SYSCALL_USER_DISPATCH=y
# CONFIG_KPROBES is not set
CONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not set
# CONFIG_STATIC_CALL_SELFTEST is not set
CONFIG_UPROBES=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_ARCH_USE_BUILTIN_BSWAP=y
CONFIG_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_KPROBES_ON_FTRACE=y
CONFIG_ARCH_CORRECT_STACKTRACE_ON_KRETPROBE=y
CONFIG_HAVE_FUNCTION_ERROR_INJECTION=y
CONFIG_HAVE_NMI=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_NMI_SUPPORT=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_CONTIGUOUS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_ARCH_HAS_FORTIFY_SOURCE=y
CONFIG_ARCH_HAS_SET_MEMORY=y
CONFIG_ARCH_HAS_SET_DIRECT_MAP=y
CONFIG_ARCH_HAS_CPU_FINALIZE_INIT=y
CONFIG_ARCH_HAS_DELAY_TIMER=y
CONFIG_ARCH_HAS_CPU_PASID=y
CONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=y
CONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT=y
CONFIG_ARCH_WANTS_NO_INSTR=y
CONFIG_ARCH_MEMORY_ORDER_TSO=y
CONFIG_HAVE_ASM_MODVERSIONS=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_RSEQ=y
CONFIG_HAVE_RUST=y
CONFIG_HAVE_FUNCTION_ARG_ACCESS_API=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_HARDLOCKUP_DETECTOR_PERF=y
CONFIG_UNWIND_USER=y
CONFIG_HAVE_UNWIND_USER_FP=y
CONFIG_HAVE_PERF_REGS=y
CONFIG_HAVE_PERF_USER_STACK_DUMP=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_HAVE_ARCH_JUMP_LABEL_RELATIVE=y
CONFIG_MMU_GATHER_TABLE_FREE=y
CONFIG_MMU_GATHER_RCU_TABLE_FREE=y
CONFIG_MMU_GATHER_MERGE_VMAS=y
CONFIG_ARCH_WANT_IRQS_OFF_ACTIVATE_MM=y
CONFIG_MMU_LAZY_TLB_REFCOUNT=y
CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
CONFIG_ARCH_HAVE_EXTRA_ELF_NOTES=y
CONFIG_ARCH_HAS_NMI_SAFE_THIS_CPU_OPS=y
CONFIG_HAVE_ALIGNED_STRUCT_PAGE=y
CONFIG_HAVE_CMPXCHG_LOCAL=y
CONFIG_HAVE_CMPXCHG_DOUBLE=y
CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y
CONFIG_ARCH_WANT_OLD_COMPAT_IPC=y
CONFIG_HAVE_ARCH_SECCOMP=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP=y
CONFIG_SECCOMP_FILTER=y
# CONFIG_SECCOMP_CACHE_DEBUG is not set
CONFIG_HAVE_ARCH_KSTACK_ERASE=y
CONFIG_HAVE_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR_STRONG=y
CONFIG_ARCH_SUPPORTS_LTO_CLANG=y
CONFIG_ARCH_SUPPORTS_LTO_CLANG_THIN=y
CONFIG_HAS_LTO_CLANG=y
CONFIG_LTO_NONE=y
# CONFIG_LTO_CLANG_FULL is not set
# CONFIG_LTO_CLANG_THIN is not set
# CONFIG_LTO_CLANG_THIN_DIST is not set
CONFIG_AUTOFDO_CLANG=y
CONFIG_PROPELLER_CLANG=y
CONFIG_ARCH_SUPPORTS_CFI=y
# CONFIG_CFI is not set
CONFIG_HAVE_CFI_ICALL_NORMALIZE_INTEGERS=y
CONFIG_HAVE_CFI_ICALL_NORMALIZE_INTEGERS_RUSTC=y
CONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=y
CONFIG_HAVE_CONTEXT_TRACKING_USER=y
CONFIG_HAVE_CONTEXT_TRACKING_USER_OFFSTACK=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_PV_STEAL_CLOCK_GEN=y
CONFIG_HAVE_MOVE_PUD=y
CONFIG_HAVE_MOVE_PMD=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD=y
CONFIG_HAVE_ARCH_HUGE_VMAP=y
CONFIG_HAVE_ARCH_HUGE_VMALLOC=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_HAVE_ARCH_SOFT_DIRTY=y
CONFIG_HAVE_MOD_ARCH_SPECIFIC=y
CONFIG_MODULES_USE_ELF_RELA=y
CONFIG_ARCH_HAS_EXECMEM_ROX=y
CONFIG_HAVE_IRQ_EXIT_ON_IRQ_STACK=y
CONFIG_HAVE_SOFTIRQ_ON_OWN_STACK=y
CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
CONFIG_HAVE_ARCH_MMAP_RND_BITS=y
CONFIG_HAVE_EXIT_THREAD=y
CONFIG_ARCH_MMAP_RND_BITS=28
CONFIG_HAVE_ARCH_MMAP_RND_COMPAT_BITS=y
CONFIG_ARCH_MMAP_RND_COMPAT_BITS=8
CONFIG_HAVE_ARCH_COMPAT_MMAP_BASES=y
CONFIG_HAVE_PAGE_SIZE_4KB=y
CONFIG_PAGE_SIZE_4KB=y
CONFIG_PAGE_SIZE_LESS_THAN_64KB=y
CONFIG_PAGE_SIZE_LESS_THAN_256KB=y
CONFIG_PAGE_SHIFT=12
CONFIG_HAVE_OBJTOOL=y
CONFIG_HAVE_JUMP_LABEL_HACK=y
CONFIG_HAVE_NOINSTR_HACK=y
CONFIG_HAVE_NOINSTR_VALIDATION=y
CONFIG_HAVE_UACCESS_VALIDATION=y
CONFIG_HAVE_STACK_VALIDATION=y
CONFIG_HAVE_RELIABLE_STACKTRACE=y
CONFIG_OLD_SIGSUSPEND3=y
CONFIG_COMPAT_OLD_SIGACTION=y
CONFIG_COMPAT_32BIT_TIME=y
CONFIG_ARCH_SUPPORTS_RT=y
CONFIG_HAVE_ARCH_VMAP_STACK=y
CONFIG_VMAP_STACK=y
CONFIG_HAVE_ARCH_RANDOMIZE_KSTACK_OFFSET=y
CONFIG_RANDOMIZE_KSTACK_OFFSET=y
# CONFIG_RANDOMIZE_KSTACK_OFFSET_DEFAULT is not set
CONFIG_ARCH_HAS_STRICT_KERNEL_RWX=y
CONFIG_STRICT_KERNEL_RWX=y
CONFIG_ARCH_HAS_STRICT_MODULE_RWX=y
CONFIG_STRICT_MODULE_RWX=y
CONFIG_HAVE_ARCH_PREL32_RELOCATIONS=y
# CONFIG_LOCK_EVENT_COUNTS is not set
CONFIG_ARCH_HAS_MEM_ENCRYPT=y
CONFIG_HAVE_STATIC_CALL=y
CONFIG_HAVE_STATIC_CALL_INLINE=y
CONFIG_HAVE_PREEMPT_DYNAMIC=y
CONFIG_HAVE_PREEMPT_DYNAMIC_CALL=y
CONFIG_ARCH_WANT_LD_ORPHAN_WARN=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_ARCH_SUPPORTS_PAGE_TABLE_CHECK=y
CONFIG_ARCH_HAS_ELFCORE_COMPAT=y
CONFIG_ARCH_HAS_PARANOID_L1D_FLUSH=y
CONFIG_DYNAMIC_SIGFRAME=y
CONFIG_HAVE_ARCH_NODE_DEV_GROUP=y
CONFIG_ARCH_HAS_HW_PTE_YOUNG=y
CONFIG_ARCH_HAS_NONLEAF_PMD_YOUNG=y
CONFIG_ARCH_HAS_KERNEL_FPU_SUPPORT=y
CONFIG_HAVE_GENERIC_TIF_BITS=y

#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
# end of GCOV-based kernel profiling

CONFIG_HAVE_GCC_PLUGINS=y
CONFIG_FUNCTION_ALIGNMENT_4B=y
CONFIG_FUNCTION_ALIGNMENT_16B=y
CONFIG_FUNCTION_ALIGNMENT=16
CONFIG_CC_HAS_SANE_FUNCTION_ALIGNMENT=y
CONFIG_ARCH_HAS_CPU_ATTACK_VECTORS=y
# end of General architecture-dependent options

CONFIG_RT_MUTEXES=y
CONFIG_MODULE_SIG_FORMAT=y
CONFIG_MODULES=y
# CONFIG_MODULE_DEBUG is not set
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_MODULE_UNLOAD_TAINT_TRACKING is not set
CONFIG_MODVERSIONS=y
# CONFIG_GENKSYMS is not set
CONFIG_GENDWARFKSYMS=y
CONFIG_ASM_MODVERSIONS=y
# CONFIG_EXTENDED_MODVERSIONS is not set
# CONFIG_BASIC_MODVERSIONS is not set
CONFIG_MODULE_SRCVERSION_ALL=y
CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set
# CONFIG_MODULE_SIG_ALL is not set
CONFIG_MODULE_SIG_SHA256=y
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not set
# CONFIG_MODULE_SIG_SHA3_256 is not set
# CONFIG_MODULE_SIG_SHA3_384 is not set
# CONFIG_MODULE_SIG_SHA3_512 is not set
CONFIG_MODULE_SIG_HASH="sha256"
# CONFIG_MODULE_COMPRESS is not set
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set
CONFIG_MODPROBE_PATH="/sbin/modprobe"
# CONFIG_TRIM_UNUSED_KSYMS is not set
CONFIG_MODULES_TREE_LOOKUP=y
CONFIG_BLOCK=y
CONFIG_BLOCK_LEGACY_AUTOLOAD=y
CONFIG_BLK_RQ_ALLOC_TIME=y
CONFIG_BLK_CGROUP_RWSTAT=y
CONFIG_BLK_CGROUP_PUNT_BIO=y
CONFIG_BLK_DEV_BSG_COMMON=y
CONFIG_BLK_ICQ=y
CONFIG_BLK_DEV_BSGLIB=y
CONFIG_BLK_DEV_INTEGRITY=y
# CONFIG_BLK_DEV_WRITE_MOUNTED is not set
CONFIG_BLK_DEV_ZONED=y
CONFIG_BLK_DEV_THROTTLING=y
CONFIG_BLK_WBT=y
CONFIG_BLK_WBT_MQ=y
CONFIG_BLK_CGROUP_IOLATENCY=y
# CONFIG_BLK_CGROUP_FC_APPID is not set
CONFIG_BLK_CGROUP_IOCOST=y
CONFIG_BLK_CGROUP_IOPRIO=y
CONFIG_BLK_DEBUG_FS=y
# CONFIG_BLK_SED_OPAL is not set
CONFIG_BLK_INLINE_ENCRYPTION=y
CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK=y

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_ACORN_PARTITION=y
CONFIG_ACORN_PARTITION_CUMANA=y
CONFIG_ACORN_PARTITION_EESOX=y
CONFIG_ACORN_PARTITION_ICS=y
CONFIG_ACORN_PARTITION_ADFS=y
CONFIG_ACORN_PARTITION_POWERTEC=y
CONFIG_ACORN_PARTITION_RISCIX=y
CONFIG_AIX_PARTITION=y
CONFIG_OSF_PARTITION=y
CONFIG_AMIGA_PARTITION=y
CONFIG_ATARI_PARTITION=y
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_MINIX_SUBPARTITION=y
CONFIG_SOLARIS_X86_PARTITION=y
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
CONFIG_SGI_PARTITION=y
CONFIG_ULTRIX_PARTITION=y
CONFIG_SUN_PARTITION=y
CONFIG_KARMA_PARTITION=y
CONFIG_EFI_PARTITION=y
CONFIG_SYSV68_PARTITION=y
CONFIG_CMDLINE_PARTITION=y
# CONFIG_OF_PARTITION is not set
# end of Partition Types

CONFIG_BLK_PM=y
CONFIG_BLOCK_HOLDER_DEPRECATED=y
CONFIG_BLK_MQ_STACKING=y
# CONFIG_BLK_ERROR_INJECTION is not set

#
# IO Schedulers
#
CONFIG_MQ_IOSCHED_DEADLINE=y
CONFIG_MQ_IOSCHED_KYBER=y
CONFIG_IOSCHED_BFQ=y
CONFIG_BFQ_GROUP_IOSCHED=y
CONFIG_BFQ_CGROUP_DEBUG=y
# end of IO Schedulers

CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_PADATA=y
CONFIG_ASN1=y
CONFIG_UNINLINE_SPIN_UNLOCK=y
CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_RWSEM_SPIN_ON_OWNER=y
CONFIG_LOCK_SPIN_ON_OWNER=y
CONFIG_ARCH_USE_QUEUED_SPINLOCKS=y
CONFIG_QUEUED_SPINLOCKS=y
# CONFIG_QUEUED_SPINLOCKS_TRACE_CONTENDED_RELEASE is not set
CONFIG_ARCH_USE_QUEUED_RWLOCKS=y
CONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE=y
CONFIG_ARCH_HAS_SYNC_CORE_BEFORE_USERMODE=y
CONFIG_ARCH_HAS_SYSCALL_WRAPPER=y
CONFIG_FREEZER=y

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_ELFCORE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_BINFMT_SCRIPT=y
CONFIG_BINFMT_MISC=y
CONFIG_COREDUMP=y
# end of Executable file formats

#
# Memory Management options
#
CONFIG_SWAP=y
CONFIG_ZSWAP=y
CONFIG_ZSWAP_DEFAULT_ON=y
CONFIG_ZSWAP_SHRINKER_DEFAULT_ON=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_DEFLATE is not set
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZO is not set
CONFIG_ZSWAP_COMPRESSOR_DEFAULT_842=y
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4 is not set
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4HC is not set
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_ZSTD is not set
CONFIG_ZSWAP_COMPRESSOR_DEFAULT="842"
CONFIG_ZSMALLOC=y

#
# Zsmalloc allocator options
#

#
# Zsmalloc is a common backend allocator for zswap & zram
#
# CONFIG_ZSMALLOC_STAT is not set
CONFIG_ZSMALLOC_CHAIN_SIZE=8
# end of Zsmalloc allocator options

#
# Slab allocator options
#
CONFIG_SLUB=y
CONFIG_KVFREE_RCU_BATCHED=y
# CONFIG_SLUB_TINY is not set
CONFIG_SLAB_MERGE_DEFAULT=y
# CONFIG_SLAB_FREELIST_RANDOM is not set
# CONFIG_SLAB_FREELIST_HARDENED is not set
# CONFIG_SLAB_BUCKETS is not set
# CONFIG_SLUB_STATS is not set
# CONFIG_KMALLOC_PARTITION_CACHES is not set
# end of Slab allocator options

# CONFIG_SHUFFLE_PAGE_ALLOCATOR is not set
# CONFIG_COMPAT_BRK is not set
CONFIG_SPARSEMEM=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_SPARSEMEM_VMEMMAP_PREINIT=y
CONFIG_ARCH_WANT_OPTIMIZE_DAX_VMEMMAP=y
CONFIG_ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP=y
CONFIG_ARCH_WANT_HUGETLB_VMEMMAP_PREINIT=y
CONFIG_HAVE_GUP_FAST=y
CONFIG_NUMA_KEEP_MEMINFO=y
CONFIG_MEMORY_ISOLATION=y
CONFIG_EXCLUSIVE_SYSTEM_RAM=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTPLUG=y
# CONFIG_MHP_DEFAULT_ONLINE_TYPE_OFFLINE is not set
CONFIG_MHP_DEFAULT_ONLINE_TYPE_ONLINE_AUTO=y
# CONFIG_MHP_DEFAULT_ONLINE_TYPE_ONLINE_KERNEL is not set
# CONFIG_MHP_DEFAULT_ONLINE_TYPE_ONLINE_MOVABLE is not set
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_MHP_MEMMAP_ON_MEMORY=y
CONFIG_ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE=y
CONFIG_SPLIT_PTE_PTLOCKS=y
CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y
CONFIG_SPLIT_PMD_PTLOCKS=y
CONFIG_BALLOON=y
# CONFIG_BALLOON_MIGRATION is not set
CONFIG_COMPACTION=y
CONFIG_COMPACT_UNEVICTABLE_DEFAULT=0
CONFIG_PAGE_REPORTING=y
CONFIG_NUMA_MIGRATION=y
CONFIG_MIGRATION=y
CONFIG_DEVICE_MIGRATION=y
CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=y
CONFIG_CONTIG_ALLOC=y
CONFIG_PCP_BATCH_SCALE_MAX=5
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_MMU_NOTIFIER=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_MEMORY_FAILURE is not set
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ARCH_WANTS_THP_SWAP=y
CONFIG_PAGE_MAPCOUNT=y
CONFIG_PGTABLE_HAS_HUGE_LEAVES=y
CONFIG_HAVE_GIGANTIC_FOLIOS=y
CONFIG_ASYNC_KERNEL_PGTABLE_FREE=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_USE_PERCPU_NUMA_NODE_ID=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_CMA=y
# CONFIG_CMA_DEBUGFS is not set
# CONFIG_CMA_SYSFS is not set
CONFIG_CMA_AREAS=20
CONFIG_PAGE_BLOCK_MAX_ORDER=10
CONFIG_MEM_SOFT_DIRTY=y
CONFIG_GENERIC_EARLY_IOREMAP=y
# CONFIG_DEFERRED_STRUCT_PAGE_INIT is not set
CONFIG_PAGE_IDLE_FLAG=y
# CONFIG_IDLE_PAGE_TRACKING is not set
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_ARCH_HAS_CURRENT_STACK_POINTER=y
CONFIG_ARCH_HAS_ZONE_DMA_SET=y
CONFIG_ZONE_DMA=y
CONFIG_ZONE_DMA32=y
CONFIG_ZONE_DEVICE=y
CONFIG_HMM_MIRROR=y
CONFIG_GET_FREE_REGION=y
CONFIG_DEVICE_PRIVATE=y
CONFIG_ARCH_USES_HIGH_VMA_FLAGS=y
CONFIG_ARCH_HAS_PKEYS=y
CONFIG_ARCH_USES_PG_ARCH_2=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PERCPU_STATS=y
# CONFIG_GUP_TEST is not set
# CONFIG_DMAPOOL_TEST is not set
CONFIG_ARCH_HAS_PTE_SPECIAL=y
CONFIG_MAPPING_DIRTY_HELPERS=y
CONFIG_KMAP_LOCAL=y
CONFIG_MEMFD_CREATE=y
CONFIG_SECRETMEM=y
CONFIG_ANON_VMA_NAME=y
CONFIG_HAVE_ARCH_USERFAULTFD_WP=y
CONFIG_HAVE_ARCH_USERFAULTFD_MINOR=y
CONFIG_USERFAULTFD_RWP=y
CONFIG_USERFAULTFD=y
# CONFIG_PTE_MARKER_UFFD_WP is not set
# CONFIG_LRU_GEN is not set
CONFIG_ARCH_SUPPORTS_PER_VMA_LOCK=y
CONFIG_PER_VMA_LOCK=y
CONFIG_LOCK_MM_AND_FIND_VMA=y
CONFIG_IOMMU_MM_DATA=y
CONFIG_EXECMEM=y
CONFIG_NUMA_MEMBLKS=y
CONFIG_NUMA_EMU=y
CONFIG_ARCH_HAS_USER_SHADOW_STACK=y
CONFIG_PT_RECLAIM=y

#
# Data Access Monitoring
#
CONFIG_DAMON=y
# CONFIG_DAMON_DEBUG_SANITY is not set
CONFIG_DAMON_VADDR=y
CONFIG_DAMON_PADDR=y
# CONFIG_DAMON_SYSFS is not set
CONFIG_DAMON_RECLAIM=y
# CONFIG_DAMON_LRU_SORT is not set
# CONFIG_DAMON_STAT is not set
# end of Data Access Monitoring
# end of Memory Management options

CONFIG_NET=y
CONFIG_WANT_COMPAT_NETLINK_MESSAGES=y
CONFIG_COMPAT_NETLINK_MESSAGES=y
CONFIG_NET_INGRESS=y
CONFIG_NET_EGRESS=y
CONFIG_NET_XGRESS=y
CONFIG_NET_REDIRECT=y
CONFIG_SKB_DECRYPTED=y
CONFIG_SKB_EXTENSIONS=y
CONFIG_NET_DEVMEM=y
CONFIG_NET_SHAPER=y
CONFIG_NET_CRC32C=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_DIAG=y
CONFIG_INET_PSP=y
CONFIG_UNIX=y
CONFIG_AF_UNIX_OOB=y
CONFIG_UNIX_DIAG=y
CONFIG_TLS=y
CONFIG_TLS_DEVICE=y
CONFIG_XFRM=y
CONFIG_XFRM_OFFLOAD=y
CONFIG_XFRM_ALGO=y
CONFIG_XFRM_USER=y
CONFIG_XFRM_USER_COMPAT=y
CONFIG_XFRM_INTERFACE=y
CONFIG_XFRM_SUB_POLICY=y
CONFIG_XFRM_MIGRATE=y
CONFIG_XFRM_STATISTICS=y
CONFIG_XFRM_AH=y
CONFIG_XFRM_ESP=y
CONFIG_XFRM_IPCOMP=y
CONFIG_NET_KEY=y
CONFIG_NET_KEY_MIGRATE=y
CONFIG_XFRM_IPTFS=y
CONFIG_XFRM_ESPINTCP=y
CONFIG_SMC=y
CONFIG_SMC_DIAG=y
# CONFIG_SMC_HS_CTRL_BPF is not set
CONFIG_DIBS=y
CONFIG_DIBS_LO=y
CONFIG_XDP_SOCKETS=y
CONFIG_XDP_SOCKETS_DIAG=y
CONFIG_NET_HANDSHAKE=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_FIB_TRIE_STATS=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_ROUTE_CLASSID=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
CONFIG_NET_IPIP=y
CONFIG_NET_IPGRE_DEMUX=y
CONFIG_NET_IP_TUNNEL=y
CONFIG_NET_IPGRE=y
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE_COMMON=y
CONFIG_IP_MROUTE=y
CONFIG_IP_MROUTE_MULTIPLE_TABLES=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_SYN_COOKIES=y
CONFIG_NET_IPVTI=y
CONFIG_NET_UDP_TUNNEL=y
CONFIG_NET_FOU=y
CONFIG_NET_FOU_IP_TUNNELS=y
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_ESP_OFFLOAD=y
CONFIG_INET_ESPINTCP=y
CONFIG_INET_IPCOMP=y
CONFIG_INET_TABLE_PERTURB_ORDER=16
CONFIG_INET_XFRM_TUNNEL=y
CONFIG_INET_TUNNEL=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_INET_UDP_DIAG=y
CONFIG_INET_RAW_DIAG=y
CONFIG_INET_DIAG_DESTROY=y
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_CONG_BIC=y
CONFIG_TCP_CONG_CUBIC=y
CONFIG_TCP_CONG_WESTWOOD=y
CONFIG_TCP_CONG_HTCP=y
CONFIG_TCP_CONG_HSTCP=y
CONFIG_TCP_CONG_HYBLA=y
CONFIG_TCP_CONG_VEGAS=y
CONFIG_TCP_CONG_NV=y
CONFIG_TCP_CONG_SCALABLE=y
CONFIG_TCP_CONG_LP=y
CONFIG_TCP_CONG_VENO=y
CONFIG_TCP_CONG_YEAH=y
CONFIG_TCP_CONG_ILLINOIS=y
CONFIG_TCP_CONG_DCTCP=y
CONFIG_TCP_CONG_CDG=y
CONFIG_TCP_CONG_BBR=y
# CONFIG_DEFAULT_BIC is not set
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_HTCP is not set
# CONFIG_DEFAULT_HYBLA is not set
# CONFIG_DEFAULT_VEGAS is not set
# CONFIG_DEFAULT_VENO is not set
# CONFIG_DEFAULT_WESTWOOD is not set
# CONFIG_DEFAULT_DCTCP is not set
# CONFIG_DEFAULT_CDG is not set
# CONFIG_DEFAULT_BBR is not set
# CONFIG_DEFAULT_RENO is not set
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_AO is not set
CONFIG_TCP_MD5SIG=y
CONFIG_IPV6=y
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=y
CONFIG_INET6_ESP=y
CONFIG_INET6_ESP_OFFLOAD=y
CONFIG_INET6_ESPINTCP=y
CONFIG_INET6_IPCOMP=y
CONFIG_IPV6_MIP6=y
CONFIG_IPV6_ILA=y
CONFIG_INET6_XFRM_TUNNEL=y
CONFIG_INET6_TUNNEL=y
CONFIG_IPV6_VTI=y
CONFIG_IPV6_SIT=y
CONFIG_IPV6_SIT_6RD=y
CONFIG_IPV6_NDISC_NODETYPE=y
CONFIG_IPV6_TUNNEL=y
CONFIG_IPV6_GRE=y
CONFIG_IPV6_FOU=y
CONFIG_IPV6_FOU_TUNNEL=y
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
CONFIG_IPV6_PIMSM_V2=y
CONFIG_IPV6_SEG6_LWTUNNEL=y
CONFIG_IPV6_SEG6_HMAC=y
CONFIG_IPV6_SEG6_BPF=y
CONFIG_IPV6_RPL_LWTUNNEL=y
# CONFIG_IPV6_IOAM6_LWTUNNEL is not set
CONFIG_NETLABEL=y
CONFIG_MPTCP=y
CONFIG_INET_MPTCP_DIAG=y
CONFIG_MPTCP_IPV6=y
CONFIG_NETWORK_SECMARK=y
CONFIG_NET_PTP_CLASSIFY=y
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
CONFIG_NETFILTER=y
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_INGRESS=y
CONFIG_NETFILTER_EGRESS=y
CONFIG_NETFILTER_SKIP_EGRESS=y
CONFIG_NETFILTER_NETLINK=y
CONFIG_NETFILTER_FAMILY_BRIDGE=y
CONFIG_NETFILTER_FAMILY_ARP=y
CONFIG_NETFILTER_BPF_LINK=y
# CONFIG_NETFILTER_NETLINK_HOOK is not set
CONFIG_NETFILTER_NETLINK_ACCT=y
CONFIG_NETFILTER_NETLINK_QUEUE=y
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NETFILTER_NETLINK_OSF=y
CONFIG_NF_CONNTRACK=y
CONFIG_NF_LOG_SYSLOG=y
CONFIG_NETFILTER_CONNCOUNT=y
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_ZONES=y
# CONFIG_NF_CONNTRACK_PROCFS is not set
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CONNTRACK_TIMEOUT=y
CONFIG_NF_CONNTRACK_TIMESTAMP=y
CONFIG_NF_CONNTRACK_LABELS=y
CONFIG_NF_CONNTRACK_OVS=y
CONFIG_NF_CT_PROTO_GRE=y
CONFIG_NF_CT_PROTO_SCTP=y
CONFIG_NF_CONNTRACK_AMANDA=y
CONFIG_NF_CONNTRACK_FTP=y
CONFIG_NF_CONNTRACK_H323=y
CONFIG_NF_CONNTRACK_IRC=y
CONFIG_NF_CONNTRACK_BROADCAST=y
CONFIG_NF_CONNTRACK_NETBIOS_NS=y
CONFIG_NF_CONNTRACK_SNMP=y
CONFIG_NF_CONNTRACK_PPTP=y
CONFIG_NF_CONNTRACK_SANE=y
CONFIG_NF_CONNTRACK_SIP=y
CONFIG_NF_CONNTRACK_TFTP=y
CONFIG_NF_CT_NETLINK=y
CONFIG_NF_CT_NETLINK_TIMEOUT=y
CONFIG_NF_CT_NETLINK_HELPER=y
CONFIG_NETFILTER_NETLINK_GLUE_CT=y
CONFIG_NF_NAT=y
CONFIG_NF_NAT_AMANDA=y
CONFIG_NF_NAT_FTP=y
CONFIG_NF_NAT_IRC=y
CONFIG_NF_NAT_SIP=y
CONFIG_NF_NAT_TFTP=y
CONFIG_NF_NAT_REDIRECT=y
CONFIG_NF_NAT_MASQUERADE=y
CONFIG_NF_NAT_OVS=y
CONFIG_NETFILTER_SYNPROXY=y
CONFIG_NF_TABLES=y
CONFIG_NF_TABLES_INET=y
CONFIG_NF_TABLES_NETDEV=y
CONFIG_NFT_NUMGEN=y
CONFIG_NFT_CT=y
CONFIG_NFT_EXTHDR_DCCP=y
CONFIG_NFT_FLOW_OFFLOAD=y
CONFIG_NFT_CONNLIMIT=y
CONFIG_NFT_LOG=y
CONFIG_NFT_LIMIT=y
CONFIG_NFT_MASQ=y
CONFIG_NFT_REDIR=y
CONFIG_NFT_NAT=y
CONFIG_NFT_TUNNEL=y
CONFIG_NFT_QUEUE=y
CONFIG_NFT_QUOTA=y
CONFIG_NFT_REJECT=y
CONFIG_NFT_REJECT_INET=y
CONFIG_NFT_COMPAT=y
CONFIG_NFT_HASH=y
CONFIG_NFT_FIB=y
CONFIG_NFT_FIB_INET=y
CONFIG_NFT_XFRM=y
CONFIG_NFT_SOCKET=y
CONFIG_NFT_OSF=y
CONFIG_NFT_TPROXY=y
CONFIG_NFT_SYNPROXY=y
CONFIG_NF_DUP_NETDEV=y
CONFIG_NFT_DUP_NETDEV=y
CONFIG_NFT_FWD_NETDEV=y
CONFIG_NFT_FIB_NETDEV=y
CONFIG_NFT_REJECT_NETDEV=y
CONFIG_NF_FLOW_TABLE_INET=y
CONFIG_NF_FLOW_TABLE=y
# CONFIG_NF_FLOW_TABLE_PROCFS is not set
CONFIG_NETFILTER_XTABLES=y
CONFIG_NETFILTER_XTABLES_COMPAT=y

#
# Xtables combined modules
#
CONFIG_NETFILTER_XT_MARK=y
CONFIG_NETFILTER_XT_CONNMARK=y
CONFIG_NETFILTER_XT_SET=y

#
# Xtables targets
#
CONFIG_NETFILTER_XT_TARGET_AUDIT=y
CONFIG_NETFILTER_XT_TARGET_CHECKSUM=y
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=y
CONFIG_NETFILTER_XT_TARGET_CONNMARK=y
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=y
# CONFIG_NETFILTER_XT_TARGET_CT is not set
CONFIG_NETFILTER_XT_TARGET_DSCP=y
# CONFIG_NETFILTER_XT_TARGET_HL is not set
CONFIG_NETFILTER_XT_TARGET_HMARK=y
CONFIG_NETFILTER_XT_TARGET_IDLETIMER=y
CONFIG_NETFILTER_XT_TARGET_LED=y
CONFIG_NETFILTER_XT_TARGET_LOG=y
CONFIG_NETFILTER_XT_TARGET_MARK=y
CONFIG_NETFILTER_XT_NAT=y
# CONFIG_NETFILTER_XT_TARGET_NETMAP is not set
CONFIG_NETFILTER_XT_TARGET_NFLOG=y
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y
CONFIG_NETFILTER_XT_TARGET_RATEEST=y
# CONFIG_NETFILTER_XT_TARGET_REDIRECT is not set
CONFIG_NETFILTER_XT_TARGET_MASQUERADE=y
CONFIG_NETFILTER_XT_TARGET_TEE=y
CONFIG_NETFILTER_XT_TARGET_TPROXY=y
CONFIG_NETFILTER_XT_TARGET_SECMARK=y
CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=y

#
# Xtables matches
#
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=y
CONFIG_NETFILTER_XT_MATCH_BPF=y
CONFIG_NETFILTER_XT_MATCH_CGROUP=y
CONFIG_NETFILTER_XT_MATCH_CLUSTER=y
CONFIG_NETFILTER_XT_MATCH_COMMENT=y
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=y
CONFIG_NETFILTER_XT_MATCH_CONNLABEL=y
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=y
CONFIG_NETFILTER_XT_MATCH_CONNMARK=y
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
CONFIG_NETFILTER_XT_MATCH_CPU=y
CONFIG_NETFILTER_XT_MATCH_DCCP=y
CONFIG_NETFILTER_XT_MATCH_DEVGROUP=y
CONFIG_NETFILTER_XT_MATCH_DSCP=y
CONFIG_NETFILTER_XT_MATCH_ECN=y
CONFIG_NETFILTER_XT_MATCH_ESP=y
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=y
CONFIG_NETFILTER_XT_MATCH_HELPER=y
CONFIG_NETFILTER_XT_MATCH_HL=y
CONFIG_NETFILTER_XT_MATCH_IPCOMP=y
CONFIG_NETFILTER_XT_MATCH_IPRANGE=y
CONFIG_NETFILTER_XT_MATCH_IPVS=y
CONFIG_NETFILTER_XT_MATCH_L2TP=y
CONFIG_NETFILTER_XT_MATCH_LENGTH=y
CONFIG_NETFILTER_XT_MATCH_LIMIT=y
CONFIG_NETFILTER_XT_MATCH_MAC=y
CONFIG_NETFILTER_XT_MATCH_MARK=y
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=y
CONFIG_NETFILTER_XT_MATCH_NFACCT=y
CONFIG_NETFILTER_XT_MATCH_OSF=y
CONFIG_NETFILTER_XT_MATCH_OWNER=y
CONFIG_NETFILTER_XT_MATCH_POLICY=y
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=y
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=y
CONFIG_NETFILTER_XT_MATCH_QUOTA=y
CONFIG_NETFILTER_XT_MATCH_RATEEST=y
CONFIG_NETFILTER_XT_MATCH_REALM=y
CONFIG_NETFILTER_XT_MATCH_RECENT=y
CONFIG_NETFILTER_XT_MATCH_SCTP=y
CONFIG_NETFILTER_XT_MATCH_SOCKET=y
CONFIG_NETFILTER_XT_MATCH_STATE=y
CONFIG_NETFILTER_XT_MATCH_STATISTIC=y
CONFIG_NETFILTER_XT_MATCH_STRING=y
CONFIG_NETFILTER_XT_MATCH_TCPMSS=y
CONFIG_NETFILTER_XT_MATCH_TIME=y
CONFIG_NETFILTER_XT_MATCH_U32=y
# end of Core Netfilter Configuration

CONFIG_IP_SET=y
CONFIG_IP_SET_MAX=256
CONFIG_IP_SET_BITMAP_IP=y
CONFIG_IP_SET_BITMAP_IPMAC=y
CONFIG_IP_SET_BITMAP_PORT=y
CONFIG_IP_SET_HASH_IP=y
CONFIG_IP_SET_HASH_IPMARK=y
CONFIG_IP_SET_HASH_IPPORT=y
CONFIG_IP_SET_HASH_IPPORTIP=y
CONFIG_IP_SET_HASH_IPPORTNET=y
CONFIG_IP_SET_HASH_IPMAC=y
CONFIG_IP_SET_HASH_MAC=y
CONFIG_IP_SET_HASH_NETPORTNET=y
CONFIG_IP_SET_HASH_NET=y
CONFIG_IP_SET_HASH_NETNET=y
CONFIG_IP_SET_HASH_NETPORT=y
CONFIG_IP_SET_HASH_NETIFACE=y
CONFIG_IP_SET_LIST_SET=y
CONFIG_IP_VS=y
CONFIG_IP_VS_IPV6=y
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12

#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_AH_ESP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y
CONFIG_IP_VS_PROTO_SCTP=y

#
# IPVS scheduler
#
CONFIG_IP_VS_RR=y
CONFIG_IP_VS_WRR=y
CONFIG_IP_VS_LC=y
CONFIG_IP_VS_WLC=y
CONFIG_IP_VS_FO=y
CONFIG_IP_VS_OVF=y
CONFIG_IP_VS_LBLC=y
CONFIG_IP_VS_LBLCR=y
CONFIG_IP_VS_DH=y
CONFIG_IP_VS_SH=y
CONFIG_IP_VS_MH=y
CONFIG_IP_VS_SED=y
CONFIG_IP_VS_NQ=y
CONFIG_IP_VS_TWOS=y

#
# IPVS SH scheduler
#
CONFIG_IP_VS_SH_TAB_BITS=8

#
# IPVS MH scheduler
#
CONFIG_IP_VS_MH_TAB_INDEX=12

#
# IPVS application helper
#
CONFIG_IP_VS_FTP=y
CONFIG_IP_VS_NFCT=y
CONFIG_IP_VS_PE_SIP=y

#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=y
CONFIG_NF_SOCKET_IPV4=y
CONFIG_NF_TPROXY_IPV4=y
CONFIG_NF_TABLES_IPV4=y
CONFIG_NFT_REJECT_IPV4=y
CONFIG_NFT_DUP_IPV4=y
CONFIG_NFT_FIB_IPV4=y
CONFIG_NF_TABLES_ARP=y
CONFIG_NF_DUP_IPV4=y
CONFIG_NF_LOG_ARP=y
CONFIG_NF_LOG_IPV4=y
CONFIG_NF_REJECT_IPV4=y
CONFIG_NF_NAT_SNMP_BASIC=y
CONFIG_NF_NAT_PPTP=y
CONFIG_NF_NAT_H323=y
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_AH=y
CONFIG_IP_NF_MATCH_ECN=y
CONFIG_IP_NF_MATCH_RPFILTER=y
CONFIG_IP_NF_MATCH_TTL=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_SYNPROXY=y
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_NFT_COMPAT_ARP=y
CONFIG_IP_NF_ARP_MANGLE=y
# end of IP: Netfilter Configuration

#
# IPv6: Netfilter Configuration
#
CONFIG_NF_SOCKET_IPV6=y
CONFIG_NF_TPROXY_IPV6=y
CONFIG_NF_TABLES_IPV6=y
CONFIG_NFT_REJECT_IPV6=y
CONFIG_NFT_DUP_IPV6=y
CONFIG_NFT_FIB_IPV6=y
CONFIG_NF_DUP_IPV6=y
CONFIG_NF_REJECT_IPV6=y
CONFIG_NF_LOG_IPV6=y
CONFIG_IP6_NF_IPTABLES=y
CONFIG_IP6_NF_MATCH_AH=y
CONFIG_IP6_NF_MATCH_EUI64=y
CONFIG_IP6_NF_MATCH_FRAG=y
CONFIG_IP6_NF_MATCH_OPTS=y
CONFIG_IP6_NF_MATCH_HL=y
CONFIG_IP6_NF_MATCH_IPV6HEADER=y
CONFIG_IP6_NF_MATCH_MH=y
CONFIG_IP6_NF_MATCH_RPFILTER=y
CONFIG_IP6_NF_MATCH_RT=y
CONFIG_IP6_NF_MATCH_SRH=y
CONFIG_IP6_NF_TARGET_REJECT=y
CONFIG_IP6_NF_TARGET_SYNPROXY=y
CONFIG_IP6_NF_TARGET_NPT=y
# end of IPv6: Netfilter Configuration

CONFIG_NF_DEFRAG_IPV6=y
CONFIG_NF_TABLES_BRIDGE=y
CONFIG_NFT_BRIDGE_META=y
CONFIG_NFT_BRIDGE_REJECT=y
CONFIG_NF_CONNTRACK_BRIDGE=y
CONFIG_BRIDGE_NF_EBTABLES=y
CONFIG_BRIDGE_EBT_802_3=y
CONFIG_BRIDGE_EBT_AMONG=y
CONFIG_BRIDGE_EBT_ARP=y
CONFIG_BRIDGE_EBT_IP=y
CONFIG_BRIDGE_EBT_IP6=y
CONFIG_BRIDGE_EBT_LIMIT=y
CONFIG_BRIDGE_EBT_MARK=y
CONFIG_BRIDGE_EBT_PKTTYPE=y
CONFIG_BRIDGE_EBT_STP=y
CONFIG_BRIDGE_EBT_VLAN=y
CONFIG_BRIDGE_EBT_ARPREPLY=y
CONFIG_BRIDGE_EBT_DNAT=y
CONFIG_BRIDGE_EBT_MARK_T=y
CONFIG_BRIDGE_EBT_REDIRECT=y
CONFIG_BRIDGE_EBT_SNAT=y
CONFIG_BRIDGE_EBT_LOG=y
CONFIG_BRIDGE_EBT_NFLOG=y
CONFIG_IP_SCTP=y
# CONFIG_SCTP_DBG_OBJCNT is not set
CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA256=y
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not set
CONFIG_INET_SCTP_DIAG=y
CONFIG_RDS=y
CONFIG_RDS_RDMA=y
CONFIG_RDS_TCP=y
# CONFIG_RDS_DEBUG is not set
CONFIG_TIPC=y
CONFIG_TIPC_MEDIA_IB=y
CONFIG_TIPC_MEDIA_UDP=y
CONFIG_TIPC_CRYPTO=y
CONFIG_TIPC_DIAG=y
CONFIG_ATM=y
CONFIG_ATM_BR2684=y
# CONFIG_ATM_BR2684_IPFILTER is not set
CONFIG_L2TP=y
# CONFIG_L2TP_DEBUGFS is not set
CONFIG_L2TP_V3=y
CONFIG_L2TP_IP=y
CONFIG_L2TP_ETH=y
CONFIG_STP=y
CONFIG_GARP=y
CONFIG_MRP=y
CONFIG_BRIDGE=y
CONFIG_BRIDGE_IGMP_SNOOPING=y
CONFIG_BRIDGE_VLAN_FILTERING=y
CONFIG_BRIDGE_MRP=y
CONFIG_BRIDGE_CFM=y
CONFIG_NET_DSA=y
# CONFIG_NET_DSA_TAG_NONE is not set
# CONFIG_NET_DSA_TAG_AR9331 is not set
CONFIG_NET_DSA_TAG_BRCM_COMMON=y
CONFIG_NET_DSA_TAG_BRCM=y
# CONFIG_NET_DSA_TAG_BRCM_LEGACY is not set
# CONFIG_NET_DSA_TAG_BRCM_LEGACY_FCS is not set
CONFIG_NET_DSA_TAG_BRCM_PREPEND=y
# CONFIG_NET_DSA_TAG_HELLCREEK is not set
# CONFIG_NET_DSA_TAG_GSWIP is not set
# CONFIG_NET_DSA_TAG_DSA is not set
# CONFIG_NET_DSA_TAG_EDSA is not set
# CONFIG_NET_DSA_TAG_MT7628 is not set
CONFIG_NET_DSA_TAG_MTK=y
# CONFIG_NET_DSA_TAG_MXL_862XX is not set
# CONFIG_NET_DSA_TAG_MXL_GSW1XX is not set
# CONFIG_NET_DSA_TAG_KSZ is not set
# CONFIG_NET_DSA_TAG_NETC is not set
# CONFIG_NET_DSA_TAG_OCELOT is not set
# CONFIG_NET_DSA_TAG_OCELOT_8021Q is not set
CONFIG_NET_DSA_TAG_QCA=y
CONFIG_NET_DSA_TAG_RTL4_A=y
# CONFIG_NET_DSA_TAG_RTL8_4 is not set
# CONFIG_NET_DSA_TAG_RZN1_A5PSW is not set
# CONFIG_NET_DSA_TAG_LAN9303 is not set
# CONFIG_NET_DSA_TAG_SJA1105 is not set
# CONFIG_NET_DSA_TAG_TRAILER is not set
# CONFIG_NET_DSA_TAG_VSC73XX_8021Q is not set
# CONFIG_NET_DSA_TAG_XRS700X is not set
# CONFIG_NET_DSA_TAG_YT921X is not set
CONFIG_VLAN_8021Q=y
CONFIG_VLAN_8021Q_GVRP=y
CONFIG_VLAN_8021Q_MVRP=y
CONFIG_LLC=y
CONFIG_LLC2=y
CONFIG_X25=y
CONFIG_LAPB=y
CONFIG_PHONET=y
CONFIG_6LOWPAN=y
# CONFIG_6LOWPAN_DEBUGFS is not set
CONFIG_6LOWPAN_NHC=y
CONFIG_6LOWPAN_NHC_DEST=y
CONFIG_6LOWPAN_NHC_FRAGMENT=y
CONFIG_6LOWPAN_NHC_HOP=y
CONFIG_6LOWPAN_NHC_IPV6=y
CONFIG_6LOWPAN_NHC_MOBILITY=y
CONFIG_6LOWPAN_NHC_ROUTING=y
CONFIG_6LOWPAN_NHC_UDP=y
CONFIG_6LOWPAN_GHC_EXT_HDR_HOP=y
CONFIG_6LOWPAN_GHC_UDP=y
CONFIG_6LOWPAN_GHC_ICMPV6=y
CONFIG_6LOWPAN_GHC_EXT_HDR_DEST=y
CONFIG_6LOWPAN_GHC_EXT_HDR_FRAG=y
CONFIG_6LOWPAN_GHC_EXT_HDR_ROUTE=y
CONFIG_IEEE802154=y
CONFIG_IEEE802154_NL802154_EXPERIMENTAL=y
CONFIG_IEEE802154_SOCKET=y
CONFIG_IEEE802154_6LOWPAN=y
CONFIG_MAC802154=y
CONFIG_NET_SCHED=y

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_HTB=y
CONFIG_NET_SCH_HFSC=y
CONFIG_NET_SCH_PRIO=y
CONFIG_NET_SCH_MULTIQ=y
CONFIG_NET_SCH_RED=y
CONFIG_NET_SCH_SFB=y
CONFIG_NET_SCH_SFQ=y
CONFIG_NET_SCH_TEQL=y
CONFIG_NET_SCH_TBF=y
CONFIG_NET_SCH_CBS=y
CONFIG_NET_SCH_ETF=y
CONFIG_NET_SCH_MQPRIO_LIB=y
CONFIG_NET_SCH_TAPRIO=y
CONFIG_NET_SCH_GRED=y
CONFIG_NET_SCH_NETEM=y
CONFIG_NET_SCH_DRR=y
CONFIG_NET_SCH_MQPRIO=y
CONFIG_NET_SCH_SKBPRIO=y
CONFIG_NET_SCH_CHOKE=y
CONFIG_NET_SCH_QFQ=y
CONFIG_NET_SCH_CODEL=y
CONFIG_NET_SCH_FQ_CODEL=y
CONFIG_NET_SCH_CAKE=y
CONFIG_NET_SCH_FQ=y
CONFIG_NET_SCH_HHF=y
CONFIG_NET_SCH_PIE=y
CONFIG_NET_SCH_FQ_PIE=y
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_SCH_PLUG=y
CONFIG_NET_SCH_ETS=y
# CONFIG_NET_SCH_DUALPI2 is not set
CONFIG_NET_SCH_DEFAULT=y
# CONFIG_DEFAULT_FQ is not set
CONFIG_DEFAULT_CODEL=y
# CONFIG_DEFAULT_FQ_CODEL is not set
# CONFIG_DEFAULT_FQ_PIE is not set
# CONFIG_DEFAULT_SFQ is not set
# CONFIG_DEFAULT_PFIFO_FAST is not set
CONFIG_DEFAULT_NET_SCH="pfifo_fast"

#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_FLOW=y
CONFIG_NET_CLS_CGROUP=y
CONFIG_NET_CLS_BPF=y
CONFIG_NET_CLS_FLOWER=y
CONFIG_NET_CLS_MATCHALL=y
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=y
CONFIG_NET_EMATCH_NBYTE=y
CONFIG_NET_EMATCH_U32=y
CONFIG_NET_EMATCH_META=y
CONFIG_NET_EMATCH_TEXT=y
CONFIG_NET_EMATCH_CANID=y
CONFIG_NET_EMATCH_IPSET=y
CONFIG_NET_EMATCH_IPT=y
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=y
CONFIG_NET_ACT_GACT=y
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=y
CONFIG_NET_ACT_SAMPLE=y
CONFIG_NET_ACT_NAT=y
CONFIG_NET_ACT_PEDIT=y
CONFIG_NET_ACT_SIMP=y
CONFIG_NET_ACT_SKBEDIT=y
CONFIG_NET_ACT_CSUM=y
CONFIG_NET_ACT_MPLS=y
CONFIG_NET_ACT_VLAN=y
CONFIG_NET_ACT_BPF=y
CONFIG_NET_ACT_CONNMARK=y
CONFIG_NET_ACT_CTINFO=y
CONFIG_NET_ACT_SKBMOD=y
CONFIG_NET_ACT_IFE=y
CONFIG_NET_ACT_TUNNEL_KEY=y
CONFIG_NET_ACT_CT=y
CONFIG_NET_ACT_GATE=y
CONFIG_NET_IFE_SKBMARK=y
CONFIG_NET_IFE_SKBPRIO=y
CONFIG_NET_IFE_SKBTCINDEX=y
CONFIG_NET_TC_SKB_EXT=y
CONFIG_NET_SCH_FIFO=y
CONFIG_DCB=y
CONFIG_DNS_RESOLVER=y
CONFIG_BATMAN_ADV=y
CONFIG_BATMAN_ADV_BATMAN_V=y
CONFIG_BATMAN_ADV_BLA=y
CONFIG_BATMAN_ADV_DAT=y
CONFIG_BATMAN_ADV_MCAST=y
# CONFIG_BATMAN_ADV_DEBUG is not set
# CONFIG_BATMAN_ADV_TRACING is not set
CONFIG_OPENVSWITCH=y
CONFIG_VSOCKETS=y
CONFIG_VSOCKETS_DIAG=y
CONFIG_VSOCKETS_LOOPBACK=y
# CONFIG_VMWARE_VMCI_VSOCKETS is not set
CONFIG_VIRTIO_VSOCKETS=y
CONFIG_VIRTIO_VSOCKETS_COMMON=y
CONFIG_NETLINK_DIAG=y
CONFIG_MPLS=y
CONFIG_NET_MPLS_GSO=y
CONFIG_MPLS_ROUTING=y
CONFIG_MPLS_IPTUNNEL=y
CONFIG_NET_NSH=y
CONFIG_HSR=y
CONFIG_NET_SWITCHDEV=y
CONFIG_NET_L3_MASTER_DEV=y
CONFIG_QRTR=y
CONFIG_QRTR_TUN=y
# CONFIG_QRTR_MHI is not set
CONFIG_NET_NCSI=y
# CONFIG_NCSI_OEM_CMD_GET_MAC is not set
# CONFIG_NCSI_OEM_CMD_KEEP_PHY is not set
# CONFIG_PCPU_DEV_REFCNT is not set
CONFIG_MAX_SKB_FRAGS=17
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_SOCK_RX_QUEUE_MAPPING=y
CONFIG_XPS=y
CONFIG_CGROUP_NET_PRIO=y
CONFIG_CGROUP_NET_CLASSID=y
CONFIG_BQL=y
CONFIG_NET_FLOW_LIMIT=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NET_DROP_MONITOR=y
# end of Network testing
# end of Networking options

CONFIG_CAN=y
CONFIG_CAN_RAW=y
CONFIG_CAN_BCM=y
CONFIG_CAN_GW=y
CONFIG_CAN_J1939=y
CONFIG_CAN_ISOTP=y
CONFIG_BT=y
CONFIG_BT_BREDR=y
CONFIG_BT_RFCOMM=y
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=y
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=y
CONFIG_BT_LE=y
CONFIG_BT_LE_L2CAP_ECRED=y
CONFIG_BT_6LOWPAN=y
CONFIG_BT_LEDS=y
CONFIG_BT_MSFTEXT=y
# CONFIG_BT_AOSPEXT is not set
# CONFIG_BT_DEBUGFS is not set
# CONFIG_BT_SELFTEST is not set

#
# Bluetooth device drivers
#
CONFIG_BT_INTEL=y
CONFIG_BT_BCM=y
CONFIG_BT_RTL=y
CONFIG_BT_QCA=y
CONFIG_BT_MTK=y
CONFIG_BT_HCIBTUSB=y
CONFIG_BT_HCIBTUSB_AUTOSUSPEND=y
CONFIG_BT_HCIBTUSB_POLL_SYNC=y
CONFIG_BT_HCIBTUSB_BCM=y
CONFIG_BT_HCIBTUSB_MTK=y
CONFIG_BT_HCIBTUSB_RTL=y
# CONFIG_BT_HCIBTSDIO is not set
CONFIG_BT_HCIUART=y
CONFIG_BT_HCIUART_SERDEV=y
CONFIG_BT_HCIUART_H4=y
# CONFIG_BT_HCIUART_NOKIA is not set
CONFIG_BT_HCIUART_BCSP=y
# CONFIG_BT_HCIUART_ATH3K is not set
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIUART_3WIRE=y
# CONFIG_BT_HCIUART_INTEL is not set
# CONFIG_BT_HCIUART_BCM is not set
# CONFIG_BT_HCIUART_RTL is not set
CONFIG_BT_HCIUART_QCA=y
CONFIG_BT_HCIUART_AG6XX=y
CONFIG_BT_HCIUART_MRVL=y
# CONFIG_BT_HCIUART_AML is not set
CONFIG_BT_HCIBCM203X=y
# CONFIG_BT_HCIBCM4377 is not set
CONFIG_BT_HCIBPA10X=y
CONFIG_BT_HCIBFUSB=y
CONFIG_BT_HCIVHCI=y
CONFIG_BT_MRVL=y
CONFIG_BT_MRVL_SDIO=y
CONFIG_BT_ATH3K=y
CONFIG_BT_MTKSDIO=y
CONFIG_BT_MTKUART=y
# CONFIG_BT_VIRTIO is not set
# CONFIG_BT_NXPUART is not set
# CONFIG_BT_INTEL_PCIE is not set
# end of Bluetooth device drivers

CONFIG_AF_RXRPC=y
CONFIG_AF_RXRPC_IPV6=y
# CONFIG_AF_RXRPC_INJECT_LOSS is not set
# CONFIG_AF_RXRPC_INJECT_RX_DELAY is not set
# CONFIG_AF_RXRPC_DEBUG is not set
CONFIG_RXKAD=y
# CONFIG_RXGK is not set
# CONFIG_RXPERF is not set
CONFIG_AF_KCM=y
CONFIG_STREAM_PARSER=y
CONFIG_MCTP=y
CONFIG_FIB_RULES=y
CONFIG_WIRELESS=y
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_CFG80211=y
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
# CONFIG_CFG80211_CERTIFICATION_ONUS is not set
CONFIG_CFG80211_REQUIRE_SIGNED_REGDB=y
CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=y
CONFIG_CFG80211_DEFAULT_PS=y
CONFIG_CFG80211_DEBUGFS=y
CONFIG_CFG80211_CRDA_SUPPORT=y
CONFIG_CFG80211_WEXT=y
CONFIG_MAC80211=y
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
CONFIG_MAC80211_MESH=y
CONFIG_MAC80211_LEDS=y
CONFIG_MAC80211_DEBUGFS=y
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
CONFIG_MAC80211_STA_HASH_MAX_SIZE=0
CONFIG_RFKILL=y
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_GPIO is not set
CONFIG_NET_9P=y
CONFIG_NET_9P_FD=y
CONFIG_NET_9P_VIRTIO=y
# CONFIG_NET_9P_USBG is not set
CONFIG_NET_9P_RDMA=y
# CONFIG_NET_9P_DEBUG is not set
CONFIG_CEPH_LIB=y
# CONFIG_CEPH_LIB_PRETTYDEBUG is not set
CONFIG_CEPH_LIB_USE_DNS_RESOLVER=y
CONFIG_NFC=y
CONFIG_NFC_DIGITAL=y
CONFIG_NFC_NCI=y
# CONFIG_NFC_NCI_SPI is not set
CONFIG_NFC_NCI_UART=y
CONFIG_NFC_HCI=y
CONFIG_NFC_SHDLC=y

#
# Near Field Communication (NFC) devices
#
# CONFIG_NFC_TRF7970A is not set
# CONFIG_NFC_MEI_PHY is not set
CONFIG_NFC_SIM=y
CONFIG_NFC_PORT100=y
CONFIG_NFC_VIRTUAL_NCI=y
CONFIG_NFC_FDP=y
# CONFIG_NFC_FDP_I2C is not set
# CONFIG_NFC_PN544_I2C is not set
CONFIG_NFC_PN533=y
CONFIG_NFC_PN533_USB=y
# CONFIG_NFC_PN533_I2C is not set
# CONFIG_NFC_PN532_UART is not set
# CONFIG_NFC_MICROREAD_I2C is not set
CONFIG_NFC_MRVL=y
CONFIG_NFC_MRVL_USB=y
# CONFIG_NFC_MRVL_UART is not set
# CONFIG_NFC_MRVL_I2C is not set
# CONFIG_NFC_ST21NFCA_I2C is not set
# CONFIG_NFC_ST_NCI_I2C is not set
# CONFIG_NFC_ST_NCI_SPI is not set
# CONFIG_NFC_NXP_NCI is not set
# CONFIG_NFC_S3FWRN5_I2C is not set
# CONFIG_NFC_S3FWRN82_UART is not set
# CONFIG_NFC_ST95HF is not set
# end of Near Field Communication (NFC) devices

CONFIG_PSAMPLE=y
CONFIG_NET_IFE=y
CONFIG_LWTUNNEL=y
CONFIG_LWTUNNEL_BPF=y
CONFIG_DST_CACHE=y
CONFIG_GRO_CELLS=y
CONFIG_SOCK_VALIDATE_XMIT=y
CONFIG_NET_SELFTESTS=y
CONFIG_NET_SOCK_MSG=y
CONFIG_NET_DEVLINK=y
CONFIG_PAGE_POOL=y
# CONFIG_PAGE_POOL_STATS is not set
CONFIG_FAILOVER=y
CONFIG_ETHTOOL_NETLINK=y

#
# Device Drivers
#
CONFIG_HAVE_PCI=y
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCIEPORTBUS=y
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_PCIEAER=y
# CONFIG_PCIEAER_INJECT is not set
# CONFIG_PCIE_ECRC is not set
CONFIG_PCIEASPM=y
CONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not set
CONFIG_PCIE_PME=y
# CONFIG_PCIE_DPC is not set
# CONFIG_PCIE_PTM is not set
CONFIG_PCI_MSI=y
CONFIG_PCI_QUIRKS=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_REALLOC_ENABLE_AUTO is not set
# CONFIG_PCI_STUB is not set
# CONFIG_PCI_PF_STUB is not set
CONFIG_PCI_ATS=y
# CONFIG_PCI_TSM is not set
# CONFIG_PCI_DOE is not set
CONFIG_PCI_ECAM=y
CONFIG_PCI_LOCKLESS_CONFIG=y
CONFIG_PCI_IOV=y
# CONFIG_PCI_NPEM is not set
CONFIG_PCI_PRI=y
CONFIG_PCI_PASID=y
# CONFIG_PCIE_TPH is not set
# CONFIG_PCI_P2PDMA is not set
CONFIG_PCI_LABEL=y
# CONFIG_PCI_DYNAMIC_OF_NODES is not set
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
CONFIG_HOTPLUG_PCI=y
# CONFIG_HOTPLUG_PCI_ACPI is not set
# CONFIG_HOTPLUG_PCI_CPCI is not set
# CONFIG_HOTPLUG_PCI_OCTEONEP is not set
# CONFIG_HOTPLUG_PCI_SHPC is not set

#
# PCI controller drivers
#
CONFIG_PCI_HOST_COMMON=y
# CONFIG_PCI_FTPCI100 is not set
CONFIG_PCI_HOST_GENERIC=y
# CONFIG_VMD is not set
# CONFIG_PCIE_XILINX is not set

#
# Cadence-based PCIe controllers
#
# CONFIG_PCIE_CADENCE_PLAT_HOST is not set
# CONFIG_PCIE_CADENCE_PLAT_EP is not set
# end of Cadence-based PCIe controllers

#
# DesignWare-based PCIe controllers
#
# CONFIG_PCI_MESON is not set
# CONFIG_PCIE_INTEL_GW is not set
# CONFIG_PCIE_DW_PLAT_HOST is not set
# CONFIG_PCIE_DW_PLAT_EP is not set
# end of DesignWare-based PCIe controllers

#
# Mobiveil-based PCIe controllers
#
# end of Mobiveil-based PCIe controllers

#
# PLDA-based PCIe controllers
#
# CONFIG_PCIE_MICROCHIP_HOST is not set
# end of PLDA-based PCIe controllers
# end of PCI controller drivers

#
# PCI Endpoint
#
CONFIG_PCI_ENDPOINT=y
# CONFIG_PCI_ENDPOINT_CONFIGFS is not set
# CONFIG_PCI_ENDPOINT_MSI_DOORBELL is not set
# CONFIG_PCI_EPF_TEST is not set
# CONFIG_PCI_EPF_NTB is not set
# end of PCI Endpoint

#
# PCI switch controller drivers
#
# CONFIG_PCI_SW_SWITCHTEC is not set
# end of PCI switch controller drivers

# CONFIG_PCI_PWRCTRL_GENERIC is not set
# CONFIG_PCI_PWRCTRL_TC9563 is not set
# CONFIG_CXL_BUS is not set
CONFIG_PCCARD=y
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=y
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
# CONFIG_PD6729 is not set
CONFIG_PCCARD_NONSTATIC=y
# CONFIG_RAPIDIO is not set
# CONFIG_PC104 is not set

#
# Generic Driver Options
#
CONFIG_AUXILIARY_BUS=y
CONFIG_UEVENT_HELPER=y
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
# CONFIG_DEVTMPFS_SAFE is not set
CONFIG_DRIVER_DEFERRED_PROBE_TIMEOUT=10
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y

#
# Firmware loader
#
CONFIG_FW_LOADER=y
# CONFIG_FW_LOADER_DEBUG is not set
CONFIG_FW_LOADER_PAGED_BUF=y
CONFIG_FW_LOADER_SYSFS=y
CONFIG_EXTRA_FIRMWARE=""
CONFIG_FW_LOADER_USER_HELPER=y
CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y
CONFIG_FW_LOADER_COMPRESS=y
# CONFIG_FW_LOADER_COMPRESS_XZ is not set
# CONFIG_FW_LOADER_COMPRESS_ZSTD is not set
CONFIG_FW_CACHE=y
# CONFIG_FW_UPLOAD is not set
# end of Firmware loader

CONFIG_WANT_DEV_COREDUMP=y
CONFIG_ALLOW_DEV_COREDUMP=y
CONFIG_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
CONFIG_DEBUG_DEVRES=y
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
# CONFIG_TEST_ASYNC_DRIVER_PROBE is not set
CONFIG_GENERIC_CPU_DEVICES=y
CONFIG_GENERIC_CPU_AUTOPROBE=y
CONFIG_GENERIC_CPU_VULNERABILITIES=y
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=y
CONFIG_REGMAP_SPI=y
CONFIG_REGMAP_MMIO=y
CONFIG_REGMAP_IRQ=y
CONFIG_DMA_SHARED_BUFFER=y
# CONFIG_FW_DEVLINK_SYNC_STATE_TIMEOUT is not set
# end of Generic Driver Options

#
# Bus devices
#
# CONFIG_MOXTET is not set
CONFIG_MHI_BUS=y
# CONFIG_MHI_BUS_DEBUG is not set
# CONFIG_MHI_BUS_PCI_GENERIC is not set
# CONFIG_MHI_BUS_EP is not set
# end of Bus devices

CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y

#
# Firmware Drivers
#

#
# ARM System Control and Management Interface Protocol
#
# end of ARM System Control and Management Interface Protocol

# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
CONFIG_DMIID=y
# CONFIG_DMI_SYSFS is not set
CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y
# CONFIG_ISCSI_IBFT is not set
# CONFIG_FW_CFG_SYSFS is not set
CONFIG_SYSFB=y
# CONFIG_SYSFB_SIMPLEFB is not set
CONFIG_GOOGLE_FIRMWARE=y
# CONFIG_GOOGLE_SMI is not set
# CONFIG_GOOGLE_CBMEM is not set
CONFIG_GOOGLE_COREBOOT_TABLE=y
CONFIG_GOOGLE_MEMCONSOLE=y
# CONFIG_GOOGLE_MEMCONSOLE_X86_LEGACY is not set
# CONFIG_GOOGLE_FRAMEBUFFER_COREBOOT is not set
CONFIG_GOOGLE_MEMCONSOLE_COREBOOT=y
CONFIG_GOOGLE_VPD=y

#
# Qualcomm firmware drivers
#
# CONFIG_QCOM_PAS is not set
# CONFIG_QCOM_PAS_TEE is not set
# CONFIG_QCOM_SCM is not set
# end of Qualcomm firmware drivers

#
# Tegra firmware driver
#
# end of Tegra firmware driver
# end of Firmware Drivers

# CONFIG_FWCTL is not set
CONFIG_GNSS=y
# CONFIG_GNSS_MTK_SERIAL is not set
# CONFIG_GNSS_SIRF_SERIAL is not set
# CONFIG_GNSS_UBX_SERIAL is not set
CONFIG_GNSS_USB=y
CONFIG_MTD=y
# CONFIG_MTD_TESTS is not set

#
# Partition parsers
#
# CONFIG_MTD_CMDLINE_PARTS is not set
# CONFIG_MTD_OF_PARTS is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
# end of Partition parsers

#
# User Modules And Translation Layers
#
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y

#
# Note that in some cases UBI block is preferred. See MTD_UBI_BLOCK.
#
CONFIG_FTL=y
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_SM_FTL is not set
# CONFIG_MTD_OOPS is not set
# CONFIG_MTD_SWAP is not set
# CONFIG_MTD_PARTITIONED_MASTER is not set

#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# end of RAM/ROM/Flash chip drivers

#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PLATRAM is not set
# end of Mapping drivers for chip access

#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_DATAFLASH is not set
# CONFIG_MTD_MCHP23K256 is not set
# CONFIG_MTD_MCHP48L640 is not set
# CONFIG_MTD_SST25L is not set
CONFIG_MTD_SLRAM=y
CONFIG_MTD_PHRAM=y
CONFIG_MTD_MTDRAM=y
CONFIG_MTDRAM_TOTAL_SIZE=128
CONFIG_MTDRAM_ERASE_SIZE=4
CONFIG_MTD_BLOCK2MTD=y

#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOCG3 is not set
# end of Self-contained MTD device drivers

#
# NAND
#
# CONFIG_MTD_ONENAND is not set
# CONFIG_MTD_RAW_NAND is not set
# CONFIG_MTD_SPI_NAND is not set

#
# ECC engine support
#
# CONFIG_MTD_NAND_ECC_SW_HAMMING is not set
# CONFIG_MTD_NAND_ECC_SW_BCH is not set
# CONFIG_MTD_NAND_ECC_MXIC is not set
# end of ECC engine support
# end of NAND

#
# LPDDR & LPDDR2 PCM memory drivers
#
# CONFIG_MTD_LPDDR is not set
# end of LPDDR & LPDDR2 PCM memory drivers

# CONFIG_MTD_SPI_NOR is not set
CONFIG_MTD_UBI=y
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_LIMIT=20
# CONFIG_MTD_UBI_FASTMAP is not set
# CONFIG_MTD_UBI_GLUEBI is not set
# CONFIG_MTD_UBI_BLOCK is not set
# CONFIG_MTD_UBI_FAULT_INJECTION is not set
# CONFIG_MTD_UBI_NVMEM is not set
# CONFIG_MTD_HYPERBUS is not set
CONFIG_DTC=y
CONFIG_OF=y
# CONFIG_OF_UNITTEST is not set
CONFIG_OF_FLATTREE=y
CONFIG_OF_EARLY_FLATTREE=y
CONFIG_OF_KOBJ=y
CONFIG_OF_ADDRESS=y
CONFIG_OF_IRQ=y
CONFIG_OF_RESERVED_MEM=y
# CONFIG_OF_OVERLAY is not set
CONFIG_OF_NUMA=y
CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
CONFIG_PARPORT=y
# CONFIG_PARPORT_PC is not set
# CONFIG_PARPORT_1284 is not set
CONFIG_PARPORT_NOT_PC=y
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y

#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_NULL_BLK=y
CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION=y
# CONFIG_BLK_DEV_FD is not set
CONFIG_CDROM=y
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
CONFIG_ZRAM=y
# CONFIG_ZRAM_BACKEND_LZ4 is not set
# CONFIG_ZRAM_BACKEND_LZ4HC is not set
# CONFIG_ZRAM_BACKEND_ZSTD is not set
# CONFIG_ZRAM_BACKEND_DEFLATE is not set
# CONFIG_ZRAM_BACKEND_842 is not set
CONFIG_ZRAM_BACKEND_FORCE_LZO=y
CONFIG_ZRAM_BACKEND_LZO=y
# CONFIG_ZRAM_DEF_COMP_LZORLE is not set
CONFIG_ZRAM_DEF_COMP_LZO=y
CONFIG_ZRAM_DEF_COMP="lzo"
# CONFIG_ZRAM_WRITEBACK is not set
# CONFIG_ZRAM_TRACK_ENTRY_ACTIME is not set
# CONFIG_ZRAM_MEMORY_TRACKING is not set
# CONFIG_ZRAM_MULTI_COMP is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=16
# CONFIG_BLK_DEV_DRBD is not set
CONFIG_BLK_DEV_NBD=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_ATA_OVER_ETH=y
CONFIG_VIRTIO_BLK=y
# CONFIG_BLK_DEV_RBD is not set
CONFIG_BLK_DEV_UBLK=y
CONFIG_BLKDEV_UBLK_LEGACY_OPCODES=y
CONFIG_BLK_DEV_RNBD=y
CONFIG_BLK_DEV_RNBD_CLIENT=y
# CONFIG_BLK_DEV_ZONED_LOOP is not set

#
# NVME Support
#
CONFIG_NVME_CORE=y
CONFIG_BLK_DEV_NVME=y
CONFIG_NVME_MULTIPATH=y
# CONFIG_NVME_VERBOSE_ERRORS is not set
# CONFIG_NVME_HWMON is not set
CONFIG_NVME_FABRICS=y
CONFIG_NVME_RDMA=y
CONFIG_NVME_FC=y
CONFIG_NVME_TCP=y
# CONFIG_NVME_TCP_TLS is not set
# CONFIG_NVME_HOST_AUTH is not set
CONFIG_NVME_TARGET=y
# CONFIG_NVME_TARGET_DEBUGFS is not set
# CONFIG_NVME_TARGET_PASSTHRU is not set
CONFIG_NVME_TARGET_LOOP=y
CONFIG_NVME_TARGET_RDMA=y
CONFIG_NVME_TARGET_FC=y
CONFIG_NVME_TARGET_FCLOOP=y
CONFIG_NVME_TARGET_TCP=y
# CONFIG_NVME_TARGET_TCP_TLS is not set
# CONFIG_NVME_TARGET_AUTH is not set
# CONFIG_NVME_TARGET_PCI_EPF is not set
# end of NVME Support

#
# Misc devices
#
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_PHANTOM is not set
# CONFIG_RPMB is not set
# CONFIG_TI_FPC202 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not set
# CONFIG_APDS9802ALS is not set
# CONFIG_ISL29003 is not set
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1770 is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_VMWARE_BALLOON is not set
# CONFIG_LATTICE_ECP3_CONFIG is not set
# CONFIG_SRAM is not set
# CONFIG_DW_XDATA_PCIE is not set
# CONFIG_PCI_ENDPOINT_TEST is not set
# CONFIG_XILINX_SDFEC is not set
CONFIG_MISC_RTSX=y
# CONFIG_OPEN_DICE is not set
# CONFIG_NTSYNC is not set
# CONFIG_VCPU_STALL_DETECTOR is not set
# CONFIG_NSM is not set
# CONFIG_C2PORT is not set

#
# EEPROM support
#
# CONFIG_EEPROM_MAX6875 is not set
CONFIG_EEPROM_93CX6=y
# CONFIG_EEPROM_IDT_89HPESX is not set
# end of EEPROM support

# CONFIG_CB710_CORE is not set
# CONFIG_SENSORS_LIS3_I2C is not set
# CONFIG_ALTERA_STAPL is not set
CONFIG_INTEL_MEI=y
CONFIG_INTEL_MEI_ME=y
# CONFIG_INTEL_MEI_TXE is not set
# CONFIG_INTEL_MEI_CSC is not set
# CONFIG_INTEL_MEI_VSC_HW is not set
CONFIG_VMWARE_VMCI=y
# CONFIG_GENWQE is not set
# CONFIG_BCM_VK is not set
# CONFIG_MISC_ALCOR_PCI is not set
# CONFIG_MISC_RTSX_PCI is not set
CONFIG_MISC_RTSX_USB=y
# CONFIG_UACCE is not set
# CONFIG_PVPANIC is not set
# CONFIG_GP_PCI1XXXX is not set
# CONFIG_KEBA_CP500 is not set
# CONFIG_MISC_RP1 is not set
# CONFIG_INTEL_SSEI is not set
# end of Misc devices

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
CONFIG_RAID_ATTRS=y
CONFIG_SCSI_COMMON=y
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
CONFIG_BLK_DEV_SR=y
CONFIG_CHR_DEV_SG=y
CONFIG_BLK_DEV_BSG=y
# CONFIG_CHR_DEV_SCH is not set
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=y
CONFIG_SCSI_ISCSI_ATTRS=y
CONFIG_SCSI_SAS_ATTRS=y
CONFIG_SCSI_SAS_LIBSAS=y
CONFIG_SCSI_SAS_ATA=y
# CONFIG_SCSI_SAS_HOST_SMP is not set
CONFIG_SCSI_SRP_ATTRS=y
# end of SCSI Transports

CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_CXGB4_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
CONFIG_SCSI_HPSA=y
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_MVUMI is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_MPT3SAS is not set
# CONFIG_SCSI_MPT2SAS is not set
# CONFIG_SCSI_MPI3MR is not set
# CONFIG_SCSI_LEAPRAID is not set
# CONFIG_SCSI_SMARTPQI is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_MYRB is not set
# CONFIG_SCSI_MYRS is not set
# CONFIG_VMWARE_PVSCSI is not set
# CONFIG_LIBFC is not set
# CONFIG_SCSI_SNIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_FDOMAIN_PCI is not set
# CONFIG_SCSI_ISCI is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_EFCT is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_WD719X is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
# CONFIG_SCSI_BFA_FC is not set
CONFIG_SCSI_VIRTIO=y
# CONFIG_SCSI_CHELSIO_FCOE is not set
# CONFIG_SCSI_LOWLEVEL_PCMCIA is not set
# CONFIG_SCSI_DH is not set
# end of SCSI device support

CONFIG_ATA=y
CONFIG_SATA_HOST=y
CONFIG_PATA_TIMINGS=y
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_FORCE=y
CONFIG_ATA_ACPI=y
# CONFIG_SATA_ZPODD is not set
CONFIG_SATA_PMP=y

#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=y
CONFIG_SATA_MOBILE_LPM_POLICY=3
# CONFIG_SATA_AHCI_PLATFORM is not set
# CONFIG_AHCI_DWC is not set
# CONFIG_AHCI_CEVA is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y

#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not set
CONFIG_ATA_BMDMA=y

#
# SATA SFF controllers with BMDMA
#
CONFIG_ATA_PIIX=y
# CONFIG_SATA_DWC is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set

#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
CONFIG_PATA_AMD=y
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
CONFIG_PATA_OLDPIIX=y
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
CONFIG_PATA_SCH=y
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set

#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_PCMCIA is not set
# CONFIG_PATA_OF_PLATFORM is not set
# CONFIG_PATA_RZ1000 is not set

#
# Generic fallback / legacy drivers
#
# CONFIG_PATA_ACPI is not set
CONFIG_ATA_GENERIC=y
# CONFIG_PATA_LEGACY is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_BITMAP=y
# CONFIG_MD_LLBITMAP is not set
CONFIG_MD_AUTODETECT=y
CONFIG_MD_BITMAP_FILE=y
# CONFIG_MD_LINEAR is not set
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID10=y
CONFIG_MD_RAID456=y
# CONFIG_MD_CLUSTER is not set
CONFIG_BCACHE=y
# CONFIG_BCACHE_DEBUG is not set
# CONFIG_BCACHE_ASYNC_REGISTRATION is not set
CONFIG_BLK_DEV_DM_BUILTIN=y
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
CONFIG_DM_BUFIO=y
# CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING is not set
CONFIG_DM_BIO_PRISON=y
CONFIG_DM_PERSISTENT_DATA=y
# CONFIG_DM_UNSTRIPED is not set
CONFIG_DM_CRYPT=y
# CONFIG_DM_INLINECRYPT is not set
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_THIN_PROVISIONING=y
CONFIG_DM_CACHE=y
CONFIG_DM_CACHE_SMQ=y
CONFIG_DM_WRITECACHE=y
# CONFIG_DM_EBS is not set
# CONFIG_DM_ERA is not set
CONFIG_DM_CLONE=y
CONFIG_DM_MIRROR=y
# CONFIG_DM_LOG_USERSPACE is not set
CONFIG_DM_RAID=y
CONFIG_DM_ZERO=y
CONFIG_DM_MULTIPATH=y
CONFIG_DM_MULTIPATH_QL=y
CONFIG_DM_MULTIPATH_ST=y
# CONFIG_DM_MULTIPATH_HST is not set
# CONFIG_DM_MULTIPATH_IOA is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_DUST is not set
# CONFIG_DM_INIT is not set
CONFIG_DM_UEVENT=y
CONFIG_DM_FLAKEY=y
CONFIG_DM_VERITY=y
# CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG is not set
CONFIG_DM_VERITY_FEC=y
# CONFIG_DM_SWITCH is not set
# CONFIG_DM_LOG_WRITES is not set
CONFIG_DM_INTEGRITY=y
CONFIG_DM_ZONED=y
CONFIG_DM_AUDIT=y
# CONFIG_DM_VDO is not set
CONFIG_TARGET_CORE=y
# CONFIG_TCM_IBLOCK is not set
# CONFIG_TCM_FILEIO is not set
# CONFIG_TCM_PSCSI is not set
# CONFIG_LOOPBACK_TARGET is not set
# CONFIG_ISCSI_TARGET is not set
# CONFIG_SBP_TARGET is not set
# CONFIG_REMOTE_TARGET is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
CONFIG_FIREWIRE=y
CONFIG_FIREWIRE_OHCI=y
CONFIG_FIREWIRE_SBP2=y
CONFIG_FIREWIRE_NET=y
# CONFIG_FIREWIRE_NOSY is not set
# end of IEEE 1394 (FireWire) support

# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
CONFIG_MII=y
CONFIG_NET_CORE=y
CONFIG_BONDING=y
CONFIG_DUMMY=y
CONFIG_WIREGUARD=y
# CONFIG_WIREGUARD_DEBUG is not set
# CONFIG_OVPN is not set
CONFIG_EQUALIZER=y
CONFIG_NET_FC=y
CONFIG_IFB=y
CONFIG_NET_TEAM=y
CONFIG_NET_TEAM_MODE_BROADCAST=y
CONFIG_NET_TEAM_MODE_ROUNDROBIN=y
CONFIG_NET_TEAM_MODE_RANDOM=y
CONFIG_NET_TEAM_MODE_ACTIVEBACKUP=y
CONFIG_NET_TEAM_MODE_LOADBALANCE=y
CONFIG_MACVLAN=y
CONFIG_MACVTAP=y
CONFIG_IPVLAN_L3S=y
CONFIG_IPVLAN=y
CONFIG_IPVTAP=y
CONFIG_VXLAN=y
CONFIG_GENEVE=y
CONFIG_BAREUDP=y
CONFIG_GTP=y
# CONFIG_PFCP is not set
# CONFIG_AMT is not set
CONFIG_MACSEC=y
CONFIG_NETCONSOLE=y
# CONFIG_NETCONSOLE_DYNAMIC is not set
# CONFIG_NETCONSOLE_EXTENDED_LOG is not set
CONFIG_NETPOLL=y
CONFIG_NET_POLL_CONTROLLER=y
CONFIG_TUN=y
CONFIG_TAP=y
CONFIG_TUN_VNET_CROSS_LE=y
CONFIG_VETH=y
CONFIG_VIRTIO_NET=y
CONFIG_NLMON=y
# CONFIG_NETKIT is not set
CONFIG_NET_VRF=y
CONFIG_VSOCKMON=y
# CONFIG_MHI_NET is not set
# CONFIG_ARCNET is not set
CONFIG_ATM_DRIVERS=y
# CONFIG_ATM_SOLOS is not set

#
# Distributed Switch Architecture drivers
#
# CONFIG_B53 is not set
# CONFIG_NET_DSA_BCM_SF2 is not set
# CONFIG_NET_DSA_LOOP is not set
# CONFIG_NET_DSA_HIRSCHMANN_HELLCREEK is not set
# CONFIG_NET_DSA_LANTIQ_GSWIP is not set
# CONFIG_NET_DSA_MXL_GSW1XX is not set
# CONFIG_NET_DSA_MT7530 is not set
# CONFIG_NET_DSA_MV88E6060 is not set
# CONFIG_NET_DSA_MICROCHIP_KSZ_COMMON is not set
# CONFIG_NET_DSA_MV88E6XXX is not set
# CONFIG_NET_DSA_MXL862 is not set
# CONFIG_NET_DSA_AR9331 is not set
# CONFIG_NET_DSA_QCA8K is not set
# CONFIG_NET_DSA_SJA1105 is not set
# CONFIG_NET_DSA_XRS700X_I2C is not set
# CONFIG_NET_DSA_XRS700X_MDIO is not set
# CONFIG_NET_DSA_REALTEK is not set
# CONFIG_NET_DSA_KS8995 is not set
# CONFIG_NET_DSA_SMSC_LAN9303_I2C is not set
# CONFIG_NET_DSA_SMSC_LAN9303_MDIO is not set
# CONFIG_NET_DSA_VITESSE_VSC73XX_SPI is not set
# CONFIG_NET_DSA_VITESSE_VSC73XX_PLATFORM is not set
# CONFIG_NET_DSA_YT921X is not set
# end of Distributed Switch Architecture drivers

CONFIG_ETHERNET=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_ADAPTEC is not set
# CONFIG_NET_VENDOR_AGERE is not set
# CONFIG_NET_VENDOR_ALACRITECH is not set
CONFIG_NET_VENDOR_ALIBABA=y
# CONFIG_ALIBABA_EEA is not set
# CONFIG_ALTERA_TSE is not set
CONFIG_NET_VENDOR_AMAZON=y
# CONFIG_ENA_ETHERNET is not set
# CONFIG_NET_VENDOR_AMD is not set
# CONFIG_NET_VENDOR_AQUANTIA is not set
# CONFIG_NET_VENDOR_ARC is not set
CONFIG_NET_VENDOR_ASIX=y
# CONFIG_SPI_AX88796C is not set
# CONFIG_NET_VENDOR_ATHEROS is not set
# CONFIG_CX_ECAT is not set
# CONFIG_NET_VENDOR_BROADCOM is not set
# CONFIG_NET_VENDOR_CADENCE is not set
# CONFIG_NET_VENDOR_CAVIUM is not set
# CONFIG_NET_VENDOR_CHELSIO is not set
CONFIG_NET_VENDOR_CISCO=y
# CONFIG_ENIC is not set
# CONFIG_NET_VENDOR_CORTINA is not set
CONFIG_NET_VENDOR_DAVICOM=y
# CONFIG_DM9051 is not set
# CONFIG_NET_VENDOR_DEC is not set
# CONFIG_NET_VENDOR_DLINK is not set
# CONFIG_NET_VENDOR_EMULEX is not set
CONFIG_NET_VENDOR_ENGLEDER=y
# CONFIG_TSNEP is not set
# CONFIG_NET_VENDOR_EZCHIP is not set
CONFIG_NET_VENDOR_FUNGIBLE=y
# CONFIG_FUN_ETH is not set
CONFIG_NET_VENDOR_GOOGLE=y
CONFIG_GVE=y
CONFIG_NET_VENDOR_HISILICON=y
# CONFIG_HIBMCGE is not set
# CONFIG_NET_VENDOR_HUAWEI is not set
CONFIG_NET_VENDOR_I825XX=y
CONFIG_NET_VENDOR_INTEL=y
CONFIG_E100=y
CONFIG_E1000=y
CONFIG_E1000E=y
CONFIG_E1000E_HWTS=y
# CONFIG_IGB is not set
# CONFIG_IGBVF is not set
# CONFIG_IXGBE is not set
# CONFIG_IXGBEVF is not set
# CONFIG_I40E is not set
# CONFIG_I40EVF is not set
# CONFIG_ICE is not set
# CONFIG_FM10K is not set
# CONFIG_IGC is not set
# CONFIG_IDPF is not set
# CONFIG_IXD is not set
# CONFIG_JME is not set
# CONFIG_NET_VENDOR_ADI is not set
CONFIG_NET_VENDOR_LITEX=y
# CONFIG_LITEX_LITEETH is not set
# CONFIG_NET_VENDOR_MARVELL is not set
CONFIG_NET_VENDOR_MELLANOX=y
# CONFIG_MLX4_EN is not set
CONFIG_MLX4_CORE=y
# CONFIG_MLX4_DEBUG is not set
# CONFIG_MLX4_CORE_GEN2 is not set
# CONFIG_MLX5_CORE is not set
# CONFIG_MLXSW_CORE is not set
# CONFIG_MLXFW is not set
CONFIG_NET_VENDOR_META=y
# CONFIG_FBNIC is not set
# CONFIG_NET_VENDOR_MICREL is not set
# CONFIG_NET_VENDOR_MICROCHIP is not set
# CONFIG_NET_VENDOR_MICROSEMI is not set
CONFIG_NET_VENDOR_MICROSOFT=y
CONFIG_NET_VENDOR_MUCSE=y
# CONFIG_MGBE is not set
# CONFIG_NET_VENDOR_MYRI is not set
# CONFIG_FEALNX is not set
# CONFIG_NET_VENDOR_NI is not set
# CONFIG_NET_VENDOR_NATSEMI is not set
# CONFIG_NET_VENDOR_NETRONOME is not set
# CONFIG_NET_VENDOR_NVIDIA is not set
# CONFIG_NET_VENDOR_OKI is not set
# CONFIG_ETHOC is not set
# CONFIG_NET_VENDOR_PENSANDO is not set
# CONFIG_NET_VENDOR_QLOGIC is not set
# CONFIG_NET_VENDOR_BROCADE is not set
# CONFIG_NET_VENDOR_QUALCOMM is not set
# CONFIG_NET_VENDOR_RDC is not set
# CONFIG_NET_VENDOR_REALTEK is not set
# CONFIG_NET_VENDOR_RENESAS is not set
# CONFIG_NET_VENDOR_ROCKER is not set
# CONFIG_NET_VENDOR_SAMSUNG is not set
# CONFIG_NET_VENDOR_SEEQ is not set
# CONFIG_NET_VENDOR_SILAN is not set
# CONFIG_NET_VENDOR_SIS is not set
# CONFIG_NET_VENDOR_SOLARFLARE is not set
# CONFIG_NET_VENDOR_SMSC is not set
# CONFIG_NET_VENDOR_SOCIONEXT is not set
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_NET_VENDOR_SUN is not set
# CONFIG_NET_VENDOR_SYNOPSYS is not set
# CONFIG_NET_VENDOR_TEHUTI is not set
# CONFIG_NET_VENDOR_TI is not set
CONFIG_NET_VENDOR_VERTEXCOM=y
# CONFIG_MSE102X is not set
# CONFIG_NET_VENDOR_VIA is not set
CONFIG_NET_VENDOR_WANGXUN=y
# CONFIG_NGBE is not set
# CONFIG_TXGBE is not set
# CONFIG_TXGBEVF is not set
# CONFIG_NGBEVF is not set
# CONFIG_NET_VENDOR_WIZNET is not set
# CONFIG_NET_VENDOR_XILINX is not set
# CONFIG_NET_VENDOR_XIRCOM is not set
CONFIG_NET_VENDOR_ZTE=y
# CONFIG_DINGHAI is not set
CONFIG_FDDI=y
# CONFIG_DEFXX is not set
# CONFIG_SKFP is not set
CONFIG_PHYLINK=y
CONFIG_PHYLIB=y
CONFIG_SWPHY=y
CONFIG_PHY_PACKAGE=y
# CONFIG_LED_TRIGGER_PHY is not set
CONFIG_PHYLIB_LEDS=y
CONFIG_FIXED_PHY=y
# CONFIG_SFP is not set

#
# MII PHY device drivers
#
# CONFIG_AS21XXX_PHY is not set
# CONFIG_AIR_AN8801_PHY is not set
# CONFIG_AIR_EN8811H_PHY is not set
# CONFIG_AMD_PHY is not set
# CONFIG_ADIN_PHY is not set
# CONFIG_ADIN1100_PHY is not set
# CONFIG_ADIN1140_PHY is not set
# CONFIG_AQUANTIA_PHY is not set
CONFIG_AX88796B_PHY=y
# CONFIG_BROADCOM_PHY is not set
# CONFIG_BCM54140_PHY is not set
# CONFIG_BCM7XXX_PHY is not set
# CONFIG_BCM84881_PHY is not set
# CONFIG_BCM87XX_PHY is not set
# CONFIG_CICADA_PHY is not set
# CONFIG_CORTINA_PHY is not set
# CONFIG_DAP8211R_PHY is not set
# CONFIG_DAVICOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
# CONFIG_LXT_PHY is not set
# CONFIG_INTEL_XWAY_PHY is not set
# CONFIG_LSI_ET1011C_PHY is not set
# CONFIG_MARVELL_PHY is not set
# CONFIG_MARVELL_10G_PHY is not set
# CONFIG_MARVELL_88Q2XXX_PHY is not set
# CONFIG_MARVELL_88X2222_PHY is not set
# CONFIG_MAXLINEAR_GPHY is not set
# CONFIG_MAXLINEAR_86110_PHY is not set
# CONFIG_MEDIATEK_GE_PHY is not set
# CONFIG_MICREL_PHY is not set
# CONFIG_MICROCHIP_T1S_PHY is not set
CONFIG_MICROCHIP_PHY=y
# CONFIG_MICROCHIP_T1_PHY is not set
# CONFIG_MICROSEMI_PHY is not set
# CONFIG_MOTORCOMM_PHY is not set
# CONFIG_NATIONAL_PHY is not set
# CONFIG_NXP_CBTX_PHY is not set
# CONFIG_NXP_C45_TJA11XX_PHY is not set
# CONFIG_NXP_TJA11XX_PHY is not set
# CONFIG_NCN26000_PHY is not set
# CONFIG_AT803X_PHY is not set
# CONFIG_QCA83XX_PHY is not set
# CONFIG_QCA808X_PHY is not set
# CONFIG_QCA807X_PHY is not set
# CONFIG_QSEMI_PHY is not set
CONFIG_REALTEK_PHY=y
# CONFIG_REALTEK_PHY_HWMON is not set
# CONFIG_RENESAS_PHY is not set
# CONFIG_ROCKCHIP_PHY is not set
CONFIG_SMSC_PHY=y
# CONFIG_STE10XP is not set
# CONFIG_TERANETICS_PHY is not set
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
# CONFIG_DP83848_PHY is not set
# CONFIG_DP83867_PHY is not set
# CONFIG_DP83869_PHY is not set
# CONFIG_DP83TD510_PHY is not set
# CONFIG_DP83TG720_PHY is not set
# CONFIG_VITESSE_PHY is not set
# CONFIG_XILINX_GMII2RGMII is not set
# CONFIG_PSE_CONTROLLER is not set
CONFIG_CAN_DEV=y
CONFIG_CAN_VCAN=y
CONFIG_CAN_VXCAN=y
CONFIG_CAN_NETLINK=y
CONFIG_CAN_CALC_BITTIMING=y
CONFIG_CAN_RX_OFFLOAD=y
# CONFIG_CAN_CAN327 is not set
# CONFIG_CAN_DUMMY is not set
# CONFIG_CAN_FLEXCAN is not set
# CONFIG_CAN_GRCAN is not set
# CONFIG_CAN_KVASER_PCIEFD is not set
CONFIG_CAN_SLCAN=y
# CONFIG_CAN_VIRTIO_CAN is not set
# CONFIG_CAN_C_CAN is not set
# CONFIG_CAN_CC770 is not set
# CONFIG_CAN_CTUCANFD_PCI is not set
# CONFIG_CAN_CTUCANFD_PLATFORM is not set
# CONFIG_CAN_ESD_402_PCI is not set
CONFIG_CAN_IFI_CANFD=y
# CONFIG_CAN_M_CAN is not set
# CONFIG_CAN_PEAK_PCIEFD is not set
# CONFIG_CAN_SJA1000 is not set
# CONFIG_CAN_SOFTING is not set

#
# CAN SPI interfaces
#
# CONFIG_CAN_HI311X is not set
# CONFIG_CAN_MCP251X is not set
# CONFIG_CAN_MCP251XFD is not set
# end of CAN SPI interfaces

#
# CAN USB interfaces
#
CONFIG_CAN_8DEV_USB=y
CONFIG_CAN_EMS_USB=y
CONFIG_CAN_ESD_USB=y
CONFIG_CAN_ETAS_ES58X=y
CONFIG_CAN_F81604=y
CONFIG_CAN_GS_USB=y
CONFIG_CAN_KVASER_USB=y
CONFIG_CAN_MCBA_USB=y
CONFIG_CAN_PEAK_USB=y
CONFIG_CAN_UCAN=y
# end of CAN USB interfaces

# CONFIG_CAN_DEBUG_DEVICES is not set

#
# MCTP Device Drivers
#
# CONFIG_MCTP_SERIAL is not set
# CONFIG_MCTP_TRANSPORT_I2C is not set
# CONFIG_MCTP_TRANSPORT_USBLIB is not set
# CONFIG_MCTP_TRANSPORT_USB is not set
# end of MCTP Device Drivers

#
# MDIO controller drivers
#
CONFIG_FWNODE_MDIO=y
CONFIG_OF_MDIO=y
CONFIG_ACPI_MDIO=y
# CONFIG_MDIO_BITBANG is not set
# CONFIG_MDIO_BCM_UNIMAC is not set
# CONFIG_MDIO_HISI_FEMAC is not set
CONFIG_MDIO_MVUSB=y
# CONFIG_MDIO_MSCC_MIIM is not set
# CONFIG_MDIO_OCTEON is not set
# CONFIG_MDIO_IPQ4019 is not set
# CONFIG_MDIO_IPQ8064 is not set
# CONFIG_MDIO_THUNDER is not set

#
# MDIO Multiplexers
#
# CONFIG_MDIO_BUS_MUX_GPIO is not set
# CONFIG_MDIO_BUS_MUX_MULTIPLEXER is not set
# CONFIG_MDIO_BUS_MUX_MMIOREG is not set
# end of MDIO Multiplexers
# end of MDIO controller drivers

#
# PCS device drivers
#
# CONFIG_PCS_XPCS is not set
# end of PCS device drivers

# CONFIG_PLIP is not set
CONFIG_PPP=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_MPPE=y
CONFIG_PPP_MULTILINK=y
CONFIG_PPPOATM=y
CONFIG_PPPOX=y
CONFIG_PPPOE=y
CONFIG_PPPOE_HASH_BITS_1=y
# CONFIG_PPPOE_HASH_BITS_2 is not set
# CONFIG_PPPOE_HASH_BITS_4 is not set
# CONFIG_PPPOE_HASH_BITS_8 is not set
CONFIG_PPPOE_HASH_BITS=1
CONFIG_PPTP=y
CONFIG_PPPOL2TP=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_SLIP=y
CONFIG_SLHC=y
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
CONFIG_USB_NET_DRIVERS=y
CONFIG_USB_CATC=y
CONFIG_USB_KAWETH=y
CONFIG_USB_PEGASUS=y
CONFIG_USB_RTL8150=y
CONFIG_USB_RTL8152=y
CONFIG_USB_LAN78XX=y
CONFIG_USB_USBNET=y
CONFIG_USB_NET_AX8817X=y
CONFIG_USB_NET_AX88179_178A=y
CONFIG_USB_NET_CDCETHER=y
CONFIG_USB_NET_CDC_EEM=y
CONFIG_USB_NET_CDC_NCM=y
CONFIG_USB_NET_HUAWEI_CDC_NCM=y
CONFIG_USB_NET_CDC_MBIM=y
CONFIG_USB_NET_DM9601=y
CONFIG_USB_NET_SR9700=y
CONFIG_USB_NET_SR9800=y
CONFIG_USB_NET_SMSC75XX=y
CONFIG_USB_NET_SMSC95XX=y
CONFIG_USB_NET_GL620A=y
CONFIG_USB_NET_NET1080=y
CONFIG_USB_NET_PLUSB=y
CONFIG_USB_NET_MCS7830=y
CONFIG_USB_NET_RNDIS_HOST=y
CONFIG_USB_NET_CDC_SUBSET_ENABLE=y
CONFIG_USB_NET_CDC_SUBSET=y
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_KC2190=y
CONFIG_USB_NET_ZAURUS=y
CONFIG_USB_NET_CX82310_ETH=y
CONFIG_USB_NET_KALMIA=y
CONFIG_USB_NET_QMI_WWAN=y
CONFIG_USB_HSO=y
CONFIG_USB_NET_INT51X1=y
CONFIG_USB_CDC_PHONET=y
CONFIG_USB_IPHETH=y
CONFIG_USB_SIERRA_NET=y
CONFIG_USB_VL600=y
CONFIG_USB_NET_CH9200=y
CONFIG_USB_NET_AQC111=y
CONFIG_USB_RTL8153_ECM=y
CONFIG_WLAN=y
CONFIG_WLAN_VENDOR_ADMTEK=y
# CONFIG_ADM8211 is not set
CONFIG_ATH_COMMON=y
CONFIG_WLAN_VENDOR_ATH=y
# CONFIG_ATH_DEBUG is not set
# CONFIG_ATH5K is not set
# CONFIG_ATH5K_PCI is not set
CONFIG_ATH9K_HW=y
CONFIG_ATH9K_COMMON=y
CONFIG_ATH9K_COMMON_DEBUG=y
CONFIG_ATH9K_BTCOEX_SUPPORT=y
CONFIG_ATH9K=y
CONFIG_ATH9K_PCI=y
CONFIG_ATH9K_AHB=y
CONFIG_ATH9K_DEBUGFS=y
# CONFIG_ATH9K_STATION_STATISTICS is not set
CONFIG_ATH9K_DYNACK=y
# CONFIG_ATH9K_WOW is not set
CONFIG_ATH9K_RFKILL=y
CONFIG_ATH9K_CHANNEL_CONTEXT=y
CONFIG_ATH9K_PCOEM=y
# CONFIG_ATH9K_PCI_NO_EEPROM is not set
CONFIG_ATH9K_HTC=y
CONFIG_ATH9K_HTC_DEBUGFS=y
# CONFIG_ATH9K_HWRNG is not set
CONFIG_ATH9K_COMMON_SPECTRAL=y
CONFIG_CARL9170=y
CONFIG_CARL9170_LEDS=y
# CONFIG_CARL9170_DEBUGFS is not set
CONFIG_CARL9170_WPC=y
CONFIG_CARL9170_HWRNG=y
CONFIG_ATH6KL=y
# CONFIG_ATH6KL_SDIO is not set
CONFIG_ATH6KL_USB=y
# CONFIG_ATH6KL_DEBUG is not set
# CONFIG_ATH6KL_TRACING is not set
CONFIG_AR5523=y
# CONFIG_WIL6210 is not set
CONFIG_ATH10K=y
CONFIG_ATH10K_CE=y
CONFIG_ATH10K_PCI=y
# CONFIG_ATH10K_AHB is not set
# CONFIG_ATH10K_SDIO is not set
CONFIG_ATH10K_USB=y
# CONFIG_ATH10K_DEBUG is not set
# CONFIG_ATH10K_DEBUGFS is not set
CONFIG_ATH10K_LEDS=y
# CONFIG_ATH10K_TRACING is not set
# CONFIG_WCN36XX is not set
CONFIG_ATH11K=y
# CONFIG_ATH11K_PCI is not set
# CONFIG_ATH11K_DEBUG is not set
# CONFIG_ATH11K_DEBUGFS is not set
# CONFIG_ATH11K_TRACING is not set
# CONFIG_ATH12K is not set
# CONFIG_WLAN_VENDOR_ATMEL is not set
# CONFIG_WLAN_VENDOR_BROADCOM is not set
# CONFIG_WLAN_VENDOR_INTEL is not set
# CONFIG_WLAN_VENDOR_INTERSIL is not set
# CONFIG_WLAN_VENDOR_MARVELL is not set
# CONFIG_WLAN_VENDOR_MEDIATEK is not set
# CONFIG_WLAN_VENDOR_MICROCHIP is not set
CONFIG_WLAN_VENDOR_MORSEMICRO=y
# CONFIG_MM81X_USB is not set
# CONFIG_MM81X_SDIO is not set
CONFIG_WLAN_VENDOR_NXP=y
# CONFIG_NXPWIFI_SDIO is not set
CONFIG_WLAN_VENDOR_PURELIFI=y
CONFIG_PLFXLC=y
# CONFIG_WLAN_VENDOR_RALINK is not set
# CONFIG_WLAN_VENDOR_REALTEK is not set
# CONFIG_WLAN_VENDOR_RSI is not set
CONFIG_WLAN_VENDOR_SILABS=y
# CONFIG_WFX is not set
# CONFIG_WLAN_VENDOR_ST is not set
# CONFIG_WLAN_VENDOR_TI is not set
# CONFIG_WLAN_VENDOR_ZYDAS is not set
# CONFIG_WLAN_VENDOR_QUANTENNA is not set
CONFIG_MAC80211_HWSIM=y
CONFIG_VIRT_WIFI=y
CONFIG_WAN=y
CONFIG_HDLC=y
CONFIG_HDLC_RAW=y
CONFIG_HDLC_RAW_ETH=y
CONFIG_HDLC_CISCO=y
CONFIG_HDLC_FR=y
CONFIG_HDLC_PPP=y
CONFIG_HDLC_X25=y
# CONFIG_FRAMER is not set
# CONFIG_PCI200SYN is not set
# CONFIG_WANXL is not set
# CONFIG_PC300TOO is not set
# CONFIG_FARSYNC is not set
CONFIG_LAPBETHER=y
CONFIG_IEEE802154_DRIVERS=y
# CONFIG_IEEE802154_FAKELB is not set
# CONFIG_IEEE802154_AT86RF230 is not set
# CONFIG_IEEE802154_MRF24J40 is not set
# CONFIG_IEEE802154_CC2520 is not set
CONFIG_IEEE802154_ATUSB=y
# CONFIG_IEEE802154_ADF7242 is not set
# CONFIG_IEEE802154_CA8210 is not set
# CONFIG_IEEE802154_MCR20A is not set
CONFIG_IEEE802154_HWSIM=y

#
# Wireless WAN
#
CONFIG_WWAN=y
# CONFIG_WWAN_DEBUGFS is not set
# CONFIG_WWAN_HWSIM is not set
CONFIG_MHI_WWAN_CTRL=y
# CONFIG_MHI_WWAN_MBIM is not set
# CONFIG_IOSM is not set
# CONFIG_MTK_T7XX is not set
# end of Wireless WAN

CONFIG_VMXNET3=y
# CONFIG_FUJITSU_ES is not set
CONFIG_USB4_NET=y
CONFIG_NETDEVSIM=y
CONFIG_NET_FAILOVER=y

#
# Input device support
#
CONFIG_INPUT=y
CONFIG_INPUT_LEDS=y
CONFIG_INPUT_FF_MEMLESS=y
CONFIG_INPUT_SPARSEKMAP=y
# CONFIG_INPUT_MATRIXKMAP is not set
CONFIG_INPUT_VIVALDIFMAP=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADC is not set
# CONFIG_KEYBOARD_ADP5588 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1050 is not set
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_DLINK_DIR685 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_GPIO is not set
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
# CONFIG_KEYBOARD_CHARLIEPLEX is not set
# CONFIG_KEYBOARD_LM8323 is not set
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_PINEPHONE is not set
# CONFIG_KEYBOARD_SAMSUNG is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_OMAP4 is not set
# CONFIG_KEYBOARD_TM2_TOUCHKEY is not set
# CONFIG_KEYBOARD_TWL4030 is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_CAP11XX is not set
# CONFIG_KEYBOARD_BCM is not set
# CONFIG_KEYBOARD_CYPRESS_SF is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_BYD=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=y
CONFIG_MOUSE_PS2_CYPRESS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_PS2_FOCALTECH=y
# CONFIG_MOUSE_PS2_VMMOUSE is not set
CONFIG_MOUSE_PS2_SMBUS=y
# CONFIG_MOUSE_SERIAL is not set
CONFIG_MOUSE_APPLETOUCH=y
CONFIG_MOUSE_BCM5974=y
# CONFIG_MOUSE_CYAPA is not set
# CONFIG_MOUSE_ELAN_I2C is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
CONFIG_MOUSE_SYNAPTICS_USB=y
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADC is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
CONFIG_JOYSTICK_IFORCE=y
CONFIG_JOYSTICK_IFORCE_USB=y
# CONFIG_JOYSTICK_IFORCE_232 is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_ZHENHUA is not set
# CONFIG_JOYSTICK_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_JOYSTICK_AS5011 is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
CONFIG_JOYSTICK_XPAD=y
CONFIG_JOYSTICK_XPAD_FF=y
CONFIG_JOYSTICK_XPAD_LEDS=y
# CONFIG_JOYSTICK_WALKERA0701 is not set
# CONFIG_JOYSTICK_PSXPAD_SPI is not set
CONFIG_JOYSTICK_PXRC=y
# CONFIG_JOYSTICK_QWIIC is not set
# CONFIG_JOYSTICK_FSIA6B is not set
# CONFIG_JOYSTICK_SENSEHAT is not set
# CONFIG_JOYSTICK_SEESAW is not set
CONFIG_INPUT_TABLET=y
CONFIG_TABLET_USB_ACECAD=y
CONFIG_TABLET_USB_AIPTEK=y
CONFIG_TABLET_USB_HANWANG=y
CONFIG_TABLET_USB_KBTAB=y
CONFIG_TABLET_USB_PEGASUS=y
# CONFIG_TABLET_SERIAL_WACOM4 is not set
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_ADS7846 is not set
# CONFIG_TOUCHSCREEN_AD7877 is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_TOUCHSCREEN_ADC is not set
# CONFIG_TOUCHSCREEN_AR1021_I2C is not set
# CONFIG_TOUCHSCREEN_ATMEL_MXT is not set
# CONFIG_TOUCHSCREEN_AUO_PIXCIR is not set
# CONFIG_TOUCHSCREEN_BU21013 is not set
# CONFIG_TOUCHSCREEN_BU21029 is not set
# CONFIG_TOUCHSCREEN_CHIPONE_ICN8318 is not set
# CONFIG_TOUCHSCREEN_CHIPONE_ICN8505 is not set
# CONFIG_TOUCHSCREEN_CY8CTMA140 is not set
# CONFIG_TOUCHSCREEN_CY8CTMG110 is not set
# CONFIG_TOUCHSCREEN_CYTTSP_CORE is not set
# CONFIG_TOUCHSCREEN_CYTTSP5 is not set
# CONFIG_TOUCHSCREEN_DYNAPRO is not set
# CONFIG_TOUCHSCREEN_HAMPSHIRE is not set
# CONFIG_TOUCHSCREEN_EETI is not set
# CONFIG_TOUCHSCREEN_EGALAX is not set
# CONFIG_TOUCHSCREEN_EGALAX_SERIAL is not set
# CONFIG_TOUCHSCREEN_EXC3000 is not set
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GOODIX is not set
# CONFIG_TOUCHSCREEN_GOODIX_BERLIN_I2C is not set
# CONFIG_TOUCHSCREEN_GOODIX_BERLIN_SPI is not set
# CONFIG_TOUCHSCREEN_HIDEEP is not set
# CONFIG_TOUCHSCREEN_HIMAX_HX852X is not set
# CONFIG_TOUCHSCREEN_HYCON_HY46XX is not set
# CONFIG_TOUCHSCREEN_HYNITRON_CSTXXX is not set
# CONFIG_TOUCHSCREEN_HYNITRON_CST816X is not set
# CONFIG_TOUCHSCREEN_ILI210X is not set
# CONFIG_TOUCHSCREEN_ILITEK is not set
# CONFIG_TOUCHSCREEN_S6SY761 is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_TOUCHSCREEN_EKTF2127 is not set
# CONFIG_TOUCHSCREEN_ELAN is not set
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_WACOM_W8001 is not set
# CONFIG_TOUCHSCREEN_WACOM_I2C is not set
# CONFIG_TOUCHSCREEN_WACOM_W9000 is not set
# CONFIG_TOUCHSCREEN_MAX11801 is not set
# CONFIG_TOUCHSCREEN_MMS114 is not set
# CONFIG_TOUCHSCREEN_MELFAS_MIP4 is not set
# CONFIG_TOUCHSCREEN_MSG2638 is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_NOVATEK_NVT_TS is not set
# CONFIG_TOUCHSCREEN_IMAGIS is not set
# CONFIG_TOUCHSCREEN_IMX6UL_TSC is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_EDT_FT5X06 is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_PIXCIR is not set
# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set
CONFIG_TOUCHSCREEN_USB_COMPOSITE=y
CONFIG_TOUCHSCREEN_USB_EGALAX=y
CONFIG_TOUCHSCREEN_USB_PANJIT=y
CONFIG_TOUCHSCREEN_USB_3M=y
CONFIG_TOUCHSCREEN_USB_ITM=y
CONFIG_TOUCHSCREEN_USB_ETURBO=y
CONFIG_TOUCHSCREEN_USB_GUNZE=y
CONFIG_TOUCHSCREEN_USB_DMC_TSC10=y
CONFIG_TOUCHSCREEN_USB_IRTOUCH=y
CONFIG_TOUCHSCREEN_USB_IDEALTEK=y
CONFIG_TOUCHSCREEN_USB_GENERAL_TOUCH=y
CONFIG_TOUCHSCREEN_USB_GOTOP=y
CONFIG_TOUCHSCREEN_USB_JASTEC=y
CONFIG_TOUCHSCREEN_USB_ELO=y
CONFIG_TOUCHSCREEN_USB_E2I=y
CONFIG_TOUCHSCREEN_USB_ZYTRONIC=y
CONFIG_TOUCHSCREEN_USB_ETT_TC45USB=y
CONFIG_TOUCHSCREEN_USB_NEXIO=y
CONFIG_TOUCHSCREEN_USB_EASYTOUCH=y
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_TOUCHSCREEN_TSC_SERIO is not set
# CONFIG_TOUCHSCREEN_TSC2004 is not set
# CONFIG_TOUCHSCREEN_TSC2005 is not set
# CONFIG_TOUCHSCREEN_TSC2007 is not set
# CONFIG_TOUCHSCREEN_RM_TS is not set
# CONFIG_TOUCHSCREEN_SILEAD is not set
# CONFIG_TOUCHSCREEN_SIS_I2C is not set
# CONFIG_TOUCHSCREEN_ST1232 is not set
# CONFIG_TOUCHSCREEN_STMFTS is not set
CONFIG_TOUCHSCREEN_SUR40=y
# CONFIG_TOUCHSCREEN_SURFACE3_SPI is not set
# CONFIG_TOUCHSCREEN_SX8654 is not set
# CONFIG_TOUCHSCREEN_TPS6507X is not set
# CONFIG_TOUCHSCREEN_ZET6223 is not set
# CONFIG_TOUCHSCREEN_ZFORCE is not set
# CONFIG_TOUCHSCREEN_COLIBRI_VF50 is not set
# CONFIG_TOUCHSCREEN_ROHM_BU21023 is not set
# CONFIG_TOUCHSCREEN_IQS5XX is not set
# CONFIG_TOUCHSCREEN_IQS7211 is not set
# CONFIG_TOUCHSCREEN_ZINITIX is not set
# CONFIG_TOUCHSCREEN_HIMAX_HX83112B is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_AD714X is not set
# CONFIG_INPUT_ATMEL_CAPTOUCH is not set
# CONFIG_INPUT_AW86927 is not set
# CONFIG_INPUT_BMA150 is not set
# CONFIG_INPUT_E3X0_BUTTON is not set
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_MMA8450 is not set
# CONFIG_INPUT_APANEL is not set
# CONFIG_INPUT_GPIO_BEEPER is not set
# CONFIG_INPUT_GPIO_DECODER is not set
# CONFIG_INPUT_GPIO_VIBRA is not set
# CONFIG_INPUT_ATLAS_BTNS is not set
CONFIG_INPUT_ATI_REMOTE2=y
CONFIG_INPUT_KEYSPAN_REMOTE=y
# CONFIG_INPUT_KXTJ9 is not set
CONFIG_INPUT_POWERMATE=y
CONFIG_INPUT_YEALINK=y
CONFIG_INPUT_CM109=y
# CONFIG_INPUT_REGULATOR_HAPTIC is not set
# CONFIG_INPUT_RETU_PWRBUTTON is not set
# CONFIG_INPUT_TWL4030_PWRBUTTON is not set
# CONFIG_INPUT_TWL4030_VIBRA is not set
CONFIG_INPUT_UINPUT=y
# CONFIG_INPUT_PCF8574 is not set
# CONFIG_INPUT_GPIO_ROTARY_ENCODER is not set
# CONFIG_INPUT_DA7280_HAPTICS is not set
# CONFIG_INPUT_ADXL34X is not set
# CONFIG_INPUT_IBM_PANEL is not set
CONFIG_INPUT_IMS_PCU=y
# CONFIG_INPUT_IQS269A is not set
# CONFIG_INPUT_IQS626A is not set
# CONFIG_INPUT_IQS7222 is not set
# CONFIG_INPUT_ISA1200_HAPTIC is not set
# CONFIG_INPUT_CMA3000 is not set
# CONFIG_INPUT_IDEAPAD_SLIDEBAR is not set
# CONFIG_INPUT_AMD_SFH_TABLETMODE is not set
# CONFIG_INPUT_DRV260X_HAPTICS is not set
# CONFIG_INPUT_DRV2665_HAPTICS is not set
# CONFIG_INPUT_DRV2667_HAPTICS is not set
CONFIG_RMI4_CORE=y
# CONFIG_RMI4_I2C is not set
# CONFIG_RMI4_SPI is not set
# CONFIG_RMI4_SMB is not set
CONFIG_RMI4_F03=y
CONFIG_RMI4_F03_SERIO=y
CONFIG_RMI4_2D_SENSOR=y
CONFIG_RMI4_F11=y
CONFIG_RMI4_F12=y
# CONFIG_RMI4_F1A is not set
# CONFIG_RMI4_F21 is not set
CONFIG_RMI4_F30=y
# CONFIG_RMI4_F34 is not set
CONFIG_RMI4_F3A=y
# CONFIG_RMI4_F54 is not set
# CONFIG_RMI4_F55 is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_ARCH_MIGHT_HAVE_PC_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_SERIO_PS2MULT is not set
# CONFIG_SERIO_ARC_PS2 is not set
# CONFIG_SERIO_APBPS2 is not set
# CONFIG_SERIO_GPIO_PS2 is not set
CONFIG_USERIO=y
# CONFIG_GAMEPORT is not set
# end of Hardware I/O ports
# end of Input device support

#
# Character devices
#
CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_LEGACY_TIOCSTI=y
CONFIG_LDISC_AUTOLOAD=y

#
# Serial drivers
#
CONFIG_SERIAL_EARLYCON=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_16550A_VARIANTS is not set
# CONFIG_SERIAL_8250_FINTEK is not set
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_DMA=y
CONFIG_SERIAL_8250_PCILIB=y
CONFIG_SERIAL_8250_PCI=y
# CONFIG_SERIAL_8250_EXAR is not set
CONFIG_SERIAL_8250_MOXA_PCIE=y
# CONFIG_SERIAL_8250_CS is not set
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
CONFIG_SERIAL_8250_MANY_PORTS=y
# CONFIG_SERIAL_8250_PCI1XXXX is not set
# CONFIG_SERIAL_8250_DW is not set
# CONFIG_SERIAL_8250_RT288X is not set
CONFIG_SERIAL_8250_LPSS=y
CONFIG_SERIAL_8250_MID=y
CONFIG_SERIAL_8250_PERICOM=y
# CONFIG_SERIAL_8250_NI is not set
# CONFIG_SERIAL_OF_PLATFORM is not set
CONFIG_SERIAL_8250_DWLIB=y

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_UARTLITE is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_SIFIVE is not set
# CONFIG_SERIAL_LANTIQ is not set
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_XILINX_PS_UART is not set
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
# CONFIG_SERIAL_FSL_LINFLEXUART is not set
# CONFIG_SERIAL_CONEXANT_DIGICOLOR is not set
# CONFIG_SERIAL_SPRD is not set
# end of Serial drivers

CONFIG_SERIAL_MCTRL_GPIO=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
CONFIG_N_HDLC=y
CONFIG_N_GSM=y
CONFIG_NOZOMI=y
CONFIG_NULL_TTY=y
CONFIG_HVC_DRIVER=y
CONFIG_SERIAL_DEV_BUS=y
CONFIG_SERIAL_DEV_CTRL_TTYPORT=y
CONFIG_TTY_PRINTK=y
CONFIG_TTY_PRINTK_LEVEL=6
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
CONFIG_VIRTIO_CONSOLE=y
# CONFIG_IPMI_HANDLER is not set
# CONFIG_SSIF_IPMI_BMC is not set
# CONFIG_IPMB_DEVICE_INTERFACE is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_HW_RANDOM_INTEL is not set
# CONFIG_HW_RANDOM_AMD is not set
# CONFIG_HW_RANDOM_BA431 is not set
# CONFIG_HW_RANDOM_VIA is not set
CONFIG_HW_RANDOM_VIRTIO=y
# CONFIG_HW_RANDOM_CCTRNG is not set
# CONFIG_HW_RANDOM_XIPHERA is not set
# CONFIG_DEVMEM is not set
CONFIG_NVRAM=y
# CONFIG_DEVPORT is not set
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
CONFIG_HPET_MMAP_DEFAULT=y
# CONFIG_HANGCHECK_TIMER is not set
CONFIG_TCG_TPM=y
# CONFIG_TCG_TPM2_HMAC is not set
# CONFIG_HW_RANDOM_TPM is not set
CONFIG_TCG_TIS_CORE=y
CONFIG_TCG_TIS=y
# CONFIG_TCG_TIS_SPI is not set
# CONFIG_TCG_TIS_I2C is not set
# CONFIG_TCG_TIS_I2C_CR50 is not set
# CONFIG_TCG_TIS_I2C_ATMEL is not set
# CONFIG_TCG_TIS_I2C_INFINEON is not set
# CONFIG_TCG_TIS_I2C_NUVOTON is not set
# CONFIG_TCG_NSC is not set
# CONFIG_TCG_ATMEL is not set
# CONFIG_TCG_INFINEON is not set
CONFIG_TCG_CRB=y
# CONFIG_TCG_VTPM_PROXY is not set
# CONFIG_TCG_TIS_ST33ZP24_I2C is not set
# CONFIG_TCG_TIS_ST33ZP24_SPI is not set
# CONFIG_TELCLOCK is not set
CONFIG_XILLYBUS_CLASS=y
# CONFIG_XILLYBUS is not set
CONFIG_XILLYUSB=y
# end of Character devices

#
# I2C support
#
CONFIG_I2C=y
CONFIG_ACPI_I2C_OPREGION=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_MUX=y

#
# Multiplexer I2C Chip support
#
# CONFIG_I2C_ARB_GPIO_CHALLENGE is not set
# CONFIG_I2C_MUX_GPIO is not set
# CONFIG_I2C_MUX_GPMUX is not set
# CONFIG_I2C_MUX_LTC4306 is not set
# CONFIG_I2C_MUX_PCA9541 is not set
# CONFIG_I2C_MUX_PCA954x is not set
CONFIG_I2C_MUX_REG=y
# CONFIG_I2C_MUX_MLXCPLD is not set
# end of Multiplexer I2C Chip support

CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_SMBUS=y
CONFIG_I2C_ALGOBIT=y

#
# I2C Hardware Bus support
#

#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_AMD_MP2 is not set
CONFIG_I2C_I801=y
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_ISMT is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_CHT_WC is not set
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_NVIDIA_GPU is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
# CONFIG_I2C_ZHAOXIN is not set

#
# ACPI drivers
#
# CONFIG_I2C_SCMI is not set

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_CBUS_GPIO is not set
CONFIG_I2C_DESIGNWARE_CORE=y
CONFIG_I2C_DESIGNWARE_PLATFORM=y
# CONFIG_I2C_DESIGNWARE_BAYTRAIL is not set
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_EMEV2 is not set
# CONFIG_I2C_GPIO is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_RK3X is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set

#
# External I2C/SMBus adapter drivers
#
CONFIG_I2C_DIOLAN_U2C=y
CONFIG_I2C_DLN2=y
CONFIG_I2C_LJCA=y
CONFIG_I2C_CP2615=y
# CONFIG_I2C_PARPORT is not set
# CONFIG_I2C_PCI1XXXX is not set
CONFIG_I2C_ROBOTFUZZ_OSIF=y
# CONFIG_I2C_TAOS_EVM is not set
CONFIG_I2C_TINY_USB=y
CONFIG_I2C_VIPERBOARD=y

#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_MLXCPLD is not set
# CONFIG_I2C_VIRTIO is not set
# end of I2C Hardware Bus support

# CONFIG_I2C_STUB is not set
CONFIG_I2C_SLAVE=y
CONFIG_I2C_SLAVE_EEPROM=y
# CONFIG_I2C_SLAVE_TESTUNIT is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# end of I2C support

# CONFIG_I3C is not set
CONFIG_I3C_OR_I2C=y
CONFIG_SPI=y
# CONFIG_SPI_DEBUG is not set
CONFIG_SPI_MASTER=y
# CONFIG_SPI_MEM is not set

#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
# CONFIG_SPI_AXI_SPI_ENGINE is not set
# CONFIG_SPI_BITBANG is not set
# CONFIG_SPI_BUTTERFLY is not set
# CONFIG_SPI_CADENCE is not set
# CONFIG_SPI_CADENCE_QUADSPI is not set
# CONFIG_SPI_CH341 is not set
# CONFIG_SPI_DESIGNWARE is not set
CONFIG_SPI_DLN2=y
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_LM70_LLP is not set
# CONFIG_SPI_FSL_SPI is not set
CONFIG_SPI_LJCA=y
# CONFIG_SPI_MICROCHIP_CORE_QSPI is not set
# CONFIG_SPI_MICROCHIP_CORE_SPI is not set
# CONFIG_SPI_LANTIQ_SSC is not set
# CONFIG_SPI_OC_TINY is not set
# CONFIG_SPI_PCI1XXXX is not set
# CONFIG_SPI_PXA2XX is not set
# CONFIG_SPI_SC18IS602 is not set
# CONFIG_SPI_SIFIVE is not set
# CONFIG_SPI_MXIC is not set
# CONFIG_SPI_VIRTIO is not set
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set

#
# SPI Multiplexer support
#
# CONFIG_SPI_MUX is not set

#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
# CONFIG_SPI_LOOPBACK_TEST is not set
# CONFIG_SPI_TLE62X0 is not set
# CONFIG_SPI_SLAVE is not set
CONFIG_SPI_DYNAMIC=y
# CONFIG_SPMI is not set
# CONFIG_HSI is not set
CONFIG_PPS=y
# CONFIG_PPS_DEBUG is not set

#
# PPS clients support
#
# CONFIG_PPS_CLIENT_KTIMER is not set
# CONFIG_PPS_CLIENT_LDISC is not set
# CONFIG_PPS_CLIENT_PARPORT is not set
# CONFIG_PPS_CLIENT_GPIO is not set
# CONFIG_PPS_GENERATOR is not set

#
# PTP clock support
#
CONFIG_PTP_1588_CLOCK=y
CONFIG_PTP_1588_CLOCK_OPTIONAL=y

#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks.
#
CONFIG_PTP_1588_CLOCK_KVM=y
CONFIG_PTP_1588_CLOCK_VMCLOCK=y
# CONFIG_PTP_1588_CLOCK_IDT82P33 is not set
# CONFIG_PTP_1588_CLOCK_IDTCM is not set
# CONFIG_PTP_1588_CLOCK_FC3W is not set
# CONFIG_PTP_1588_CLOCK_MOCK is not set
# CONFIG_PTP_1588_CLOCK_VMW is not set
# CONFIG_PTP_1588_CLOCK_OCP is not set
# CONFIG_PTP_NETC_V4_TIMER is not set
# end of PTP clock support

#
# DPLL device support
#
# CONFIG_ZL3073X_I2C is not set
# CONFIG_ZL3073X_SPI is not set
# end of DPLL device support

# CONFIG_PINCTRL is not set
CONFIG_GPIOLIB_LEGACY=y
CONFIG_GPIOLIB=y
CONFIG_GPIOLIB_FASTPATH_LIMIT=512
CONFIG_OF_GPIO=y
CONFIG_GPIO_ACPI=y
CONFIG_GPIOLIB_IRQCHIP=y
# CONFIG_DEBUG_GPIO is not set
# CONFIG_GPIO_SYSFS is not set
# CONFIG_GPIO_CDEV is not set

#
# Memory mapped GPIO drivers
#
# CONFIG_GPIO_74XX_MMIO is not set
# CONFIG_GPIO_ALTERA is not set
# CONFIG_GPIO_AMDPT is not set
# CONFIG_GPIO_BY_PINCTRL is not set
# CONFIG_GPIO_CADENCE is not set
# CONFIG_GPIO_DWAPB is not set
# CONFIG_GPIO_FTGPIO010 is not set
# CONFIG_GPIO_GENERIC_PLATFORM is not set
# CONFIG_GPIO_GRANITERAPIDS is not set
# CONFIG_GPIO_GRGPIO is not set
# CONFIG_GPIO_HLWD is not set
# CONFIG_GPIO_ICH is not set
# CONFIG_GPIO_LOGICVC is not set
# CONFIG_GPIO_MB86S7X is not set
# CONFIG_GPIO_POLARFIRE_SOC is not set
# CONFIG_GPIO_SIFIVE is not set
# CONFIG_GPIO_SYSCON is not set
# CONFIG_GPIO_WAVESHARE_DSI_TOUCH is not set
# CONFIG_GPIO_XILINX is not set
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers

#
# Port-mapped I/O GPIO drivers
#
# CONFIG_GPIO_VX855 is not set
# CONFIG_GPIO_F7188X is not set
# CONFIG_GPIO_IT87 is not set
# CONFIG_GPIO_NOVALAKE is not set
# CONFIG_GPIO_SCH311X is not set
# CONFIG_GPIO_WINBOND is not set
# CONFIG_GPIO_WS16C48 is not set
# end of Port-mapped I/O GPIO drivers

#
# I2C GPIO expanders
#
# CONFIG_GPIO_ADNP is not set
# CONFIG_GPIO_FXL6408 is not set
# CONFIG_GPIO_DS4520 is not set
# CONFIG_GPIO_GW_PLD is not set
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
# CONFIG_GPIO_PCA953X is not set
# CONFIG_GPIO_PCA9570 is not set
# CONFIG_GPIO_PCF857X is not set
# CONFIG_GPIO_TPIC2810 is not set
# end of I2C GPIO expanders

#
# MFD GPIO expanders
#
CONFIG_GPIO_DLN2=y
CONFIG_GPIO_LJCA=y
# CONFIG_GPIO_TWL4030 is not set
# CONFIG_GPIO_WHISKEY_COVE is not set
# end of MFD GPIO expanders

#
# Auxiliary Bus GPIO drivers
#
# end of Auxiliary Bus GPIO drivers

#
# PCI GPIO expanders
#
# CONFIG_GPIO_AMD8111 is not set
# CONFIG_GPIO_BT8XX is not set
# CONFIG_GPIO_ML_IOH is not set
# CONFIG_GPIO_PCI_IDIO_16 is not set
# CONFIG_GPIO_PCIE_IDIO_24 is not set
# CONFIG_GPIO_RDC321X is not set
# CONFIG_GPIO_SODAVILLE is not set
# end of PCI GPIO expanders

#
# SPI GPIO expanders
#
# CONFIG_GPIO_74X164 is not set
# CONFIG_GPIO_MAX3191X is not set
# CONFIG_GPIO_MAX7301 is not set
# CONFIG_GPIO_MC33880 is not set
# CONFIG_GPIO_PISOSR is not set
# CONFIG_GPIO_XRA1403 is not set
# end of SPI GPIO expanders

#
# USB GPIO expanders
#
CONFIG_GPIO_VIPERBOARD=y
# CONFIG_GPIO_MPSSE is not set
# end of USB GPIO expanders

#
# Virtual GPIO drivers
#
# CONFIG_GPIO_AGGREGATOR is not set
# CONFIG_GPIO_LATCH is not set
# CONFIG_GPIO_LINE_MUX is not set
# CONFIG_GPIO_MOCKUP is not set
# CONFIG_GPIO_VIRTIO is not set
# CONFIG_GPIO_SIM is not set
# end of Virtual GPIO drivers

#
# GPIO Debugging utilities
#
# CONFIG_GPIO_SLOPPY_LOGIC_ANALYZER is not set
# CONFIG_GPIO_VIRTUSER is not set
# end of GPIO Debugging utilities

# CONFIG_W1 is not set
# CONFIG_POWER_RESET is not set
# CONFIG_POWER_SEQUENCING is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
CONFIG_POWER_SUPPLY_HWMON=y
# CONFIG_GENERIC_ADC_BATTERY is not set
# CONFIG_IP5XXX_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_CHARGER_ADP5061 is not set
# CONFIG_BATTERY_CHAGALL is not set
# CONFIG_BATTERY_CW2015 is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2781 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_SAMSUNG_SDI is not set
# CONFIG_BATTERY_S2MU005 is not set
# CONFIG_BATTERY_SBS is not set
# CONFIG_CHARGER_SBS is not set
# CONFIG_MANAGER_SBS is not set
# CONFIG_BATTERY_BQ27XXX is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_BATTERY_MAX1720X is not set
CONFIG_CHARGER_ISP1704=y
# CONFIG_CHARGER_MAX8903 is not set
# CONFIG_CHARGER_TWL4030 is not set
# CONFIG_CHARGER_TWL6030 is not set
# CONFIG_CHARGER_LP8727 is not set
# CONFIG_CHARGER_GPIO is not set
# CONFIG_CHARGER_MANAGER is not set
# CONFIG_CHARGER_LT3651 is not set
# CONFIG_CHARGER_LTC4162L is not set
# CONFIG_CHARGER_DETECTOR_MAX14656 is not set
# CONFIG_CHARGER_MAX77976 is not set
# CONFIG_CHARGER_MAX8971 is not set
# CONFIG_CHARGER_MT6360 is not set
# CONFIG_CHARGER_MT6370 is not set
# CONFIG_CHARGER_BQ2415X is not set
CONFIG_CHARGER_BQ24190=y
# CONFIG_CHARGER_BQ24257 is not set
# CONFIG_CHARGER_BQ24735 is not set
# CONFIG_CHARGER_BQ2515X is not set
# CONFIG_CHARGER_BQ25890 is not set
# CONFIG_CHARGER_BQ25980 is not set
# CONFIG_CHARGER_BQ25630 is not set
# CONFIG_CHARGER_BQ256XX is not set
# CONFIG_CHARGER_SGM41542 is not set
# CONFIG_CHARGER_SMB347 is not set
# CONFIG_BATTERY_GAUGE_LTC2941 is not set
# CONFIG_BATTERY_GOLDFISH is not set
# CONFIG_BATTERY_RT5033 is not set
# CONFIG_CHARGER_RT9455 is not set
# CONFIG_CHARGER_RT9467 is not set
# CONFIG_CHARGER_RT9471 is not set
# CONFIG_CHARGER_RT9756 is not set
# CONFIG_FUEL_GAUGE_STC3117 is not set
# CONFIG_CHARGER_UCS1002 is not set
# CONFIG_CHARGER_BD99954 is not set
# CONFIG_BATTERY_SURFACE is not set
# CONFIG_CHARGER_SURFACE is not set
# CONFIG_BATTERY_UG3105 is not set
# CONFIG_BATTERY_CHARGER_SURFACE_RT is not set
# CONFIG_FUEL_GAUGE_MM8013 is not set
CONFIG_HWMON=y
# CONFIG_HWMON_DEBUG_CHIP is not set

#
# Native drivers
#
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7314 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
# CONFIG_SENSORS_ADM1025 is not set
# CONFIG_SENSORS_ADM1026 is not set
# CONFIG_SENSORS_ADM1029 is not set
# CONFIG_SENSORS_ADM1031 is not set
# CONFIG_SENSORS_ADM1177 is not set
# CONFIG_SENSORS_ADM9240 is not set
# CONFIG_SENSORS_ADT7310 is not set
# CONFIG_SENSORS_ADT7410 is not set
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
# CONFIG_SENSORS_ADT7475 is not set
# CONFIG_SENSORS_AHT10 is not set
CONFIG_SENSORS_AQUACOMPUTER_D5NEXT=y
# CONFIG_SENSORS_AS370 is not set
# CONFIG_SENSORS_ASC7621 is not set
# CONFIG_SENSORS_ASUS_ROG_RYUJIN is not set
# CONFIG_SENSORS_AXI_FAN_CONTROL is not set
# CONFIG_SENSORS_K8TEMP is not set
# CONFIG_SENSORS_K10TEMP is not set
# CONFIG_SENSORS_KB9002 is not set
# CONFIG_SENSORS_FAM15H_POWER is not set
# CONFIG_SENSORS_APPLESMC is not set
# CONFIG_SENSORS_ARCTIC_FAN_CONTROLLER is not set
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
# CONFIG_SENSORS_CHIPCAP2 is not set
CONFIG_SENSORS_CORSAIR_CPRO=y
CONFIG_SENSORS_CORSAIR_PSU=y
# CONFIG_SENSORS_DRIVETEMP is not set
# CONFIG_SENSORS_DS620 is not set
# CONFIG_SENSORS_DS1621 is not set
# CONFIG_SENSORS_DELL_SMM is not set
# CONFIG_SENSORS_I5K_AMB is not set
# CONFIG_SENSORS_F71805F is not set
# CONFIG_SENSORS_F71882FG is not set
# CONFIG_SENSORS_F75375S is not set
# CONFIG_SENSORS_FSCHMD is not set
# CONFIG_SENSORS_FTSTEUTATES is not set
CONFIG_SENSORS_GIGABYTE_WATERFORCE=y
# CONFIG_SENSORS_GL518SM is not set
# CONFIG_SENSORS_GL520SM is not set
# CONFIG_SENSORS_GPD is not set
# CONFIG_SENSORS_G760A is not set
# CONFIG_SENSORS_G762 is not set
# CONFIG_SENSORS_GPIO_FAN is not set
# CONFIG_SENSORS_HIH6130 is not set
# CONFIG_SENSORS_HS3001 is not set
# CONFIG_SENSORS_HTU31 is not set
# CONFIG_SENSORS_IIO_HWMON is not set
# CONFIG_SENSORS_I5500 is not set
# CONFIG_SENSORS_CORETEMP is not set
# CONFIG_SENSORS_ISL28022 is not set
# CONFIG_SENSORS_IT87 is not set
# CONFIG_SENSORS_JC42 is not set
CONFIG_SENSORS_POWERZ=y
# CONFIG_SENSORS_POWR1220 is not set
# CONFIG_SENSORS_PROM21_XHCI is not set
# CONFIG_SENSORS_LATTEPANDA_SIGMA_EC is not set
# CONFIG_SENSORS_LENOVO_EC is not set
# CONFIG_SENSORS_LINEAGE is not set
# CONFIG_SENSORS_LTC2945 is not set
# CONFIG_SENSORS_LTC2947_I2C is not set
# CONFIG_SENSORS_LTC2947_SPI is not set
# CONFIG_SENSORS_LTC2990 is not set
# CONFIG_SENSORS_LTC2991 is not set
# CONFIG_SENSORS_LTC2992 is not set
# CONFIG_SENSORS_LTC4151 is not set
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4222 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LTC4260 is not set
# CONFIG_SENSORS_LTC4261 is not set
# CONFIG_SENSORS_LTC4282 is not set
# CONFIG_SENSORS_LTC4283 is not set
# CONFIG_SENSORS_MAX1111 is not set
# CONFIG_SENSORS_MAX127 is not set
# CONFIG_SENSORS_MAX16065 is not set
# CONFIG_SENSORS_MAX1619 is not set
# CONFIG_SENSORS_MAX1668 is not set
# CONFIG_SENSORS_MAX197 is not set
# CONFIG_SENSORS_MAX31722 is not set
# CONFIG_SENSORS_MAX31730 is not set
# CONFIG_SENSORS_MAX31760 is not set
# CONFIG_MAX31827 is not set
# CONFIG_SENSORS_MAX6620 is not set
# CONFIG_SENSORS_MAX6621 is not set
# CONFIG_SENSORS_MAX6639 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_MAX6697 is not set
# CONFIG_SENSORS_MAX31790 is not set
# CONFIG_SENSORS_MC34VR500 is not set
# CONFIG_SENSORS_MCP3021 is not set
# CONFIG_SENSORS_MCP9982 is not set
# CONFIG_SENSORS_TC654 is not set
# CONFIG_SENSORS_TPS23861 is not set
# CONFIG_SENSORS_MR75203 is not set
# CONFIG_SENSORS_ADCXX is not set
# CONFIG_SENSORS_LM63 is not set
# CONFIG_SENSORS_LM70 is not set
# CONFIG_SENSORS_LM73 is not set
# CONFIG_SENSORS_LM75 is not set
# CONFIG_SENSORS_LM77 is not set
# CONFIG_SENSORS_LM78 is not set
# CONFIG_SENSORS_LM80 is not set
# CONFIG_SENSORS_LM83 is not set
# CONFIG_SENSORS_LM85 is not set
# CONFIG_SENSORS_LM87 is not set
# CONFIG_SENSORS_LM90 is not set
# CONFIG_SENSORS_LM92 is not set
# CONFIG_SENSORS_LM93 is not set
# CONFIG_SENSORS_LM95234 is not set
# CONFIG_SENSORS_LM95241 is not set
# CONFIG_SENSORS_LM95245 is not set
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_PC87427 is not set
# CONFIG_SENSORS_NTC_THERMISTOR is not set
# CONFIG_SENSORS_NCT6683 is not set
# CONFIG_SENSORS_NCT6775 is not set
# CONFIG_SENSORS_NCT6775_I2C is not set
# CONFIG_SENSORS_NCT7363 is not set
# CONFIG_SENSORS_NCT7802 is not set
# CONFIG_SENSORS_NCT7904 is not set
# CONFIG_SENSORS_NPCM7XX is not set
CONFIG_SENSORS_NZXT_KRAKEN2=y
# CONFIG_SENSORS_NZXT_KRAKEN3 is not set
CONFIG_SENSORS_NZXT_SMART2=y
# CONFIG_SENSORS_OCC_P8_I2C is not set
# CONFIG_SENSORS_PCF8591 is not set
# CONFIG_PMBUS is not set
# CONFIG_SENSORS_PT5161L is not set
# CONFIG_SENSORS_SHT15 is not set
# CONFIG_SENSORS_SHT21 is not set
# CONFIG_SENSORS_SHT3x is not set
# CONFIG_SENSORS_SHT4x is not set
# CONFIG_SENSORS_SHTC1 is not set
# CONFIG_SENSORS_SIS5595 is not set
# CONFIG_SENSORS_DME1737 is not set
# CONFIG_SENSORS_EMC1403 is not set
# CONFIG_SENSORS_EMC1812 is not set
# CONFIG_SENSORS_EMC2103 is not set
# CONFIG_SENSORS_EMC2305 is not set
# CONFIG_SENSORS_EMC6W201 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
# CONFIG_SENSORS_SMSC47M192 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SCH5627 is not set
# CONFIG_SENSORS_SCH5636 is not set
# CONFIG_SENSORS_STTS751 is not set
# CONFIG_SENSORS_SURFACE_FAN is not set
# CONFIG_SENSORS_SURFACE_TEMP is not set
# CONFIG_SENSORS_ADC128D818 is not set
# CONFIG_SENSORS_ADS7828 is not set
# CONFIG_SENSORS_ADS7871 is not set
# CONFIG_SENSORS_AMC6821 is not set
# CONFIG_SENSORS_INA209 is not set
# CONFIG_SENSORS_INA2XX is not set
# CONFIG_SENSORS_INA238 is not set
# CONFIG_SENSORS_INA3221 is not set
# CONFIG_SENSORS_SPD5118 is not set
# CONFIG_SENSORS_TC74 is not set
# CONFIG_SENSORS_THMC50 is not set
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP103 is not set
# CONFIG_SENSORS_TMP108 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
# CONFIG_SENSORS_TMP464 is not set
# CONFIG_SENSORS_TMP513 is not set
# CONFIG_SENSORS_TSC1641 is not set
# CONFIG_SENSORS_VIA_CPUTEMP is not set
# CONFIG_SENSORS_VIA686A is not set
# CONFIG_SENSORS_VT1211 is not set
# CONFIG_SENSORS_VT8231 is not set
# CONFIG_SENSORS_W83773G is not set
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
# CONFIG_SENSORS_XGENE is not set
# CONFIG_SENSORS_YOGAFAN is not set

#
# ACPI drivers
#
# CONFIG_SENSORS_ACPI_POWER is not set
# CONFIG_SENSORS_ATK0110 is not set
# CONFIG_SENSORS_ASUS_WMI is not set
# CONFIG_SENSORS_ASUS_EC is not set
# CONFIG_SENSORS_HP_WMI is not set
CONFIG_THERMAL=y
CONFIG_THERMAL_NETLINK=y
# CONFIG_THERMAL_STATISTICS is not set
# CONFIG_THERMAL_DEBUGFS is not set
# CONFIG_THERMAL_CORE_TESTING is not set
CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0
CONFIG_THERMAL_HWMON=y
# CONFIG_THERMAL_OF is not set
CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set
# CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set
# CONFIG_THERMAL_GOV_FAIR_SHARE is not set
CONFIG_THERMAL_GOV_STEP_WISE=y
# CONFIG_THERMAL_GOV_BANG_BANG is not set
# CONFIG_THERMAL_GOV_USER_SPACE is not set
# CONFIG_PCIE_THERMAL is not set
# CONFIG_THERMAL_EMULATION is not set
# CONFIG_THERMAL_MMIO is not set

#
# Intel thermal drivers
#
# CONFIG_INTEL_POWERCLAMP is not set
CONFIG_X86_THERMAL_VECTOR=y
# CONFIG_X86_PKG_TEMP_THERMAL is not set
# CONFIG_INTEL_SOC_DTS_THERMAL is not set

#
# ACPI INT340X thermal drivers
#
# CONFIG_INT340X_THERMAL is not set
# end of ACPI INT340X thermal drivers

# CONFIG_INTEL_BXT_PMIC_THERMAL is not set
# CONFIG_INTEL_PCH_THERMAL is not set
# CONFIG_INTEL_TCC_COOLING is not set
# CONFIG_INTEL_HFI_THERMAL is not set
# end of Intel thermal drivers

# CONFIG_GENERIC_ADC_THERMAL is not set
CONFIG_WATCHDOG=y
# CONFIG_WATCHDOG_CORE is not set
# CONFIG_WATCHDOG_NOWAYOUT is not set
CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=y
CONFIG_WATCHDOG_OPEN_TIMEOUT=0
# CONFIG_WATCHDOG_SYSFS is not set
# CONFIG_WATCHDOG_HRTIMER_PRETIMEOUT is not set

#
# Watchdog Pretimeout Governors
#

#
# Watchdog Device Drivers
#
# CONFIG_SOFT_WATCHDOG is not set
# CONFIG_GPIO_WATCHDOG is not set
# CONFIG_LENOVO_SE10_WDT is not set
# CONFIG_LENOVO_SE30_WDT is not set
# CONFIG_LENOVO_SE30G2_SE60_WDT is not set
# CONFIG_WDAT_WDT is not set
# CONFIG_XILINX_WATCHDOG is not set
# CONFIG_ZIIRAVE_WATCHDOG is not set
# CONFIG_CADENCE_WATCHDOG is not set
# CONFIG_DW_WATCHDOG is not set
# CONFIG_TWL4030_WATCHDOG is not set
# CONFIG_MAX63XX_WATCHDOG is not set
# CONFIG_RETU_WATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_ADVANTECH_WDT is not set
# CONFIG_ADVANTECH_EC_WDT is not set
# CONFIG_ALIM1535_WDT is not set
# CONFIG_ALIM7101_WDT is not set
# CONFIG_EBC_C384_WDT is not set
# CONFIG_EXAR_WDT is not set
# CONFIG_F71808E_WDT is not set
# CONFIG_SP5100_TCO is not set
# CONFIG_SBC_FITPC2_WATCHDOG is not set
# CONFIG_EUROTECH_WDT is not set
# CONFIG_IB700_WDT is not set
# CONFIG_IBMASR is not set
# CONFIG_WAFER_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_IE6XX_WDT is not set
# CONFIG_INTEL_OC_WATCHDOG is not set
# CONFIG_ITCO_WDT is not set
# CONFIG_IT8712F_WDT is not set
# CONFIG_IT87_WDT is not set
# CONFIG_HP_WATCHDOG is not set
# CONFIG_SC1200_WDT is not set
# CONFIG_PC87413_WDT is not set
# CONFIG_NV_TCO is not set
# CONFIG_60XX_WDT is not set
# CONFIG_SMSC_SCH311X_WDT is not set
# CONFIG_SMSC37B787_WDT is not set
# CONFIG_TQMX86_WDT is not set
# CONFIG_VIA_WDT is not set
# CONFIG_W83627HF_WDT is not set
# CONFIG_W83877F_WDT is not set
# CONFIG_W83977F_WDT is not set
# CONFIG_SBC_EPX_C3_WATCHDOG is not set
# CONFIG_INTEL_MEI_WDT is not set
# CONFIG_NI903X_WDT is not set
# CONFIG_NIC7018_WDT is not set
# CONFIG_MEN_A21_WDT is not set

#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set

#
# USB-based Watchdog Cards
#
CONFIG_USBPCWATCHDOG=y
CONFIG_SSB_POSSIBLE=y
CONFIG_SSB=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
# CONFIG_SSB_PCIHOST is not set
CONFIG_SSB_PCMCIAHOST_POSSIBLE=y
# CONFIG_SSB_PCMCIAHOST is not set
CONFIG_SSB_SDIOHOST_POSSIBLE=y
# CONFIG_SSB_SDIOHOST is not set
# CONFIG_SSB_DRIVER_GPIO is not set
CONFIG_BCMA_POSSIBLE=y
CONFIG_BCMA=y
CONFIG_BCMA_HOST_PCI_POSSIBLE=y
# CONFIG_BCMA_HOST_PCI is not set
# CONFIG_BCMA_HOST_SOC is not set
# CONFIG_BCMA_DRIVER_PCI is not set
# CONFIG_BCMA_DRIVER_GMAC_CMN is not set
# CONFIG_BCMA_DRIVER_GPIO is not set
# CONFIG_BCMA_DEBUG is not set

#
# Multifunction device drivers
#
CONFIG_MFD_CORE=y
# CONFIG_MFD_ADP5585 is not set
# CONFIG_MFD_ACT8945A is not set
# CONFIG_MFD_AS3711 is not set
# CONFIG_MFD_SMPRO is not set
# CONFIG_MFD_AS3722 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
# CONFIG_MFD_ATMEL_FLEXCOM is not set
# CONFIG_MFD_ATMEL_HLCDC is not set
# CONFIG_MFD_BCM590XX is not set
# CONFIG_MFD_BD9571MWV is not set
# CONFIG_MFD_AXP20X_I2C is not set
# CONFIG_MFD_CGBC is not set
# CONFIG_MFD_CS40L50_I2C is not set
# CONFIG_MFD_CS40L50_SPI is not set
# CONFIG_MFD_CS42L43_I2C is not set
# CONFIG_MFD_CS42L43_SDW is not set
# CONFIG_MFD_LOCHNAGAR is not set
# CONFIG_MFD_MADERA is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DA9150 is not set
CONFIG_MFD_DLN2=y
# CONFIG_MFD_GATEWORKS_GSC is not set
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_MFD_MP2629 is not set
# CONFIG_MFD_PF1550 is not set
# CONFIG_MFD_HI6421_PMIC is not set
# CONFIG_MFD_INTEL_QUARK_I2C_GPIO is not set
CONFIG_LPC_ICH=y
# CONFIG_LPC_SCH is not set
# CONFIG_INTEL_SOC_PMIC is not set
CONFIG_INTEL_SOC_PMIC_BXTWC=y
CONFIG_INTEL_SOC_PMIC_CHTWC=y
# CONFIG_INTEL_SOC_PMIC_CHTDC_TI is not set
# CONFIG_MFD_INTEL_LPSS_ACPI is not set
# CONFIG_MFD_INTEL_LPSS_PCI is not set
CONFIG_MFD_INTEL_PMC_BXT=y
# CONFIG_MFD_IQS62X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_88PM886_PMIC is not set
# CONFIG_MFD_MAX5970 is not set
# CONFIG_MFD_MAX14577 is not set
# CONFIG_MFD_MAX77541 is not set
# CONFIG_MFD_MAX77620 is not set
# CONFIG_MFD_MAX77650 is not set
# CONFIG_MFD_MAX77686 is not set
# CONFIG_MFD_MAX77693 is not set
# CONFIG_MFD_MAX77705 is not set
# CONFIG_MFD_MAX77714 is not set
# CONFIG_MFD_MAX77759 is not set
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
CONFIG_MFD_MT6360=y
CONFIG_MFD_MT6370=y
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_MFD_NCT6694 is not set
# CONFIG_MFD_OCELOT is not set
# CONFIG_MFD_CPCAP is not set
CONFIG_MFD_VIPERBOARD=y
# CONFIG_MFD_NTXEC is not set
CONFIG_MFD_RETU=y
# CONFIG_MFD_SY7636A is not set
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RT4831 is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RT5120 is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_RK8XX_I2C is not set
# CONFIG_MFD_RK8XX_SPI is not set
# CONFIG_MFD_RN5T618 is not set
# CONFIG_MFD_SEC_I2C is not set
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_SKY81452 is not set
# CONFIG_MFD_STMPE is not set
CONFIG_MFD_SYSCON=y
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
# CONFIG_MFD_TI_LMU is not set
# CONFIG_MFD_BQ257XX is not set
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
# CONFIG_MFD_TPS65086 is not set
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TPS65217 is not set
# CONFIG_MFD_TI_LP873X is not set
# CONFIG_MFD_TI_LP87565 is not set
# CONFIG_MFD_TPS65218 is not set
# CONFIG_MFD_TPS65219 is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS6594_I2C is not set
# CONFIG_MFD_TPS6594_SPI is not set
CONFIG_TWL4030_CORE=y
# CONFIG_MFD_TWL4030_AUDIO is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_TQMX86 is not set
# CONFIG_MFD_VX855 is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_ROHM_BD718XX is not set
# CONFIG_MFD_ROHM_BD71828 is not set
# CONFIG_MFD_ROHM_BD957XMUF is not set
# CONFIG_MFD_ROHM_BD96801 is not set
# CONFIG_MFD_STPMIC1 is not set
# CONFIG_MFD_STMFX is not set
# CONFIG_MFD_ATC260X_I2C is not set
# CONFIG_MFD_QCOM_PM8008 is not set
# CONFIG_RAVE_SP_CORE is not set
# CONFIG_MFD_INTEL_M10_BMC_SPI is not set
# CONFIG_MFD_QNAP_MCU is not set
# CONFIG_MFD_RSMU_I2C is not set
# CONFIG_MFD_RSMU_SPI is not set
# CONFIG_MFD_UPBOARD_FPGA is not set
# CONFIG_MFD_MAX7360 is not set
# end of Multifunction device drivers

CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
CONFIG_REGULATOR_FIXED_VOLTAGE=y
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
# CONFIG_REGULATOR_NETLINK_EVENTS is not set
# CONFIG_REGULATOR_88PG86X is not set
# CONFIG_REGULATOR_ACT8865 is not set
# CONFIG_REGULATOR_AD5398 is not set
# CONFIG_REGULATOR_ADP5055 is not set
# CONFIG_REGULATOR_AW37503 is not set
# CONFIG_REGULATOR_DA9121 is not set
# CONFIG_REGULATOR_DA9210 is not set
# CONFIG_REGULATOR_DA9211 is not set
# CONFIG_REGULATOR_FAN53555 is not set
# CONFIG_REGULATOR_FAN53880 is not set
# CONFIG_REGULATOR_GPIO is not set
# CONFIG_REGULATOR_ISL9305 is not set
# CONFIG_REGULATOR_ISL6271A is not set
# CONFIG_REGULATOR_FP9931 is not set
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_REGULATOR_LP3972 is not set
# CONFIG_REGULATOR_LP872X is not set
# CONFIG_REGULATOR_LP8755 is not set
# CONFIG_REGULATOR_LTC3589 is not set
# CONFIG_REGULATOR_LTC3676 is not set
# CONFIG_REGULATOR_MAX1586 is not set
# CONFIG_REGULATOR_MAX77503 is not set
# CONFIG_REGULATOR_MAX77675 is not set
# CONFIG_REGULATOR_MAX77857 is not set
# CONFIG_REGULATOR_MAX8649 is not set
# CONFIG_REGULATOR_MAX8660 is not set
# CONFIG_REGULATOR_MAX8893 is not set
# CONFIG_REGULATOR_MAX8952 is not set
# CONFIG_REGULATOR_MAX20086 is not set
# CONFIG_REGULATOR_MAX20411 is not set
# CONFIG_REGULATOR_MAX77826 is not set
# CONFIG_REGULATOR_MAX77838 is not set
# CONFIG_REGULATOR_MCP16502 is not set
# CONFIG_REGULATOR_MP5416 is not set
# CONFIG_REGULATOR_MP8859 is not set
# CONFIG_REGULATOR_MP886X is not set
# CONFIG_REGULATOR_MPQ7920 is not set
# CONFIG_REGULATOR_MT6311 is not set
# CONFIG_REGULATOR_MT6360 is not set
# CONFIG_REGULATOR_MT6370 is not set
# CONFIG_REGULATOR_PCA9450 is not set
# CONFIG_REGULATOR_PF9453 is not set
# CONFIG_REGULATOR_PF0900 is not set
# CONFIG_REGULATOR_PF530X is not set
# CONFIG_REGULATOR_PF8X00 is not set
# CONFIG_REGULATOR_PFUZE100 is not set
# CONFIG_REGULATOR_PV88060 is not set
# CONFIG_REGULATOR_PV88080 is not set
# CONFIG_REGULATOR_PV88090 is not set
# CONFIG_REGULATOR_RAA215300 is not set
# CONFIG_REGULATOR_RT4801 is not set
# CONFIG_REGULATOR_RT4803 is not set
# CONFIG_REGULATOR_RT5133 is not set
# CONFIG_REGULATOR_RT5190A is not set
# CONFIG_REGULATOR_RT5739 is not set
# CONFIG_REGULATOR_RT5759 is not set
# CONFIG_REGULATOR_RT6160 is not set
# CONFIG_REGULATOR_RT6190 is not set
# CONFIG_REGULATOR_RT6245 is not set
# CONFIG_REGULATOR_RT8092 is not set
# CONFIG_REGULATOR_RTQ2134 is not set
# CONFIG_REGULATOR_RTMV20 is not set
# CONFIG_REGULATOR_RTQ6752 is not set
# CONFIG_REGULATOR_RTQ2208 is not set
# CONFIG_REGULATOR_SGM3804 is not set
# CONFIG_REGULATOR_SLG51000 is not set
# CONFIG_REGULATOR_SY8106A is not set
# CONFIG_REGULATOR_SY8824X is not set
# CONFIG_REGULATOR_SY8827N is not set
# CONFIG_REGULATOR_TPS51632 is not set
# CONFIG_REGULATOR_TPS62360 is not set
# CONFIG_REGULATOR_TPS6286X is not set
# CONFIG_REGULATOR_TPS6287X is not set
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set
# CONFIG_REGULATOR_TPS65132 is not set
# CONFIG_REGULATOR_TPS65185 is not set
# CONFIG_REGULATOR_TPS6524X is not set
CONFIG_REGULATOR_TWL4030=y
# CONFIG_REGULATOR_VCTRL is not set
CONFIG_RC_CORE=y
# CONFIG_LIRC is not set
# CONFIG_RC_MAP is not set
# CONFIG_RC_DECODERS is not set
CONFIG_RC_DEVICES=y
# CONFIG_IR_ENE is not set
# CONFIG_IR_FINTEK is not set
# CONFIG_IR_GPIO_CIR is not set
# CONFIG_IR_HIX5HD2 is not set
CONFIG_IR_IGORPLUGUSB=y
CONFIG_IR_IGUANA=y
CONFIG_IR_IMON=y
CONFIG_IR_IMON_RAW=y
# CONFIG_IR_ITE_CIR is not set
CONFIG_IR_MCEUSB=y
# CONFIG_IR_NUVOTON is not set
CONFIG_IR_REDRAT3=y
# CONFIG_IR_SERIAL is not set
CONFIG_IR_STREAMZAP=y
CONFIG_IR_TOY=y
CONFIG_IR_TTUSBIR=y
# CONFIG_IR_WINBOND_CIR is not set
CONFIG_RC_ATI_REMOTE=y
# CONFIG_RC_LOOPBACK is not set
CONFIG_RC_XBOX_DVD=y
CONFIG_CEC_CORE=y

#
# CEC support
#
# CONFIG_MEDIA_CEC_RC is not set
CONFIG_MEDIA_CEC_SUPPORT=y
# CONFIG_CEC_CH7322 is not set
# CONFIG_CEC_NXP_TDA9950 is not set
# CONFIG_CEC_GPIO is not set
# CONFIG_CEC_SECO is not set
# CONFIG_USB_EXTRON_DA_HD_4K_PLUS_CEC is not set
CONFIG_USB_PULSE8_CEC=y
CONFIG_USB_RAINSHADOW_CEC=y
# end of CEC support

CONFIG_MEDIA_SUPPORT=y
CONFIG_MEDIA_SUPPORT_FILTER=y
# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set

#
# Media device types
#
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y
CONFIG_MEDIA_RADIO_SUPPORT=y
CONFIG_MEDIA_SDR_SUPPORT=y
CONFIG_MEDIA_PLATFORM_SUPPORT=y
CONFIG_MEDIA_TEST_SUPPORT=y
# end of Media device types

CONFIG_VIDEO_DEV=y
CONFIG_MEDIA_CONTROLLER=y
CONFIG_DVB_CORE=y

#
# Video4Linux options
#
CONFIG_VIDEO_V4L2_I2C=y
CONFIG_VIDEO_V4L2_SUBDEV_API=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_TUNER=y
CONFIG_V4L2_MEM2MEM_DEV=y
# end of Video4Linux options

#
# Media controller options
#
CONFIG_MEDIA_CONTROLLER_DVB=y
# end of Media controller options

#
# Digital TV options
#
# CONFIG_DVB_MMAP is not set
# CONFIG_DVB_NET is not set
CONFIG_DVB_MAX_ADAPTERS=16
# CONFIG_DVB_DYNAMIC_MINORS is not set
# CONFIG_DVB_DEMUX_SECTION_LOSS_LOG is not set
# CONFIG_DVB_ULE_DEBUG is not set
# end of Digital TV options

#
# Media drivers
#

#
# Drivers filtered as selected at 'Filter media drivers'
#

#
# Media drivers
#
CONFIG_MEDIA_USB_SUPPORT=y

#
# Webcam devices
#
CONFIG_USB_GSPCA=y
CONFIG_USB_GSPCA_BENQ=y
CONFIG_USB_GSPCA_CONEX=y
CONFIG_USB_GSPCA_CPIA1=y
CONFIG_USB_GSPCA_DTCS033=y
CONFIG_USB_GSPCA_ETOMS=y
CONFIG_USB_GSPCA_FINEPIX=y
CONFIG_USB_GSPCA_JEILINJ=y
CONFIG_USB_GSPCA_JL2005BCD=y
CONFIG_USB_GSPCA_KINECT=y
CONFIG_USB_GSPCA_KONICA=y
CONFIG_USB_GSPCA_MARS=y
CONFIG_USB_GSPCA_MR97310A=y
CONFIG_USB_GSPCA_NW80X=y
CONFIG_USB_GSPCA_OV519=y
CONFIG_USB_GSPCA_OV534=y
CONFIG_USB_GSPCA_OV534_9=y
CONFIG_USB_GSPCA_PAC207=y
CONFIG_USB_GSPCA_PAC7302=y
CONFIG_USB_GSPCA_PAC7311=y
CONFIG_USB_GSPCA_SE401=y
CONFIG_USB_GSPCA_SN9C2028=y
CONFIG_USB_GSPCA_SN9C20X=y
CONFIG_USB_GSPCA_SONIXB=y
CONFIG_USB_GSPCA_SONIXJ=y
CONFIG_USB_GSPCA_SPCA1528=y
CONFIG_USB_GSPCA_SPCA500=y
CONFIG_USB_GSPCA_SPCA501=y
CONFIG_USB_GSPCA_SPCA505=y
CONFIG_USB_GSPCA_SPCA506=y
CONFIG_USB_GSPCA_SPCA508=y
CONFIG_USB_GSPCA_SPCA561=y
CONFIG_USB_GSPCA_SQ905=y
CONFIG_USB_GSPCA_SQ905C=y
CONFIG_USB_GSPCA_SQ930X=y
CONFIG_USB_GSPCA_STK014=y
CONFIG_USB_GSPCA_STK1135=y
CONFIG_USB_GSPCA_STV0680=y
CONFIG_USB_GSPCA_SUNPLUS=y
CONFIG_USB_GSPCA_T613=y
CONFIG_USB_GSPCA_TOPRO=y
CONFIG_USB_GSPCA_TOUPTEK=y
CONFIG_USB_GSPCA_TV8532=y
CONFIG_USB_GSPCA_VC032X=y
CONFIG_USB_GSPCA_VICAM=y
CONFIG_USB_GSPCA_XIRLINK_CIT=y
CONFIG_USB_GSPCA_ZC3XX=y
CONFIG_USB_GL860=y
CONFIG_USB_M5602=y
CONFIG_USB_STV06XX=y
CONFIG_USB_PWC=y
# CONFIG_USB_PWC_DEBUG is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
CONFIG_USB_S2255=y
CONFIG_VIDEO_USBTV=y
CONFIG_USB_VIDEO_CLASS=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y

#
# Analog TV USB devices
#
CONFIG_VIDEO_GO7007=y
CONFIG_VIDEO_GO7007_USB=y
CONFIG_VIDEO_GO7007_LOADER=y
CONFIG_VIDEO_GO7007_USB_S2250_BOARD=y
CONFIG_VIDEO_HDPVR=y
CONFIG_VIDEO_PVRUSB2=y
CONFIG_VIDEO_PVRUSB2_SYSFS=y
CONFIG_VIDEO_PVRUSB2_DVB=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_STK1160=y

#
# Analog/digital TV USB devices
#
CONFIG_VIDEO_AU0828=y
CONFIG_VIDEO_AU0828_V4L2=y
CONFIG_VIDEO_AU0828_RC=y
CONFIG_VIDEO_CX231XX=y
CONFIG_VIDEO_CX231XX_RC=y
CONFIG_VIDEO_CX231XX_ALSA=y
CONFIG_VIDEO_CX231XX_DVB=y

#
# Digital TV USB devices
#
CONFIG_DVB_AS102=y
CONFIG_DVB_B2C2_FLEXCOP_USB=y
# CONFIG_DVB_B2C2_FLEXCOP_USB_DEBUG is not set
CONFIG_DVB_USB_V2=y
CONFIG_DVB_USB_AF9015=y
CONFIG_DVB_USB_AF9035=y
CONFIG_DVB_USB_ANYSEE=y
CONFIG_DVB_USB_AU6610=y
CONFIG_DVB_USB_AZ6007=y
CONFIG_DVB_USB_CE6230=y
CONFIG_DVB_USB_DVBSKY=y
CONFIG_DVB_USB_EC168=y
CONFIG_DVB_USB_GL861=y
CONFIG_DVB_USB_LME2510=y
CONFIG_DVB_USB_MXL111SF=y
CONFIG_DVB_USB_RTL28XXU=y
CONFIG_DVB_USB_ZD1301=y
CONFIG_DVB_USB=y
# CONFIG_DVB_USB_DEBUG is not set
CONFIG_DVB_USB_A800=y
CONFIG_DVB_USB_AF9005=y
CONFIG_DVB_USB_AF9005_REMOTE=y
CONFIG_DVB_USB_AZ6027=y
CONFIG_DVB_USB_CINERGY_T2=y
CONFIG_DVB_USB_CXUSB=y
CONFIG_DVB_USB_CXUSB_ANALOG=y
CONFIG_DVB_USB_DIB0700=y
CONFIG_DVB_USB_DIB3000MC=y
CONFIG_DVB_USB_DIBUSB_MB=y
# CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set
CONFIG_DVB_USB_DIBUSB_MC=y
CONFIG_DVB_USB_DIGITV=y
CONFIG_DVB_USB_DTT200U=y
CONFIG_DVB_USB_DTV5100=y
CONFIG_DVB_USB_DW2102=y
CONFIG_DVB_USB_GP8PSK=y
CONFIG_DVB_USB_M920X=y
CONFIG_DVB_USB_NOVA_T_USB2=y
CONFIG_DVB_USB_OPERA1=y
CONFIG_DVB_USB_PCTV452E=y
CONFIG_DVB_USB_TECHNISAT_USB2=y
CONFIG_DVB_USB_TTUSB2=y
CONFIG_DVB_USB_UMT_010=y
CONFIG_DVB_USB_VP702X=y
CONFIG_DVB_USB_VP7045=y
CONFIG_SMS_USB_DRV=y
CONFIG_DVB_TTUSB_BUDGET=y
CONFIG_DVB_TTUSB_DEC=y

#
# Webcam, TV (analog/digital) USB devices
#
CONFIG_VIDEO_EM28XX=y
CONFIG_VIDEO_EM28XX_V4L2=y
CONFIG_VIDEO_EM28XX_ALSA=y
CONFIG_VIDEO_EM28XX_DVB=y
CONFIG_VIDEO_EM28XX_RC=y

#
# Software defined radio USB devices
#
CONFIG_USB_AIRSPY=y
CONFIG_USB_HACKRF=y
CONFIG_USB_MSI2500=y
# CONFIG_MEDIA_PCI_SUPPORT is not set
CONFIG_RADIO_ADAPTERS=y
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_SAA7706H is not set
CONFIG_RADIO_SHARK=y
CONFIG_RADIO_SHARK2=y
CONFIG_RADIO_SI4713=y
CONFIG_RADIO_TEA575X=y
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_RADIO_TEF6862 is not set
CONFIG_USB_DSBR=y
CONFIG_USB_KEENE=y
CONFIG_USB_MA901=y
CONFIG_USB_MR800=y
CONFIG_USB_RAREMONO=y
CONFIG_RADIO_SI470X=y
CONFIG_USB_SI470X=y
# CONFIG_I2C_SI470X is not set
CONFIG_USB_SI4713=y
# CONFIG_PLATFORM_SI4713 is not set
CONFIG_I2C_SI4713=y
# CONFIG_MEDIA_PLATFORM_DRIVERS is not set

#
# MMC/SDIO DVB adapters
#
CONFIG_SMS_SDIO_DRV=y
CONFIG_V4L_TEST_DRIVERS=y
CONFIG_VIDEO_VIM2M=y
CONFIG_VIDEO_VICODEC=y
CONFIG_VIDEO_VIMC=y
CONFIG_VIDEO_VIVID=y
CONFIG_VIDEO_VIVID_CEC=y
# CONFIG_VIDEO_VIVID_OSD is not set
CONFIG_VIDEO_VIVID_MAX_DEVS=64
# CONFIG_VIDEO_VISL is not set
CONFIG_DVB_TEST_DRIVERS=y
CONFIG_DVB_VIDTV=y

#
# FireWire (IEEE 1394) Adapters
#
# CONFIG_DVB_FIREDTV is not set
CONFIG_MEDIA_COMMON_OPTIONS=y

#
# common driver options
#
CONFIG_CYPRESS_FIRMWARE=y
CONFIG_TTPCI_EEPROM=y
CONFIG_UVC_COMMON=y
CONFIG_VIDEO_CX2341X=y
CONFIG_VIDEO_TVEEPROM=y
CONFIG_DVB_B2C2_FLEXCOP=y
CONFIG_SMS_SIANO_MDTV=y
CONFIG_SMS_SIANO_RC=y
CONFIG_SMS_SIANO_DEBUGFS=y
CONFIG_VIDEO_V4L2_TPG=y
CONFIG_VIDEOBUF2_CORE=y
CONFIG_VIDEOBUF2_V4L2=y
CONFIG_VIDEOBUF2_MEMOPS=y
CONFIG_VIDEOBUF2_DMA_CONTIG=y
CONFIG_VIDEOBUF2_VMALLOC=y
CONFIG_VIDEOBUF2_DMA_SG=y
# end of Media drivers

#
# Media ancillary drivers
#
CONFIG_MEDIA_ATTACH=y
# CONFIG_VIDEO_IR_I2C is not set
# CONFIG_VIDEO_CAMERA_SENSOR is not set

#
# Camera ISPs
#
# CONFIG_VIDEO_THP7312 is not set
# end of Camera ISPs

# CONFIG_VIDEO_CAMERA_LENS is not set

#
# Flash devices
#
# CONFIG_VIDEO_ADP1653 is not set
# CONFIG_VIDEO_LM3560 is not set
# CONFIG_VIDEO_LM3646 is not set
# end of Flash devices

#
# Audio decoders, processors and mixers
#
# CONFIG_VIDEO_CS3308 is not set
# CONFIG_VIDEO_CS5345 is not set
CONFIG_VIDEO_CS53L32A=y
CONFIG_VIDEO_MSP3400=y
# CONFIG_VIDEO_SONY_BTF_MPX is not set
# CONFIG_VIDEO_TDA1997X is not set
# CONFIG_VIDEO_TDA7432 is not set
# CONFIG_VIDEO_TDA9840 is not set
# CONFIG_VIDEO_TEA6415C is not set
# CONFIG_VIDEO_TEA6420 is not set
# CONFIG_VIDEO_TLV320AIC23B is not set
# CONFIG_VIDEO_TVAUDIO is not set
# CONFIG_VIDEO_UDA1342 is not set
# CONFIG_VIDEO_VP27SMPX is not set
# CONFIG_VIDEO_WM8739 is not set
CONFIG_VIDEO_WM8775=y
# end of Audio decoders, processors and mixers

#
# RDS decoders
#
# CONFIG_VIDEO_SAA6588 is not set
# end of RDS decoders

#
# Video decoders
#
# CONFIG_VIDEO_ADV7180 is not set
# CONFIG_VIDEO_ADV7183 is not set
# CONFIG_VIDEO_ADV748X is not set
# CONFIG_VIDEO_ADV7604 is not set
# CONFIG_VIDEO_ADV7842 is not set
# CONFIG_VIDEO_BT819 is not set
# CONFIG_VIDEO_BT856 is not set
# CONFIG_VIDEO_BT866 is not set
# CONFIG_VIDEO_ISL7998X is not set
# CONFIG_VIDEO_LT6911UXE is not set
# CONFIG_VIDEO_KS0127 is not set
# CONFIG_VIDEO_MAX9286 is not set
# CONFIG_VIDEO_ML86V7667 is not set
# CONFIG_VIDEO_SAA7110 is not set
CONFIG_VIDEO_SAA711X=y
# CONFIG_VIDEO_TC358743 is not set
# CONFIG_VIDEO_TC358746 is not set
# CONFIG_VIDEO_TVP514X is not set
# CONFIG_VIDEO_TVP5150 is not set
# CONFIG_VIDEO_TVP7002 is not set
# CONFIG_VIDEO_TW2804 is not set
# CONFIG_VIDEO_TW9900 is not set
# CONFIG_VIDEO_TW9903 is not set
# CONFIG_VIDEO_TW9906 is not set
# CONFIG_VIDEO_TW9910 is not set
# CONFIG_VIDEO_VPX3220 is not set

#
# Video and audio decoders
#
# CONFIG_VIDEO_SAA717X is not set
CONFIG_VIDEO_CX25840=y
# end of Video decoders

#
# Video encoders
#
# CONFIG_VIDEO_ADV7170 is not set
# CONFIG_VIDEO_ADV7175 is not set
# CONFIG_VIDEO_ADV7343 is not set
# CONFIG_VIDEO_ADV7393 is not set
# CONFIG_VIDEO_ADV7511 is not set
# CONFIG_VIDEO_AK881X is not set
# CONFIG_VIDEO_SAA7127 is not set
# CONFIG_VIDEO_SAA7185 is not set
# CONFIG_VIDEO_THS8200 is not set
# end of Video encoders

#
# Video improvement chips
#
# CONFIG_VIDEO_UPD64031A is not set
# CONFIG_VIDEO_UPD64083 is not set
# end of Video improvement chips

#
# Audio/Video compression chips
#
# CONFIG_VIDEO_SAA6752HS is not set
# end of Audio/Video compression chips

#
# SDR tuner chips
#
# CONFIG_SDR_MAX2175 is not set
# end of SDR tuner chips

#
# Miscellaneous helper chips
#
# CONFIG_VIDEO_INTEL_CVS is not set
# CONFIG_VIDEO_I2C is not set
# CONFIG_VIDEO_M52790 is not set
# CONFIG_VIDEO_ST_MIPID02 is not set
# CONFIG_VIDEO_THS7303 is not set
# end of Miscellaneous helper chips

#
# Video serializers and deserializers
#
# CONFIG_VIDEO_DS90UB913 is not set
# CONFIG_VIDEO_DS90UB953 is not set
# CONFIG_VIDEO_DS90UB960 is not set
# CONFIG_VIDEO_MAX96714 is not set
# CONFIG_VIDEO_MAX96717 is not set
# end of Video serializers and deserializers

#
# Media SPI Adapters
#
# CONFIG_CXD2880_SPI_DRV is not set
# CONFIG_VIDEO_GS1662 is not set
# end of Media SPI Adapters

CONFIG_MEDIA_TUNER=y

#
# Customize TV tuners
#
# CONFIG_MEDIA_TUNER_E4000 is not set
# CONFIG_MEDIA_TUNER_FC0011 is not set
# CONFIG_MEDIA_TUNER_FC0012 is not set
# CONFIG_MEDIA_TUNER_FC0013 is not set
# CONFIG_MEDIA_TUNER_FC2580 is not set
# CONFIG_MEDIA_TUNER_IT913X is not set
# CONFIG_MEDIA_TUNER_M88RS6000T is not set
# CONFIG_MEDIA_TUNER_MAX2165 is not set
# CONFIG_MEDIA_TUNER_MC44S803 is not set
CONFIG_MEDIA_TUNER_MSI001=y
# CONFIG_MEDIA_TUNER_MT2060 is not set
# CONFIG_MEDIA_TUNER_MT2063 is not set
# CONFIG_MEDIA_TUNER_MT20XX is not set
# CONFIG_MEDIA_TUNER_MT2131 is not set
# CONFIG_MEDIA_TUNER_MT2266 is not set
# CONFIG_MEDIA_TUNER_MXL301RF is not set
# CONFIG_MEDIA_TUNER_MXL5005S is not set
# CONFIG_MEDIA_TUNER_MXL5007T is not set
# CONFIG_MEDIA_TUNER_QM1D1B0004 is not set
# CONFIG_MEDIA_TUNER_QM1D1C0042 is not set
# CONFIG_MEDIA_TUNER_QT1010 is not set
# CONFIG_MEDIA_TUNER_R820T is not set
# CONFIG_MEDIA_TUNER_SI2157 is not set
# CONFIG_MEDIA_TUNER_SIMPLE is not set
# CONFIG_MEDIA_TUNER_TDA18212 is not set
# CONFIG_MEDIA_TUNER_TDA18218 is not set
# CONFIG_MEDIA_TUNER_TDA18250 is not set
# CONFIG_MEDIA_TUNER_TDA18271 is not set
# CONFIG_MEDIA_TUNER_TDA827X is not set
# CONFIG_MEDIA_TUNER_TDA8290 is not set
# CONFIG_MEDIA_TUNER_TDA9887 is not set
# CONFIG_MEDIA_TUNER_TEA5761 is not set
# CONFIG_MEDIA_TUNER_TEA5767 is not set
# CONFIG_MEDIA_TUNER_TUA9001 is not set
# CONFIG_MEDIA_TUNER_XC2028 is not set
# CONFIG_MEDIA_TUNER_XC4000 is not set
# CONFIG_MEDIA_TUNER_XC5000 is not set
# end of Customize TV tuners

#
# Customise DVB Frontends
#

#
# Multistandard (satellite) frontends
#
# CONFIG_DVB_M88DS3103 is not set
# CONFIG_DVB_MXL5XX is not set
# CONFIG_DVB_STB0899 is not set
# CONFIG_DVB_STB6100 is not set
# CONFIG_DVB_STV090x is not set
# CONFIG_DVB_STV0910 is not set
# CONFIG_DVB_STV6110x is not set
# CONFIG_DVB_STV6111 is not set

#
# Multistandard (cable + terrestrial) frontends
#
# CONFIG_DVB_DRXK is not set
# CONFIG_DVB_MN88472 is not set
# CONFIG_DVB_MN88473 is not set
# CONFIG_DVB_SI2165 is not set
# CONFIG_DVB_TDA18271C2DD is not set

#
# DVB-S (satellite) frontends
#
# CONFIG_DVB_CX24110 is not set
# CONFIG_DVB_CX24116 is not set
# CONFIG_DVB_CX24117 is not set
# CONFIG_DVB_CX24120 is not set
# CONFIG_DVB_CX24123 is not set
# CONFIG_DVB_DS3000 is not set
# CONFIG_DVB_MB86A16 is not set
# CONFIG_DVB_MT312 is not set
# CONFIG_DVB_S5H1420 is not set
# CONFIG_DVB_SI21XX is not set
# CONFIG_DVB_STB6000 is not set
# CONFIG_DVB_STV0288 is not set
# CONFIG_DVB_STV0299 is not set
# CONFIG_DVB_STV0900 is not set
# CONFIG_DVB_STV6110 is not set
# CONFIG_DVB_TDA10071 is not set
# CONFIG_DVB_TDA10086 is not set
# CONFIG_DVB_TDA8083 is not set
# CONFIG_DVB_TDA8261 is not set
# CONFIG_DVB_TDA826X is not set
# CONFIG_DVB_TS2020 is not set
# CONFIG_DVB_TUA6100 is not set
# CONFIG_DVB_TUNER_CX24113 is not set
# CONFIG_DVB_TUNER_ITD1000 is not set
# CONFIG_DVB_VES1X93 is not set
# CONFIG_DVB_ZL10036 is not set
# CONFIG_DVB_ZL10039 is not set

#
# DVB-T (terrestrial) frontends
#
CONFIG_DVB_AF9013=y
CONFIG_DVB_AS102_FE=y
# CONFIG_DVB_CX22700 is not set
# CONFIG_DVB_CX22702 is not set
# CONFIG_DVB_CXD2820R is not set
# CONFIG_DVB_CXD2841ER is not set
CONFIG_DVB_DIB3000MB=y
CONFIG_DVB_DIB3000MC=y
# CONFIG_DVB_DIB7000M is not set
# CONFIG_DVB_DIB7000P is not set
# CONFIG_DVB_DIB9000 is not set
# CONFIG_DVB_DRXD is not set
CONFIG_DVB_EC100=y
CONFIG_DVB_GP8PSK_FE=y
# CONFIG_DVB_L64781 is not set
# CONFIG_DVB_MT352 is not set
# CONFIG_DVB_NXT6000 is not set
CONFIG_DVB_RTL2830=y
CONFIG_DVB_RTL2832=y
CONFIG_DVB_RTL2832_SDR=y
# CONFIG_DVB_S5H1432 is not set
# CONFIG_DVB_SI2168 is not set
# CONFIG_DVB_SP887X is not set
# CONFIG_DVB_STV0367 is not set
# CONFIG_DVB_TDA10048 is not set
# CONFIG_DVB_TDA1004X is not set
# CONFIG_DVB_ZD1301_DEMOD is not set
CONFIG_DVB_ZL10353=y
# CONFIG_DVB_CXD2880 is not set

#
# DVB-C (cable) frontends
#
# CONFIG_DVB_STV0297 is not set
# CONFIG_DVB_TDA10021 is not set
# CONFIG_DVB_TDA10023 is not set
# CONFIG_DVB_VES1820 is not set

#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends
#
# CONFIG_DVB_AU8522_DTV is not set
# CONFIG_DVB_AU8522_V4L is not set
# CONFIG_DVB_BCM3510 is not set
# CONFIG_DVB_LG2160 is not set
# CONFIG_DVB_LGDT3305 is not set
# CONFIG_DVB_LGDT3306A is not set
# CONFIG_DVB_LGDT330X is not set
# CONFIG_DVB_MXL692 is not set
# CONFIG_DVB_NXT200X is not set
# CONFIG_DVB_OR51132 is not set
# CONFIG_DVB_OR51211 is not set
# CONFIG_DVB_S5H1409 is not set
# CONFIG_DVB_S5H1411 is not set

#
# ISDB-T (terrestrial) frontends
#
# CONFIG_DVB_DIB8000 is not set
# CONFIG_DVB_MB86A20S is not set
# CONFIG_DVB_S921 is not set

#
# ISDB-S (satellite) & ISDB-T (terrestrial) frontends
#
# CONFIG_DVB_MN88443X is not set
# CONFIG_DVB_TC90522 is not set

#
# Digital terrestrial only tuners/PLL
#
# CONFIG_DVB_PLL is not set
# CONFIG_DVB_TUNER_DIB0070 is not set
# CONFIG_DVB_TUNER_DIB0090 is not set

#
# SEC control devices for DVB-S
#
# CONFIG_DVB_A8293 is not set
CONFIG_DVB_AF9033=y
# CONFIG_DVB_ASCOT2E is not set
# CONFIG_DVB_ATBM8830 is not set
# CONFIG_DVB_HELENE is not set
# CONFIG_DVB_HORUS3A is not set
# CONFIG_DVB_ISL6405 is not set
# CONFIG_DVB_ISL6421 is not set
# CONFIG_DVB_ISL6423 is not set
# CONFIG_DVB_IX2505V is not set
# CONFIG_DVB_LGS8GL5 is not set
# CONFIG_DVB_LGS8GXX is not set
# CONFIG_DVB_LNBH25 is not set
# CONFIG_DVB_LNBH29 is not set
# CONFIG_DVB_LNBP21 is not set
# CONFIG_DVB_LNBP22 is not set
# CONFIG_DVB_M88RS2000 is not set
# CONFIG_DVB_TDA665x is not set
# CONFIG_DVB_DRX39XYJ is not set

#
# Common Interface (EN50221) controller drivers
#
# CONFIG_DVB_CXD2099 is not set
# CONFIG_DVB_SP2 is not set
# end of Customise DVB Frontends

#
# Tools to develop new frontends
#
# CONFIG_DVB_DUMMY_FE is not set
# end of Media ancillary drivers

#
# Graphics support
#
CONFIG_APERTURE_HELPERS=y
CONFIG_SCREEN_INFO=y
CONFIG_VIDEO=y
# CONFIG_AUXDISPLAY is not set
# CONFIG_PANEL is not set
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
CONFIG_INTEL_GTT=y
# CONFIG_VGA_SWITCHEROO is not set
CONFIG_DRM=y

#
# DRM debugging options
#
# CONFIG_DRM_WERROR is not set
CONFIG_DRM_DEBUG_MM=y
# end of DRM debugging options

CONFIG_DRM_KMS_HELPER=y
# CONFIG_DRM_PANIC is not set
# CONFIG_DRM_RAS is not set
# CONFIG_DRM_DEBUG_DP_MST_TOPOLOGY_REFS is not set
# CONFIG_DRM_DEBUG_MODESET_LOCK is not set
CONFIG_DRM_CLIENT=y
CONFIG_DRM_CLIENT_LIB=y
CONFIG_DRM_CLIENT_SELECTION=y
CONFIG_DRM_CLIENT_SETUP=y

#
# Supported DRM clients
#
CONFIG_DRM_FBDEV_EMULATION=y
CONFIG_DRM_FBDEV_OVERALLOC=100
# CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM is not set
# CONFIG_DRM_CLIENT_LOG is not set
CONFIG_DRM_CLIENT_DEFAULT_FBDEV=y
CONFIG_DRM_CLIENT_DEFAULT="fbdev"
# end of Supported DRM clients

# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
CONFIG_DRM_DISPLAY_DP_AUX_BUS=y
CONFIG_DRM_DISPLAY_HELPER=y
# CONFIG_DRM_DISPLAY_DP_AUX_CEC is not set
# CONFIG_DRM_DISPLAY_DP_AUX_CHARDEV is not set
CONFIG_DRM_DISPLAY_DP_HELPER=y
CONFIG_DRM_TTM=y
CONFIG_DRM_TTM_HELPER=y
CONFIG_DRM_GEM_SHMEM_HELPER=y
# CONFIG_DRM_AMDGPU is not set

#
# ARM devices
#
# CONFIG_DRM_KOMEDA is not set
# end of ARM devices

# CONFIG_DRM_AST is not set
CONFIG_DRM_BRIDGE=y
CONFIG_DRM_PANEL_BRIDGE=y
CONFIG_DRM_AUX_BRIDGE=y
CONFIG_DRM_AUX_HPD_BRIDGE=y

#
# Display Interface Bridges
#
# CONFIG_DRM_CHIPONE_ICN6211 is not set
# CONFIG_DRM_CHRONTEL_CH7033 is not set
# CONFIG_DRM_DISPLAY_CONNECTOR is not set
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_ITE_IT6263 is not set
# CONFIG_DRM_ITE_IT6505 is not set
# CONFIG_DRM_LONTIUM_LT8912B is not set
# CONFIG_DRM_LONTIUM_LT9211 is not set
# CONFIG_DRM_LONTIUM_LT9611 is not set
# CONFIG_DRM_LONTIUM_LT9611UXC is not set
# CONFIG_DRM_LONTIUM_LT8713SX is not set
# CONFIG_DRM_ITE_IT66121 is not set
# CONFIG_DRM_LVDS_CODEC is not set
# CONFIG_DRM_MEGACHIPS_STDPXXXX_GE_B850V3_FW is not set
# CONFIG_DRM_NWL_MIPI_DSI is not set
# CONFIG_DRM_NXP_PTN3460 is not set
# CONFIG_DRM_PARADE_PS8622 is not set
# CONFIG_DRM_PARADE_PS8640 is not set
# CONFIG_DRM_SAMSUNG_DSIM is not set
# CONFIG_DRM_SIL_SII8620 is not set
# CONFIG_DRM_SII902X is not set
# CONFIG_DRM_SII9234 is not set
# CONFIG_DRM_SIMPLE_BRIDGE is not set
# CONFIG_DRM_SOLOMON_SSD2825 is not set
# CONFIG_DRM_THINE_THC63LVD1024 is not set
# CONFIG_DRM_TOSHIBA_TC358762 is not set
# CONFIG_DRM_TOSHIBA_TC358764 is not set
# CONFIG_DRM_TOSHIBA_TC358767 is not set
# CONFIG_DRM_TOSHIBA_TC358768 is not set
# CONFIG_DRM_TOSHIBA_TC358775 is not set
# CONFIG_DRM_TI_DLPC3433 is not set
# CONFIG_DRM_TI_TDP158 is not set
# CONFIG_DRM_TI_TFP410 is not set
# CONFIG_DRM_TI_SN65DSI83 is not set
# CONFIG_DRM_TI_SN65DSI86 is not set
# CONFIG_DRM_TI_TPD12S015 is not set
# CONFIG_DRM_WAVESHARE_BRIDGE is not set
# CONFIG_DRM_ANALOGIX_ANX6345 is not set
# CONFIG_DRM_ANALOGIX_ANX78XX is not set
# CONFIG_DRM_ANALOGIX_ANX7625 is not set
# CONFIG_DRM_I2C_ADV7511 is not set
# CONFIG_DRM_CDNS_DSI is not set
# CONFIG_DRM_CDNS_MHDP8546 is not set
# end of Display Interface Bridges

# CONFIG_DRM_ETNAVIV is not set
# CONFIG_DRM_GMA500 is not set
CONFIG_DRM_GUD=y
# CONFIG_DRM_HISI_HIBMC is not set
# CONFIG_DRM_LOGICVC is not set
# CONFIG_DRM_MGAG200 is not set
# CONFIG_DRM_NOUVEAU is not set
CONFIG_DRM_PANEL=y

#
# Display Panels
#
# CONFIG_DRM_PANEL_ABT_Y030XX067A is not set
# CONFIG_DRM_PANEL_ARM_VERSATILE is not set
# CONFIG_DRM_PANEL_AUO_A030JTN01 is not set
# CONFIG_DRM_PANEL_LVDS is not set
# CONFIG_DRM_PANEL_ILITEK_IL9322 is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9341 is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9806E_SPI is not set
# CONFIG_DRM_PANEL_INNOLUX_EJ030NA is not set
# CONFIG_DRM_PANEL_LG_LB035Q02 is not set
# CONFIG_DRM_PANEL_LG_LG4573 is not set
# CONFIG_DRM_PANEL_NEC_NL8048HL11 is not set
# CONFIG_DRM_PANEL_NEWVISION_NV3052C is not set
# CONFIG_DRM_PANEL_NOVATEK_NT39016 is not set
# CONFIG_DRM_PANEL_OLIMEX_LCD_OLINUXINO is not set
# CONFIG_DRM_PANEL_ORISETECH_OTA5601A is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E88A0_AMS452EF01 is not set
# CONFIG_DRM_PANEL_SAMSUNG_ATNA33XC20 is not set
# CONFIG_DRM_PANEL_SAMSUNG_DB7430 is not set
# CONFIG_DRM_PANEL_SAMSUNG_LD9040 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6D27A1 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6D7AA0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E63M0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E8AA0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E8FC0 is not set
# CONFIG_DRM_PANEL_SEIKO_43WVF1G is not set
# CONFIG_DRM_PANEL_SHARP_LS037V7DW01 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7701 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7789V is not set
# CONFIG_DRM_PANEL_SONY_ACX565AKM is not set
CONFIG_DRM_PANEL_EDP=y
# CONFIG_DRM_PANEL_SIMPLE is not set
# CONFIG_DRM_PANEL_TPO_TD028TTEC1 is not set
# CONFIG_DRM_PANEL_TPO_TD043MTEA1 is not set
# CONFIG_DRM_PANEL_TPO_TPG110 is not set
# CONFIG_DRM_PANEL_WIDECHIPS_WS2401 is not set
# end of Display Panels

# CONFIG_DRM_QXL is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_ST7571 is not set
# CONFIG_DRM_ST7586 is not set
# CONFIG_DRM_ST7735R is not set
# CONFIG_DRM_ST7920 is not set
# CONFIG_DRM_SSD130X is not set

#
# Drivers for system framebuffers
#
CONFIG_DRM_SYSFB_HELPER=y
CONFIG_DRM_SIMPLEDRM=y
# CONFIG_DRM_VESADRM is not set
# end of Drivers for system framebuffers

# CONFIG_DRM_APPLETBDRM is not set
# CONFIG_DRM_ARCPGU is not set
CONFIG_DRM_BOCHS=y
CONFIG_DRM_CIRRUS_QEMU=y
CONFIG_DRM_GM12U320=y
# CONFIG_DRM_PANEL_MIPI_DBI is not set
# CONFIG_DRM_PIXPAPER is not set
# CONFIG_TINYDRM_HX8357D is not set
# CONFIG_TINYDRM_ILI9163 is not set
# CONFIG_TINYDRM_ILI9225 is not set
# CONFIG_TINYDRM_ILI9341 is not set
# CONFIG_TINYDRM_ILI9486 is not set
# CONFIG_TINYDRM_MI0283QT is not set
# CONFIG_TINYDRM_REPAPER is not set
# CONFIG_TINYDRM_SHARP_MEMORY is not set
CONFIG_DRM_UDL=y
# CONFIG_DRM_VBOXVIDEO is not set
CONFIG_DRM_VGEM=y
CONFIG_DRM_VIRTIO_GPU=y
CONFIG_DRM_VIRTIO_GPU_KMS=y
# CONFIG_DRM_VKMS is not set
CONFIG_DRM_VMWGFX=y
# CONFIG_DRM_VMWGFX_MKSSTATS is not set
# CONFIG_DRM_XE is not set
CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y

#
# Frame buffer Devices
#
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=y
# CONFIG_FB_UVESA is not set
CONFIG_FB_VESA=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_OPENCORES is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I740 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_IBM_GXT4500 is not set
CONFIG_FB_VIRTUAL=y
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_SSD1307 is not set
# CONFIG_FB_SM712 is not set
CONFIG_FB_CORE=y
CONFIG_FB_NOTIFY=y
CONFIG_FB_DEVICE=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SYS_FILLRECT=y
CONFIG_FB_SYS_COPYAREA=y
CONFIG_FB_SYS_IMAGEBLIT=y
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYSMEM_FOPS=y
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_IOMEM_FOPS=y
CONFIG_FB_IOMEM_HELPERS=y
CONFIG_FB_SYSMEM_HELPERS=y
CONFIG_FB_SYSMEM_HELPERS_DEFERRED=y
CONFIG_FB_TILEBLITTING=y
# end of Frame buffer Devices

#
# Backlight & LCD device support
#
CONFIG_LCD_CLASS_DEVICE=y
# CONFIG_LCD_L4F00242T03 is not set
# CONFIG_LCD_LMS283GF05 is not set
# CONFIG_LCD_LTV350QV is not set
# CONFIG_LCD_ILI922X is not set
# CONFIG_LCD_ILI9320 is not set
# CONFIG_LCD_TDO24M is not set
# CONFIG_LCD_VGG2432A4 is not set
# CONFIG_LCD_PLATFORM is not set
# CONFIG_LCD_AMS369FG06 is not set
# CONFIG_LCD_LMS501KF03 is not set
# CONFIG_LCD_HX8357 is not set
# CONFIG_LCD_OTM3225A is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_AW99706 is not set
# CONFIG_BACKLIGHT_KTD253 is not set
# CONFIG_BACKLIGHT_KTD2801 is not set
# CONFIG_BACKLIGHT_KTZ8866 is not set
# CONFIG_BACKLIGHT_SY7758 is not set
# CONFIG_BACKLIGHT_MAX25014 is not set
# CONFIG_BACKLIGHT_MT6370 is not set
# CONFIG_BACKLIGHT_APPLE is not set
# CONFIG_BACKLIGHT_QCOM_WLED is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_LM3509 is not set
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_PANDORA is not set
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_BACKLIGHT_ARCXCNN is not set
# CONFIG_BACKLIGHT_LED is not set
# end of Backlight & LCD device support

CONFIG_VGASTATE=y
CONFIG_VIDEOMODE_HELPERS=y
CONFIG_HDMI=y
# CONFIG_FIRMWARE_EDID is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_DUMMY_CONSOLE_COLUMNS=80
CONFIG_DUMMY_CONSOLE_ROWS=25
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION is not set
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is not set
# end of Console display driver support

CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_MONO_FILE="drivers/video/logo/logo_linux_mono.pbm"
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_VGA16_FILE="drivers/video/logo/logo_linux_vga16.ppm"
# CONFIG_LOGO_LINUX_CLUT224 is not set
# CONFIG_TRACE_GPU_MEM is not set
# end of Graphics support

# CONFIG_DRM_ACCEL is not set
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=y
CONFIG_SND_SEQ_DEVICE=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_UMP=y
CONFIG_SND_UMP_LEGACY_RAWMIDI=y
CONFIG_SND_JACK=y
CONFIG_SND_JACK_INPUT_DEV=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_PCM_TIMER=y
CONFIG_SND_HRTIMER=y
# CONFIG_SND_DYNAMIC_MINORS is not set
# CONFIG_SND_SUPPORT_OLD_API is not set
CONFIG_SND_PROC_FS=y
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_CTL_FAST_LOOKUP=y
CONFIG_SND_DEBUG=y
# CONFIG_SND_DEBUG_VERBOSE is not set
CONFIG_SND_PCM_XRUN_DEBUG=y
# CONFIG_SND_CTL_INPUT_VALIDATION is not set
# CONFIG_SND_CTL_DEBUG is not set
# CONFIG_SND_JACK_INJECTION_DEBUG is not set
# CONFIG_SND_UTIMER is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_CTL_LED=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_SEQ_DUMMY=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_SEQ_MIDI_EVENT=y
CONFIG_SND_SEQ_MIDI=y
CONFIG_SND_SEQ_VIRMIDI=y
# CONFIG_SND_SEQ_UMP is not set
CONFIG_SND_DRIVERS=y
# CONFIG_SND_PCSP is not set
CONFIG_SND_DUMMY=y
CONFIG_SND_ALOOP=y
# CONFIG_SND_PCMTEST is not set
CONFIG_SND_VIRMIDI=y
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_SERIAL_GENERIC is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_PORTMAN2X4 is not set
CONFIG_SND_PCI=y
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ASIHPI is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CTXFI is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_INDIGOIOX is not set
# CONFIG_SND_INDIGODJX is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_LOLA is not set
# CONFIG_SND_LX6464ES is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SE6X is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set

#
# HD-Audio
#
CONFIG_SND_HDA=y
CONFIG_SND_HDA_HWDEP=y
CONFIG_SND_HDA_RECONFIG=y
CONFIG_SND_HDA_INPUT_BEEP=y
CONFIG_SND_HDA_INPUT_BEEP_MODE=1
CONFIG_SND_HDA_PATCH_LOADER=y
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
# CONFIG_SND_HDA_CTL_DEV_ID is not set
CONFIG_SND_HDA_PREALLOC_SIZE=0
CONFIG_SND_HDA_INTEL=y
# CONFIG_SND_HDA_ACPI is not set
CONFIG_SND_HDA_GENERIC_LEDS=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
# CONFIG_SND_HDA_CODEC_SENARYTECH is not set
CONFIG_SND_HDA_CODEC_CA0110=y
CONFIG_SND_HDA_CODEC_CA0132=y
# CONFIG_SND_HDA_CODEC_CA0132_DSP is not set
CONFIG_SND_HDA_CODEC_CMEDIA=y
# CONFIG_SND_HDA_CODEC_CM9825 is not set
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
CONFIG_SND_HDA_CODEC_REALTEK=y
# CONFIG_SND_HDA_CODEC_ALC260 is not set
# CONFIG_SND_HDA_CODEC_ALC262 is not set
# CONFIG_SND_HDA_CODEC_ALC268 is not set
# CONFIG_SND_HDA_CODEC_ALC269 is not set
# CONFIG_SND_HDA_CODEC_ALC662 is not set
# CONFIG_SND_HDA_CODEC_ALC680 is not set
# CONFIG_SND_HDA_CODEC_ALC861 is not set
# CONFIG_SND_HDA_CODEC_ALC861VD is not set
# CONFIG_SND_HDA_CODEC_ALC880 is not set
# CONFIG_SND_HDA_CODEC_ALC882 is not set
CONFIG_SND_HDA_CODEC_CIRRUS=y
# CONFIG_SND_HDA_CODEC_CS420X is not set
# CONFIG_SND_HDA_CODEC_CS421X is not set
# CONFIG_SND_HDA_CODEC_CS8409 is not set
CONFIG_SND_HDA_CODEC_HDMI=y
# CONFIG_SND_HDA_CODEC_HDMI_GENERIC is not set
# CONFIG_SND_HDA_CODEC_HDMI_SIMPLE is not set
# CONFIG_SND_HDA_CODEC_HDMI_INTEL is not set
# CONFIG_SND_HDA_CODEC_HDMI_ATI is not set
# CONFIG_SND_HDA_CODEC_HDMI_NVIDIA is not set
# CONFIG_SND_HDA_CODEC_HDMI_NVIDIA_MCP is not set
# CONFIG_SND_HDA_CODEC_HDMI_TEGRA is not set
# CONFIG_SND_HDA_SCODEC_AW88399_I2C is not set
# CONFIG_SND_HDA_SCODEC_CS35L56_I2C is not set
# CONFIG_SND_HDA_SCODEC_CS35L56_SPI is not set
CONFIG_SND_HDA_CORE=y
CONFIG_SND_INTEL_NHLT=y
CONFIG_SND_INTEL_DSP_CONFIG=y
CONFIG_SND_INTEL_SOUNDWIRE_ACPI=y
# end of HD-Audio

# CONFIG_SND_SPI is not set
CONFIG_SND_USB=y
CONFIG_SND_USB_AUDIO=y
CONFIG_SND_USB_AUDIO_MIDI_V2=y
CONFIG_SND_USB_AUDIO_USE_MEDIA_CONTROLLER=y
CONFIG_SND_USB_UA101=y
CONFIG_SND_USB_USX2Y=y
CONFIG_SND_USB_CAIAQ=y
CONFIG_SND_USB_CAIAQ_INPUT=y
CONFIG_SND_USB_US122L=y
# CONFIG_SND_USB_US144MKII is not set
CONFIG_SND_USB_6FIRE=y
CONFIG_SND_USB_HIFACE=y
CONFIG_SND_BCD2000=y
CONFIG_SND_USB_LINE6=y
CONFIG_SND_USB_POD=y
CONFIG_SND_USB_PODHD=y
CONFIG_SND_USB_TONEPORT=y
CONFIG_SND_USB_VARIAX=y
# CONFIG_SND_FIREWIRE is not set
CONFIG_SND_PCMCIA=y
# CONFIG_SND_VXPOCKET is not set
# CONFIG_SND_PDAUDIOCF is not set
CONFIG_SND_SOC=y
# CONFIG_SND_SOC_USB is not set

#
# Analog Devices
#
# CONFIG_SND_SOC_ADI_AXI_I2S is not set
# CONFIG_SND_SOC_ADI_AXI_SPDIF is not set
# end of Analog Devices

#
# AMD
#
# CONFIG_SND_SOC_AMD_ACP is not set
# CONFIG_SND_SOC_AMD_ACP3x is not set
# CONFIG_SND_SOC_AMD_RENOIR is not set
# CONFIG_SND_SOC_AMD_ACP5x is not set
# CONFIG_SND_SOC_AMD_ACP6x is not set
# CONFIG_SND_AMD_ACP_CONFIG is not set
# CONFIG_SND_SOC_AMD_ACP_COMMON is not set
# end of AMD

#
# Apple
#
# end of Apple

#
# Atmel
#
# CONFIG_SND_SOC_MIKROE_PROTO is not set
# end of Atmel

#
# Au1x
#
# end of Au1x

#
# Broadcom
#
# CONFIG_SND_BCM63XX_I2S_WHISTLER is not set
# end of Broadcom

#
# Cirrus Logic
#
# end of Cirrus Logic

#
# DesignWare
#
# CONFIG_SND_DESIGNWARE_I2S is not set
# end of DesignWare

#
# Freescale
#

#
# Common SoC Audio options for Freescale CPUs:
#
# CONFIG_SND_SOC_FSL_ASRC is not set
# CONFIG_SND_SOC_FSL_SAI is not set
# CONFIG_SND_SOC_FSL_AUDMIX is not set
# CONFIG_SND_SOC_FSL_SSI is not set
# CONFIG_SND_SOC_FSL_SPDIF is not set
# CONFIG_SND_SOC_FSL_ESAI is not set
# CONFIG_SND_SOC_FSL_MICFIL is not set
# CONFIG_SND_SOC_FSL_XCVR is not set
# CONFIG_SND_SOC_IMX_AUDMUX is not set
# end of Freescale

#
# Google
#
# CONFIG_SND_SOC_CHV3_I2S is not set
# end of Google

#
# Hisilicon
#
# CONFIG_SND_I2S_HI6210_I2S is not set
# end of Hisilicon

#
# JZ4740
#
# end of JZ4740

#
# Kirkwood
#
# end of Kirkwood

#
# Loongson
#
# end of Loongson

#
# Intel
#
# CONFIG_SND_SOC_INTEL_SST_TOPLEVEL is not set
# CONFIG_SND_SOC_INTEL_AVS is not set
# end of Intel

#
# Mediatek
#
# CONFIG_SND_SOC_MTK_BTCVSD is not set
# end of Mediatek

#
# PXA
#
# end of PXA

#
# SoundWire (SDCA)
#
# CONFIG_SND_SOC_SDCA is not set
CONFIG_SND_SOC_SDCA_OPTIONAL=y
# end of SoundWire (SDCA)

#
# ST SPEAr
#
# end of ST SPEAr

#
# Spreadtrum
#
# end of Spreadtrum

#
# STMicroelectronics STM32
#
# end of STMicroelectronics STM32

#
# Tegra
#
# end of Tegra

#
# Xilinx
#
# CONFIG_SND_SOC_XILINX_I2S is not set
# CONFIG_SND_SOC_XILINX_AUDIO_FORMATTER is not set
# CONFIG_SND_SOC_XILINX_SPDIF is not set
# end of Xilinx

#
# Xtensa
#
# CONFIG_SND_SOC_XTFPGA_I2S is not set
# end of Xtensa

# CONFIG_SND_SOC_SOF_TOPLEVEL is not set
CONFIG_SND_SOC_I2C_AND_SPI=y

#
# CODEC drivers
#
# CONFIG_SND_SOC_AC97_CODEC is not set
# CONFIG_SND_SOC_ADAU1372_I2C is not set
# CONFIG_SND_SOC_ADAU1372_SPI is not set
# CONFIG_SND_SOC_ADAU1373 is not set
# CONFIG_SND_SOC_ADAU1701 is not set
# CONFIG_SND_SOC_ADAU1761_I2C is not set
# CONFIG_SND_SOC_ADAU1761_SPI is not set
# CONFIG_SND_SOC_ADAU7002 is not set
# CONFIG_SND_SOC_ADAU7118_HW is not set
# CONFIG_SND_SOC_ADAU7118_I2C is not set
# CONFIG_SND_SOC_AK4104 is not set
# CONFIG_SND_SOC_AK4118 is not set
# CONFIG_SND_SOC_AK4375 is not set
# CONFIG_SND_SOC_AK4458 is not set
# CONFIG_SND_SOC_AK4554 is not set
# CONFIG_SND_SOC_AK4613 is not set
# CONFIG_SND_SOC_AK4619 is not set
# CONFIG_SND_SOC_AK4642 is not set
# CONFIG_SND_SOC_AK5386 is not set
# CONFIG_SND_SOC_AK5558 is not set
# CONFIG_SND_SOC_ALC5623 is not set
# CONFIG_SND_SOC_AUDIO_IIO_AUX is not set
# CONFIG_SND_SOC_AW8738 is not set
# CONFIG_SND_SOC_AW88395 is not set
# CONFIG_SND_SOC_AW88166 is not set
# CONFIG_SND_SOC_AW88261 is not set
# CONFIG_SND_SOC_AW88081 is not set
# CONFIG_SND_SOC_AW87390 is not set
# CONFIG_SND_SOC_AW88399 is not set
# CONFIG_SND_SOC_BD28623 is not set
# CONFIG_SND_SOC_BT_SCO is not set
# CONFIG_SND_SOC_CHV3_CODEC is not set
# CONFIG_SND_SOC_CS35L32 is not set
# CONFIG_SND_SOC_CS35L33 is not set
# CONFIG_SND_SOC_CS35L34 is not set
# CONFIG_SND_SOC_CS35L35 is not set
# CONFIG_SND_SOC_CS35L36 is not set
# CONFIG_SND_SOC_CS35L41_SPI is not set
# CONFIG_SND_SOC_CS35L41_I2C is not set
# CONFIG_SND_SOC_CS35L45_SPI is not set
# CONFIG_SND_SOC_CS35L45_I2C is not set
# CONFIG_SND_SOC_CS35L56_I2C is not set
# CONFIG_SND_SOC_CS35L56_SPI is not set
# CONFIG_SND_SOC_CS35L56_SDW is not set
# CONFIG_SND_SOC_CS42L42 is not set
# CONFIG_SND_SOC_CS42L42_SDW is not set
# CONFIG_SND_SOC_CS42L51_I2C is not set
# CONFIG_SND_SOC_CS42L52 is not set
# CONFIG_SND_SOC_CS42L56 is not set
# CONFIG_SND_SOC_CS42L73 is not set
# CONFIG_SND_SOC_CS42L83 is not set
# CONFIG_SND_SOC_CS42L84 is not set
# CONFIG_SND_SOC_CS4234 is not set
# CONFIG_SND_SOC_CS4265 is not set
# CONFIG_SND_SOC_CS4270 is not set
# CONFIG_SND_SOC_CS4271_I2C is not set
# CONFIG_SND_SOC_CS4271_SPI is not set
# CONFIG_SND_SOC_CS42XX8_SPI is not set
# CONFIG_SND_SOC_CS42XX8_I2C is not set
# CONFIG_SND_SOC_CS43130 is not set
# CONFIG_SND_SOC_CS4341 is not set
# CONFIG_SND_SOC_CS4349 is not set
# CONFIG_SND_SOC_CS48L32 is not set
# CONFIG_SND_SOC_CS53L30 is not set
# CONFIG_SND_SOC_CS530X_I2C is not set
# CONFIG_SND_SOC_CS530X_SPI is not set
# CONFIG_SND_SOC_CX2072X is not set
# CONFIG_SND_SOC_DA7213 is not set
# CONFIG_SND_SOC_DMIC is not set
# CONFIG_SND_SOC_ES7134 is not set
# CONFIG_SND_SOC_ES7241 is not set
# CONFIG_SND_SOC_ES8311 is not set
# CONFIG_SND_SOC_ES8316 is not set
# CONFIG_SND_SOC_ES8323 is not set
# CONFIG_SND_SOC_ES8326 is not set
# CONFIG_SND_SOC_ES8328_I2C is not set
# CONFIG_SND_SOC_ES8328_SPI is not set
# CONFIG_SND_SOC_ES8375 is not set
# CONFIG_SND_SOC_ES8389 is not set
# CONFIG_SND_SOC_FS210X is not set
# CONFIG_SND_SOC_GTM601 is not set
# CONFIG_SND_SOC_HDA is not set
# CONFIG_SND_SOC_ICS43432 is not set
# CONFIG_SND_SOC_IDT821034 is not set
# CONFIG_SND_SOC_MAX98088 is not set
# CONFIG_SND_SOC_MAX98090 is not set
# CONFIG_SND_SOC_MAX98357A is not set
# CONFIG_SND_SOC_MAX98504 is not set
# CONFIG_SND_SOC_MAX9867 is not set
# CONFIG_SND_SOC_MAX98927 is not set
# CONFIG_SND_SOC_MAX98520 is not set
# CONFIG_SND_SOC_MAX98363 is not set
# CONFIG_SND_SOC_MAX98373_I2C is not set
# CONFIG_SND_SOC_MAX98373_SDW is not set
# CONFIG_SND_SOC_MAX98388 is not set
# CONFIG_SND_SOC_MAX98390 is not set
# CONFIG_SND_SOC_MAX98396 is not set
# CONFIG_SND_SOC_MAX9860 is not set
# CONFIG_SND_SOC_MSM8916_WCD_DIGITAL is not set
# CONFIG_SND_SOC_PCM1681 is not set
# CONFIG_SND_SOC_PCM1754 is not set
# CONFIG_SND_SOC_PCM1789_I2C is not set
# CONFIG_SND_SOC_PCM179X_I2C is not set
# CONFIG_SND_SOC_PCM179X_SPI is not set
# CONFIG_SND_SOC_PCM186X_I2C is not set
# CONFIG_SND_SOC_PCM186X_SPI is not set
# CONFIG_SND_SOC_PCM3060_I2C is not set
# CONFIG_SND_SOC_PCM3060_SPI is not set
# CONFIG_SND_SOC_PCM3168A_I2C is not set
# CONFIG_SND_SOC_PCM3168A_SPI is not set
# CONFIG_SND_SOC_PCM5102A is not set
# CONFIG_SND_SOC_PCM512x_I2C is not set
# CONFIG_SND_SOC_PCM512x_SPI is not set
# CONFIG_SND_SOC_PCM6240 is not set
# CONFIG_SND_SOC_PEB2466 is not set
# CONFIG_SND_SOC_PM4125_SDW is not set
# CONFIG_SND_SOC_RT1017_SDCA_SDW is not set
# CONFIG_SND_SOC_RT1308_SDW is not set
# CONFIG_SND_SOC_RT1316_SDW is not set
# CONFIG_SND_SOC_RT1318_SDW is not set
# CONFIG_SND_SOC_RT1320_SDW is not set
# CONFIG_SND_SOC_RT5575 is not set
# CONFIG_SND_SOC_RT5616 is not set
# CONFIG_SND_SOC_RT5631 is not set
# CONFIG_SND_SOC_RT5640 is not set
# CONFIG_SND_SOC_RT5645 is not set
# CONFIG_SND_SOC_RT5659 is not set
# CONFIG_SND_SOC_RT5677 is not set
# CONFIG_SND_SOC_RT5682_SDW is not set
# CONFIG_SND_SOC_RT700_SDW is not set
# CONFIG_SND_SOC_RT711_SDW is not set
# CONFIG_SND_SOC_RT711_SDCA_SDW is not set
# CONFIG_SND_SOC_RT712_SDCA_SDW is not set
# CONFIG_SND_SOC_RT712_SDCA_DMIC_SDW is not set
# CONFIG_SND_SOC_RT721_SDCA_SDW is not set
# CONFIG_SND_SOC_RT722_SDCA_SDW is not set
# CONFIG_SND_SOC_RT715_SDW is not set
# CONFIG_SND_SOC_RT715_SDCA_SDW is not set
# CONFIG_SND_SOC_RT9120 is not set
# CONFIG_SND_SOC_RT9123 is not set
# CONFIG_SND_SOC_RT9123P is not set
# CONFIG_SND_SOC_RTQ9124 is not set
# CONFIG_SND_SOC_RTQ9128 is not set
# CONFIG_SND_SOC_SDW_MOCKUP is not set
# CONFIG_SND_SOC_SGTL5000 is not set
# CONFIG_SND_SOC_SIMPLE_AMPLIFIER is not set
# CONFIG_SND_SOC_SIMPLE_MUX is not set
# CONFIG_SND_SOC_SMA1303 is not set
# CONFIG_SND_SOC_SMA1307 is not set
# CONFIG_SND_SOC_SPDIF is not set
# CONFIG_SND_SOC_SRC4XXX_I2C is not set
# CONFIG_SND_SOC_SSM2305 is not set
# CONFIG_SND_SOC_SSM2518 is not set
# CONFIG_SND_SOC_SSM2602_SPI is not set
# CONFIG_SND_SOC_SSM2602_I2C is not set
# CONFIG_SND_SOC_SSM3515 is not set
# CONFIG_SND_SOC_SSM4567 is not set
# CONFIG_SND_SOC_STA32X is not set
# CONFIG_SND_SOC_STA350 is not set
# CONFIG_SND_SOC_STI_SAS is not set
# CONFIG_SND_SOC_TAS2552 is not set
# CONFIG_SND_SOC_TAS2562 is not set
# CONFIG_SND_SOC_TAS2764 is not set
# CONFIG_SND_SOC_TAS2770 is not set
# CONFIG_SND_SOC_TAS2780 is not set
# CONFIG_SND_SOC_TAS2781_I2C is not set
# CONFIG_SND_SOC_TAS5086 is not set
# CONFIG_SND_SOC_TAS571X is not set
# CONFIG_SND_SOC_TAS5720 is not set
# CONFIG_SND_SOC_TAS5805M is not set
# CONFIG_SND_SOC_TAS6424 is not set
# CONFIG_SND_SOC_TAS675X is not set
# CONFIG_SND_SOC_TDA7419 is not set
# CONFIG_SND_SOC_TFA9879 is not set
# CONFIG_SND_SOC_TFA989X is not set
# CONFIG_SND_SOC_TLV320ADC3XXX is not set
# CONFIG_SND_SOC_TLV320AIC23_I2C is not set
# CONFIG_SND_SOC_TLV320AIC23_SPI is not set
# CONFIG_SND_SOC_TLV320AIC31XX is not set
# CONFIG_SND_SOC_TLV320AIC32X4_I2C is not set
# CONFIG_SND_SOC_TLV320AIC32X4_SPI is not set
# CONFIG_SND_SOC_TLV320AIC3X_I2C is not set
# CONFIG_SND_SOC_TLV320AIC3X_SPI is not set
# CONFIG_SND_SOC_TLV320ADCX140 is not set
# CONFIG_SND_SOC_TS3A227E is not set
# CONFIG_SND_SOC_TSCS42XX is not set
# CONFIG_SND_SOC_TSCS454 is not set
# CONFIG_SND_SOC_UDA1334 is not set
# CONFIG_SND_SOC_UDA1342 is not set
# CONFIG_SND_SOC_UDA1380 is not set
# CONFIG_SND_SOC_WCD937X_SDW is not set
# CONFIG_SND_SOC_WCD938X_SDW is not set
# CONFIG_SND_SOC_WCD939X_SDW is not set
# CONFIG_SND_SOC_WM8510 is not set
# CONFIG_SND_SOC_WM8523 is not set
# CONFIG_SND_SOC_WM8524 is not set
# CONFIG_SND_SOC_WM8580 is not set
# CONFIG_SND_SOC_WM8711 is not set
# CONFIG_SND_SOC_WM8728 is not set
# CONFIG_SND_SOC_WM8731_I2C is not set
# CONFIG_SND_SOC_WM8731_SPI is not set
# CONFIG_SND_SOC_WM8737 is not set
# CONFIG_SND_SOC_WM8741 is not set
# CONFIG_SND_SOC_WM8750 is not set
# CONFIG_SND_SOC_WM8753 is not set
# CONFIG_SND_SOC_WM8770 is not set
# CONFIG_SND_SOC_WM8776 is not set
# CONFIG_SND_SOC_WM8782 is not set
# CONFIG_SND_SOC_WM8804_I2C is not set
# CONFIG_SND_SOC_WM8804_SPI is not set
# CONFIG_SND_SOC_WM8903 is not set
# CONFIG_SND_SOC_WM8904 is not set
# CONFIG_SND_SOC_WM8940 is not set
# CONFIG_SND_SOC_WM8960 is not set
# CONFIG_SND_SOC_WM8961 is not set
# CONFIG_SND_SOC_WM8962 is not set
# CONFIG_SND_SOC_WM8974 is not set
# CONFIG_SND_SOC_WM8978 is not set
# CONFIG_SND_SOC_WM8985 is not set
# CONFIG_SND_SOC_WSA881X is not set
# CONFIG_SND_SOC_WSA883X is not set
# CONFIG_SND_SOC_WSA884X is not set
# CONFIG_SND_SOC_WSA885X is not set
# CONFIG_SND_SOC_ZL38060 is not set
# CONFIG_SND_SOC_MAX9759 is not set
# CONFIG_SND_SOC_MT6351 is not set
# CONFIG_SND_SOC_MT6357 is not set
# CONFIG_SND_SOC_MT6358 is not set
# CONFIG_SND_SOC_MT6660 is not set
# CONFIG_SND_SOC_NAU8315 is not set
# CONFIG_SND_SOC_NAU8325 is not set
# CONFIG_SND_SOC_NAU8540 is not set
# CONFIG_SND_SOC_NAU8810 is not set
# CONFIG_SND_SOC_NAU8821 is not set
# CONFIG_SND_SOC_NAU8822 is not set
# CONFIG_SND_SOC_NAU8824 is not set
# CONFIG_SND_SOC_NTP8918 is not set
# CONFIG_SND_SOC_NTP8835 is not set
# CONFIG_SND_SOC_TPA6130A2 is not set
# CONFIG_SND_SOC_LPASS_WSA_MACRO is not set
# CONFIG_SND_SOC_LPASS_VA_MACRO is not set
# CONFIG_SND_SOC_LPASS_RX_MACRO is not set
# CONFIG_SND_SOC_LPASS_TX_MACRO is not set
# end of CODEC drivers

#
# Generic drivers
#
# CONFIG_SND_SIMPLE_CARD is not set
# CONFIG_SND_AUDIO_GRAPH_CARD is not set
# CONFIG_SND_AUDIO_GRAPH_CARD2 is not set
# CONFIG_SND_TEST_COMPONENT is not set
# end of Generic drivers

CONFIG_SND_X86=y
CONFIG_SND_VIRTIO=y
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
CONFIG_HID_BATTERY_STRENGTH=y
CONFIG_HIDRAW=y
CONFIG_UHID=y
CONFIG_HID_GENERIC=y
CONFIG_HID_HAPTIC=y

#
# Special HID drivers
#
CONFIG_HID_A4TECH=y
CONFIG_HID_ACCUTOUCH=y
CONFIG_HID_ACRUX=y
CONFIG_HID_ACRUX_FF=y
CONFIG_HID_APPLE=y
CONFIG_HID_APPLEIR=y
# CONFIG_HID_APPLETB_BL is not set
# CONFIG_HID_APPLETB_KBD is not set
CONFIG_HID_ASUS=y
CONFIG_HID_AUREAL=y
CONFIG_HID_BELKIN=y
CONFIG_HID_BETOP_FF=y
CONFIG_HID_BIGBEN_FF=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
CONFIG_HID_CORSAIR=y
CONFIG_HID_COUGAR=y
CONFIG_HID_MACALLY=y
CONFIG_HID_PRODIKEYS=y
CONFIG_HID_CMEDIA=y
CONFIG_HID_CP2112=y
CONFIG_HID_CREATIVE_SB0540=y
CONFIG_HID_CYPRESS=y
CONFIG_HID_DRAGONRISE=y
CONFIG_DRAGONRISE_FF=y
CONFIG_HID_EMS_FF=y
CONFIG_HID_ELAN=y
CONFIG_HID_ELECOM=y
CONFIG_HID_ELO=y
CONFIG_HID_EVISION=y
CONFIG_HID_EZKEY=y
CONFIG_HID_FT260=y
CONFIG_HID_GEMBIRD=y
CONFIG_HID_GFRM=y
CONFIG_HID_GLORIOUS=y
CONFIG_HID_HOLTEK=y
CONFIG_HOLTEK_FF=y
# CONFIG_HID_HYPERX is not set
CONFIG_HID_VIVALDI_COMMON=y
# CONFIG_HID_GOODIX_SPI is not set
CONFIG_HID_GOOGLE_STADIA_FF=y
CONFIG_HID_VIVALDI=y
CONFIG_HID_GT683R=y
# CONFIG_HID_MSI is not set
CONFIG_HID_KEYTOUCH=y
CONFIG_HID_KYE=y
# CONFIG_HID_KYSONA is not set
CONFIG_HID_UCLOGIC=y
CONFIG_HID_WALTOP=y
CONFIG_HID_VIEWSONIC=y
CONFIG_HID_VRC2=y
CONFIG_HID_XIAOMI=y
CONFIG_HID_GYRATION=y
CONFIG_HID_ICADE=y
CONFIG_HID_ITE=y
CONFIG_HID_JABRA=y
CONFIG_HID_TWINHAN=y
CONFIG_HID_KENSINGTON=y
CONFIG_HID_LCPOWER=y
CONFIG_HID_LED=y
CONFIG_HID_LENOVO=y
# CONFIG_HID_LENOVO_GO is not set
# CONFIG_HID_LENOVO_GO_S is not set
CONFIG_HID_LETSKETCH=y
CONFIG_HID_LOGITECH=y
CONFIG_HID_LOGITECH_DJ=y
CONFIG_HID_LOGITECH_HIDPP=y
CONFIG_LOGITECH_FF=y
CONFIG_LOGIRUMBLEPAD2_FF=y
CONFIG_LOGIG940_FF=y
CONFIG_LOGIWHEELS_FF=y
CONFIG_HID_MAGICMOUSE=y
CONFIG_HID_MALTRON=y
CONFIG_HID_MAYFLASH=y
CONFIG_HID_MEGAWORLD_FF=y
# CONFIG_HID_RAKK is not set
CONFIG_HID_REDRAGON=y
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
CONFIG_HID_MULTITOUCH=y
CONFIG_HID_NINTENDO=y
CONFIG_NINTENDO_FF=y
CONFIG_HID_NTI=y
CONFIG_HID_NTRIG=y
CONFIG_HID_NVIDIA_SHIELD=y
CONFIG_NVIDIA_SHIELD_FF=y
CONFIG_HID_ORTEK=y
# CONFIG_HID_OXP is not set
CONFIG_HID_PANTHERLORD=y
CONFIG_PANTHERLORD_FF=y
CONFIG_HID_PENMOUNT=y
CONFIG_HID_PETALYNX=y
CONFIG_HID_PICOLCD=y
CONFIG_HID_PICOLCD_FB=y
CONFIG_HID_PICOLCD_BACKLIGHT=y
CONFIG_HID_PICOLCD_LCD=y
CONFIG_HID_PICOLCD_LEDS=y
CONFIG_HID_PICOLCD_CIR=y
CONFIG_HID_PLANTRONICS=y
CONFIG_HID_PLAYSTATION=y
CONFIG_PLAYSTATION_FF=y
CONFIG_HID_PXRC=y
# CONFIG_HID_RAPOO is not set
CONFIG_HID_RAZER=y
CONFIG_HID_PRIMAX=y
CONFIG_HID_RETRODE=y
CONFIG_HID_ROCCAT=y
CONFIG_HID_SAITEK=y
CONFIG_HID_SAMSUNG=y
CONFIG_HID_SEMITEK=y
CONFIG_HID_SIGMAMICRO=y
CONFIG_HID_SONY=y
CONFIG_SONY_FF=y
CONFIG_HID_SPEEDLINK=y
CONFIG_HID_STEAM=y
CONFIG_STEAM_FF=y
CONFIG_HID_STEELSERIES=y
CONFIG_HID_SUNPLUS=y
CONFIG_HID_RMI=y
CONFIG_HID_GREENASIA=y
CONFIG_GREENASIA_FF=y
CONFIG_HID_SMARTJOYPLUS=y
CONFIG_SMARTJOYPLUS_FF=y
CONFIG_HID_TIVO=y
CONFIG_HID_TOPSEED=y
CONFIG_HID_TOPRE=y
CONFIG_HID_THINGM=y
CONFIG_HID_THRUSTMASTER=y
CONFIG_THRUSTMASTER_FF=y
CONFIG_HID_UDRAW_PS3=y
CONFIG_HID_U2FZERO=y
# CONFIG_HID_UNIVERSAL_PIDFF is not set
CONFIG_HID_WACOM=y
CONFIG_HID_WIIMOTE=y
# CONFIG_HID_WINWING is not set
CONFIG_HID_XINMO=y
CONFIG_HID_ZEROPLUS=y
CONFIG_ZEROPLUS_FF=y
CONFIG_HID_ZYDACRON=y
CONFIG_HID_SENSOR_HUB=y
CONFIG_HID_SENSOR_CUSTOM_SENSOR=y
CONFIG_HID_ALPS=y
CONFIG_HID_MCP2200=y
CONFIG_HID_MCP2221=y
CONFIG_HID_HUAWEI=y
# end of Special HID drivers

#
# HID-BPF support
#
# end of HID-BPF support

CONFIG_I2C_HID=y
CONFIG_I2C_HID_ACPI=y
CONFIG_I2C_HID_OF=y
# CONFIG_I2C_HID_OF_ELAN is not set
# CONFIG_I2C_HID_OF_GOODIX is not set
CONFIG_I2C_HID_CORE=y

#
# Intel ISH HID support
#
CONFIG_INTEL_ISH_HID=y
CONFIG_INTEL_ISH_FIRMWARE_DOWNLOADER=y
# end of Intel ISH HID support

#
# AMD SFH HID Support
#
CONFIG_AMD_SFH_HID=y
# end of AMD SFH HID Support

#
# Surface System Aggregator Module HID support
#
CONFIG_SURFACE_HID=y
CONFIG_SURFACE_KBD=y
# end of Surface System Aggregator Module HID support

CONFIG_SURFACE_HID_CORE=y

#
# Intel THC HID Support
#
# CONFIG_INTEL_THC_HID is not set
# end of Intel THC HID Support

#
# USB HID support
#
CONFIG_USB_HID=y
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
# end of USB HID support

CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
CONFIG_USB_LED_TRIG=y
CONFIG_USB_ULPI_BUS=y
CONFIG_USB_CONN_GPIO=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=y
CONFIG_USB_PCI=y
CONFIG_USB_PCI_AMD=y
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEFAULT_PERSIST=y
CONFIG_USB_FEW_INIT_RETRIES=y
CONFIG_USB_DYNAMIC_MINORS=y
CONFIG_USB_OTG=y
# CONFIG_USB_OTG_PRODUCTLIST is not set
# CONFIG_USB_OTG_DISABLE_EXTERNAL_HUB is not set
CONFIG_USB_OTG_FSM=y
CONFIG_USB_LEDS_TRIGGER_USBPORT=y
CONFIG_USB_AUTOSUSPEND_DELAY=2
CONFIG_USB_DEFAULT_AUTHORIZATION_MODE=1
CONFIG_USB_MON=y

#
# USB Host Controller Drivers
#
CONFIG_USB_C67X00_HCD=y
CONFIG_USB_XHCI_HCD=y
CONFIG_USB_XHCI_DBGCAP=y
CONFIG_USB_XHCI_PCI=y
CONFIG_USB_XHCI_PCI_RENESAS=y
CONFIG_USB_XHCI_PLATFORM=y
# CONFIG_USB_XHCI_SIDEBAND is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
CONFIG_USB_EHCI_PCI=y
CONFIG_USB_EHCI_FSL=y
CONFIG_USB_EHCI_HCD_PLATFORM=y
CONFIG_USB_OXU210HP_HCD=y
CONFIG_USB_ISP116X_HCD=y
CONFIG_USB_MAX3421_HCD=y
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_PCI=y
# CONFIG_USB_OHCI_HCD_SSB is not set
CONFIG_USB_OHCI_HCD_PLATFORM=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_SL811_HCD=y
CONFIG_USB_SL811_HCD_ISO=y
CONFIG_USB_SL811_CS=y
CONFIG_USB_R8A66597_HCD=y
CONFIG_USB_HCD_BCMA=y
CONFIG_USB_HCD_SSB=y
# CONFIG_USB_HCD_TEST_MODE is not set

#
# USB Device Class drivers
#
CONFIG_USB_ACM=y
CONFIG_USB_PRINTER=y
CONFIG_USB_WDM=y
CONFIG_USB_TMC=y

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
CONFIG_USB_STORAGE_REALTEK=y
CONFIG_REALTEK_AUTOPM=y
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_STORAGE_ALAUDA=y
CONFIG_USB_STORAGE_ONETOUCH=y
CONFIG_USB_STORAGE_KARMA=y
CONFIG_USB_STORAGE_CYPRESS_ATACB=y
CONFIG_USB_STORAGE_ENE_UB6250=y
CONFIG_USB_UAS=y

#
# USB Imaging devices
#
CONFIG_USB_MDC800=y
CONFIG_USB_MICROTEK=y
CONFIG_USBIP_CORE=y
CONFIG_USBIP_VHCI_HCD=y
CONFIG_USBIP_VHCI_HC_PORTS=8
CONFIG_USBIP_VHCI_NR_HCS=16
CONFIG_USBIP_HOST=y
CONFIG_USBIP_VUDC=y
# CONFIG_USBIP_DEBUG is not set

#
# USB dual-mode controller drivers
#
CONFIG_USB_CDNS_SUPPORT=y
CONFIG_USB_CDNS3=y
CONFIG_USB_CDNS3_HOST=y
CONFIG_USB_CDNS3_GADGET=y

#
# Platform glue driver support
#
CONFIG_USB_CDNS3_PCI_WRAP=y
CONFIG_USB_CDNSP_PCI=y
CONFIG_USB_MUSB_HDRC=y
# CONFIG_USB_MUSB_HOST is not set
# CONFIG_USB_MUSB_GADGET is not set
CONFIG_USB_MUSB_DUAL_ROLE=y

#
# Platform Glue Layer
#

#
# MUSB DMA mode
#
CONFIG_MUSB_PIO_ONLY=y
CONFIG_USB_DWC3=y
CONFIG_USB_DWC3_ULPI=y
# CONFIG_USB_DWC3_HOST is not set
CONFIG_USB_DWC3_GADGET=y
# CONFIG_USB_DWC3_DUAL_ROLE is not set

#
# Platform Glue Driver Support
#
CONFIG_USB_DWC3_PCI=y
CONFIG_USB_DWC3_HAPS=y
CONFIG_USB_DWC3_OF_SIMPLE=y
CONFIG_USB_DWC3_GENERIC_PLAT=y
# CONFIG_USB_DWC3_GOOGLE is not set
CONFIG_USB_DWC2=y
CONFIG_USB_DWC2_HOST=y

#
# Gadget/Dual-role mode requires USB Gadget support to be enabled
#
# CONFIG_USB_DWC2_PERIPHERAL is not set
# CONFIG_USB_DWC2_DUAL_ROLE is not set
CONFIG_USB_DWC2_PCI=y
# CONFIG_USB_DWC2_DEBUG is not set
# CONFIG_USB_DWC2_TRACK_MISSED_SOFS is not set
CONFIG_USB_CHIPIDEA=y
CONFIG_USB_CHIPIDEA_UDC=y
CONFIG_USB_CHIPIDEA_HOST=y
CONFIG_USB_CHIPIDEA_PCI=y
CONFIG_USB_CHIPIDEA_MSM=y
CONFIG_USB_CHIPIDEA_NPCM=y
# CONFIG_USB_CHIPIDEA_IMX is not set
CONFIG_USB_CHIPIDEA_GENERIC=y
# CONFIG_USB_CHIPIDEA_TEGRA is not set
CONFIG_USB_ISP1760=y
CONFIG_USB_ISP1760_HCD=y
CONFIG_USB_ISP1761_UDC=y
# CONFIG_USB_ISP1760_HOST_ROLE is not set
# CONFIG_USB_ISP1760_GADGET_ROLE is not set
CONFIG_USB_ISP1760_DUAL_ROLE=y

#
# USB port drivers
#
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CONSOLE=y
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_SIMPLE=y
CONFIG_USB_SERIAL_AIRCABLE=y
CONFIG_USB_SERIAL_ARK3116=y
CONFIG_USB_SERIAL_BELKIN=y
CONFIG_USB_SERIAL_CH341=y
CONFIG_USB_SERIAL_WHITEHEAT=y
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=y
CONFIG_USB_SERIAL_CP210X=y
CONFIG_USB_SERIAL_CYPRESS_M8=y
CONFIG_USB_SERIAL_EMPEG=y
CONFIG_USB_SERIAL_FTDI_SIO=y
CONFIG_USB_SERIAL_VISOR=y
CONFIG_USB_SERIAL_IPAQ=y
CONFIG_USB_SERIAL_IR=y
CONFIG_USB_SERIAL_EDGEPORT=y
CONFIG_USB_SERIAL_EDGEPORT_TI=y
CONFIG_USB_SERIAL_F81232=y
CONFIG_USB_SERIAL_F8153X=y
CONFIG_USB_SERIAL_GARMIN=y
CONFIG_USB_SERIAL_IPW=y
CONFIG_USB_SERIAL_IUU=y
CONFIG_USB_SERIAL_KEYSPAN_PDA=y
CONFIG_USB_SERIAL_KEYSPAN=y
CONFIG_USB_SERIAL_KLSI=y
CONFIG_USB_SERIAL_KOBIL_SCT=y
CONFIG_USB_SERIAL_MCT_U232=y
CONFIG_USB_SERIAL_METRO=y
CONFIG_USB_SERIAL_MOS7720=y
CONFIG_USB_SERIAL_MOS7715_PARPORT=y
CONFIG_USB_SERIAL_MOS7840=y
CONFIG_USB_SERIAL_MXUPORT=y
CONFIG_USB_SERIAL_NAVMAN=y
CONFIG_USB_SERIAL_PL2303=y
CONFIG_USB_SERIAL_OTI6858=y
CONFIG_USB_SERIAL_QCAUX=y
CONFIG_USB_SERIAL_QUALCOMM=y
CONFIG_USB_SERIAL_SPCP8X5=y
CONFIG_USB_SERIAL_SAFE=y
# CONFIG_USB_SERIAL_SAFE_PADDED is not set
CONFIG_USB_SERIAL_SIERRAWIRELESS=y
CONFIG_USB_SERIAL_SYMBOL=y
CONFIG_USB_SERIAL_TI=y
CONFIG_USB_SERIAL_CYBERJACK=y
CONFIG_USB_SERIAL_WWAN=y
CONFIG_USB_SERIAL_OPTION=y
CONFIG_USB_SERIAL_OMNINET=y
CONFIG_USB_SERIAL_OPTICON=y
CONFIG_USB_SERIAL_XSENS_MT=y
CONFIG_USB_SERIAL_WISHBONE=y
CONFIG_USB_SERIAL_SSU100=y
CONFIG_USB_SERIAL_QT2=y
CONFIG_USB_SERIAL_UPD78F0730=y
CONFIG_USB_SERIAL_XR=y
CONFIG_USB_SERIAL_DEBUG=y

#
# USB Miscellaneous drivers
#
CONFIG_USB_USS720=y
CONFIG_USB_EMI62=y
CONFIG_USB_EMI26=y
CONFIG_USB_ADUTUX=y
CONFIG_USB_SEVSEG=y
CONFIG_USB_LEGOTOWER=y
CONFIG_USB_LCD=y
CONFIG_USB_CYPRESS_CY7C63=y
CONFIG_USB_CYTHERM=y
CONFIG_USB_IDMOUSE=y
CONFIG_USB_APPLEDISPLAY=y
CONFIG_APPLE_MFI_FASTCHARGE=y
CONFIG_USB_LJCA=y
# CONFIG_USB_USBIO is not set
CONFIG_USB_SISUSBVGA=y
CONFIG_USB_LD=y
CONFIG_USB_TRANCEVIBRATOR=y
CONFIG_USB_IOWARRIOR=y
CONFIG_USB_TEST=y
CONFIG_USB_EHSET_TEST_FIXTURE=y
CONFIG_USB_ISIGHTFW=y
CONFIG_USB_YUREX=y
CONFIG_USB_EZUSB_FX2=y
CONFIG_USB_HUB_USB251XB=y
CONFIG_USB_HSIC_USB3503=y
CONFIG_USB_HSIC_USB4604=y
CONFIG_USB_LINK_LAYER_TEST=y
CONFIG_USB_CHAOSKEY=y
# CONFIG_USB_ONBOARD_DEV is not set
CONFIG_USB_ATM=y
CONFIG_USB_SPEEDTOUCH=y
CONFIG_USB_CXACRU=y
CONFIG_USB_UEAGLEATM=y
CONFIG_USB_XUSBATM=y

#
# USB Physical Layer drivers
#
CONFIG_USB_PHY=y
CONFIG_NOP_USB_XCEIV=y
CONFIG_TAHVO_USB=y
CONFIG_TAHVO_USB_HOST_BY_DEFAULT=y
CONFIG_USB_ISP1301=y
# end of USB Physical Layer drivers

CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG is not set
CONFIG_USB_GADGET_DEBUG_FILES=y
CONFIG_USB_GADGET_DEBUG_FS=y
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2
CONFIG_U_SERIAL_CONSOLE=y

#
# USB Peripheral Controller
#
CONFIG_USB_GR_UDC=y
CONFIG_USB_R8A66597=y
CONFIG_USB_PXA27X=y
CONFIG_USB_SNP_CORE=y
# CONFIG_USB_SNP_UDC_PLAT is not set
# CONFIG_USB_M66592 is not set
CONFIG_USB_BDC_UDC=y
CONFIG_USB_AMD5536UDC=y
CONFIG_USB_NET2280=y
CONFIG_USB_GOKU=y
CONFIG_USB_EG20T=y
# CONFIG_USB_GADGET_XILINX is not set
CONFIG_USB_MAX3420_UDC=y
CONFIG_USB_CDNS2_UDC=y
CONFIG_USB_DUMMY_HCD=y
# end of USB Peripheral Controller

CONFIG_USB_LIBCOMPOSITE=y
CONFIG_USB_F_ACM=y
CONFIG_USB_F_SS_LB=y
CONFIG_USB_U_SERIAL=y
CONFIG_USB_U_ETHER=y
CONFIG_USB_U_AUDIO=y
CONFIG_USB_F_SERIAL=y
CONFIG_USB_F_OBEX=y
CONFIG_USB_F_NCM=y
CONFIG_USB_F_ECM=y
CONFIG_USB_F_PHONET=y
CONFIG_USB_F_EEM=y
CONFIG_USB_F_SUBSET=y
CONFIG_USB_F_RNDIS=y
CONFIG_USB_F_MASS_STORAGE=y
CONFIG_USB_F_FS=y
CONFIG_USB_F_UAC1=y
CONFIG_USB_F_UAC1_LEGACY=y
CONFIG_USB_F_UAC2=y
CONFIG_USB_F_UVC=y
CONFIG_USB_F_MIDI=y
CONFIG_USB_F_MIDI2=y
CONFIG_USB_F_HID=y
CONFIG_USB_F_PRINTER=y
CONFIG_USB_F_TCM=y
CONFIG_USB_CONFIGFS=y
CONFIG_USB_CONFIGFS_SERIAL=y
CONFIG_USB_CONFIGFS_ACM=y
CONFIG_USB_CONFIGFS_OBEX=y
CONFIG_USB_CONFIGFS_NCM=y
CONFIG_USB_CONFIGFS_ECM=y
CONFIG_USB_CONFIGFS_ECM_SUBSET=y
CONFIG_USB_CONFIGFS_RNDIS=y
CONFIG_USB_CONFIGFS_EEM=y
CONFIG_USB_CONFIGFS_PHONET=y
CONFIG_USB_CONFIGFS_MASS_STORAGE=y
CONFIG_USB_CONFIGFS_F_LB_SS=y
CONFIG_USB_CONFIGFS_F_FS=y
CONFIG_USB_CONFIGFS_F_UAC1=y
CONFIG_USB_CONFIGFS_F_UAC1_LEGACY=y
CONFIG_USB_CONFIGFS_F_UAC2=y
CONFIG_USB_CONFIGFS_F_MIDI=y
CONFIG_USB_CONFIGFS_F_MIDI2=y
CONFIG_USB_CONFIGFS_F_HID=y
CONFIG_USB_CONFIGFS_F_UVC=y
CONFIG_USB_CONFIGFS_F_PRINTER=y
CONFIG_USB_CONFIGFS_F_TCM=y

#
# USB Gadget precomposed configurations
#
# CONFIG_USB_ZERO is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ETH is not set
# CONFIG_USB_G_NCM is not set
CONFIG_USB_GADGETFS=y
# CONFIG_USB_FUNCTIONFS is not set
# CONFIG_USB_MASS_STORAGE is not set
# CONFIG_USB_GADGET_TARGET is not set
# CONFIG_USB_G_SERIAL is not set
# CONFIG_USB_MIDI_GADGET is not set
# CONFIG_USB_G_PRINTER is not set
# CONFIG_USB_CDC_COMPOSITE is not set
# CONFIG_USB_G_NOKIA is not set
# CONFIG_USB_G_ACM_MS is not set
# CONFIG_USB_G_MULTI is not set
# CONFIG_USB_G_HID is not set
# CONFIG_USB_G_DBGP is not set
# CONFIG_USB_G_WEBCAM is not set
CONFIG_USB_RAW_GADGET=y
# end of USB Gadget precomposed configurations

CONFIG_TYPEC=y
CONFIG_TYPEC_TCPM=y
CONFIG_TYPEC_TCPCI=y
CONFIG_TYPEC_RT1711H=y
CONFIG_TYPEC_MT6360=y
CONFIG_TYPEC_TCPCI_MT6370=y
CONFIG_TYPEC_TCPCI_MAXIM=y
CONFIG_TYPEC_FUSB302=y
CONFIG_TYPEC_WCOVE=y
CONFIG_TYPEC_UCSI=y
CONFIG_UCSI_CCG=y
CONFIG_UCSI_ACPI=y
CONFIG_UCSI_STM32G0=y
CONFIG_TYPEC_TPS6598X=y
CONFIG_TYPEC_ANX7411=y
CONFIG_TYPEC_RT1719=y
CONFIG_TYPEC_HD3SS3220=y
CONFIG_TYPEC_STUSB160X=y
CONFIG_TYPEC_WUSB3801=y

#
# USB Type-C Multiplexer/DeMultiplexer Switch support
#
CONFIG_TYPEC_MUX_FSA4480=y
CONFIG_TYPEC_MUX_GPIO_SBU=y
CONFIG_TYPEC_MUX_PI3USB30532=y
CONFIG_TYPEC_MUX_INTEL_PMC=y
# CONFIG_TYPEC_MUX_IT5205 is not set
CONFIG_TYPEC_MUX_NB7VPQ904M=y
# CONFIG_TYPEC_MUX_PS883X is not set
CONFIG_TYPEC_MUX_PTN36502=y
# CONFIG_TYPEC_MUX_TUSB1046 is not set
CONFIG_TYPEC_MUX_WCD939X_USBSS=y
# end of USB Type-C Multiplexer/DeMultiplexer Switch support

#
# USB Type-C Alternate Mode drivers
#
CONFIG_TYPEC_DP_ALTMODE=y
CONFIG_TYPEC_NVIDIA_ALTMODE=y
# CONFIG_TYPEC_TBT_ALTMODE is not set
# end of USB Type-C Alternate Mode drivers

CONFIG_USB_ROLE_SWITCH=y
CONFIG_USB_ROLES_INTEL_XHCI=y
CONFIG_MMC=y
# CONFIG_PWRSEQ_EMMC is not set
# CONFIG_PWRSEQ_SD8787 is not set
# CONFIG_PWRSEQ_SIMPLE is not set
# CONFIG_MMC_BLOCK is not set
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set
# CONFIG_MMC_CRYPTO is not set

#
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_SDHCI is not set
# CONFIG_MMC_WBSD is not set
# CONFIG_MMC_TIFM_SD is not set
# CONFIG_MMC_SPI is not set
# CONFIG_MMC_SDRICOH_CS is not set
# CONFIG_MMC_CB710 is not set
# CONFIG_MMC_VIA_SDMMC is not set
CONFIG_MMC_VUB300=y
CONFIG_MMC_USHC=y
# CONFIG_MMC_USDHI6ROL0 is not set
CONFIG_MMC_REALTEK_USB=y
# CONFIG_MMC_CQHCI is not set
# CONFIG_MMC_HSQ is not set
# CONFIG_MMC_TOSHIBA_PCI is not set
# CONFIG_MMC_MTK is not set
# CONFIG_SCSI_UFSHCD is not set
CONFIG_MEMSTICK=y
# CONFIG_MEMSTICK_DEBUG is not set

#
# MemoryStick drivers
#
# CONFIG_MEMSTICK_UNSAFE_RESUME is not set
# CONFIG_MSPRO_BLOCK is not set
# CONFIG_MS_BLOCK is not set

#
# MemoryStick Host Controller Drivers
#
# CONFIG_MEMSTICK_TIFM_MS is not set
# CONFIG_MEMSTICK_JMICRON_38X is not set
# CONFIG_MEMSTICK_R592 is not set
CONFIG_MEMSTICK_REALTEK_USB=y
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
# CONFIG_LEDS_CLASS_FLASH is not set
CONFIG_LEDS_CLASS_MULTICOLOR=y
# CONFIG_LEDS_BRIGHTNESS_HW_CHANGED is not set

#
# LED drivers
#
# CONFIG_LEDS_AN30259A is not set
# CONFIG_LEDS_APU is not set
# CONFIG_LEDS_OSRAM_AMS_AS3668 is not set
# CONFIG_LEDS_AW200XX is not set
# CONFIG_LEDS_AW2013 is not set
# CONFIG_LEDS_BCM6328 is not set
# CONFIG_LEDS_BCM6358 is not set
# CONFIG_LEDS_CHT_WCOVE is not set
# CONFIG_LEDS_CR0014114 is not set
# CONFIG_LEDS_EL15203000 is not set
# CONFIG_LEDS_LM3530 is not set
# CONFIG_LEDS_LM3532 is not set
# CONFIG_LEDS_LM3642 is not set
# CONFIG_LEDS_LM3692X is not set
# CONFIG_LEDS_PCA9532 is not set
# CONFIG_LEDS_GPIO is not set
# CONFIG_LEDS_LP3944 is not set
# CONFIG_LEDS_LP3952 is not set
# CONFIG_LEDS_LP50XX is not set
# CONFIG_LEDS_LP55XX_COMMON is not set
# CONFIG_LEDS_LP8860 is not set
# CONFIG_LEDS_LP8864 is not set
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_PCA995X is not set
# CONFIG_LEDS_DAC124S085 is not set
# CONFIG_LEDS_REGULATOR is not set
# CONFIG_LEDS_BD2606MVV is not set
# CONFIG_LEDS_BD2802 is not set
# CONFIG_LEDS_INTEL_SS4200 is not set
# CONFIG_LEDS_LT3593 is not set
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
# CONFIG_LEDS_LM355x is not set
# CONFIG_LEDS_IS31FL319X is not set
# CONFIG_LEDS_IS31FL32XX is not set

#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)
#
# CONFIG_LEDS_BLINKM is not set
# CONFIG_LEDS_SYSCON is not set
# CONFIG_LEDS_MLXCPLD is not set
# CONFIG_LEDS_MLXREG is not set
# CONFIG_LEDS_USER is not set
# CONFIG_LEDS_NIC78BX is not set
# CONFIG_LEDS_SPI_BYTE is not set
# CONFIG_LEDS_LM3697 is not set
# CONFIG_LEDS_ST1202 is not set
# CONFIG_LEDS_LTC3220 is not set
# CONFIG_LEDS_LGM is not set

#
# Flash and Torch LED drivers
#

#
# RGB LED drivers
#
# CONFIG_LEDS_GROUP_MULTICOLOR is not set
# CONFIG_LEDS_KTD202X is not set
# CONFIG_LEDS_LP5812 is not set
# CONFIG_LEDS_LP5860_CORE is not set
# CONFIG_LEDS_LP5860_SPI is not set
# CONFIG_LEDS_NCP5623 is not set
# CONFIG_LEDS_MT6370_RGB is not set

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
# CONFIG_LEDS_TRIGGER_TIMER is not set
# CONFIG_LEDS_TRIGGER_ONESHOT is not set
# CONFIG_LEDS_TRIGGER_DISK is not set
# CONFIG_LEDS_TRIGGER_MTD is not set
# CONFIG_LEDS_TRIGGER_HEARTBEAT is not set
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
# CONFIG_LEDS_TRIGGER_ACTIVITY is not set
# CONFIG_LEDS_TRIGGER_GPIO is not set
# CONFIG_LEDS_TRIGGER_DEFAULT_ON is not set

#
# iptables trigger is under Netfilter config (LED target)
#
# CONFIG_LEDS_TRIGGER_TRANSIENT is not set
# CONFIG_LEDS_TRIGGER_CAMERA is not set
# CONFIG_LEDS_TRIGGER_PANIC is not set
# CONFIG_LEDS_TRIGGER_NETDEV is not set
# CONFIG_LEDS_TRIGGER_PATTERN is not set
# CONFIG_LEDS_TRIGGER_TTY is not set
# CONFIG_LEDS_TRIGGER_INPUT_EVENTS is not set

#
# Simatic LED drivers
#
# CONFIG_ACCESSIBILITY is not set
CONFIG_INFINIBAND=y
CONFIG_INFINIBAND_USER_MAD=y
CONFIG_INFINIBAND_USER_ACCESS=y
CONFIG_INFINIBAND_USER_ACCESS_CORE=y
CONFIG_INFINIBAND_USER_MEM=y
CONFIG_INFINIBAND_ON_DEMAND_PAGING=y
CONFIG_INFINIBAND_ADDR_TRANS=y
CONFIG_INFINIBAND_ADDR_TRANS_CONFIGFS=y
CONFIG_INFINIBAND_VIRT_DMA=y
# CONFIG_INFINIBAND_EFA is not set
# CONFIG_INFINIBAND_ERDMA is not set
CONFIG_MLX4_INFINIBAND=y
# CONFIG_INFINIBAND_MTHCA is not set
# CONFIG_INFINIBAND_OCRDMA is not set
# CONFIG_INFINIBAND_USNIC is not set
# CONFIG_INFINIBAND_VMWARE_PVRDMA is not set
# CONFIG_INFINIBAND_RDMAVT is not set
CONFIG_RDMA_RXE=y
CONFIG_RDMA_SIW=y
CONFIG_INFINIBAND_IPOIB=y
CONFIG_INFINIBAND_IPOIB_CM=y
CONFIG_INFINIBAND_IPOIB_DEBUG=y
# CONFIG_INFINIBAND_IPOIB_DEBUG_DATA is not set
CONFIG_INFINIBAND_SRP=y
# CONFIG_INFINIBAND_SRPT is not set
CONFIG_INFINIBAND_ISER=y
CONFIG_INFINIBAND_RTRS=y
CONFIG_INFINIBAND_RTRS_CLIENT=y
# CONFIG_INFINIBAND_RTRS_SERVER is not set
CONFIG_EDAC_ATOMIC_SCRUB=y
CONFIG_EDAC_SUPPORT=y
CONFIG_EDAC=y
# CONFIG_EDAC_DEBUG is not set
# CONFIG_EDAC_DECODE_MCE is not set
# CONFIG_EDAC_SCRUB is not set
# CONFIG_EDAC_ECS is not set
# CONFIG_EDAC_MEM_REPAIR is not set
# CONFIG_EDAC_E752X is not set
# CONFIG_EDAC_I82975X is not set
# CONFIG_EDAC_I3000 is not set
# CONFIG_EDAC_I3200 is not set
# CONFIG_EDAC_IE31200 is not set
# CONFIG_EDAC_X38 is not set
# CONFIG_EDAC_I5400 is not set
# CONFIG_EDAC_I7CORE is not set
# CONFIG_EDAC_I5100 is not set
# CONFIG_EDAC_I7300 is not set
# CONFIG_EDAC_SBRIDGE is not set
# CONFIG_EDAC_SKX is not set
# CONFIG_EDAC_I10NM is not set
# CONFIG_EDAC_IMH is not set
# CONFIG_EDAC_PND2 is not set
# CONFIG_EDAC_IGEN6 is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_MC146818_LIB=y
CONFIG_RTC_CLASS=y
# CONFIG_RTC_HCTOSYS is not set
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_SYSTOHC_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
# CONFIG_RTC_NVMEM is not set

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set

#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_ABB5ZES3 is not set
# CONFIG_RTC_DRV_ABEOZ9 is not set
# CONFIG_RTC_DRV_ABX80X is not set
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_HYM8563 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_MAX31335 is not set
# CONFIG_RTC_DRV_NCT3018Y is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_ISL12026 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8523 is not set
# CONFIG_RTC_DRV_PCF85363 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_TWL4030 is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8010 is not set
# CONFIG_RTC_DRV_RX8111 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
# CONFIG_RTC_DRV_RV3028 is not set
# CONFIG_RTC_DRV_RV3032 is not set
# CONFIG_RTC_DRV_RV8803 is not set
# CONFIG_RTC_DRV_SD2405AL is not set
# CONFIG_RTC_DRV_SD3078 is not set

#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
# CONFIG_RTC_DRV_DS1302 is not set
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1343 is not set
# CONFIG_RTC_DRV_DS1347 is not set
# CONFIG_RTC_DRV_DS1390 is not set
# CONFIG_RTC_DRV_MAX6916 is not set
# CONFIG_RTC_DRV_R9701 is not set
# CONFIG_RTC_DRV_RX4581 is not set
# CONFIG_RTC_DRV_RS5C348 is not set
# CONFIG_RTC_DRV_MAX6902 is not set
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_MCP795 is not set
CONFIG_RTC_I2C_AND_SPI=y

#
# SPI and I2C RTC drivers
#
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_PCF2127 is not set
# CONFIG_RTC_DRV_PCF85063 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set
# CONFIG_RTC_DRV_RX6110 is not set

#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1685_FAMILY is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_DS2404 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_ZYNQMP is not set

#
# on-CPU RTC drivers
#
# CONFIG_RTC_DRV_CADENCE is not set
# CONFIG_RTC_DRV_FTRTC010 is not set
# CONFIG_RTC_DRV_R7301 is not set
# CONFIG_RTC_DRV_GOLDFISH is not set

#
# HID Sensor RTC drivers
#
CONFIG_RTC_DRV_HID_SENSOR_TIME=y
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set

#
# DMA Devices
#
CONFIG_DMA_ENGINE=y
CONFIG_DMA_VIRTUAL_CHANNELS=y
CONFIG_DMA_ACPI=y
CONFIG_DMA_OF=y
# CONFIG_ALTERA_MSGDMA is not set
# CONFIG_DW_AXI_DMAC is not set
# CONFIG_FSL_EDMA is not set
CONFIG_INTEL_IDMA64=y
# CONFIG_INTEL_IDXD is not set
# CONFIG_INTEL_IDXD_COMPAT is not set
CONFIG_INTEL_IOATDMA=y
# CONFIG_PLX_DMA is not set
# CONFIG_SWITCHTEC_DMA is not set
# CONFIG_XILINX_DMA is not set
# CONFIG_XILINX_XDMA is not set
# CONFIG_XILINX_ZYNQMP_DPDMA is not set
# CONFIG_AMD_PTDMA is not set
# CONFIG_AMD_QDMA is not set
# CONFIG_QCOM_HIDMA_MGMT is not set
# CONFIG_QCOM_HIDMA is not set
CONFIG_DW_DMAC_CORE=y
# CONFIG_DW_DMAC is not set
# CONFIG_DW_DMAC_PCI is not set
# CONFIG_DW_EDMA is not set
CONFIG_HSU_DMA=y
# CONFIG_SF_PDMA is not set
# CONFIG_INTEL_LDMA is not set

#
# DMA Clients
#
CONFIG_ASYNC_TX_DMA=y
# CONFIG_DMATEST is not set
CONFIG_DMA_ENGINE_RAID=y

#
# DMABUF options
#
CONFIG_SYNC_FILE=y
CONFIG_SW_SYNC=y
CONFIG_UDMABUF=y
# CONFIG_DMABUF_DEBUG is not set
CONFIG_DMABUF_HEAPS=y
CONFIG_DMABUF_HEAPS_SYSTEM=y
# CONFIG_DMABUF_HEAPS_SYSTEM_CC_SHARED is not set
CONFIG_DMABUF_HEAPS_CMA=y
# end of DMABUF options

CONFIG_DCA=y
# CONFIG_UIO is not set
CONFIG_VFIO=y
CONFIG_VFIO_DEVICE_CDEV=y
# CONFIG_VFIO_GROUP is not set
# CONFIG_VFIO_NOIOMMU is not set
CONFIG_VFIO_VIRQFD=y
# CONFIG_VFIO_DEBUGFS is not set

#
# VFIO support for PCI devices
#
CONFIG_VFIO_PCI_CORE=y
CONFIG_VFIO_PCI_INTX=y
CONFIG_VFIO_PCI=y
# CONFIG_VFIO_PCI_VGA is not set
# CONFIG_VFIO_PCI_IGD is not set
# CONFIG_VIRTIO_VFIO_PCI is not set
# end of VFIO support for PCI devices

CONFIG_IRQ_BYPASS_MANAGER=y
# CONFIG_VIRT_DRIVERS is not set
CONFIG_VIRTIO_ANCHOR=y
CONFIG_VIRTIO=y
CONFIG_VIRTIO_PCI_LIB=y
CONFIG_VIRTIO_PCI_LIB_LEGACY=y
CONFIG_VIRTIO_MENU=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_PCI_ADMIN_LEGACY=y
CONFIG_VIRTIO_PCI_LEGACY=y
CONFIG_VIRTIO_VDPA=y
CONFIG_VIRTIO_PMEM=y
CONFIG_VIRTIO_BALLOON=y
CONFIG_VIRTIO_MEM=y
CONFIG_VIRTIO_INPUT=y
CONFIG_VIRTIO_MMIO=y
CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
CONFIG_VIRTIO_DMA_SHARED_BUFFER=y
# CONFIG_VIRTIO_DEBUG is not set
# CONFIG_VIRTIO_RTC is not set
CONFIG_VDPA=y
CONFIG_VDPA_SIM=y
CONFIG_VDPA_SIM_NET=y
CONFIG_VDPA_SIM_BLOCK=y
# CONFIG_VDPA_USER is not set
# CONFIG_IFCVF is not set
# CONFIG_MLX5_VDPA_STEERING_DEBUG is not set
CONFIG_VP_VDPA=y
# CONFIG_ALIBABA_ENI_VDPA is not set
# CONFIG_SNET_VDPA is not set
# CONFIG_OCTEONEP_VDPA is not set
CONFIG_VHOST_IOTLB=y
CONFIG_VHOST_RING=y
CONFIG_VHOST_TASK=y
CONFIG_VHOST=y
CONFIG_VHOST_MENU=y
CONFIG_VHOST_NET=y
# CONFIG_VHOST_SCSI is not set
CONFIG_VHOST_VSOCK=y
CONFIG_VHOST_VDPA=y
CONFIG_VHOST_CROSS_ENDIAN_LEGACY=y
CONFIG_VHOST_ENABLE_FORK_OWNER_CONTROL=y

#
# Microsoft Hyper-V guest support
#
# CONFIG_HYPERV is not set
# end of Microsoft Hyper-V guest support

CONFIG_GREYBUS=y
# CONFIG_GREYBUS_BEAGLEPLAY is not set
CONFIG_GREYBUS_ES2=y
CONFIG_COMEDI=y
# CONFIG_COMEDI_DEBUG is not set
CONFIG_COMEDI_DEFAULT_BUF_SIZE_KB=2048
CONFIG_COMEDI_DEFAULT_BUF_MAXSIZE_KB=20480
CONFIG_COMEDI_MISC_DRIVERS=y
CONFIG_COMEDI_BOND=y
CONFIG_COMEDI_TEST=y
CONFIG_COMEDI_PARPORT=y
CONFIG_COMEDI_ISA_DRIVERS=y
CONFIG_COMEDI_PCL711=y
CONFIG_COMEDI_PCL724=y
CONFIG_COMEDI_PCL726=y
CONFIG_COMEDI_PCL730=y
CONFIG_COMEDI_PCL812=y
CONFIG_COMEDI_PCL816=y
CONFIG_COMEDI_PCL818=y
CONFIG_COMEDI_PCM3724=y
CONFIG_COMEDI_AMPLC_DIO200_ISA=y
CONFIG_COMEDI_AMPLC_PC236_ISA=y
CONFIG_COMEDI_AMPLC_PC263_ISA=y
CONFIG_COMEDI_RTI800=y
CONFIG_COMEDI_RTI802=y
CONFIG_COMEDI_DAC02=y
CONFIG_COMEDI_DAS16M1=y
CONFIG_COMEDI_DAS08_ISA=y
# CONFIG_COMEDI_DAS16 is not set
CONFIG_COMEDI_DAS800=y
CONFIG_COMEDI_DAS1800=y
CONFIG_COMEDI_DAS6402=y
CONFIG_COMEDI_DT2801=y
CONFIG_COMEDI_DT2811=y
CONFIG_COMEDI_DT2814=y
CONFIG_COMEDI_DT2815=y
CONFIG_COMEDI_DT2817=y
CONFIG_COMEDI_DT282X=y
CONFIG_COMEDI_DMM32AT=y
CONFIG_COMEDI_FL512=y
CONFIG_COMEDI_AIO_AIO12_8=y
CONFIG_COMEDI_AIO_IIRO_16=y
# CONFIG_COMEDI_II_PCI20KC is not set
CONFIG_COMEDI_C6XDIGIO=y
CONFIG_COMEDI_MPC624=y
CONFIG_COMEDI_ADQ12B=y
CONFIG_COMEDI_NI_AT_A2150=y
CONFIG_COMEDI_NI_AT_AO=y
# CONFIG_COMEDI_NI_ATMIO is not set
CONFIG_COMEDI_NI_ATMIO16D=y
CONFIG_COMEDI_NI_LABPC_ISA=y
CONFIG_COMEDI_PCMAD=y
CONFIG_COMEDI_PCMDA12=y
CONFIG_COMEDI_PCMMIO=y
CONFIG_COMEDI_PCMUIO=y
CONFIG_COMEDI_MULTIQ3=y
CONFIG_COMEDI_S526=y
CONFIG_COMEDI_PCI_DRIVERS=y
CONFIG_COMEDI_8255_PCI=y
# CONFIG_COMEDI_ADDI_APCI_1032 is not set
# CONFIG_COMEDI_ADDI_APCI_1500 is not set
# CONFIG_COMEDI_ADDI_APCI_1516 is not set
# CONFIG_COMEDI_ADDI_APCI_1564 is not set
# CONFIG_COMEDI_ADDI_APCI_16XX is not set
# CONFIG_COMEDI_ADDI_APCI_2032 is not set
# CONFIG_COMEDI_ADDI_APCI_2200 is not set
# CONFIG_COMEDI_ADDI_APCI_3120 is not set
# CONFIG_COMEDI_ADDI_APCI_3501 is not set
# CONFIG_COMEDI_ADDI_APCI_3XXX is not set
# CONFIG_COMEDI_ADL_PCI6208 is not set
# CONFIG_COMEDI_ADL_PCI7250 is not set
# CONFIG_COMEDI_ADL_PCI7X3X is not set
# CONFIG_COMEDI_ADL_PCI8164 is not set
# CONFIG_COMEDI_ADL_PCI9111 is not set
CONFIG_COMEDI_ADL_PCI9118=y
# CONFIG_COMEDI_ADV_PCI1710 is not set
# CONFIG_COMEDI_ADV_PCI1720 is not set
# CONFIG_COMEDI_ADV_PCI1723 is not set
# CONFIG_COMEDI_ADV_PCI1724 is not set
# CONFIG_COMEDI_ADV_PCI1760 is not set
# CONFIG_COMEDI_ADV_PCI_DIO is not set
# CONFIG_COMEDI_AMPLC_DIO200_PCI is not set
# CONFIG_COMEDI_AMPLC_PC236_PCI is not set
# CONFIG_COMEDI_AMPLC_PC263_PCI is not set
# CONFIG_COMEDI_AMPLC_PCI224 is not set
# CONFIG_COMEDI_AMPLC_PCI230 is not set
# CONFIG_COMEDI_CONTEC_PCI_DIO is not set
# CONFIG_COMEDI_DAS08_PCI is not set
# CONFIG_COMEDI_DT3000 is not set
# CONFIG_COMEDI_DYNA_PCI10XX is not set
# CONFIG_COMEDI_GSC_HPDI is not set
# CONFIG_COMEDI_MF6X4 is not set
# CONFIG_COMEDI_ICP_MULTI is not set
# CONFIG_COMEDI_DAQBOARD2000 is not set
# CONFIG_COMEDI_JR3_PCI is not set
# CONFIG_COMEDI_KE_COUNTER is not set
# CONFIG_COMEDI_CB_PCIDAS64 is not set
# CONFIG_COMEDI_CB_PCIDAS is not set
# CONFIG_COMEDI_CB_PCIDDA is not set
# CONFIG_COMEDI_CB_PCIMDAS is not set
# CONFIG_COMEDI_CB_PCIMDDA is not set
# CONFIG_COMEDI_ME4000 is not set
# CONFIG_COMEDI_ME_DAQ is not set
# CONFIG_COMEDI_NI_6527 is not set
# CONFIG_COMEDI_NI_65XX is not set
# CONFIG_COMEDI_NI_660X is not set
# CONFIG_COMEDI_NI_670X is not set
CONFIG_COMEDI_NI_LABPC_PCI=y
# CONFIG_COMEDI_NI_PCIDIO is not set
# CONFIG_COMEDI_NI_PCIMIO is not set
# CONFIG_COMEDI_RTD520 is not set
# CONFIG_COMEDI_S626 is not set
CONFIG_COMEDI_PCMCIA_DRIVERS=y
# CONFIG_COMEDI_CB_DAS16_CS is not set
# CONFIG_COMEDI_DAS08_CS is not set
CONFIG_COMEDI_NI_DAQ_700_CS=y
# CONFIG_COMEDI_NI_DAQ_DIO24_CS is not set
CONFIG_COMEDI_NI_LABPC_CS=y
# CONFIG_COMEDI_NI_MIO_CS is not set
# CONFIG_COMEDI_QUATECH_DAQP_CS is not set
CONFIG_COMEDI_USB_DRIVERS=y
CONFIG_COMEDI_DT9812=y
CONFIG_COMEDI_NI_USB6501=y
CONFIG_COMEDI_USBDUX=y
CONFIG_COMEDI_USBDUXFAST=y
CONFIG_COMEDI_USBDUXSIGMA=y
CONFIG_COMEDI_VMK80XX=y
CONFIG_COMEDI_8254=y
CONFIG_COMEDI_8255=y
CONFIG_COMEDI_8255_SA=y
CONFIG_COMEDI_KCOMEDILIB=y
CONFIG_COMEDI_AMPLC_DIO200=y
CONFIG_COMEDI_AMPLC_PC236=y
CONFIG_COMEDI_DAS08=y
CONFIG_COMEDI_ISADMA=y
CONFIG_COMEDI_NI_LABPC=y
CONFIG_COMEDI_NI_LABPC_ISADMA=y
# CONFIG_COMEDI_TESTS is not set
# CONFIG_GPIB is not set
CONFIG_STAGING=y
# CONFIG_RTL8723BS is not set

#
# IIO staging drivers
#

#
# Accelerometers
#
# CONFIG_ADIS16203 is not set
# end of Accelerometers

#
# Analog to digital converters
#
# CONFIG_AD7816 is not set
# end of Analog to digital converters

#
# Analog digital bi-direction converters
#
# CONFIG_ADT7316 is not set
# end of Analog digital bi-direction converters

#
# Direct Digital Synthesis
#
# CONFIG_AD9832 is not set
# CONFIG_AD9834 is not set
# end of Direct Digital Synthesis

#
# Network Analyzer, Impedance Converters
#
# CONFIG_AD5933 is not set
# end of Network Analyzer, Impedance Converters
# end of IIO staging drivers

# CONFIG_FB_SM750 is not set
# CONFIG_STAGING_MEDIA is not set
# CONFIG_FB_TFT is not set
# CONFIG_MOST_COMPONENTS is not set
# CONFIG_GREYBUS_AUDIO is not set
# CONFIG_GREYBUS_BOOTROM is not set
# CONFIG_GREYBUS_FIRMWARE is not set
CONFIG_GREYBUS_HID=y
# CONFIG_GREYBUS_LOG is not set
# CONFIG_GREYBUS_LOOPBACK is not set
# CONFIG_GREYBUS_POWER is not set
# CONFIG_GREYBUS_RAW is not set
# CONFIG_GREYBUS_VIBRATOR is not set
CONFIG_GREYBUS_BRIDGED_PHY=y
# CONFIG_GREYBUS_GPIO is not set
# CONFIG_GREYBUS_I2C is not set
# CONFIG_GREYBUS_SDIO is not set
# CONFIG_GREYBUS_SPI is not set
# CONFIG_GREYBUS_UART is not set
CONFIG_GREYBUS_USB=y
# CONFIG_XIL_AXIS_FIFO is not set
# CONFIG_VME_BUS is not set
# CONFIG_GOLDFISH is not set
# CONFIG_CHROME_PLATFORMS is not set
# CONFIG_MELLANOX_PLATFORM is not set
CONFIG_SURFACE_PLATFORMS=y
# CONFIG_SURFACE3_WMI is not set
# CONFIG_SURFACE_3_POWER_OPREGION is not set
# CONFIG_SURFACE_ACPI_NOTIFY is not set
# CONFIG_SURFACE_AGGREGATOR_CDEV is not set
# CONFIG_SURFACE_AGGREGATOR_HUB is not set
CONFIG_SURFACE_AGGREGATOR_REGISTRY=y
# CONFIG_SURFACE_AGGREGATOR_TABLET_SWITCH is not set
# CONFIG_SURFACE_DTX is not set
# CONFIG_SURFACE_GPE is not set
# CONFIG_SURFACE_HOTPLUG is not set
# CONFIG_SURFACE_PLATFORM_PROFILE is not set
# CONFIG_SURFACE_PRO3_BUTTON is not set
CONFIG_SURFACE_AGGREGATOR=y
CONFIG_SURFACE_AGGREGATOR_BUS=y
CONFIG_X86_PLATFORM_DEVICES=y
CONFIG_WMI_BMOF=y
# CONFIG_HUAWEI_WMI is not set
# CONFIG_X86_PLATFORM_DRIVERS_UNIWILL is not set
# CONFIG_MXM_WMI is not set
# CONFIG_NVIDIA_WMI_EC_BACKLIGHT is not set
# CONFIG_XIAOMI_WMI is not set
# CONFIG_REDMI_WMI is not set
# CONFIG_GIGABYTE_WMI is not set
# CONFIG_BITLAND_MIFS_WMI is not set
# CONFIG_ACERHDF is not set
# CONFIG_ACER_WIRELESS is not set
# CONFIG_ACER_WMI is not set

#
# AMD HSMP Driver
#
# CONFIG_AMD_HSMP_ACPI is not set
# CONFIG_AMD_HSMP_PLAT is not set
# end of AMD HSMP Driver

# CONFIG_AMD_PMC is not set
# CONFIG_AMD_HFI is not set
# CONFIG_AMD_3D_VCACHE is not set
# CONFIG_AMD_WBRF is not set
# CONFIG_AMD_HALO_LED is not set
# CONFIG_AMD_ISP_PLATFORM is not set
# CONFIG_ADV_SWBUTTON is not set
# CONFIG_APPLE_GMUX is not set
# CONFIG_ASUS_LAPTOP is not set
# CONFIG_ASUS_WIRELESS is not set
# CONFIG_ASUS_ARMOURY is not set
CONFIG_ASUS_WMI=y
# CONFIG_ASUS_WMI_DEPRECATED_ATTRS is not set
# CONFIG_ASUS_NB_WMI is not set
CONFIG_ASUS_TF103C_DOCK=y
# CONFIG_AYANEO_EC is not set
CONFIG_EEEPC_LAPTOP=y
# CONFIG_EEEPC_WMI is not set
# CONFIG_X86_PLATFORM_DRIVERS_DELL is not set
# CONFIG_AMILO_RFKILL is not set
# CONFIG_FUJITSU_LAPTOP is not set
# CONFIG_FUJITSU_TABLET is not set
# CONFIG_GPD_POCKET_FAN is not set
# CONFIG_X86_PLATFORM_DRIVERS_HP is not set
# CONFIG_WIRELESS_HOTKEY is not set
# CONFIG_IBM_RTL is not set
# CONFIG_SENSORS_HDAPS is not set
# CONFIG_INTEL_ATOMISP2_PM is not set
# CONFIG_INTEL_IFS is not set
# CONFIG_INTEL_SAR_INT1092 is not set
# CONFIG_INTEL_SKL_INT3472 is not set

#
# Intel Speed Select Technology interface support
#
# CONFIG_INTEL_SPEED_SELECT_INTERFACE is not set
# end of Intel Speed Select Technology interface support

# CONFIG_INTEL_WMI_SBL_FW_UPDATE is not set
# CONFIG_INTEL_WMI_THUNDERBOLT is not set

#
# Intel Uncore Frequency Control
#
# CONFIG_INTEL_UNCORE_FREQ_CONTROL is not set
# end of Intel Uncore Frequency Control

# CONFIG_INTEL_HID_EVENT is not set
# CONFIG_INTEL_VBTN is not set
# CONFIG_INTEL_EHL_PSE_IO is not set
# CONFIG_INTEL_INT0002_VGPIO is not set
# CONFIG_INTEL_OAKTRAIL is not set
# CONFIG_INTEL_BXTWC_PMIC_TMU is not set
CONFIG_INTEL_CHTWC_INT33FE=y
CONFIG_INTEL_ISHTP_ECLITE=y
# CONFIG_INTEL_PUNIT_IPC is not set
# CONFIG_INTEL_RST is not set
# CONFIG_INTEL_SMARTCONNECT is not set
# CONFIG_INTEL_TURBO_MAX_3 is not set
# CONFIG_INTEL_VSEC is not set
# CONFIG_IDEAPAD_LAPTOP is not set
# CONFIG_LENOVO_WMI_HOTKEY_UTILITIES is not set
# CONFIG_LENOVO_WMI_CAMERA is not set
# CONFIG_LENOVO_YB9_KBDOCK is not set
# CONFIG_THINKPAD_ACPI is not set
# CONFIG_THINKPAD_LMI is not set
# CONFIG_YOGABOOK is not set
# CONFIG_YT2_1380 is not set
# CONFIG_LENOVO_WMI_GAMEZONE is not set
# CONFIG_LENOVO_WMI_TUNING is not set
# CONFIG_ACPI_QUICKSTART is not set
# CONFIG_MEEGOPAD_ANX7428 is not set
# CONFIG_MSI_EC is not set
# CONFIG_MSI_LAPTOP is not set
# CONFIG_MSI_WMI is not set
# CONFIG_MSI_WMI_PLATFORM is not set
# CONFIG_PCENGINES_APU2 is not set
# CONFIG_PORTWELL_EC is not set
# CONFIG_BARCO_P50_GPIO is not set
# CONFIG_SAMSUNG_GALAXYBOOK is not set
# CONFIG_SAMSUNG_LAPTOP is not set
# CONFIG_SAMSUNG_Q10 is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_TOSHIBA_BT_RFKILL is not set
# CONFIG_TOSHIBA_HAPS is not set
# CONFIG_TOSHIBA_WMI is not set
# CONFIG_ACPI_CMPC is not set
# CONFIG_COMPAL_LAPTOP is not set
# CONFIG_LG_LAPTOP is not set
# CONFIG_PANASONIC_LAPTOP is not set
# CONFIG_SONY_LAPTOP is not set
# CONFIG_SYSTEM76_ACPI is not set
# CONFIG_TOPSTAR_LAPTOP is not set
# CONFIG_SERIAL_MULTI_INSTANTIATE is not set
# CONFIG_INSPUR_PLATFORM_PROFILE is not set
# CONFIG_DASHARO_ACPI is not set
# CONFIG_INTEL_IPS is not set
CONFIG_INTEL_SCU_IPC=y
# CONFIG_INTEL_SCU_PCI is not set
# CONFIG_INTEL_SCU_PLATFORM is not set
# CONFIG_SIEMENS_SIMATIC_IPC is not set
# CONFIG_SILICOM_PLATFORM is not set
# CONFIG_WINMATE_FM07_KEYS is not set
# CONFIG_OXP_EC is not set
# CONFIG_TUXEDO_NB04_WMI_AB is not set
CONFIG_P2SB=y
CONFIG_ACPI_WMI=y
# CONFIG_ACPI_WMI_LEGACY_DEVICE_NAMES is not set
CONFIG_HAVE_CLK=y
CONFIG_HAVE_CLK_PREPARE=y
CONFIG_COMMON_CLK=y
# CONFIG_LMK04832 is not set
# CONFIG_COMMON_CLK_MAX9485 is not set
# CONFIG_COMMON_CLK_SI5341 is not set
# CONFIG_COMMON_CLK_SI5351 is not set
# CONFIG_COMMON_CLK_SI514 is not set
# CONFIG_COMMON_CLK_SI544 is not set
# CONFIG_COMMON_CLK_SI570 is not set
# CONFIG_COMMON_CLK_CDCE706 is not set
# CONFIG_COMMON_CLK_CDCE925 is not set
# CONFIG_COMMON_CLK_CS2000_CP is not set
# CONFIG_CLK_TWL is not set
# CONFIG_COMMON_CLK_AXI_CLKGEN is not set
# CONFIG_COMMON_CLK_RS9_PCIE is not set
# CONFIG_COMMON_CLK_SI521XX is not set
# CONFIG_COMMON_CLK_VC3 is not set
# CONFIG_COMMON_CLK_VC5 is not set
# CONFIG_COMMON_CLK_VC7 is not set
# CONFIG_COMMON_CLK_FIXED_MMIO is not set

#
# Cixtech Audio Subsystem Clock Driver
#
# end of Cixtech Audio Subsystem Clock Driver

# CONFIG_CLK_LGM_CGU is not set
# CONFIG_XILINX_VCU is not set
# CONFIG_COMMON_CLK_XLNX_CLKWZRD is not set
# CONFIG_HWSPINLOCK is not set

#
# Clock Source drivers
#
CONFIG_CLKEVT_I8253=y
CONFIG_I8253_LOCK=y
CONFIG_CLKBLD_I8253=y
# end of Clock Source drivers

CONFIG_MAILBOX=y
# CONFIG_PLATFORM_MHU is not set
CONFIG_PCC=y
# CONFIG_ALTERA_MBOX is not set
# CONFIG_MAILBOX_TEST is not set
CONFIG_IOMMU_IOVA=y
CONFIG_IOMMU_API=y
CONFIG_IOMMUFD_DRIVER=y
CONFIG_IOMMU_SUPPORT=y

#
# Generic IOMMU Pagetable Support
#
# end of Generic IOMMU Pagetable Support

# CONFIG_IOMMU_DEBUGFS is not set
# CONFIG_IOMMU_DEFAULT_DMA_STRICT is not set
CONFIG_IOMMU_DEFAULT_DMA_LAZY=y
# CONFIG_IOMMU_DEFAULT_PASSTHROUGH is not set
CONFIG_OF_IOMMU=y
CONFIG_IOMMU_DMA=y
CONFIG_IOMMU_SVA=y
CONFIG_IOMMU_IOPF=y
CONFIG_AMD_IOMMU=y
# CONFIG_AMD_IOMMU_IOMMUFD is not set
CONFIG_DMAR_TABLE=y
CONFIG_INTEL_IOMMU=y
CONFIG_INTEL_IOMMU_SVM=y
CONFIG_INTEL_IOMMU_DEFAULT_ON=y
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y
CONFIG_INTEL_IOMMU_PERF_EVENTS=y
CONFIG_IOMMUFD_DRIVER_CORE=y
CONFIG_IOMMUFD=y
CONFIG_IOMMUFD_TEST=y
CONFIG_IRQ_REMAP=y
# CONFIG_VIRTIO_IOMMU is not set
CONFIG_GENERIC_PT=y
CONFIG_DEBUG_GENERIC_PT=y
CONFIG_IOMMU_PT=y
CONFIG_IOMMU_PT_AMDV1=y
CONFIG_IOMMU_PT_VTDSS=y
# CONFIG_IOMMU_PT_RISCV64 is not set
CONFIG_IOMMU_PT_X86_64=y

#
# Remoteproc drivers
#
# CONFIG_REMOTEPROC is not set
# end of Remoteproc drivers

#
# Rpmsg drivers
#
# CONFIG_RPMSG_QCOM_GLINK_RPM is not set
# CONFIG_RPMSG_VIRTIO is not set
# end of Rpmsg drivers

CONFIG_SOUNDWIRE=y

#
# SoundWire Devices
#
# CONFIG_SOUNDWIRE_AMD is not set
# CONFIG_SOUNDWIRE_INTEL is not set
# CONFIG_SOUNDWIRE_QCOM is not set

#
# SOC (System On Chip) specific Drivers
#

#
# Amlogic SoC drivers
#
# end of Amlogic SoC drivers

#
# Broadcom SoC drivers
#
# end of Broadcom SoC drivers

#
# NXP/Freescale QorIQ SoC drivers
#
# end of NXP/Freescale QorIQ SoC drivers

#
# fujitsu SoC drivers
#
# end of fujitsu SoC drivers

#
# i.MX SoC drivers
#
# end of i.MX SoC drivers

#
# Enable LiteX SoC Builder specific drivers
#
# CONFIG_LITEX_SOC_CONTROLLER is not set
# end of Enable LiteX SoC Builder specific drivers

# CONFIG_WPCM450_SOC is not set
CONFIG_QCOM_QMI_HELPERS=y
# CONFIG_SOC_TI is not set

#
# Xilinx SoC drivers
#
# end of Xilinx SoC drivers
# end of SOC (System On Chip) specific Drivers

#
# PM Domains
#

#
# Amlogic PM Domains
#
# end of Amlogic PM Domains

#
# Broadcom PM Domains
#
# end of Broadcom PM Domains

#
# i.MX PM Domains
#
# end of i.MX PM Domains

#
# Qualcomm PM Domains
#
# end of Qualcomm PM Domains
# end of PM Domains

# CONFIG_PM_DEVFREQ is not set
CONFIG_EXTCON=y

#
# Extcon Device Drivers
#
# CONFIG_EXTCON_ADC_JACK is not set
# CONFIG_EXTCON_FSA9480 is not set
# CONFIG_EXTCON_GPIO is not set
# CONFIG_EXTCON_INTEL_INT3496 is not set
CONFIG_EXTCON_INTEL_CHT_WC=y
# CONFIG_EXTCON_LC824206XA is not set
# CONFIG_EXTCON_MAX3355 is not set
# CONFIG_EXTCON_MAX14526 is not set
CONFIG_EXTCON_PTN5150=y
# CONFIG_EXTCON_RT8973A is not set
# CONFIG_EXTCON_SM5502 is not set
# CONFIG_EXTCON_USB_GPIO is not set
CONFIG_EXTCON_USBC_TUSB320=y
# CONFIG_MEMORY is not set
CONFIG_IIO=y
CONFIG_IIO_BUFFER=y
# CONFIG_IIO_BUFFER_CB is not set
# CONFIG_IIO_BUFFER_DMA is not set
# CONFIG_IIO_BUFFER_DMAENGINE is not set
# CONFIG_IIO_BUFFER_HW_CONSUMER is not set
CONFIG_IIO_KFIFO_BUF=y
CONFIG_IIO_TRIGGERED_BUFFER=y
# CONFIG_IIO_CONFIGFS is not set
CONFIG_IIO_TRIGGER=y
CONFIG_IIO_CONSUMERS_PER_TRIGGER=2
# CONFIG_IIO_SW_DEVICE is not set
# CONFIG_IIO_SW_TRIGGER is not set
# CONFIG_IIO_TRIGGERED_EVENT is not set

#
# Accelerometers
#
# CONFIG_ADIS16201 is not set
# CONFIG_ADIS16209 is not set
# CONFIG_ADXL313_I2C is not set
# CONFIG_ADXL313_SPI is not set
# CONFIG_ADXL345_I2C is not set
# CONFIG_ADXL345_SPI is not set
# CONFIG_ADXL355_I2C is not set
# CONFIG_ADXL355_SPI is not set
# CONFIG_ADXL367_SPI is not set
# CONFIG_ADXL367_I2C is not set
# CONFIG_ADXL372_SPI is not set
# CONFIG_ADXL372_I2C is not set
# CONFIG_ADXL380_SPI is not set
# CONFIG_ADXL380_I2C is not set
# CONFIG_BMA180 is not set
# CONFIG_BMA220 is not set
# CONFIG_BMA400 is not set
# CONFIG_BMC150_ACCEL is not set
# CONFIG_BMI088_ACCEL is not set
# CONFIG_DA280 is not set
# CONFIG_DA311 is not set
# CONFIG_DMARD06 is not set
# CONFIG_DMARD09 is not set
# CONFIG_DMARD10 is not set
# CONFIG_FXLS8962AF_I2C is not set
# CONFIG_FXLS8962AF_SPI is not set
CONFIG_HID_SENSOR_ACCEL_3D=y
# CONFIG_IIO_ST_ACCEL_3AXIS is not set
# CONFIG_IIO_KX022A_SPI is not set
# CONFIG_IIO_KX022A_I2C is not set
# CONFIG_KXSD9 is not set
# CONFIG_KXCJK1013 is not set
# CONFIG_MC3230 is not set
# CONFIG_MMA7455_I2C is not set
# CONFIG_MMA7455_SPI is not set
# CONFIG_MMA7660 is not set
# CONFIG_MMA8452 is not set
# CONFIG_MMA9551 is not set
# CONFIG_MMA9553 is not set
# CONFIG_MSA311 is not set
# CONFIG_MXC4005 is not set
# CONFIG_MXC6255 is not set
# CONFIG_SCA3000 is not set
# CONFIG_SCA3300 is not set
# CONFIG_STK8312 is not set
# CONFIG_STK8BA50 is not set
# end of Accelerometers

#
# Analog to digital converters
#
# CONFIG_AD4000 is not set
# CONFIG_AD4080 is not set
# CONFIG_AD4130 is not set
# CONFIG_AD4134 is not set
# CONFIG_AD4170_4 is not set
# CONFIG_AD4691 is not set
# CONFIG_AD4695 is not set
# CONFIG_AD7091R5 is not set
# CONFIG_AD7091R8 is not set
# CONFIG_AD7124 is not set
# CONFIG_AD7173 is not set
# CONFIG_AD7191 is not set
# CONFIG_AD7192 is not set
# CONFIG_AD7266 is not set
# CONFIG_AD7280 is not set
# CONFIG_AD7291 is not set
# CONFIG_AD7292 is not set
# CONFIG_AD7298 is not set
# CONFIG_AD7380 is not set
# CONFIG_AD7476 is not set
# CONFIG_AD7606_IFACE_PARALLEL is not set
# CONFIG_AD7606_IFACE_SPI is not set
# CONFIG_AD7766 is not set
# CONFIG_AD7768_1 is not set
# CONFIG_AD7779 is not set
# CONFIG_AD7780 is not set
# CONFIG_AD7791 is not set
# CONFIG_AD7793 is not set
# CONFIG_AD7887 is not set
# CONFIG_AD7923 is not set
# CONFIG_AD7944 is not set
# CONFIG_AD7949 is not set
# CONFIG_AD799X is not set
# CONFIG_AD9467 is not set
# CONFIG_ADE9000 is not set
# CONFIG_CC10001_ADC is not set
CONFIG_DLN2_ADC=y
# CONFIG_ENVELOPE_DETECTOR is not set
# CONFIG_GEHC_PMC_ADC is not set
# CONFIG_HI8435 is not set
# CONFIG_HX711 is not set
# CONFIG_INA2XX_ADC is not set
# CONFIG_LTC2309 is not set
# CONFIG_LTC2471 is not set
# CONFIG_LTC2485 is not set
# CONFIG_LTC2496 is not set
# CONFIG_LTC2497 is not set
# CONFIG_MAX1027 is not set
# CONFIG_MAX11100 is not set
# CONFIG_MAX1118 is not set
# CONFIG_MAX11205 is not set
# CONFIG_MAX11410 is not set
# CONFIG_MAX1241 is not set
# CONFIG_MAX1363 is not set
# CONFIG_MAX14001 is not set
# CONFIG_MAX34408 is not set
# CONFIG_MAX9611 is not set
# CONFIG_MCP320X is not set
# CONFIG_MCP3422 is not set
# CONFIG_MCP3564 is not set
# CONFIG_MCP3911 is not set
# CONFIG_MEDIATEK_MT6360_ADC is not set
# CONFIG_MEDIATEK_MT6370_ADC is not set
# CONFIG_NAU7802 is not set
# CONFIG_NCT7201 is not set
# CONFIG_PAC1921 is not set
# CONFIG_PAC1934 is not set
# CONFIG_ROHM_BD79112 is not set
# CONFIG_ROHM_BD79124 is not set
# CONFIG_RICHTEK_RTQ6056 is not set
# CONFIG_SD_ADC_MODULATOR is not set
# CONFIG_TI_ADC081C is not set
# CONFIG_TI_ADC0832 is not set
# CONFIG_TI_ADC084S021 is not set
# CONFIG_TI_ADC108S102 is not set
# CONFIG_TI_ADC12138 is not set
# CONFIG_TI_ADC128S052 is not set
# CONFIG_TI_ADC161S626 is not set
# CONFIG_TI_ADS1015 is not set
# CONFIG_TI_ADS1018 is not set
# CONFIG_TI_ADS1100 is not set
# CONFIG_TI_ADS1119 is not set
# CONFIG_TI_ADS112C14 is not set
# CONFIG_TI_ADS124S08 is not set
# CONFIG_TI_ADS1298 is not set
# CONFIG_TI_ADS131E08 is not set
# CONFIG_TI_ADS131M02 is not set
# CONFIG_TI_ADS7138 is not set
# CONFIG_TI_ADS7924 is not set
# CONFIG_TI_ADS7950 is not set
# CONFIG_TI_ADS8344 is not set
# CONFIG_TI_ADS8688 is not set
# CONFIG_TI_LMP92064 is not set
# CONFIG_TI_TLC4541 is not set
# CONFIG_TI_TSC2046 is not set
# CONFIG_TWL4030_MADC is not set
# CONFIG_TWL6030_GPADC is not set
# CONFIG_VERSAL_SYSMON_I2C is not set
# CONFIG_VF610_ADC is not set
CONFIG_VIPERBOARD_ADC=y
# CONFIG_XILINX_XADC is not set
# end of Analog to digital converters

#
# Analog to digital and digital to analog converters
#
# CONFIG_AD74115 is not set
# CONFIG_AD74413R is not set
# end of Analog to digital and digital to analog converters

#
# Analog Front Ends
#
# CONFIG_IIO_RESCALE is not set
# end of Analog Front Ends

#
# Amplifiers
#
# CONFIG_AD8366 is not set
# CONFIG_ADA4250 is not set
# CONFIG_ADL8113 is not set
# CONFIG_HMC425 is not set
# end of Amplifiers

#
# Capacitance to digital converters
#
# CONFIG_AD7150 is not set
# CONFIG_AD7746 is not set
# end of Capacitance to digital converters

#
# Chemical Sensors
#
# CONFIG_AOSONG_AGS02MA is not set
# CONFIG_ATLAS_PH_SENSOR is not set
# CONFIG_ATLAS_EZO_SENSOR is not set
# CONFIG_BME680 is not set
# CONFIG_CCS811 is not set
# CONFIG_ENS160 is not set
# CONFIG_IAQCORE is not set
# CONFIG_MHZ19B is not set
# CONFIG_PMS7003 is not set
# CONFIG_SCD30_CORE is not set
# CONFIG_SCD4X is not set
# CONFIG_SEN0322 is not set
# CONFIG_SENSIRION_SGP30 is not set
# CONFIG_SENSIRION_SGP40 is not set
# CONFIG_SPS30_I2C is not set
# CONFIG_SPS30_SERIAL is not set
# CONFIG_SENSEAIR_SUNRISE_CO2 is not set
# CONFIG_VZ89X is not set
# end of Chemical Sensors

#
# Hid Sensor IIO Common
#
CONFIG_HID_SENSOR_IIO_COMMON=y
CONFIG_HID_SENSOR_IIO_TRIGGER=y
# end of Hid Sensor IIO Common

#
# IIO SCMI Sensors
#
# end of IIO SCMI Sensors

#
# SSP Sensor Common
#
# CONFIG_IIO_SSP_SENSORHUB is not set
# end of SSP Sensor Common

#
# Digital to analog converters
#
# CONFIG_AD3530R is not set
# CONFIG_AD3552R_HS is not set
# CONFIG_AD3552R is not set
# CONFIG_AD5064 is not set
# CONFIG_AD5360 is not set
# CONFIG_AD5380 is not set
# CONFIG_AD5421 is not set
# CONFIG_AD5446_SPI is not set
# CONFIG_AD5446_I2C is not set
# CONFIG_AD5449 is not set
# CONFIG_AD5592R is not set
# CONFIG_AD5593R is not set
# CONFIG_AD5504 is not set
# CONFIG_AD5624R_SPI is not set
# CONFIG_AD5706R is not set
# CONFIG_AD9739A is not set
# CONFIG_LTC2688 is not set
# CONFIG_AD5686_SPI is not set
# CONFIG_AD5696_I2C is not set
# CONFIG_AD5755 is not set
# CONFIG_AD5758 is not set
# CONFIG_AD5761 is not set
# CONFIG_AD5764 is not set
# CONFIG_AD5766 is not set
# CONFIG_AD5770R is not set
# CONFIG_AD5791 is not set
# CONFIG_AD7293 is not set
# CONFIG_AD7303 is not set
# CONFIG_AD8460 is not set
# CONFIG_AD8801 is not set
# CONFIG_BD79703 is not set
# CONFIG_CIO_DAC is not set
# CONFIG_DPOT_DAC is not set
# CONFIG_DS4424 is not set
# CONFIG_LTC1660 is not set
# CONFIG_LTC2632 is not set
# CONFIG_LTC2664 is not set
# CONFIG_M62332 is not set
# CONFIG_MAX517 is not set
# CONFIG_MAX22007 is not set
# CONFIG_MAX5522 is not set
# CONFIG_MAX5821 is not set
# CONFIG_MCP4725 is not set
# CONFIG_MCP4728 is not set
# CONFIG_MCP47A1 is not set
# CONFIG_MCP47FEB02 is not set
# CONFIG_MCP4821 is not set
# CONFIG_MCP4922 is not set
# CONFIG_TI_DAC082S085 is not set
# CONFIG_TI_DAC5571 is not set
# CONFIG_TI_DAC7311 is not set
# CONFIG_TI_DAC7612 is not set
# CONFIG_VF610_DAC is not set
# end of Digital to analog converters

#
# IIO dummy driver
#
# end of IIO dummy driver

#
# Filters
#
# CONFIG_ADMV8818 is not set
# end of Filters

#
# Flow sensors
#
# CONFIG_SENSIRION_SLF3S is not set
# end of Flow sensors

#
# Frequency Synthesizers DDS/PLL
#

#
# Clock Generator/Distribution
#
# CONFIG_AD9523 is not set
# end of Clock Generator/Distribution

#
# Phase-Locked Loop (PLL) frequency synthesizers
#
# CONFIG_ADF41513 is not set
# CONFIG_ADF4350 is not set
# CONFIG_ADF4371 is not set
# CONFIG_ADF4377 is not set
# CONFIG_ADMFM2000 is not set
# CONFIG_ADMV1013 is not set
# CONFIG_ADMV1014 is not set
# CONFIG_ADMV4420 is not set
# CONFIG_ADRF6780 is not set
# end of Phase-Locked Loop (PLL) frequency synthesizers
# end of Frequency Synthesizers DDS/PLL

#
# Digital gyroscope sensors
#
# CONFIG_ADIS16080 is not set
# CONFIG_ADIS16130 is not set
# CONFIG_ADIS16136 is not set
# CONFIG_ADIS16260 is not set
# CONFIG_ADXRS290 is not set
# CONFIG_ADXRS450 is not set
# CONFIG_BMG160 is not set
# CONFIG_FXAS21002C is not set
CONFIG_HID_SENSOR_GYRO_3D=y
# CONFIG_MPU3050_I2C is not set
# CONFIG_IIO_ST_GYRO_3AXIS is not set
# CONFIG_ITG3200 is not set
# end of Digital gyroscope sensors

#
# Health Sensors
#

#
# Heart Rate Monitors
#
# CONFIG_AFE4403 is not set
# CONFIG_AFE4404 is not set
# CONFIG_MAX30100 is not set
# CONFIG_MAX30102 is not set
# end of Heart Rate Monitors
# end of Health Sensors

#
# Humidity sensors
#
# CONFIG_AM2315 is not set
# CONFIG_DHT11 is not set
# CONFIG_ENS210 is not set
# CONFIG_HDC100X is not set
# CONFIG_HDC2010 is not set
# CONFIG_HDC3020 is not set
CONFIG_HID_SENSOR_HUMIDITY=y
# CONFIG_HTS221 is not set
# CONFIG_HTU21 is not set
# CONFIG_SI7005 is not set
# CONFIG_SI7020 is not set
# end of Humidity sensors

#
# Inertial measurement units
#
# CONFIG_ADIS16400 is not set
# CONFIG_ADIS16460 is not set
# CONFIG_ADIS16475 is not set
# CONFIG_ADIS16480 is not set
# CONFIG_ADIS16550 is not set
# CONFIG_BMI160_I2C is not set
# CONFIG_BMI160_SPI is not set
# CONFIG_BMI270_I2C is not set
# CONFIG_BMI270_SPI is not set
# CONFIG_BMI323_I2C is not set
# CONFIG_BMI323_SPI is not set
# CONFIG_BOSCH_BNO055_SERIAL is not set
# CONFIG_BOSCH_BNO055_I2C is not set
# CONFIG_FXOS8700_I2C is not set
# CONFIG_FXOS8700_SPI is not set
# CONFIG_KMX61 is not set
# CONFIG_INV_ICM42600_I2C is not set
# CONFIG_INV_ICM42600_SPI is not set
# CONFIG_INV_ICM42607_I2C is not set
# CONFIG_INV_ICM42607_SPI is not set
# CONFIG_INV_ICM45600_I2C is not set
# CONFIG_INV_ICM45600_SPI is not set
# CONFIG_INV_MPU6050_I2C is not set
# CONFIG_INV_MPU6050_SPI is not set
# CONFIG_SMI240 is not set
# CONFIG_SMI330_I2C is not set
# CONFIG_SMI330_SPI is not set
# CONFIG_IIO_ST_LSM6DSX is not set
# CONFIG_IIO_ST_LSM9DS0 is not set
# end of Inertial measurement units

#
# Light sensors
#
# CONFIG_ACPI_ALS is not set
# CONFIG_ADJD_S311 is not set
# CONFIG_ADUX1020 is not set
# CONFIG_AL3000A is not set
# CONFIG_AL3010 is not set
# CONFIG_AL3320A is not set
# CONFIG_APDS9160 is not set
# CONFIG_APDS9300 is not set
# CONFIG_APDS9306 is not set
# CONFIG_APDS9960 is not set
# CONFIG_APDS9999 is not set
# CONFIG_AS73211 is not set
# CONFIG_BH1745 is not set
# CONFIG_BH1750 is not set
# CONFIG_BH1780 is not set
# CONFIG_CM32181 is not set
# CONFIG_CM3232 is not set
# CONFIG_CM3323 is not set
# CONFIG_CM3605 is not set
# CONFIG_CM36651 is not set
# CONFIG_GP2AP002 is not set
# CONFIG_GP2AP020A00F is not set
# CONFIG_SENSORS_ISL29018 is not set
# CONFIG_SENSORS_ISL29028 is not set
# CONFIG_ISL29125 is not set
# CONFIG_ISL76682 is not set
CONFIG_HID_SENSOR_ALS=y
CONFIG_HID_SENSOR_PROX=y
# CONFIG_JSA1212 is not set
# CONFIG_ROHM_BU27034 is not set
# CONFIG_RPR0521 is not set
# CONFIG_LTR390 is not set
# CONFIG_LTR501 is not set
# CONFIG_LTRF216A is not set
# CONFIG_LV0104CS is not set
# CONFIG_MAX44000 is not set
# CONFIG_MAX44009 is not set
# CONFIG_NOA1305 is not set
# CONFIG_OPT3001 is not set
# CONFIG_OPT4001 is not set
# CONFIG_OPT4060 is not set
# CONFIG_PA12203001 is not set
# CONFIG_SI1133 is not set
# CONFIG_SI1145 is not set
# CONFIG_STK3310 is not set
# CONFIG_ST_UVIS25 is not set
# CONFIG_TCS3414 is not set
# CONFIG_TCS3472 is not set
# CONFIG_SENSORS_TSL2563 is not set
# CONFIG_TSL2583 is not set
# CONFIG_TSL2591 is not set
# CONFIG_TSL2772 is not set
# CONFIG_TSL4531 is not set
# CONFIG_US5182D is not set
# CONFIG_VCNL4000 is not set
# CONFIG_VCNL4035 is not set
# CONFIG_VEML3235 is not set
# CONFIG_VEML3328 is not set
# CONFIG_VEML6030 is not set
# CONFIG_VEML6040 is not set
# CONFIG_VEML6046X00 is not set
# CONFIG_VEML6070 is not set
# CONFIG_VEML6075 is not set
# CONFIG_VL6180 is not set
# CONFIG_ZOPT2201 is not set
# end of Light sensors

#
# Magnetometer sensors
#
# CONFIG_AF8133J is not set
# CONFIG_AK8974 is not set
# CONFIG_AK8975 is not set
# CONFIG_AK09911 is not set
# CONFIG_ALS31300 is not set
# CONFIG_BMC150_MAGN_I2C is not set
# CONFIG_BMC150_MAGN_SPI is not set
# CONFIG_MAG3110 is not set
CONFIG_HID_SENSOR_MAGNETOMETER_3D=y
# CONFIG_MMC35240 is not set
# CONFIG_MMC5633 is not set
# CONFIG_MMC5983 is not set
# CONFIG_IIO_ST_MAGN_3AXIS is not set
# CONFIG_INFINEON_TLV493D is not set
# CONFIG_QMC5883L is not set
# CONFIG_QMC6308 is not set
# CONFIG_SENSORS_HMC5843_I2C is not set
# CONFIG_SENSORS_HMC5843_SPI is not set
# CONFIG_SENSORS_RM3100_I2C is not set
# CONFIG_SENSORS_RM3100_SPI is not set
# CONFIG_SI7210 is not set
# CONFIG_TI_TMAG5273 is not set
# CONFIG_YAMAHA_YAS530 is not set
# end of Magnetometer sensors

#
# Multiplexers
#
# CONFIG_IIO_MUX is not set
# end of Multiplexers

#
# Inclinometer sensors
#
CONFIG_HID_SENSOR_INCLINOMETER_3D=y
CONFIG_HID_SENSOR_DEVICE_ROTATION=y
# end of Inclinometer sensors

#
# Triggers - standalone
#
# CONFIG_IIO_SYSFS_TRIGGER is not set
# end of Triggers - standalone

#
# Linear and angular position sensors
#
CONFIG_HID_SENSOR_CUSTOM_INTEL_HINGE=y
# end of Linear and angular position sensors

#
# Digital potentiometers
#
# CONFIG_AD5110 is not set
# CONFIG_AD5272 is not set
# CONFIG_DS1803 is not set
# CONFIG_MAX5432 is not set
# CONFIG_MAX5481 is not set
# CONFIG_MAX5487 is not set
# CONFIG_MCP4018 is not set
# CONFIG_MCP4131 is not set
# CONFIG_MCP4531 is not set
# CONFIG_MCP41010 is not set
# CONFIG_TPL0102 is not set
# CONFIG_X9250 is not set
# end of Digital potentiometers

#
# Digital potentiostats
#
# CONFIG_LMP91000 is not set
# end of Digital potentiostats

#
# Pressure sensors
#
# CONFIG_ABP060MG is not set
# CONFIG_ABP2030PA_I2C is not set
# CONFIG_ABP2030PA_SPI is not set
# CONFIG_ROHM_BM1390 is not set
# CONFIG_BMP280 is not set
# CONFIG_DLHL60D is not set
# CONFIG_DPS310 is not set
CONFIG_HID_SENSOR_PRESS=y
# CONFIG_HP03 is not set
# CONFIG_HSC030PA is not set
# CONFIG_ICP10100 is not set
# CONFIG_MPL115_I2C is not set
# CONFIG_MPL115_SPI is not set
# CONFIG_MPL3115 is not set
# CONFIG_MPRLS0025PA_I2C is not set
# CONFIG_MPRLS0025PA_SPI is not set
# CONFIG_MS5611 is not set
# CONFIG_MS5637 is not set
# CONFIG_SDP500 is not set
# CONFIG_IIO_ST_PRESS is not set
# CONFIG_T5403 is not set
# CONFIG_HP206C is not set
# CONFIG_ZPA2326 is not set
# CONFIG_ADP810 is not set
# end of Pressure sensors

#
# Lightning sensors
#
# CONFIG_AS3935 is not set
# end of Lightning sensors

#
# Proximity and distance sensors
#
# CONFIG_D3323AA is not set
# CONFIG_HX9023S is not set
# CONFIG_IRSD200 is not set
# CONFIG_ISL29501 is not set
# CONFIG_LIDAR_LITE_V2 is not set
# CONFIG_MB1232 is not set
# CONFIG_PING is not set
# CONFIG_RFD77402 is not set
# CONFIG_SRF04 is not set
# CONFIG_SX9310 is not set
# CONFIG_SX9324 is not set
# CONFIG_SX9360 is not set
# CONFIG_SX9500 is not set
# CONFIG_SRF08 is not set
# CONFIG_VCNL3020 is not set
# CONFIG_VL53L0X_I2C is not set
# CONFIG_VL53L1X_I2C is not set
# CONFIG_AW96103 is not set
# end of Proximity and distance sensors

#
# Resolver to digital converters
#
# CONFIG_AD2S90 is not set
# CONFIG_AD2S1200 is not set
# CONFIG_AD2S1210 is not set
# end of Resolver to digital converters

#
# Temperature sensors
#
# CONFIG_LTC2983 is not set
# CONFIG_MAXIM_THERMOCOUPLE is not set
CONFIG_HID_SENSOR_TEMP=y
# CONFIG_MLX90614 is not set
# CONFIG_MLX90632 is not set
# CONFIG_MLX90635 is not set
# CONFIG_TMP006 is not set
# CONFIG_TMP007 is not set
# CONFIG_TMP117 is not set
# CONFIG_TSYS01 is not set
# CONFIG_TSYS02D is not set
# CONFIG_MAX30208 is not set
# CONFIG_MAX31856 is not set
# CONFIG_MAX31865 is not set
# CONFIG_MCP9600 is not set
# end of Temperature sensors

# CONFIG_NTB is not set
# CONFIG_PWM is not set

#
# IRQ chip support
#
CONFIG_IRQCHIP=y
CONFIG_IRQ_MSI_LIB=y
# CONFIG_AL_FIC is not set
# CONFIG_XILINX_INTC is not set
# end of IRQ chip support

# CONFIG_IPACK_BUS is not set
CONFIG_RESET_CONTROLLER=y
# CONFIG_RESET_GPIO is not set
# CONFIG_RESET_INTEL_GW is not set
# CONFIG_RESET_SIMPLE is not set
# CONFIG_RESET_TI_SYSCON is not set
# CONFIG_RESET_TI_TPS380X is not set

#
# PHY Subsystem
#
CONFIG_GENERIC_PHY=y
# CONFIG_PHY_CAN_TRANSCEIVER is not set
CONFIG_PHY_GOOGLE_USB=y
CONFIG_USB_LGM_PHY=y
# CONFIG_PHY_NXP_PTN3222 is not set
# CONFIG_PHY_NXP_TJA1145 is not set

#
# PHY drivers for Broadcom platforms
#
# CONFIG_BCM_KONA_USB2_PHY is not set
# end of PHY drivers for Broadcom platforms

# CONFIG_PHY_CADENCE_TORRENT is not set
# CONFIG_PHY_CADENCE_DPHY is not set
# CONFIG_PHY_CADENCE_DPHY_RX is not set
# CONFIG_PHY_CADENCE_SIERRA is not set
# CONFIG_PHY_CADENCE_SALVO is not set
# CONFIG_PHY_INTEL_LGM_COMBO is not set
# CONFIG_PHY_INTEL_LGM_EMMC is not set
# CONFIG_PHY_PXA_28NM_HSIC is not set
# CONFIG_PHY_PXA_28NM_USB2 is not set
CONFIG_PHY_CPCAP_USB=y
# CONFIG_PHY_MAPPHONE_MDM6600 is not set
# CONFIG_PHY_OCELOT_SERDES is not set
CONFIG_PHY_QCOM_USB_HS=y
CONFIG_PHY_QCOM_USB_HSIC=y
CONFIG_PHY_SAMSUNG_USB2=y
# CONFIG_PHY_TI_DS125DF111 is not set
CONFIG_PHY_TUSB1210=y
# end of PHY Subsystem

# CONFIG_POWERCAP is not set
# CONFIG_MCB is not set

#
# Performance monitor support
#
# CONFIG_DWC_PCIE_PMU is not set
# end of Performance monitor support

CONFIG_RAS=y
CONFIG_USB4=y
CONFIG_USB4_CONFIGFS=y
# CONFIG_USB4_DEBUGFS_WRITE is not set
# CONFIG_USB4_DMA_TEST is not set
# CONFIG_USB4_STREAM is not set

#
# Android
#
CONFIG_ANDROID_BINDER_IPC=y
CONFIG_ANDROID_BINDERFS=y
CONFIG_ANDROID_BINDER_DEVICES="binder0,binder1"
# end of Android

CONFIG_LIBNVDIMM=y
CONFIG_BLK_DEV_PMEM=y
CONFIG_ND_CLAIM=y
CONFIG_ND_BTT=y
CONFIG_BTT=y
CONFIG_ND_PFN=y
CONFIG_NVDIMM_PFN=y
CONFIG_NVDIMM_DAX=y
CONFIG_OF_PMEM=y
# CONFIG_RAMDAX is not set
CONFIG_NVDIMM_KEYS=y
# CONFIG_NVDIMM_SECURITY_TEST is not set
CONFIG_DAX=y
CONFIG_NVMEM=y
CONFIG_NVMEM_SYSFS=y
CONFIG_NVMEM_LAYOUTS=y

#
# Layout Types
#
# CONFIG_NVMEM_LAYOUT_SL28_VPD is not set
# CONFIG_NVMEM_LAYOUT_ONIE_TLV is not set
# CONFIG_NVMEM_LAYOUT_U_BOOT_ENV is not set
# end of Layout Types

# CONFIG_EEPROM_AT24 is not set
# CONFIG_EEPROM_AT25 is not set
# CONFIG_EEPROM_93XX46 is not set
# CONFIG_EEPROM_EE1004 is not set
# CONFIG_EEPROM_M24LR is not set
# CONFIG_NVMEM_RMEM is not set
# CONFIG_NVMEM_U_BOOT_ENV is not set

#
# HW tracing support
#
# CONFIG_STM is not set
# CONFIG_INTEL_TH is not set
# end of HW tracing support

# CONFIG_FPGA is not set
# CONFIG_FSI is not set
CONFIG_TEE=y
CONFIG_TEE_DMABUF_HEAPS=y
CONFIG_OPTEE_STATIC_PROTMEM_POOL=y
# CONFIG_MUX_CORE is not set
# CONFIG_SIOX is not set
# CONFIG_SLIMBUS is not set
# CONFIG_INTERCONNECT is not set
CONFIG_COUNTER=y
# CONFIG_INTEL_QEP is not set
# CONFIG_INTERRUPT_CNT is not set
CONFIG_MOST=y
CONFIG_MOST_USB_HDM=y
# CONFIG_MOST_CDEV is not set
# CONFIG_MOST_SND is not set
# CONFIG_PECI is not set
# CONFIG_HTE is not set
# end of Device Drivers

#
# File systems
#
CONFIG_DCACHE_WORD_ACCESS=y
CONFIG_VALIDATE_FS_PARSER=y
CONFIG_FS_IOMAP=y
CONFIG_FS_STACK=y
CONFIG_BUFFER_HEAD=y
CONFIG_LEGACY_DIRECT_IO=y
# CONFIG_EXT2_FS is not set
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT2=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_JFS_FS=y
CONFIG_JFS_POSIX_ACL=y
CONFIG_JFS_SECURITY=y
CONFIG_JFS_DEBUG=y
# CONFIG_JFS_STATISTICS is not set
CONFIG_XFS_FS=y
# CONFIG_XFS_SUPPORT_V4 is not set
# CONFIG_XFS_SUPPORT_ASCII_CI is not set
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
CONFIG_XFS_DRAIN_INTENTS=y
CONFIG_XFS_LIVE_HOOKS=y
CONFIG_XFS_MEMORY_BUFS=y
CONFIG_XFS_BTREE_IN_MEM=y
CONFIG_XFS_ONLINE_SCRUB=y
# CONFIG_XFS_ONLINE_SCRUB_STATS is not set
CONFIG_XFS_ONLINE_REPAIR=y
# CONFIG_XFS_WARN is not set
# CONFIG_XFS_DEBUG is not set
CONFIG_GFS2_FS=y
CONFIG_GFS2_FS_LOCKING_DLM=y
CONFIG_OCFS2_FS=y
CONFIG_OCFS2_FS_O2CB=y
CONFIG_OCFS2_FS_USERSPACE_CLUSTER=y
CONFIG_OCFS2_FS_STATS=y
# CONFIG_OCFS2_DEBUG_MASKLOG is not set
CONFIG_OCFS2_DEBUG_FS=y
CONFIG_BTRFS_FS=y
CONFIG_BTRFS_FS_POSIX_ACL=y
# CONFIG_BTRFS_FS_RUN_SANITY_TESTS is not set
# CONFIG_BTRFS_DEBUG is not set
CONFIG_BTRFS_ASSERT=y
# CONFIG_BTRFS_EXPERIMENTAL is not set
CONFIG_NILFS2_FS=y
CONFIG_F2FS_FS=y
CONFIG_F2FS_STAT_FS=y
CONFIG_F2FS_FS_XATTR=y
CONFIG_F2FS_FS_POSIX_ACL=y
CONFIG_F2FS_FS_SECURITY=y
CONFIG_F2FS_CHECK_FS=y
CONFIG_F2FS_FAULT_INJECTION=y
CONFIG_F2FS_FS_COMPRESSION=y
CONFIG_F2FS_FS_LZO=y
CONFIG_F2FS_FS_LZORLE=y
CONFIG_F2FS_FS_LZ4=y
CONFIG_F2FS_FS_LZ4HC=y
CONFIG_F2FS_FS_ZSTD=y
# CONFIG_F2FS_IOSTAT is not set
# CONFIG_F2FS_UNFAIR_RWSEM is not set
CONFIG_ZONEFS_FS=y
CONFIG_FS_DAX=y
CONFIG_FS_POSIX_ACL=y
CONFIG_EXPORTFS=y
CONFIG_EXPORTFS_BLOCK_OPS=y
CONFIG_FILE_LOCKING=y
CONFIG_FS_ENCRYPTION=y
CONFIG_FS_ENCRYPTION_ALGS=y
CONFIG_FS_ENCRYPTION_INLINE_CRYPT=y
CONFIG_FS_VERITY=y
CONFIG_FS_VERITY_BUILTIN_SIGNATURES=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
# CONFIG_QUOTA_DEBUG is not set
CONFIG_QUOTA_TREE=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y
CONFIG_QUOTACTL=y
CONFIG_AUTOFS_FS=y
CONFIG_FUSE_FS=y
CONFIG_CUSE=y
CONFIG_VIRTIO_FS=y
CONFIG_FUSE_DAX=y
# CONFIG_FUSE_PASSTHROUGH is not set
CONFIG_FUSE_IO_URING=y
CONFIG_OVERLAY_FS=y
CONFIG_OVERLAY_FS_REDIRECT_DIR=y
CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW=y
CONFIG_OVERLAY_FS_INDEX=y
# CONFIG_OVERLAY_FS_NFS_EXPORT is not set
# CONFIG_OVERLAY_FS_XINO_AUTO is not set
# CONFIG_OVERLAY_FS_METACOPY is not set
CONFIG_OVERLAY_FS_DEBUG=y

#
# Caches
#
CONFIG_NETFS_SUPPORT=y
# CONFIG_NETFS_STATS is not set
# CONFIG_NETFS_DEBUG is not set
CONFIG_FSCACHE=y
# CONFIG_FSCACHE_STATS is not set
CONFIG_CACHEFILES=y
# CONFIG_CACHEFILES_DEBUG is not set
# CONFIG_CACHEFILES_ERROR_INJECTION is not set
# end of Caches

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=y
# end of CD-ROM/DVD Filesystems

#
# DOS/FAT/EXFAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_FAT_DEFAULT_UTF8 is not set
CONFIG_EXFAT_FS=y
CONFIG_EXFAT_DEFAULT_IOCHARSET="utf8"
# CONFIG_NTFS_FS is not set
CONFIG_NTFS3_FS=y
# CONFIG_NTFS3_64BIT_CLUSTER is not set
CONFIG_NTFS3_LZX_XPRESS=y
CONFIG_NTFS3_FS_POSIX_ACL=y
# end of DOS/FAT/EXFAT/NT Filesystems

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_VMCORE=y
# CONFIG_PROC_VMCORE_DEVICE_DUMP is not set
CONFIG_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_PROC_CHILDREN=y
CONFIG_PROC_PID_ARCH_STATUS=y
CONFIG_KERNFS=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
# CONFIG_TMPFS_INODE64 is not set
CONFIG_TMPFS_QUOTA=y
CONFIG_ARCH_SUPPORTS_HUGETLBFS=y
CONFIG_HUGETLBFS=y
# CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP_DEFAULT_ON is not set
CONFIG_HUGETLB_PAGE=y
CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP=y
CONFIG_HUGETLB_PMD_PAGE_TABLE_SHARING=y
CONFIG_ARCH_HAS_GIGANTIC_PAGE=y
CONFIG_CONFIGFS_FS=y
# end of Pseudo filesystems

CONFIG_MISC_FILESYSTEMS=y
CONFIG_ORANGEFS_FS=y
CONFIG_ADFS_FS=y
# CONFIG_ADFS_FS_RW is not set
CONFIG_AFFS_FS=y
CONFIG_ECRYPT_FS=y
CONFIG_ECRYPT_FS_MESSAGING=y
CONFIG_HFS_FS=y
CONFIG_HFSPLUS_FS=y
CONFIG_BEFS_FS=y
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=y
CONFIG_JFFS2_FS=y
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
CONFIG_JFFS2_SUMMARY=y
CONFIG_JFFS2_FS_XATTR=y
CONFIG_JFFS2_FS_POSIX_ACL=y
CONFIG_JFFS2_FS_SECURITY=y
CONFIG_JFFS2_COMPRESSION_OPTIONS=y
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_LZO=y
CONFIG_JFFS2_RTIME=y
CONFIG_JFFS2_RUBIN=y
# CONFIG_JFFS2_CMODE_NONE is not set
CONFIG_JFFS2_CMODE_PRIORITY=y
# CONFIG_JFFS2_CMODE_SIZE is not set
# CONFIG_JFFS2_CMODE_FAVOURLZO is not set
CONFIG_UBIFS_FS=y
CONFIG_UBIFS_FS_ADVANCED_COMPR=y
CONFIG_UBIFS_FS_LZO=y
CONFIG_UBIFS_FS_ZLIB=y
CONFIG_UBIFS_FS_ZSTD=y
CONFIG_UBIFS_ATIME_SUPPORT=y
CONFIG_UBIFS_FS_XATTR=y
CONFIG_UBIFS_FS_SECURITY=y
# CONFIG_UBIFS_FS_AUTHENTICATION is not set
CONFIG_CRAMFS=y
CONFIG_CRAMFS_BLOCKDEV=y
CONFIG_CRAMFS_MTD=y
CONFIG_SQUASHFS=y
# CONFIG_SQUASHFS_FILE_CACHE is not set
CONFIG_SQUASHFS_FILE_DIRECT=y
CONFIG_SQUASHFS_DECOMP_MULTI=y
# CONFIG_SQUASHFS_CHOICE_DECOMP_BY_MOUNT is not set
# CONFIG_SQUASHFS_COMPILE_DECOMP_SINGLE is not set
CONFIG_SQUASHFS_COMPILE_DECOMP_MULTI=y
# CONFIG_SQUASHFS_COMPILE_DECOMP_MULTI_PERCPU is not set
# CONFIG_SQUASHFS_MOUNT_DECOMP_THREADS is not set
CONFIG_SQUASHFS_XATTR=y
# CONFIG_SQUASHFS_COMP_CACHE_FULL is not set
CONFIG_SQUASHFS_ZLIB=y
CONFIG_SQUASHFS_LZ4=y
CONFIG_SQUASHFS_LZO=y
CONFIG_SQUASHFS_XZ=y
CONFIG_SQUASHFS_ZSTD=y
CONFIG_SQUASHFS_4K_DEVBLK_SIZE=y
# CONFIG_SQUASHFS_EMBEDDED is not set
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
CONFIG_MINIX_FS=y
CONFIG_OMFS_FS=y
CONFIG_HPFS_FS=y
CONFIG_QNX4FS_FS=y
CONFIG_QNX6FS_FS=y
# CONFIG_QNX6FS_DEBUG is not set
CONFIG_ROMFS_FS=y
# CONFIG_ROMFS_BACKED_BY_BLOCK is not set
# CONFIG_ROMFS_BACKED_BY_MTD is not set
CONFIG_ROMFS_BACKED_BY_BOTH=y
CONFIG_ROMFS_ON_BLOCK=y
CONFIG_ROMFS_ON_MTD=y
CONFIG_PSTORE=y
CONFIG_PSTORE_DEFAULT_KMSG_BYTES=10240
CONFIG_PSTORE_COMPRESS=y
# CONFIG_PSTORE_CONSOLE is not set
# CONFIG_PSTORE_PMSG is not set
# CONFIG_PSTORE_RAM is not set
# CONFIG_PSTORE_BLK is not set
CONFIG_UFS_FS=y
CONFIG_UFS_FS_WRITE=y
# CONFIG_UFS_DEBUG is not set
CONFIG_EROFS_FS=y
# CONFIG_EROFS_FS_DEBUG is not set
CONFIG_EROFS_FS_XATTR=y
CONFIG_EROFS_FS_POSIX_ACL=y
CONFIG_EROFS_FS_SECURITY=y
# CONFIG_EROFS_FS_BACKED_BY_FILE is not set
CONFIG_EROFS_FS_ZIP=y
# CONFIG_EROFS_FS_ZIP_LZMA is not set
# CONFIG_EROFS_FS_ZIP_DEFLATE is not set
# CONFIG_EROFS_FS_ZIP_ZSTD is not set
# CONFIG_EROFS_FS_ZIP_ACCEL is not set
# CONFIG_EROFS_FS_PCPU_KTHREAD is not set
# CONFIG_EROFS_FS_PAGE_CACHE_SHARE is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
# CONFIG_NFS_V2 is not set
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_SWAP is not set
CONFIG_NFS_V4_0=y
CONFIG_NFS_V4_2=y
CONFIG_PNFS_FILE_LAYOUT=y
CONFIG_PNFS_BLOCK=y
CONFIG_PNFS_FLEXFILE_LAYOUT=y
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org"
# CONFIG_NFS_V4_1_MIGRATION is not set
CONFIG_NFS_V4_SECURITY_LABEL=y
CONFIG_ROOT_NFS=y
CONFIG_NFS_FSCACHE=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
# CONFIG_NFS_DISABLE_UDP_SUPPORT is not set
CONFIG_NFS_V4_2_READ_PLUS=y
CONFIG_NFSD=y
# CONFIG_NFSD_V2 is not set
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_PNFS=y
CONFIG_NFSD_BLOCKLAYOUT=y
CONFIG_NFSD_SCSILAYOUT=y
CONFIG_NFSD_FLEXFILELAYOUT=y
CONFIG_NFSD_V4_2_INTER_SSC=y
CONFIG_NFSD_V4_SECURITY_LABEL=y
# CONFIG_NFSD_LEGACY_CLIENT_TRACKING is not set
# CONFIG_NFSD_V4_POSIX_ACLS is not set
CONFIG_GRACE_PERIOD=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
# CONFIG_NFS_LOCALIO is not set
CONFIG_NFS_V4_2_SSC_HELPER=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_SUNRPC_BACKCHANNEL=y
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_SUNRPC_DEBUG is not set
# CONFIG_SUNRPC_XPRT_RDMA is not set
CONFIG_CEPH_FS=y
CONFIG_CEPH_FSCACHE=y
CONFIG_CEPH_FS_POSIX_ACL=y
# CONFIG_CEPH_FS_SECURITY_LABEL is not set
CONFIG_CIFS=y
# CONFIG_CIFS_STATS2 is not set
CONFIG_CIFS_ALLOW_INSECURE_LEGACY=y
CONFIG_CIFS_UPCALL=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
CONFIG_CIFS_DEBUG=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_DEBUG_DUMP_KEYS is not set
CONFIG_CIFS_DFS_UPCALL=y
CONFIG_CIFS_SWN_UPCALL=y
CONFIG_CIFS_SMB_DIRECT=y
CONFIG_CIFS_FSCACHE=y
# CONFIG_CIFS_ROOT is not set
# CONFIG_CIFS_COMPRESSION is not set
CONFIG_SMB_SERVER=y
# CONFIG_SMB_SERVER_SMBDIRECT is not set
# CONFIG_SMB_SERVER_CHECK_CAP_NET_ADMIN is not set
# CONFIG_SMB_SERVER_KERBEROS5 is not set
CONFIG_SMBDIRECT=y
CONFIG_SMBFS=y
# CONFIG_CODA_FS is not set
CONFIG_AFS_FS=y
# CONFIG_AFS_DEBUG is not set
CONFIG_AFS_FSCACHE=y
# CONFIG_AFS_DEBUG_CURSOR is not set
CONFIG_9P_FS=y
CONFIG_9P_FSCACHE=y
CONFIG_9P_FS_POSIX_ACL=y
CONFIG_9P_FS_SECURITY=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=y
CONFIG_NLS_CODEPAGE_775=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=y
CONFIG_NLS_CODEPAGE_855=y
CONFIG_NLS_CODEPAGE_857=y
CONFIG_NLS_CODEPAGE_860=y
CONFIG_NLS_CODEPAGE_861=y
CONFIG_NLS_CODEPAGE_862=y
CONFIG_NLS_CODEPAGE_863=y
CONFIG_NLS_CODEPAGE_864=y
CONFIG_NLS_CODEPAGE_865=y
CONFIG_NLS_CODEPAGE_866=y
CONFIG_NLS_CODEPAGE_869=y
CONFIG_NLS_CODEPAGE_936=y
CONFIG_NLS_CODEPAGE_950=y
CONFIG_NLS_CODEPAGE_932=y
CONFIG_NLS_CODEPAGE_949=y
CONFIG_NLS_CODEPAGE_874=y
CONFIG_NLS_ISO8859_8=y
CONFIG_NLS_CODEPAGE_1250=y
CONFIG_NLS_CODEPAGE_1251=y
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=y
CONFIG_NLS_ISO8859_3=y
CONFIG_NLS_ISO8859_4=y
CONFIG_NLS_ISO8859_5=y
CONFIG_NLS_ISO8859_6=y
CONFIG_NLS_ISO8859_7=y
CONFIG_NLS_ISO8859_9=y
CONFIG_NLS_ISO8859_13=y
CONFIG_NLS_ISO8859_14=y
CONFIG_NLS_ISO8859_15=y
CONFIG_NLS_KOI8_R=y
CONFIG_NLS_KOI8_U=y
CONFIG_NLS_MAC_ROMAN=y
CONFIG_NLS_MAC_CELTIC=y
CONFIG_NLS_MAC_CENTEURO=y
CONFIG_NLS_MAC_CROATIAN=y
CONFIG_NLS_MAC_CYRILLIC=y
CONFIG_NLS_MAC_GAELIC=y
CONFIG_NLS_MAC_GREEK=y
CONFIG_NLS_MAC_ICELAND=y
CONFIG_NLS_MAC_INUIT=y
CONFIG_NLS_MAC_ROMANIAN=y
CONFIG_NLS_MAC_TURKISH=y
CONFIG_NLS_UTF8=y
CONFIG_NLS_UCS2_UTILS=y
CONFIG_DLM=y
# CONFIG_DLM_DEBUG is not set
CONFIG_UNICODE=y
CONFIG_IO_WQ=y
# end of File systems

#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_REQUEST_CACHE=y
CONFIG_PERSISTENT_KEYRINGS=y
CONFIG_BIG_KEYS=y
CONFIG_TRUSTED_KEYS=y
# CONFIG_TRUSTED_KEYS_TPM is not set
# CONFIG_TRUSTED_KEYS_TEE is not set

#
# No trust source selected!
#
CONFIG_ENCRYPTED_KEYS=y
# CONFIG_USER_DECRYPTED_DATA is not set
CONFIG_KEY_DH_OPERATIONS=y
CONFIG_KEY_NOTIFICATIONS=y
# CONFIG_SECURITY_DMESG_RESTRICT is not set
# CONFIG_PROC_MEM_ALWAYS_FORCE is not set
CONFIG_PROC_MEM_FORCE_PTRACE=y
# CONFIG_PROC_MEM_NO_FORCE is not set
CONFIG_SECURITY=y
CONFIG_HAS_SECURITY_AUDIT=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_INFINIBAND=y
CONFIG_SECURITY_NETWORK_XFRM=y
CONFIG_SECURITY_PATH=y
# CONFIG_INTEL_TXT is not set
# CONFIG_STATIC_USERMODEHELPER is not set
# CONFIG_SECURITY_SELINUX is not set
CONFIG_SECURITY_SMACK=y
# CONFIG_SECURITY_SMACK_BRINGUP is not set
CONFIG_SECURITY_SMACK_NETFILTER=y
# CONFIG_SECURITY_SMACK_APPEND_SIGNALS is not set
CONFIG_SECURITY_TOMOYO=y
CONFIG_SECURITY_TOMOYO_MAX_ACCEPT_ENTRY=64
CONFIG_SECURITY_TOMOYO_MAX_AUDIT_LOG=32
CONFIG_SECURITY_TOMOYO_OMIT_USERSPACE_LOADER=y
CONFIG_SECURITY_TOMOYO_INSECURE_BUILTIN_SETTING=y
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_SECURITY_LOADPIN is not set
CONFIG_SECURITY_YAMA=y
CONFIG_SECURITY_SAFESETID=y
CONFIG_SECURITY_LOCKDOWN_LSM=y
CONFIG_SECURITY_LOCKDOWN_LSM_EARLY=y
CONFIG_LOCK_DOWN_KERNEL_FORCE_NONE=y
# CONFIG_LOCK_DOWN_KERNEL_FORCE_INTEGRITY is not set
# CONFIG_LOCK_DOWN_KERNEL_FORCE_CONFIDENTIALITY is not set
CONFIG_SECURITY_LANDLOCK=y
CONFIG_SECURITY_LANDLOCK_LOG=y
# CONFIG_SECURITY_IPE is not set
CONFIG_INTEGRITY=y
CONFIG_INTEGRITY_SIGNATURE=y
CONFIG_INTEGRITY_ASYMMETRIC_KEYS=y
CONFIG_INTEGRITY_TRUSTED_KEYRING=y
CONFIG_INTEGRITY_AUDIT=y
CONFIG_IMA=y
CONFIG_IMA_MEASURE_PCR_IDX=10
CONFIG_IMA_LSM_RULES=y
CONFIG_IMA_NG_TEMPLATE=y
# CONFIG_IMA_SIG_TEMPLATE is not set
CONFIG_IMA_DEFAULT_TEMPLATE="ima-ng"
# CONFIG_IMA_DEFAULT_HASH_SHA1 is not set
CONFIG_IMA_DEFAULT_HASH_SHA256=y
# CONFIG_IMA_DEFAULT_HASH_SHA512 is not set
# CONFIG_IMA_DEFAULT_HASH_WP512 is not set
CONFIG_IMA_DEFAULT_HASH="sha256"
CONFIG_IMA_WRITE_POLICY=y
CONFIG_IMA_READ_POLICY=y
CONFIG_IMA_APPRAISE=y
# CONFIG_IMA_ARCH_POLICY is not set
# CONFIG_IMA_APPRAISE_BUILD_POLICY is not set
# CONFIG_IMA_APPRAISE_BOOTPARAM is not set
CONFIG_IMA_APPRAISE_MODSIG=y
# CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY is not set
# CONFIG_IMA_BLACKLIST_KEYRING is not set
# CONFIG_IMA_LOAD_X509 is not set
CONFIG_IMA_MEASURE_ASYMMETRIC_KEYS=y
CONFIG_IMA_QUEUE_EARLY_BOOT_KEYS=y
# CONFIG_IMA_DISABLE_HTABLE is not set
# CONFIG_IMA_STAGING is not set
# CONFIG_IMA_INIT_LATE_SYNC is not set
CONFIG_EVM=y
CONFIG_EVM_ATTR_FSUUID=y
CONFIG_EVM_EXTRA_SMACK_XATTRS=y
CONFIG_EVM_ADD_XATTRS=y
# CONFIG_EVM_LOAD_X509 is not set
CONFIG_DEFAULT_SECURITY_SMACK=y
# CONFIG_DEFAULT_SECURITY_TOMOYO is not set
# CONFIG_DEFAULT_SECURITY_DAC is not set
CONFIG_LSM="landlock,lockdown,yama,safesetid,integrity,tomoyo,smack,bpf"

#
# Kernel hardening options
#

#
# Memory initialization
#
CONFIG_CC_HAS_AUTO_VAR_INIT_PATTERN=y
CONFIG_CC_HAS_AUTO_VAR_INIT_ZERO_BARE=y
CONFIG_CC_HAS_AUTO_VAR_INIT_ZERO=y
# CONFIG_INIT_STACK_NONE is not set
# CONFIG_INIT_STACK_ALL_PATTERN is not set
CONFIG_INIT_STACK_ALL_ZERO=y
CONFIG_CC_HAS_SANCOV_STACK_DEPTH_CALLBACK=y
# CONFIG_KSTACK_ERASE is not set
CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y
# CONFIG_INIT_ON_FREE_DEFAULT_ON is not set
CONFIG_CC_HAS_ZERO_CALL_USED_REGS=y
# CONFIG_ZERO_CALL_USED_REGS is not set
# end of Memory initialization

#
# Bounds checking
#
CONFIG_FORTIFY_SOURCE=y
CONFIG_HARDENED_USERCOPY=y
# CONFIG_HARDENED_USERCOPY_DEFAULT_ON is not set
# end of Bounds checking

#
# Hardening of kernel data structures
#
CONFIG_LIST_HARDENED=y
CONFIG_BUG_ON_DATA_CORRUPTION=y
# end of Hardening of kernel data structures

CONFIG_CC_HAS_RANDSTRUCT=y
CONFIG_RANDSTRUCT_NONE=y
# CONFIG_RANDSTRUCT_FULL is not set
# end of Kernel hardening options
# end of Security options

CONFIG_ASYNC_CORE=y
CONFIG_ASYNC_MEMCPY=y
CONFIG_ASYNC_XOR=y
CONFIG_ASYNC_PQ=y
CONFIG_ASYNC_RAID6_RECOV=y
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_SIG=y
CONFIG_CRYPTO_SIG2=y
CONFIG_CRYPTO_SKCIPHER=y
CONFIG_CRYPTO_SKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_AKCIPHER2=y
CONFIG_CRYPTO_AKCIPHER=y
CONFIG_CRYPTO_KPP2=y
CONFIG_CRYPTO_KPP=y
CONFIG_CRYPTO_ACOMP2=y
CONFIG_CRYPTO_ACOMP=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_USER=y
# CONFIG_CRYPTO_SELFTESTS is not set
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_PCRYPT=y
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=y
CONFIG_CRYPTO_KRB5ENC=y
# CONFIG_CRYPTO_BENCHMARK is not set
CONFIG_CRYPTO_ENGINE=y
# end of Crypto core or helper

#
# Public-key cryptography
#
CONFIG_CRYPTO_RSA=y
CONFIG_CRYPTO_DH=y
# CONFIG_CRYPTO_DH_RFC7919_GROUPS is not set
CONFIG_CRYPTO_ECC=y
CONFIG_CRYPTO_ECDH=y
# CONFIG_CRYPTO_ECDSA is not set
CONFIG_CRYPTO_ECRDSA=y
CONFIG_CRYPTO_MLDSA=y
# end of Public-key cryptography

#
# Block ciphers
#
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_ANUBIS=y
CONFIG_CRYPTO_ARIA=y
CONFIG_CRYPTO_BLOWFISH=y
CONFIG_CRYPTO_BLOWFISH_COMMON=y
CONFIG_CRYPTO_CAMELLIA=y
CONFIG_CRYPTO_CAST_COMMON=y
CONFIG_CRYPTO_CAST5=y
CONFIG_CRYPTO_CAST6=y
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_KHAZAD=y
CONFIG_CRYPTO_SEED=y
CONFIG_CRYPTO_SERPENT=y
CONFIG_CRYPTO_SM4=y
CONFIG_CRYPTO_SM4_GENERIC=y
CONFIG_CRYPTO_TEA=y
CONFIG_CRYPTO_TWOFISH=y
CONFIG_CRYPTO_TWOFISH_COMMON=y
# end of Block ciphers

#
# Length-preserving ciphers and modes
#
CONFIG_CRYPTO_ADIANTUM=y
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_CHACHA20=y
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_CTR=y
CONFIG_CRYPTO_CTS=y
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_HCTR2=y
CONFIG_CRYPTO_LRW=y
CONFIG_CRYPTO_XCTR=y
CONFIG_CRYPTO_XTS=y
# end of Length-preserving ciphers and modes

#
# AEAD (authenticated encryption with associated data) ciphers
#
CONFIG_CRYPTO_AEGIS128=y
CONFIG_CRYPTO_CHACHA20POLY1305=y
CONFIG_CRYPTO_CCM=y
CONFIG_CRYPTO_GCM=y
CONFIG_CRYPTO_GENIV=y
CONFIG_CRYPTO_SEQIV=y
CONFIG_CRYPTO_ECHAINIV=y
CONFIG_CRYPTO_ESSIV=y
# end of AEAD (authenticated encryption with associated data) ciphers

#
# Hashes, digests, and MACs
#
# CONFIG_CRYPTO_BLAKE2B is not set
CONFIG_CRYPTO_CMAC=y
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
CONFIG_CRYPTO_RMD160=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
CONFIG_CRYPTO_SHA3=y
# CONFIG_CRYPTO_SM3 is not set
CONFIG_CRYPTO_STREEBOG=y
CONFIG_CRYPTO_WP512=y
CONFIG_CRYPTO_XCBC=y
# CONFIG_CRYPTO_XXHASH is not set
# end of Hashes, digests, and MACs

#
# CRCs (cyclic redundancy checks)
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CRC32 is not set
# end of CRCs (cyclic redundancy checks)

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_LZO=y
CONFIG_CRYPTO_842=y
CONFIG_CRYPTO_LZ4=y
CONFIG_CRYPTO_LZ4HC=y
CONFIG_CRYPTO_ZSTD=y
# end of Compression

#
# Random number generation
#
# CONFIG_CRYPTO_DRBG is not set
# CONFIG_CRYPTO_JITTERENTROPY is not set
CONFIG_CRYPTO_KDF800108_CTR=y
# end of Random number generation

#
# Userspace interface (deprecated)
#
CONFIG_CRYPTO_USER_API=y
CONFIG_CRYPTO_USER_API_HASH=y
CONFIG_CRYPTO_USER_API_SKCIPHER=y
CONFIG_CRYPTO_USER_API_RNG=y
CONFIG_CRYPTO_USER_API_AEAD=y
CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE=y
# end of Userspace interface (deprecated)

#
# Accelerated Cryptographic Algorithms for CPU (x86)
#
CONFIG_CRYPTO_AES_NI_INTEL=y
CONFIG_CRYPTO_BLOWFISH_X86_64=y
CONFIG_CRYPTO_CAMELLIA_X86_64=y
CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64=y
CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64=y
CONFIG_CRYPTO_CAST5_AVX_X86_64=y
CONFIG_CRYPTO_CAST6_AVX_X86_64=y
CONFIG_CRYPTO_SERPENT_SSE2_X86_64=y
CONFIG_CRYPTO_SERPENT_AVX_X86_64=y
CONFIG_CRYPTO_SERPENT_AVX2_X86_64=y
CONFIG_CRYPTO_SM4_AESNI_AVX_X86_64=y
CONFIG_CRYPTO_SM4_AESNI_AVX2_X86_64=y
CONFIG_CRYPTO_TWOFISH_X86_64=y
CONFIG_CRYPTO_TWOFISH_X86_64_3WAY=y
CONFIG_CRYPTO_TWOFISH_AVX_X86_64=y
CONFIG_CRYPTO_ARIA_AESNI_AVX_X86_64=y
# CONFIG_CRYPTO_ARIA_AESNI_AVX2_X86_64 is not set
# CONFIG_CRYPTO_ARIA_GFNI_AVX512_X86_64 is not set
CONFIG_CRYPTO_AEGIS128_AESNI_SSE2=y
# end of Accelerated Cryptographic Algorithms for CPU (x86)

CONFIG_CRYPTO_HW=y
CONFIG_CRYPTO_DEV_PADLOCK=y
CONFIG_CRYPTO_DEV_PADLOCK_AES=y
CONFIG_CRYPTO_DEV_PADLOCK_SHA=y
# CONFIG_CRYPTO_DEV_ATMEL_ECC is not set
# CONFIG_CRYPTO_DEV_ATMEL_SHA204A is not set
CONFIG_CRYPTO_DEV_CCP=y
CONFIG_CRYPTO_DEV_CCP_DD=y
# CONFIG_CRYPTO_DEV_SP_CCP is not set
# CONFIG_CRYPTO_DEV_SP_PSP is not set
# CONFIG_CRYPTO_DEV_NITROX_CNN55XX is not set
CONFIG_CRYPTO_DEV_QAT=y
CONFIG_CRYPTO_DEV_QAT_DH895xCC=y
CONFIG_CRYPTO_DEV_QAT_C3XXX=y
CONFIG_CRYPTO_DEV_QAT_C62X=y
# CONFIG_CRYPTO_DEV_QAT_4XXX is not set
# CONFIG_CRYPTO_DEV_QAT_420XX is not set
# CONFIG_CRYPTO_DEV_QAT_6XXX is not set
CONFIG_CRYPTO_DEV_QAT_DH895xCCVF=y
CONFIG_CRYPTO_DEV_QAT_C3XXXVF=y
CONFIG_CRYPTO_DEV_QAT_C62XVF=y
# CONFIG_CRYPTO_DEV_QAT_ERROR_INJECTION is not set
CONFIG_CRYPTO_DEV_VIRTIO=y
# CONFIG_CRYPTO_DEV_SAFEXCEL is not set
# CONFIG_CRYPTO_DEV_CCREE is not set
# CONFIG_CRYPTO_DEV_AMLOGIC_GXL is not set
CONFIG_ASYMMETRIC_KEY_TYPE=y
CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y
CONFIG_X509_CERTIFICATE_PARSER=y
CONFIG_PKCS8_PRIVATE_KEY_PARSER=y
CONFIG_PKCS7_MESSAGE_PARSER=y
# CONFIG_PKCS7_WAIVE_AUTHATTRS_REJECTION_FOR_MLDSA is not set
CONFIG_PKCS7_TEST_KEY=y
CONFIG_SIGNED_PE_FILE_VERIFICATION=y
# CONFIG_FIPS_SIGNATURE_SELFTEST is not set

#
# Certificates for signature checking
#
CONFIG_MODULE_SIG_KEY="certs/signing_key.pem"
# CONFIG_MODULE_SIG_KEY_TYPE_RSA is not set
CONFIG_MODULE_SIG_KEY_TYPE_MLDSA_44=y
# CONFIG_MODULE_SIG_KEY_TYPE_MLDSA_65 is not set
# CONFIG_MODULE_SIG_KEY_TYPE_MLDSA_87 is not set
CONFIG_SYSTEM_TRUSTED_KEYRING=y
CONFIG_SYSTEM_TRUSTED_KEYS=""
# CONFIG_SYSTEM_EXTRA_CERTIFICATE is not set
CONFIG_SECONDARY_TRUSTED_KEYRING=y
# CONFIG_SECONDARY_TRUSTED_KEYRING_SIGNED_BY_BUILTIN is not set
# CONFIG_SYSTEM_BLACKLIST_KEYRING is not set
CONFIG_OPENSSL_SUPPORTS_ML_DSA=y
# end of Certificates for signature checking

CONFIG_CRYPTO_KRB5=y
# CONFIG_CRYPTO_KRB5_SELFTESTS is not set
CONFIG_BINARY_PRINTF=y

#
# Library routines
#
CONFIG_LINEAR_RANGES=y
# CONFIG_PACKING is not set
CONFIG_BITREVERSE=y
CONFIG_GENERIC_BITREVERSE=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_NET_UTILS=y
# CONFIG_CORDIC is not set
# CONFIG_PRIME_NUMBERS is not set
CONFIG_RATIONAL=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
CONFIG_ARCH_HAS_FAST_MULTIPLIER=y
CONFIG_ARCH_USE_SYM_ANNOTATIONS=y
CONFIG_CRC8=y
CONFIG_CRC16=y
CONFIG_CRC_CCITT=y
CONFIG_CRC_ITU_T=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_T10DIF_ARCH=y
CONFIG_CRC32=y
CONFIG_CRC32_ARCH=y
CONFIG_CRC64=y
CONFIG_CRC64_ARCH=y
CONFIG_CRC_OPTIMIZATIONS=y
CONFIG_CRYPTO_HASH_INFO=y
CONFIG_CRYPTO_LIB_UTILS=y
CONFIG_CRYPTO_LIB_AES=y
CONFIG_CRYPTO_LIB_AES_ARCH=y
CONFIG_CRYPTO_LIB_AES_CBC=y
CONFIG_CRYPTO_LIB_AES_CBC_MACS=y
CONFIG_CRYPTO_LIB_AES_CCM=y
CONFIG_CRYPTO_LIB_AES_CTR=y
CONFIG_CRYPTO_LIB_AES_ECB=y
CONFIG_CRYPTO_LIB_AES_GCM=y
CONFIG_CRYPTO_LIB_AES_XTS=y
CONFIG_CRYPTO_LIB_ARC4=y
CONFIG_CRYPTO_LIB_GF128MUL=y
CONFIG_CRYPTO_LIB_BLAKE2B=y
CONFIG_CRYPTO_LIB_BLAKE2S_ARCH=y
CONFIG_CRYPTO_LIB_CHACHA=y
CONFIG_CRYPTO_LIB_CHACHA_ARCH=y
CONFIG_CRYPTO_LIB_CURVE25519=y
CONFIG_CRYPTO_LIB_CURVE25519_ARCH=y
CONFIG_CRYPTO_LIB_CURVE25519_GENERIC=y
CONFIG_CRYPTO_LIB_DES=y
CONFIG_CRYPTO_LIB_GF128HASH=y
CONFIG_CRYPTO_LIB_GF128HASH_ARCH=y
CONFIG_CRYPTO_LIB_MD5=y
CONFIG_CRYPTO_LIB_MLDSA=y
CONFIG_CRYPTO_LIB_NH=y
CONFIG_CRYPTO_LIB_NH_ARCH=y
CONFIG_CRYPTO_LIB_POLY1305=y
CONFIG_CRYPTO_LIB_POLY1305_ARCH=y
CONFIG_CRYPTO_LIB_POLY1305_GENERIC=y
CONFIG_CRYPTO_LIB_POLY1305_RSIZE=11
CONFIG_CRYPTO_LIB_CHACHA20POLY1305=y
CONFIG_CRYPTO_LIB_SHA1=y
CONFIG_CRYPTO_LIB_SHA1_ARCH=y
CONFIG_CRYPTO_LIB_SHA256=y
CONFIG_CRYPTO_LIB_SHA256_ARCH=y
CONFIG_CRYPTO_LIB_SHA512=y
CONFIG_CRYPTO_LIB_SHA512_ARCH=y
CONFIG_CRYPTO_LIB_SHA3=y
CONFIG_XOR_BLOCKS=y
CONFIG_XOR_BLOCKS_ARCH=y
CONFIG_RAID6_PQ=y
CONFIG_RAID6_PQ_ARCH=y
# CONFIG_RAID6_PQ_BENCHMARK is not set
CONFIG_XXHASH=y
CONFIG_842_COMPRESS=y
CONFIG_842_DECOMPRESS=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_LZ4_COMPRESS=y
CONFIG_LZ4HC_COMPRESS=y
CONFIG_LZ4_DECOMPRESS=y
CONFIG_ZSTD_COMMON=y
CONFIG_ZSTD_COMPRESS=y
CONFIG_ZSTD_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_ARM64=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_RISCV=y
# CONFIG_XZ_DEC_MICROLZMA is not set
CONFIG_XZ_DEC_BCJ=y
# CONFIG_XZ_DEC_TEST is not set
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_DECOMPRESS_LZ4=y
CONFIG_DECOMPRESS_ZSTD=y
CONFIG_GENERIC_ALLOCATOR=y
CONFIG_REED_SOLOMON=y
CONFIG_REED_SOLOMON_DEC8=y
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=y
CONFIG_TEXTSEARCH_BM=y
CONFIG_TEXTSEARCH_FSM=y
CONFIG_INTERVAL_TREE=y
CONFIG_INTERVAL_TREE_SPAN_ITER=y
CONFIG_XARRAY_MULTI=y
CONFIG_ASSOCIATIVE_ARRAY=y
CONFIG_CLOSURES=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_IOPORT_MAP=y
CONFIG_HAS_DMA=y
CONFIG_DMA_OPS_HELPERS=y
CONFIG_NEED_SG_DMA_FLAGS=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_DMA_DECLARE_COHERENT=y
CONFIG_SWIOTLB=y
CONFIG_SWIOTLB_DEFAULT_SIZE_MB=64
# CONFIG_SWIOTLB_DYNAMIC is not set
CONFIG_DMA_NEED_SYNC=y
# CONFIG_DMA_RESTRICTED_POOL is not set
CONFIG_DMA_CMA=y
# CONFIG_DMA_NUMA_CMA is not set

#
# Default contiguous memory area size:
#
CONFIG_CMA_SIZE_MBYTES=0
CONFIG_CMA_SIZE_PERCENTAGE=0
# CONFIG_CMA_SIZE_SEL_MBYTES is not set
# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
# CONFIG_CMA_SIZE_SEL_MIN is not set
CONFIG_CMA_SIZE_SEL_MAX=y
CONFIG_CMA_ALIGNMENT=8
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_DMA_MAP_BENCHMARK is not set
CONFIG_SGL_ALLOC=y
CONFIG_CHECK_SIGNATURE=y
# CONFIG_CPUMASK_OFFSTACK is not set
CONFIG_CPU_RMAP=y
CONFIG_DQL=y
CONFIG_GLOB=y
CONFIG_NLATTR=y
CONFIG_CLZ_TAB=y
CONFIG_IRQ_POLL=y
CONFIG_MPILIB=y
CONFIG_SIGNATURE=y
CONFIG_DIMLIB=y
CONFIG_LIBFDT=y
CONFIG_OID_REGISTRY=y
CONFIG_VDSO_DATASTORE=y
CONFIG_GENERIC_GETTIMEOFDAY=y
CONFIG_GENERIC_VDSO_OVERFLOW_PROTECT=y
CONFIG_VDSO_GETRANDOM=y
CONFIG_FONT_SUPPORT=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_SG_POOL=y
CONFIG_ARCH_HAS_PMEM_API=y
CONFIG_MEMREGION=y
CONFIG_ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION=y
CONFIG_ARCH_HAS_UACCESS_FLUSHCACHE=y
CONFIG_ARCH_HAS_COPY_MC=y
CONFIG_ARCH_STACKWALK=y
CONFIG_STACKDEPOT=y
CONFIG_STACKDEPOT_ALWAYS_INIT=y
CONFIG_STACKDEPOT_MAX_FRAMES=64
CONFIG_REF_TRACKER=y
CONFIG_SBITMAP=y
# CONFIG_LWQ_TEST is not set
# end of Library routines

CONFIG_FIRMWARE_TABLE=y
CONFIG_UNION_FIND=y

#
# Kernel hacking
#

#
# printk and dmesg options
#
CONFIG_PRINTK_TIME=y
CONFIG_PRINTK_CALLER=y
# CONFIG_STACKTRACE_BUILD_ID is not set
CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7
CONFIG_CONSOLE_LOGLEVEL_QUIET=4
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4
# CONFIG_BOOT_PRINTK_DELAY is not set
CONFIG_DYNAMIC_DEBUG=y
CONFIG_DYNAMIC_DEBUG_CORE=y
CONFIG_SYMBOLIC_ERRNAME=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_BUGVERBOSE_DETAILED=y
# end of printk and dmesg options

CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_MISC=y

#
# Compile-time checks and compiler options
#
CONFIG_DEBUG_INFO=y
CONFIG_AS_HAS_NON_CONST_ULEB128=y
# CONFIG_DEBUG_INFO_NONE is not set
# CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT is not set
CONFIG_DEBUG_INFO_DWARF4=y
# CONFIG_DEBUG_INFO_DWARF5 is not set
# CONFIG_DEBUG_INFO_REDUCED is not set
CONFIG_DEBUG_INFO_COMPRESSED_NONE=y
# CONFIG_DEBUG_INFO_COMPRESSED_ZLIB is not set
# CONFIG_DEBUG_INFO_COMPRESSED_ZSTD is not set
# CONFIG_DEBUG_INFO_SPLIT is not set
# CONFIG_DEBUG_INFO_BTF is not set
CONFIG_PAHOLE_HAS_BTF_TAG=y
CONFIG_PAHOLE_HAS_LANG_EXCLUDE=y
# CONFIG_GDB_SCRIPTS is not set
CONFIG_FRAME_WARN=2048
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_HEADERS_INSTALL is not set
CONFIG_SECTION_MISMATCH_WARN_ONLY=y
# CONFIG_DEBUG_FORCE_FUNCTION_ALIGN_64B is not set
CONFIG_OBJTOOL=y
# CONFIG_OBJTOOL_WERROR is not set
CONFIG_NOINSTR_VALIDATION=y
# CONFIG_VMLINUX_MAP is not set
# end of Compile-time checks and compiler options

#
# Generic Kernel Debugging Instruments
#
# CONFIG_MAGIC_SYSRQ is not set
CONFIG_DEBUG_FS=y
CONFIG_DEBUG_FS_ALLOW_ALL=y
# CONFIG_DEBUG_FS_ALLOW_NONE is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
CONFIG_ARCH_HAS_UBSAN=y
CONFIG_UBSAN=y
# CONFIG_UBSAN_TRAP is not set
CONFIG_CC_HAS_UBSAN_ARRAY_BOUNDS=y
CONFIG_UBSAN_BOUNDS=y
CONFIG_UBSAN_ARRAY_BOUNDS=y
CONFIG_UBSAN_SHIFT=y
# CONFIG_UBSAN_BOOL is not set
# CONFIG_UBSAN_ENUM is not set
# CONFIG_UBSAN_ALIGNMENT is not set
# CONFIG_TEST_UBSAN is not set
CONFIG_HAVE_ARCH_KCSAN=y
CONFIG_HAVE_KCSAN_COMPILER=y
# end of Generic Kernel Debugging Instruments

#
# Networking Debugging
#
CONFIG_NET_DEV_REFCNT_TRACKER=y
CONFIG_NET_NS_REFCNT_TRACKER=y
CONFIG_DEBUG_NET=y
# CONFIG_DEBUG_NET_SMALL_RTNL is not set
# end of Networking Debugging

#
# Memory Debugging
#
CONFIG_PAGE_EXTENSION=y
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_SLUB_DEBUG=y
# CONFIG_SLUB_DEBUG_ON is not set
CONFIG_SLUB_RCU_DEBUG=y
CONFIG_PAGE_OWNER=y
CONFIG_PAGE_TABLE_CHECK=y
CONFIG_PAGE_TABLE_CHECK_ENFORCED=y
CONFIG_PAGE_POISONING=y
# CONFIG_DEBUG_PAGE_REF is not set
# CONFIG_DEBUG_RODATA_TEST is not set
CONFIG_ARCH_HAS_DEBUG_WX=y
CONFIG_DEBUG_WX=y
CONFIG_ARCH_HAS_PTDUMP=y
CONFIG_PTDUMP=y
CONFIG_PTDUMP_DEBUGFS=y
CONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_PER_VMA_LOCK_STATS is not set
# CONFIG_MEM_ALLOC_PROFILING is not set
CONFIG_DEBUG_OBJECTS=y
# CONFIG_DEBUG_OBJECTS_SELFTEST is not set
CONFIG_DEBUG_OBJECTS_FREE=y
CONFIG_DEBUG_OBJECTS_TIMERS=y
CONFIG_DEBUG_OBJECTS_WORK=y
CONFIG_DEBUG_OBJECTS_RCU_HEAD=y
CONFIG_DEBUG_OBJECTS_PERCPU_COUNTER=y
CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=1
# CONFIG_SHRINKER_DEBUG is not set
CONFIG_DEBUG_STACK_USAGE=y
CONFIG_SCHED_STACK_END_CHECK=y
CONFIG_ARCH_HAS_DEBUG_VM_PGTABLE=y
CONFIG_DEBUG_VFS=y
CONFIG_DEBUG_VM=y
CONFIG_DEBUG_VM_MAPLE_TREE=y
CONFIG_DEBUG_VM_RB=y
CONFIG_DEBUG_VM_PGFLAGS=y
CONFIG_DEBUG_VM_PGTABLE=y
CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
CONFIG_DEBUG_VIRTUAL=y
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_DEBUG_PER_CPU_MAPS=y
CONFIG_DEBUG_KMAP_LOCAL=y
CONFIG_ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP=y
CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP=y
CONFIG_HAVE_ARCH_KASAN=y
CONFIG_HAVE_ARCH_KASAN_VMALLOC=y
CONFIG_CC_HAS_KASAN_GENERIC=y
CONFIG_CC_HAS_KASAN_SW_TAGS=y
CONFIG_CC_HAS_WORKING_NOSANITIZE_ADDRESS=y
CONFIG_KASAN=y
CONFIG_CC_HAS_KASAN_MEMINTRINSIC_PREFIX=y
CONFIG_KASAN_GENERIC=y
# CONFIG_KASAN_OUTLINE is not set
CONFIG_KASAN_INLINE=y
CONFIG_KASAN_STACK=y
CONFIG_KASAN_VMALLOC=y
# CONFIG_KASAN_EXTRA_INFO is not set
CONFIG_HAVE_ARCH_KFENCE=y
CONFIG_KFENCE=y
CONFIG_KFENCE_SAMPLE_INTERVAL=100
CONFIG_KFENCE_NUM_OBJECTS=255
# CONFIG_KFENCE_DEFERRABLE is not set
CONFIG_KFENCE_STATIC_KEYS=y
CONFIG_KFENCE_STRESS_TEST_FAULTS=0
CONFIG_HAVE_ARCH_KMSAN=y
CONFIG_HAVE_KMSAN_COMPILER=y
# end of Memory Debugging

# CONFIG_DEBUG_SHIRQ is not set

#
# Debug Oops, Lockups and Hangs
#
CONFIG_PANIC_ON_OOPS=y
CONFIG_PANIC_TIMEOUT=86400
CONFIG_LOCKUP_DETECTOR=y
CONFIG_SOFTLOCKUP_DETECTOR=y
# CONFIG_SOFTLOCKUP_DETECTOR_INTR_STORM is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC=1
CONFIG_HAVE_HARDLOCKUP_DETECTOR_BUDDY=y
CONFIG_HARDLOCKUP_DETECTOR=y
# CONFIG_HARDLOCKUP_DETECTOR_PREFER_BUDDY is not set
CONFIG_HARDLOCKUP_DETECTOR_PERF=y
# CONFIG_HARDLOCKUP_DETECTOR_BUDDY is not set
# CONFIG_HARDLOCKUP_DETECTOR_ARCH is not set
CONFIG_HARDLOCKUP_DETECTOR_COUNTS_HRTIMER=y
CONFIG_HARDLOCKUP_CHECK_TIMESTAMP=y
CONFIG_BOOTPARAM_HARDLOCKUP_PANIC=y
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=140
CONFIG_BOOTPARAM_HUNG_TASK_PANIC=1
CONFIG_WQ_WATCHDOG=y
CONFIG_BOOTPARAM_WQ_STALL_PANIC=0
# CONFIG_WQ_CPU_INTENSIVE_REPORT is not set
# CONFIG_TEST_LOCKUP is not set
# end of Debug Oops, Lockups and Hangs

#
# Scheduler Debugging
#
CONFIG_SCHED_INFO=y
CONFIG_SCHEDSTATS=y
# end of Scheduler Debugging

CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_ATOMIC is not set

#
# Lock Debugging (spinlocks, mutexes, etc...)
#
CONFIG_LOCK_DEBUGGING_SUPPORT=y
CONFIG_PROVE_LOCKING=y
CONFIG_PROVE_RAW_LOCK_NESTING=y
# CONFIG_LOCK_STAT is not set
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_WW_MUTEX_SLOWPATH=y
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_LOCKDEP=y
CONFIG_LOCKDEP_BITS=20
CONFIG_LOCKDEP_CHAINS_BITS=20
CONFIG_LOCKDEP_STACK_TRACE_BITS=20
CONFIG_LOCKDEP_STACK_TRACE_HASH_BITS=14
CONFIG_LOCKDEP_CIRCULAR_QUEUE_BITS=12
# CONFIG_DEBUG_LOCKDEP is not set
CONFIG_DEBUG_ATOMIC_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_LOCK_TORTURE_TEST is not set
# CONFIG_WW_MUTEX_SELFTEST is not set
# CONFIG_SCF_TORTURE_TEST is not set
CONFIG_CSD_LOCK_WAIT_DEBUG=y
# CONFIG_CSD_LOCK_WAIT_DEBUG_DEFAULT is not set
# end of Lock Debugging (spinlocks, mutexes, etc...)

CONFIG_TRACE_IRQFLAGS=y
CONFIG_TRACE_IRQFLAGS_NMI=y
CONFIG_NMI_CHECK_CPU=y
CONFIG_DEBUG_IRQFLAGS=y
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_KOBJECT_RELEASE is not set

#
# Debug kernel data structures
#
CONFIG_DEBUG_LIST=y
CONFIG_DEBUG_PLIST=y
CONFIG_DEBUG_SG=y
CONFIG_DEBUG_NOTIFIERS=y
# CONFIG_DEBUG_CLOSURES is not set
CONFIG_DEBUG_MAPLE_TREE=y
# end of Debug kernel data structures

#
# RCU Debugging
#
CONFIG_PROVE_RCU=y
# CONFIG_RCU_SCALE_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_REF_SCALE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=100
CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=0
# CONFIG_RCU_CPU_STALL_CPUTIME is not set
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_EQS_DEBUG=y
# end of RCU Debugging

# CONFIG_DEBUG_WQ_FORCE_RR_CPU is not set
# CONFIG_CPU_HOTPLUG_STATE_CONTROL is not set
# CONFIG_LATENCYTOP is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_NOP_TRACER=y
CONFIG_HAVE_RETHOOK=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_ARGS=y
CONFIG_HAVE_FTRACE_REGS_HAVING_PT_REGS=y
CONFIG_HAVE_DYNAMIC_FTRACE_NO_PATCHABLE=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_JMP=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_FENTRY=y
CONFIG_HAVE_OBJTOOL_MCOUNT=y
CONFIG_HAVE_OBJTOOL_NOP_MCOUNT=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_HAVE_BUILDTIME_MCOUNT_SORT=y
CONFIG_TRACE_CLOCK=y
CONFIG_RING_BUFFER=y
CONFIG_EVENT_TRACING=y
CONFIG_CONTEXT_SWITCH_TRACER=y
CONFIG_PREEMPTIRQ_TRACEPOINTS=y
CONFIG_TRACING=y
CONFIG_GENERIC_TRACER=y
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
CONFIG_TRACEFS_AUTOMOUNT_DEPRECATED=y
# CONFIG_BOOTTIME_TRACING is not set
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_PREEMPT_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_HWLAT_TRACER is not set
# CONFIG_OSNOISE_TRACER is not set
# CONFIG_TIMERLAT_TRACER is not set
# CONFIG_MMIOTRACE is not set
# CONFIG_FTRACE_SYSCALLS is not set
# CONFIG_TRACER_SNAPSHOT is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
CONFIG_BLK_DEV_IO_TRACE=y
# CONFIG_PROBE_EVENTS_DUMP_FETCHARG is not set
CONFIG_UPROBE_EVENTS=y
CONFIG_EPROBE_EVENTS=y
CONFIG_BPF_EVENTS=y
CONFIG_DYNAMIC_EVENTS=y
CONFIG_PROBE_EVENTS=y
# CONFIG_SYNTH_EVENTS is not set
# CONFIG_USER_EVENTS is not set
# CONFIG_HIST_TRIGGERS is not set
CONFIG_TRACE_EVENT_INJECT=y
# CONFIG_TRACEPOINT_BENCHMARK is not set
# CONFIG_RING_BUFFER_BENCHMARK is not set
# CONFIG_TRACE_EVAL_MAP_FILE is not set
# CONFIG_FTRACE_STARTUP_TEST is not set
# CONFIG_RING_BUFFER_STARTUP_TEST is not set
CONFIG_RING_BUFFER_VALIDATE_TIME_DELTAS=y
# CONFIG_RING_BUFFER_PERSISTENT_INJECT is not set
# CONFIG_PREEMPTIRQ_DELAY_TEST is not set
# CONFIG_RV is not set
# CONFIG_TRACE_REMOTE_TEST is not set
CONFIG_PROVIDE_OHCI1394_DMA_INIT=y
# CONFIG_SAMPLES is not set
CONFIG_HAVE_SAMPLE_FTRACE_DIRECT=y
CONFIG_HAVE_SAMPLE_FTRACE_DIRECT_MULTI=y
CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y
# CONFIG_STRICT_DEVMEM is not set

#
# x86 Debugging
#
CONFIG_EARLY_PRINTK_USB=y
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
CONFIG_EARLY_PRINTK_DBGP=y
# CONFIG_EARLY_PRINTK_USB_XDBC is not set
# CONFIG_DEBUG_TLBFLUSH is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
# CONFIG_X86_DECODER_SELFTEST is not set
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEBUG_BOOT_PARAMS=y
# CONFIG_CPA_DEBUG is not set
CONFIG_DEBUG_ENTRY=y
# CONFIG_DEBUG_NMI_SELFTEST is not set
CONFIG_X86_DEBUG_FPU=y
# CONFIG_PUNIT_ATOM_DEBUG is not set
CONFIG_UNWINDER_ORC=y
# CONFIG_UNWINDER_FRAME_POINTER is not set
# end of x86 Debugging

#
# Kernel Testing and Coverage
#
# CONFIG_KUNIT is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
CONFIG_FAULT_INJECTION=y
CONFIG_FAILSLAB=y
CONFIG_FAIL_PAGE_ALLOC=y
CONFIG_FAULT_INJECTION_USERCOPY=y
CONFIG_FAIL_MAKE_REQUEST=y
CONFIG_FAIL_IO_TIMEOUT=y
CONFIG_FAIL_FUTEX=y
CONFIG_FAULT_INJECTION_DEBUG_FS=y
# CONFIG_FAIL_MMC_REQUEST is not set
# CONFIG_FAIL_SKB_REALLOC is not set
CONFIG_FAULT_INJECTION_CONFIGFS=y
# CONFIG_FAULT_INJECTION_STACKTRACE_FILTER is not set
CONFIG_ARCH_HAS_KCOV=y
CONFIG_KCOV=y
CONFIG_KCOV_ENABLE_COMPARISONS=y
CONFIG_KCOV_INSTRUMENT_ALL=y
CONFIG_KCOV_IRQ_AREA_SIZE=0x40000
# CONFIG_KCOV_SELFTEST is not set
CONFIG_RUNTIME_TESTING_MENU=y
# CONFIG_TEST_DHRY is not set
# CONFIG_LKDTM is not set
# CONFIG_TEST_DIV64 is not set
# CONFIG_TEST_MULDIV64 is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_TEST_REF_TRACKER is not set
# CONFIG_RBTREE_TEST is not set
# CONFIG_REED_SOLOMON_TEST is not set
# CONFIG_INTERVAL_TREE_TEST is not set
# CONFIG_PERCPU_TEST is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_ASYNC_RAID6_TEST is not set
# CONFIG_TEST_HEXDUMP is not set
# CONFIG_TEST_KSTRTOX is not set
# CONFIG_TEST_BITMAP is not set
# CONFIG_TEST_XARRAY is not set
# CONFIG_TEST_MAPLE_TREE is not set
# CONFIG_TEST_RHASHTABLE is not set
# CONFIG_TEST_IDA is not set
# CONFIG_TEST_LKM is not set
# CONFIG_TEST_BITOPS is not set
# CONFIG_TEST_VMALLOC is not set
# CONFIG_TEST_WORKQUEUE is not set
# CONFIG_TEST_BPF is not set
# CONFIG_FIND_BIT_BENCHMARK is not set
# CONFIG_REGION_ALLOC_BENCHMARK is not set
# CONFIG_TEST_FIRMWARE is not set
# CONFIG_TEST_SYSCTL is not set
# CONFIG_CONTEXT_ANALYSIS_TEST is not set
# CONFIG_TEST_UDELAY is not set
# CONFIG_TEST_STATIC_KEYS is not set
# CONFIG_TEST_DYNAMIC_DEBUG is not set
# CONFIG_TEST_KMOD is not set
# CONFIG_TEST_KALLSYMS is not set
# CONFIG_TEST_DEBUG_VIRTUAL is not set
# CONFIG_TEST_MEMCAT_P is not set
# CONFIG_TEST_MEMINIT is not set
# CONFIG_TEST_FREE_PAGES is not set
# CONFIG_TEST_CLOCKSOURCE_WATCHDOG is not set
# CONFIG_TEST_OBJPOOL is not set
CONFIG_ARCH_USE_MEMTEST=y
# CONFIG_MEMTEST is not set
# end of Kernel Testing and Coverage

#
# Rust hacking
#
# end of Rust hacking
# end of Kernel hacking

CONFIG_IO_URING_BPF=y
KernelRepo git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
ReproCID 0
ReproOpts
ReproSyzID 0
SyzkallerCommit 95928915a1f68c13ccccada603cedda6b36a84b7
TargetArch amd64
TargetOS linux
TargetVMArch amd64

Outputs:
DenialOfService βœ…
Exploitable βœ…
FilesystemTrigger ❌
NetworkTrigger ❌
PeripheralTrigger ❌
RemoteTrigger ❌
Unprivileged ❌
UserNamespace ❌
VMGuestTrigger ❌
VMHostTrigger ❌
Explanation
**Bug Mechanism and Impact**
The bug is a slab-use-after-free write in the XFS filesystem's Committed Item
List (CIL) push worker. It occurs when `xfs_sync_sb_buf` commits a transaction
that logs the superblock buffer and then immediately issues a synchronous write
(`xfs_bwrite`) on the same buffer.

When the transaction commits, the buffer's log item is added to a per-CPU list
(`cilpcp->log_items`) to be processed by a background CIL push. However, the
immediate `xfs_bwrite` causes the buffer's I/O completion routine
(`xfs_buf_ioend`) to run. This routine sees the attached log item, removes it
from the Active Item List (AIL), and releases it (`xfs_buf_item_relse`), which
frees the `xfs_buf_log_item` structure back to the slab allocator.

Later, when the background CIL push worker (`xlog_cil_push_work`) aggregates the
per-CPU lists via `xlog_cil_push_pcp_aggregate`, it attempts to splice the freed
log item's `li_cil` list node (`list_splice_init`), resulting in a
use-after-free write.

Because this is a use-after-free write involving linked list pointers
(`__list_splice`), it can be used to corrupt slab metadata or overwrite
arbitrary kernel pointers, making it theoretically **Exploitable** for privilege
escalation or arbitrary code execution. It also trivially causes a kernel panic,
leading to a **Denial of Service**.

**Reachability Analysis**
Despite the severe memory corruption, the bug is highly restricted in its
reachability:
- The only caller of `xfs_sync_sb_buf` in the kernel is the `XFS_IOC_SETLABEL`
ioctl (`xfs_ioc_setlabel`).
- The `xfs_ioc_setlabel` function explicitly enforces a capability check at its
entry point: `if (!capable(CAP_SYS_ADMIN)) return -EPERM;`.
- The `capable()` function checks for capabilities in the *initial* user
namespace (unlike `ns_capable()`).
- Therefore, this bug is **not accessible from unprivileged processes** and
**not accessible from user namespaces**.
- The bug requires an explicit ioctl call from a highly privileged process (root
in the init namespace) and is not triggered automatically during mount, meaning
it cannot be exploited via a **Malicious Filesystem Trigger**.
- It is not exposed to **Network**, **Remote**, or **Peripheral** attack
vectors.

Crash report:
==================================================================
BUG: KASAN: slab-use-after-free in __list_splice include/linux/list.h:580 [inline]
BUG: KASAN: slab-use-after-free in list_splice_init include/linux/list.h:619 [inline]
BUG: KASAN: slab-use-after-free in xlog_cil_push_pcp_aggregate fs/xfs/xfs_log_cil.c:137 [inline]
BUG: KASAN: slab-use-after-free in xlog_cil_push_work+0x9b6/0x2a90 fs/xfs/xfs_log_cil.c:1417
Write of size 8 at addr ffff8880261d5d88 by task kworker/u8:9/1441

CPU: 0 UID: 0 PID: 1441 Comm: kworker/u8:9 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: xfs-cil/loop3 xlog_cil_push_work
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_address_description+0x55/0x1e0 mm/kasan/report.c:378
 print_report+0x58/0x70 mm/kasan/report.c:482
 kasan_report+0x117/0x150 mm/kasan/report.c:595
 __list_splice include/linux/list.h:580 [inline]
 list_splice_init include/linux/list.h:619 [inline]
 xlog_cil_push_pcp_aggregate fs/xfs/xfs_log_cil.c:137 [inline]
 xlog_cil_push_work+0x9b6/0x2a90 fs/xfs/xfs_log_cil.c:1417
 process_one_work kernel/workqueue.c:3396 [inline]
 process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
 kthread+0x38b/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Allocated by task 5944:
 kasan_save_stack mm/kasan/common.c:57 [inline]
 kasan_save_track+0x3e/0x80 mm/kasan/common.c:78
 unpoison_slab_object mm/kasan/common.c:340 [inline]
 __kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:366
 kasan_slab_alloc include/linux/kasan.h:253 [inline]
 slab_post_alloc_hook mm/slub.c:4683 [inline]
 slab_alloc_node mm/slub.c:4996 [inline]
 kmem_cache_alloc_noprof+0x360/0x690 mm/slub.c:5010
 xfs_buf_item_init+0x6a/0x6e0 fs/xfs/xfs_buf_item.c:872
 _xfs_trans_bjoin+0x46/0x110 fs/xfs/xfs_trans_buf.c:75
 __xfs_trans_getsb+0x65/0x4a0 fs/xfs/xfs_trans_buf.c:191
 xfs_log_sb+0x43/0x200 fs/xfs/libxfs/xfs_sb.c:1327
 xfs_sync_sb_buf+0xc2/0x290 fs/xfs/libxfs/xfs_sb.c:1479
 xfs_ioc_setlabel+0x1d7/0x340 fs/xfs/xfs_ioctl.c:1081
 xfs_file_ioctl+0x901/0x1590 fs/xfs/xfs_ioctl.c:1238
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl+0xff/0x170 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 5944:
 kasan_save_stack mm/kasan/common.c:57 [inline]
 kasan_save_track+0x3e/0x80 mm/kasan/common.c:78
 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:584
 poison_slab_object mm/kasan/common.c:253 [inline]
 __kasan_slab_free+0x5c/0x80 mm/kasan/common.c:285
 kasan_slab_free include/linux/kasan.h:235 [inline]
 slab_free_hook mm/slub.c:2748 [inline]
 slab_free mm/slub.c:6508 [inline]
 kmem_cache_free+0x187/0x6d0 mm/slub.c:6635
 xfs_buf_ioend+0x235/0x790 fs/xfs/xfs_buf.c:1167
 xfs_buf_iowait+0x133/0x420 fs/xfs/xfs_buf.c:1336
 xfs_bwrite+0x5f/0xe0 fs/xfs/xfs_buf.c:1239
 xfs_sync_sb_buf+0x172/0x290 fs/xfs/libxfs/xfs_sb.c:1489
 xfs_ioc_setlabel+0x1d7/0x340 fs/xfs/xfs_ioctl.c:1081
 xfs_file_ioctl+0x901/0x1590 fs/xfs/xfs_ioctl.c:1238
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl+0xff/0x170 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

The buggy address belongs to the object at ffff8880261d5d20
 which belongs to the cache xfs_buf_item of size 272
The buggy address is located 104 bytes inside of
 freed 272-byte region [ffff8880261d5d20, ffff8880261d5e30)

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x261d5
flags: 0x80000000000000(node=0|zone=1)
page_type: f5(slab)
raw: 0080000000000000 ffff88814043fdc0 dead000000000122 0000000000000000
raw: 0000000000000000 00000002000c000c 00000000f5000000 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0xd2c40(GFP_NOFS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 5795, tgid 5794 (syz.3.4), ts 106215173769
 set_page_owner include/linux/page_owner.h:33 [inline]
 post_alloc_hook+0x1f9/0x250 mm/page_alloc.c:1871
 prep_new_page mm/page_alloc.c:1879 [inline]
 get_page_from_freelist+0x2591/0x2600 mm/page_alloc.c:3943
 __alloc_frozen_pages_noprof+0x230/0x5c0 mm/page_alloc.c:5436
 alloc_slab_page mm/slub.c:3347 [inline]
 allocate_slab+0x7d/0x620 mm/slub.c:3462
 new_slab mm/slub.c:3513 [inline]
 refill_objects+0x2d8/0x350 mm/slub.c:7417
 refill_sheaf mm/slub.c:2885 [inline]
 __pcs_replace_empty_main+0x339/0x690 mm/slub.c:4774
 alloc_from_pcs mm/slub.c:4850 [inline]
 slab_alloc_node mm/slub.c:4984 [inline]
 kmem_cache_alloc_noprof+0x45d/0x690 mm/slub.c:5010
 xfs_buf_item_init+0x6a/0x6e0 fs/xfs/xfs_buf_item.c:872
 _xfs_trans_bjoin+0x46/0x110 fs/xfs/xfs_trans_buf.c:75
 xfs_trans_read_buf_map+0x2ee/0x820 fs/xfs/xfs_trans_buf.c:294
 xfs_trans_read_buf fs/xfs/xfs_trans.h:212 [inline]
 xfs_read_icluster+0x218/0x3e0 fs/xfs/libxfs/xfs_inode_buf.c:139
 xfs_iget_cache_miss fs/xfs/xfs_icache.c:663 [inline]
 xfs_iget+0xc34/0x2f00 fs/xfs/xfs_icache.c:804
 xfs_trans_metafile_iget+0x77/0x330 fs/xfs/xfs_icache.c:853
 xfs_rtginode_load+0x3a3/0x920 fs/xfs/libxfs/xfs_rtgroup.c:469
 xfs_rtmount_rtg fs/xfs/xfs_rtalloc.c:1684 [inline]
 xfs_rtmount_inodes+0x14f/0x7a0 fs/xfs/xfs_rtalloc.c:1721
 xfs_mountfs+0x1254/0x2380 fs/xfs/xfs_mount.c:1095
page last free pid 5581 tgid 5581 ts 106036434714 stack trace:
 reset_page_owner include/linux/page_owner.h:26 [inline]
 __free_pages_prepare mm/page_alloc.c:1418 [inline]
 __free_frozen_pages+0xf8e/0x1070 mm/page_alloc.c:2962
 __slab_free+0x250/0x2a0 mm/slub.c:5823
 qlink_free mm/kasan/quarantine.c:163 [inline]
 qlist_free_all+0x99/0x100 mm/kasan/quarantine.c:179
 kasan_quarantine_reduce+0x148/0x160 mm/kasan/quarantine.c:286
 __kasan_slab_alloc+0x22/0x80 mm/kasan/common.c:350
 kasan_slab_alloc include/linux/kasan.h:253 [inline]
 slab_post_alloc_hook mm/slub.c:4683 [inline]
 slab_alloc_node mm/slub.c:4996 [inline]
 __do_kmalloc_node mm/slub.c:5413 [inline]
 __kmalloc_node_track_caller_noprof+0x505/0x7b0 mm/slub.c:5545
 memdup_user+0x2b/0xd0 mm/util.c:221
 strndup_user+0x68/0xd0 mm/util.c:280
 copy_mount_string fs/namespace.c:4076 [inline]
 __do_sys_mount fs/namespace.c:4387 [inline]
 __se_sys_mount+0xdf/0x420 fs/namespace.c:4374
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Memory state around the buggy address:
 ffff8880261d5c80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff8880261d5d00: fc fc fc fc fa fb fb fb fb fb fb fb fb fb fb fb
>ffff8880261d5d80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                      ^
 ffff8880261d5e00: fb fb fb fb fb fb fc fc fc fc fc fc fc fc 00 00
 ffff8880261d5e80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================

Trajectory: (Expand/Collapse All)
Seq Timestamp Type Name Duration
0/0 2026/09/19 00:00 flow assessment-security
53m Results:
map[DenialOfService:true Explanation:**Bug Mechanism and Impact**
The bug is a slab-use-after-free write in the XFS filesystem's Committed Item
List (CIL) push worker. It occurs when `xfs_sync_sb_buf` commits a transaction
that logs the superblock buffer and then immediately issues a synchronous write
(`xfs_bwrite`) on the same buffer.

When the transaction commits, the buffer's log item is added to a per-CPU list
(`cilpcp->log_items`) to be processed by a background CIL push. However, the
immediate `xfs_bwrite` causes the buffer's I/O completion routine
(`xfs_buf_ioend`) to run. This routine sees the attached log item, removes it
from the Active Item List (AIL), and releases it (`xfs_buf_item_relse`), which
frees the `xfs_buf_log_item` structure back to the slab allocator.

Later, when the background CIL push worker (`xlog_cil_push_work`) aggregates the
per-CPU lists via `xlog_cil_push_pcp_aggregate`, it attempts to splice the freed
log item's `li_cil` list node (`list_splice_init`), resulting in a
use-after-free write.

Because this is a use-after-free write involving linked list pointers
(`__list_splice`), it can be used to corrupt slab metadata or overwrite
arbitrary kernel pointers, making it theoretically **Exploitable** for privilege
escalation or arbitrary code execution. It also trivially causes a kernel panic,
leading to a **Denial of Service**.

**Reachability Analysis**
Despite the severe memory corruption, the bug is highly restricted in its
reachability:
- The only caller of `xfs_sync_sb_buf` in the kernel is the `XFS_IOC_SETLABEL`
ioctl (`xfs_ioc_setlabel`).
- The `xfs_ioc_setlabel` function explicitly enforces a capability check at its
entry point: `if (!capable(CAP_SYS_ADMIN)) return -EPERM;`.
- The `capable()` function checks for capabilities in the *initial* user
namespace (unlike `ns_capable()`).
- Therefore, this bug is **not accessible from unprivileged processes** and
**not accessible from user namespaces**.
- The bug requires an explicit ioctl call from a highly privileged process (root
in the init namespace) and is not triggered automatically during mount, meaning
it cannot be exploited via a **Malicious Filesystem Trigger**.
- It is not exposed to **Network**, **Remote**, or **Peripheral** attack
vectors. Exploitable:true FilesystemTrigger:false NetworkTrigger:false PeripheralTrigger:false RemoteTrigger:false Unprivileged:false UserNamespace:false VMGuestTrigger:false VMHostTrigger:false]

1/1 2026/09/19 00:00 action syz-repro-to-c-repro
0m Results:
map[SimplifiedCRepro:]

2/1 2026/09/19 00:00 action kernel-checkouter
1m Results:
map[KernelSrc:/app/workdir/cache/src/5954088e94b7c5ecde095005a33062bb138de6d5]

3/1 2026/09/19 00:01 action kernel-builder
27m Results:
map[KernelObj:/app/workdir/cache/build/9b19c66ec68682a4ee2908af50280f321d50518b]

4/1 2026/09/19 00:29 action codesearch-prepare
15m Results:
map[Index:codesearch-index]

5/1 2026/09/19 00:45 agent expert
8m Model:
deep-reasoning

Results:
map[DenialOfService:true Exploitable:true FilesystemTrigger:false NetworkTrigger:false PeripheralTrigger:false RemoteTrigger:false Unprivileged:false UserNamespace:false VMGuestTrigger:false VMHostTrigger:false]

Instruction:
You are an experienced Linux kernel security engineer. Your task is to analyze given kernel bug report
and determine its security impact based on the following dimensions.

Use the provided tools to examine the source code, check for capability checks (e.g., capable(), ns_capable()),
and understand the nature of the bug. Analyze the given kernel build and configuration.
You can check the kernel config by grepping ".config" file; you can check kernel cmdline by grepping
".config" file for "CONFIG_CMDLINE=". Assume sysctl parameters have default values.
But analyze for the corresponding production build w/o debugging tools enabled (like KASAN, KMSAN, UBSAN).

Try different strategies when analyzing the bug:
 - think of ways in which the vulnerable code is unreachable
 - or the other way around: try to come up with different ideas of how an unprivileged user can reach the bug
If still unsure err on the side of the bug being non-exploitable/not-accessible.
In the final reply, provide a reasoning for your assessment.

Analysis dimensions:

* Exploitable:
Determine if the bug can result in memory corruption, elevated privileges, or an information leak.
Memory safety issues are almost always exploitable (KASAN or UBSAN reports for use-after-free, out-of-bounds;
refcounting issues, corrupted lists, etc). When kernel is crashing on a completely wild pointer access
(e.g. user-space address, or non-canonical address, but not on NULL or address corresponding to KASAN shadow
for NULL address), including both data accesses and control transfers, that also usually implies possibility
of exploitation. Such reports usually say "unable to handle kernel paging request".
Uses of uninitialized values detected by KMSAN may be exploitable b/c attacker frequently can affect uninit
values with spraying techniques. However, for these exploitability depends on how exactly the uninit value
is used in the code, and what it affects.
Information leaks are exploitable on their own and should be classified as such. A bug that copies kernel
memory contents to userspace (e.g. an out-of-bounds read whose result is returned to the caller, or
uninitialized stack/heap bytes written to a user buffer) is exploitable: it can reveal kernel pointer
values and defeat KASLR, expose sensitive data such as cryptographic keys or other processes' memory, and
serves as a necessary building block in most modern kernel privilege-escalation exploit chains. Do not classify
an information leak as non-exploitable solely because it does not directly cause a memory write or control-flow
hijack; the leak itself is the exploit primitive.

Think of what happens after the bug is triggered. Some bugs cause kernel panic and halt execution,
they are harder to exploit. For example, BUG reports halts the kernel. However, WARNING reports don't halt
execution in production builds. Debug bug detection tools (like KASAN, KMSAN, KCSAN, UBSAN) are also not enabled
in production builds, so attacker can freely exploit these bugs w/o being detected by these tools.
If you see an integer overflow, think how the overflowed value used later (if it's used as allocation size,
or an array index). If you see an out-of-bounds read, think if it's followed by an out-of-bounds write as well.
Some KCSAN data-races may be exploitable by skilled attackers as well. Think what data structures got corrupted
as the result of data races and how. However, note that kernel has lots of "benign" data races that don't lead
to any runtime misbehavior at all.

* Denial Of Service:
Determine if the bug can result in denial-of-service. Most bugs can, since they cause system crash,
hangs, deadlocks, or resource leaks. This is mostly applicable to WARNING bugs that won't cause system crash
in production. For these think what will be consequences of the violation of the kernel assumptions flagged
by the WARNING. In some cases the unexpected condition is also properly handled by the normal control flow
(e.g. with "if (WARN_ON(...))"), these won't cause denial-of-service. If the condition is not handled,
then it may or may not cause denial-of-service.

* Accessible From Unprivileged Processes:
Determine if the bug can be reached from a typical (non-root) user process that does NOT have any special capabilities
(like CAP_SYS_ADMIN, CAP_NET_ADMIN, CAP_NET_RAW, CAP_PERFMON) or access to device nodes restricted to root.
Assume that unprivileged_bpf_disabled=1, that is eBPF loading is not accessible. However, cBPF (classical BPF)
is still accessible to non-root processes.
Assume that user namespaces are not accessible, that is, the process cannot get the mentioned capabilities even
within a new user namespace (checked by ns_capable() function in the kernel sources).

* Accessible From User Namespaces:
Determine if the bug can be reached within a user-namespace where the process has all capabilities
(including CAP_SYS_ADMIN, CAP_NET_ADMIN, CAP_NET_RAW, CAP_PERFMON). Such capabilities are checked with ns_capable()
function in the kernel sources.

* VM Guest Trigger:
Determine if the bug can be triggered from the context of a typical KVM guest (e.g., set up by a QEMU VMM).
Consider accesses to standard Linux host paravirtualized features (virtio-blk, virtio-net, etc.),
and handling of VM exits in the KVM code.

* VM Host Trigger in The Confidential Computing Context:
Determine if the bug can be triggered in a confidential computing guest kernel from the context of a KVM host.
Consider access to standard Linux guest paravirtualized features (virtio-blk, virtio-net, etc.).

* Ethernet Network Trigger:
Determine if the bug can be triggered by processing ingress network Ethernet traffic, either directly (network stack)
or via drivers exposed to network data.

* Other Remote Trigger:
Determine if the bug can be triggered by processing remote traffic other than Ethernet (Wifi, Bluetooth, NFC, etc).

* Peripheral Trigger:
Determine if the bug can be triggered via an untrusted peripheral device that can be physically plugged
into a system, such as a USB device or a niche hardware driver handling external hardware inputs.
This is particularly important for mobile and desktop environments where users can plug in unknown devices.

* Malicious Filesystem Trigger:
Determine if the bug can be triggered by the kernel mounting and parsing a malicious filesystem image.
This is highly critical for Desktop and Mobile environments where external media or downloaded images
might be auto-mounted.

Don't make assumptions about the kernel source code (it may be different from what you assume it is).
Extensively use the provided code access tools (codesearch-*, git-*, grepper, etc)
to examine the actual source code, and confirm any assumptions.
Prefer calling several tools at the same time to save round-trips.


Use set-results tool to provide results of the analysis.
It must be called exactly once before the final reply.
Ignore results of this tool.

Prompt:
The kernel bug report is:

==================================================================
BUG: KASAN: slab-use-after-free in __list_splice include/linux/list.h:580 [inline]
BUG: KASAN: slab-use-after-free in list_splice_init include/linux/list.h:619 [inline]
BUG: KASAN: slab-use-after-free in xlog_cil_push_pcp_aggregate fs/xfs/xfs_log_cil.c:137 [inline]
BUG: KASAN: slab-use-after-free in xlog_cil_push_work+0x9b6/0x2a90 fs/xfs/xfs_log_cil.c:1417
Write of size 8 at addr ffff8880261d5d88 by task kworker/u8:9/1441

CPU: 0 UID: 0 PID: 1441 Comm: kworker/u8:9 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: xfs-cil/loop3 xlog_cil_push_work
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_address_description+0x55/0x1e0 mm/kasan/report.c:378
 print_report+0x58/0x70 mm/kasan/report.c:482
 kasan_report+0x117/0x150 mm/kasan/report.c:595
 __list_splice include/linux/list.h:580 [inline]
 list_splice_init include/linux/list.h:619 [inline]
 xlog_cil_push_pcp_aggregate fs/xfs/xfs_log_cil.c:137 [inline]
 xlog_cil_push_work+0x9b6/0x2a90 fs/xfs/xfs_log_cil.c:1417
 process_one_work kernel/workqueue.c:3396 [inline]
 process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
 kthread+0x38b/0x470 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Allocated by task 5944:
 kasan_save_stack mm/kasan/common.c:57 [inline]
 kasan_save_track+0x3e/0x80 mm/kasan/common.c:78
 unpoison_slab_object mm/kasan/common.c:340 [inline]
 __kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:366
 kasan_slab_alloc include/linux/kasan.h:253 [inline]
 slab_post_alloc_hook mm/slub.c:4683 [inline]
 slab_alloc_node mm/slub.c:4996 [inline]
 kmem_cache_alloc_noprof+0x360/0x690 mm/slub.c:5010
 xfs_buf_item_init+0x6a/0x6e0 fs/xfs/xfs_buf_item.c:872
 _xfs_trans_bjoin+0x46/0x110 fs/xfs/xfs_trans_buf.c:75
 __xfs_trans_getsb+0x65/0x4a0 fs/xfs/xfs_trans_buf.c:191
 xfs_log_sb+0x43/0x200 fs/xfs/libxfs/xfs_sb.c:1327
 xfs_sync_sb_buf+0xc2/0x290 fs/xfs/libxfs/xfs_sb.c:1479
 xfs_ioc_setlabel+0x1d7/0x340 fs/xfs/xfs_ioctl.c:1081
 xfs_file_ioctl+0x901/0x1590 fs/xfs/xfs_ioctl.c:1238
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl+0xff/0x170 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 5944:
 kasan_save_stack mm/kasan/common.c:57 [inline]
 kasan_save_track+0x3e/0x80 mm/kasan/common.c:78
 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:584
 poison_slab_object mm/kasan/common.c:253 [inline]
 __kasan_slab_free+0x5c/0x80 mm/kasan/common.c:285
 kasan_slab_free include/linux/kasan.h:235 [inline]
 slab_free_hook mm/slub.c:2748 [inline]
 slab_free mm/slub.c:6508 [inline]
 kmem_cache_free+0x187/0x6d0 mm/slub.c:6635
 xfs_buf_ioend+0x235/0x790 fs/xfs/xfs_buf.c:1167
 xfs_buf_iowait+0x133/0x420 fs/xfs/xfs_buf.c:1336
 xfs_bwrite+0x5f/0xe0 fs/xfs/xfs_buf.c:1239
 xfs_sync_sb_buf+0x172/0x290 fs/xfs/libxfs/xfs_sb.c:1489
 xfs_ioc_setlabel+0x1d7/0x340 fs/xfs/xfs_ioctl.c:1081
 xfs_file_ioctl+0x901/0x1590 fs/xfs/xfs_ioctl.c:1238
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl+0xff/0x170 fs/ioctl.c:583
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

The buggy address belongs to the object at ffff8880261d5d20
 which belongs to the cache xfs_buf_item of size 272
The buggy address is located 104 bytes inside of
 freed 272-byte region [ffff8880261d5d20, ffff8880261d5e30)

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x261d5
flags: 0x80000000000000(node=0|zone=1)
page_type: f5(slab)
raw: 0080000000000000 ffff88814043fdc0 dead000000000122 0000000000000000
raw: 0000000000000000 00000002000c000c 00000000f5000000 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0xd2c40(GFP_NOFS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 5795, tgid 5794 (syz.3.4), ts 106215173769
 set_page_owner include/linux/page_owner.h:33 [inline]
 post_alloc_hook+0x1f9/0x250 mm/page_alloc.c:1871
 prep_new_page mm/page_alloc.c:1879 [inline]
 get_page_from_freelist+0x2591/0x2600 mm/page_alloc.c:3943
 __alloc_frozen_pages_noprof+0x230/0x5c0 mm/page_alloc.c:5436
 alloc_slab_page mm/slub.c:3347 [inline]
 allocate_slab+0x7d/0x620 mm/slub.c:3462
 new_slab mm/slub.c:3513 [inline]
 refill_objects+0x2d8/0x350 mm/slub.c:7417
 refill_sheaf mm/slub.c:2885 [inline]
 __pcs_replace_empty_main+0x339/0x690 mm/slub.c:4774
 alloc_from_pcs mm/slub.c:4850 [inline]
 slab_alloc_node mm/slub.c:4984 [inline]
 kmem_cache_alloc_noprof+0x45d/0x690 mm/slub.c:5010
 xfs_buf_item_init+0x6a/0x6e0 fs/xfs/xfs_buf_item.c:872
 _xfs_trans_bjoin+0x46/0x110 fs/xfs/xfs_trans_buf.c:75
 xfs_trans_read_buf_map+0x2ee/0x820 fs/xfs/xfs_trans_buf.c:294
 xfs_trans_read_buf fs/xfs/xfs_trans.h:212 [inline]
 xfs_read_icluster+0x218/0x3e0 fs/xfs/libxfs/xfs_inode_buf.c:139
 xfs_iget_cache_miss fs/xfs/xfs_icache.c:663 [inline]
 xfs_iget+0xc34/0x2f00 fs/xfs/xfs_icache.c:804
 xfs_trans_metafile_iget+0x77/0x330 fs/xfs/xfs_icache.c:853
 xfs_rtginode_load+0x3a3/0x920 fs/xfs/libxfs/xfs_rtgroup.c:469
 xfs_rtmount_rtg fs/xfs/xfs_rtalloc.c:1684 [inline]
 xfs_rtmount_inodes+0x14f/0x7a0 fs/xfs/xfs_rtalloc.c:1721
 xfs_mountfs+0x1254/0x2380 fs/xfs/xfs_mount.c:1095
page last free pid 5581 tgid 5581 ts 106036434714 stack trace:
 reset_page_owner include/linux/page_owner.h:26 [inline]
 __free_pages_prepare mm/page_alloc.c:1418 [inline]
 __free_frozen_pages+0xf8e/0x1070 mm/page_alloc.c:2962
 __slab_free+0x250/0x2a0 mm/slub.c:5823
 qlink_free mm/kasan/quarantine.c:163 [inline]
 qlist_free_all+0x99/0x100 mm/kasan/quarantine.c:179
 kasan_quarantine_reduce+0x148/0x160 mm/kasan/quarantine.c:286
 __kasan_slab_alloc+0x22/0x80 mm/kasan/common.c:350
 kasan_slab_alloc include/linux/kasan.h:253 [inline]
 slab_post_alloc_hook mm/slub.c:4683 [inline]
 slab_alloc_node mm/slub.c:4996 [inline]
 __do_kmalloc_node mm/slub.c:5413 [inline]
 __kmalloc_node_track_caller_noprof+0x505/0x7b0 mm/slub.c:5545
 memdup_user+0x2b/0xd0 mm/util.c:221
 strndup_user+0x68/0xd0 mm/util.c:280
 copy_mount_string fs/namespace.c:4076 [inline]
 __do_sys_mount fs/namespace.c:4387 [inline]
 __se_sys_mount+0xdf/0x420 fs/namespace.c:4374
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Memory state around the buggy address:
 ffff8880261d5c80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff8880261d5d00: fc fc fc fc fa fb fb fb fb fb fb fb fb fb fb fb
>ffff8880261d5d80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                      ^
 ffff8880261d5e00: fb fb fb fb fb fb fc fc fc fc fc fc fc fc 00 00
 ffff8880261d5e80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================




Reply:
**Bug Mechanism and Impact**
The bug is a slab-use-after-free write in the XFS filesystem's Committed Item List (CIL) push worker. It occurs when `xfs_sync_sb_buf` commits a transaction that logs the superblock buffer and then immediately issues a synchronous write (`xfs_bwrite`) on the same buffer. 

When the transaction commits, the buffer's log item is added to a per-CPU list (`cilpcp->log_items`) to be processed by a background CIL push. However, the immediate `xfs_bwrite` causes the buffer's I/O completion routine (`xfs_buf_ioend`) to run. This routine sees the attached log item, removes it from the Active Item List (AIL), and releases it (`xfs_buf_item_relse`), which frees the `xfs_buf_log_item` structure back to the slab allocator. 

Later, when the background CIL push worker (`xlog_cil_push_work`) aggregates the per-CPU lists via `xlog_cil_push_pcp_aggregate`, it attempts to splice the freed log item's `li_cil` list node (`list_splice_init`), resulting in a use-after-free write.

Because this is a use-after-free write involving linked list pointers (`__list_splice`), it can be used to corrupt slab metadata or overwrite arbitrary kernel pointers, making it theoretically **Exploitable** for privilege escalation or arbitrary code execution. It also trivially causes a kernel panic, leading to a **Denial of Service**.

**Reachability Analysis**
Despite the severe memory corruption, the bug is highly restricted in its reachability:
- The only caller of `xfs_sync_sb_buf` in the kernel is the `XFS_IOC_SETLABEL` ioctl (`xfs_ioc_setlabel`).
- The `xfs_ioc_setlabel` function explicitly enforces a capability check at its entry point: `if (!capable(CAP_SYS_ADMIN)) return -EPERM;`.
- The `capable()` function checks for capabilities in the *initial* user namespace (unlike `ns_capable()`). 
- Therefore, this bug is **not accessible from unprivileged processes** and **not accessible from user namespaces**.
- The bug requires an explicit ioctl call from a highly privileged process (root in the init namespace) and is not triggered automatically during mount, meaning it cannot be exploited via a **Malicious Filesystem Trigger**.
- It is not exposed to **Network**, **Remote**, or **Peripheral** attack vectors.

6/2 2026/09/19 00:45 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 9880
							output: 48
							thoughts: 173
						

Thoughts:
**Analyzing a KASAN Slab-Use-After-Free in XFS Logging**

Okay, so I've got a KASAN report, specifically a slab-use-after-free issue, and it looks like it's buried deep in the XFS logging code. The trace points to `xlog_cil_push_work` as the entry point, which isn't entirely surprising. These kinds of memory corruption bugs often manifest in complex data structures and concurrent operations – common in a filesystem’s logging component.

The core problem, as the trace shows, is in `__list_splice`, which is indirectly called through `list_splice_init` and then `xlog_cil_push_pcp_aggregate`. That's where things are getting messed up. The report indicates a write of size 8 bytes to address `ffff8880261d5d88`. And, crucially, this write is happening within an `xfs_buf_item` object, which is 272 bytes in size. The kicker? That write is occurring 104 bytes *into* a region that's already been freed. That means data is getting written to an area that should be off-limits.

My next move is obvious: I need to scrutinize `xlog_cil_push_pcp_aggregate`. The file and line number should be in the trace, but just in case, I'll go directly to `fs/xfs/xfs_log_cil.c` to see how that function interacts with the list manipulation and buffer item management. Time to dig into the code and see what kind of race condition or memory management oversight is at play here. This is likely due to stale pointers. I suspect that this is happening on a "push" or "aggregate" operation.



7/2 2026/09/19 00:45 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_push_pcp_aggregate]

Results:
map[SourceCode: 112:	/*
 113:	 * Aggregate the CIL per cpu structures into global counts, lists, etc and
 114:	 * clear the percpu state ready for the next context to use. This is called
 115:	 * from the push code with the context lock held exclusively, hence nothing else
 116:	 * will be accessing or modifying the per-cpu counters.
 117:	 */
 118:	static void
 119:	xlog_cil_push_pcp_aggregate(
 120:		struct xfs_cil		*cil,
 121:		struct xfs_cil_ctx	*ctx)
 122:	{
 123:		struct xlog_cil_pcp	*cilpcp;
 124:		int			cpu;
 125:	
 126:		for_each_cpu(cpu, &ctx->cil_pcpmask) {
 127:			cilpcp = per_cpu_ptr(cil->xc_pcp, cpu);
 128:	
 129:			ctx->ticket->t_curr_res += cilpcp->space_reserved;
 130:			cilpcp->space_reserved = 0;
 131:	
 132:			if (!list_empty(&cilpcp->busy_extents)) {
 133:				list_splice_init(&cilpcp->busy_extents,
 134:						&ctx->busy_extents.extent_list);
 135:			}
 136:			if (!list_empty(&cilpcp->log_items))
 137:				list_splice_init(&cilpcp->log_items, &ctx->log_items);
 138:	
 139:			/*
 140:			 * We're in the middle of switching cil contexts.  Reset the
 141:			 * counter we use to detect when the current context is nearing
 142:			 * full.
 143:			 */
 144:			cilpcp->space_used = 0;
 145:		}
 146:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

8/2 2026/09/19 00:45 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 11074
							output: 48
							thoughts: 144
						

Thoughts:
**Debugging a Nasty Kernel Crash**

Okay, so the kernel's puking at line 137, right in the middle of a `list_splice_init` call: `list_splice_init(&cilpcp->log_items, &ctx->log_items);`. My immediate thought is, "Aha! `list_splice_init` – that's a modifier; it messes with both those lists."  I'm seeing a Use-After-Free (UAF), a write, and the size is only 8 bytes. That's a good hint. We're talking about an `xfs_buf_item` object, according to the dump.

Now, `cilpcp->log_items`… that's a list of log items. And those log items, from what I know of XFS, are *embedded* within `xfs_buf_item` structures. So, clearly, the problem's likely in how those lists are being handled, or how the pointers are getting shuffled around during this splice. Time to go over the `xfs_buf_item` layout; I need to verify how these log items are positioned within the structure and figure out how they interact with the list manipulation. Let's see...



9/2 2026/09/19 00:45 tool codesearch-struct-layout
0m Error:
log-in to see details

Args:
map[ContextFile:fs/xfs/xfs_buf_item.c FieldOffset:<nil> Name:xfs_buf_item]

Results:
map[Fields:<nil>]

10/2 2026/09/19 00:45 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 11554
							output: 45
							thoughts: 16
						

Thoughts:
Here's my attempt at summarizing the thought process, tailored for an expert audience and written in the first person:

**Decoding the Data Structure**

Okay, wait a minute. Looking at this... It's not what I initially thought. My brain immediately jumped to a different structure, maybe related to the metadata btree implementation, but no. The key here, the one I need to fully understand the context, is `struct xfs_buf_log_item`. That changes everything. Now I'm thinking about the buffer logging subsystem, the write-ahead logging (WAL) aspects within XFS. This narrows the scope significantly. This likely involves the journaling and ensuring data consistency. Time to recall how `xfs_buf_log_item` interacts with the buffer cache, the log structures on disk, and the checkpointing process, now that's the angle.



11/2 2026/09/19 00:45 tool codesearch-struct-layout
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_log_item]

Results:
map[Fields:[map[Name:bli_item OffsetBits:0 SizeBits:1216] map[Name:bli_buf OffsetBits:1216 SizeBits:64] map[Name:bli_flags OffsetBits:1280 SizeBits:32] map[Name:bli_recur OffsetBits:1312 SizeBits:32] map[Name:bli_refcount OffsetBits:1344 SizeBits:32] map[Name:bli_format_count OffsetBits:1376 SizeBits:32] map[Name:bli_formats OffsetBits:1408 SizeBits:64] map[Name:__bli_format OffsetBits:1472 SizeBits:704]]]

12/2 2026/09/19 00:45 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 11990
							output: 43
							thoughts: 74
						

Thoughts:
**Analyzing a Potential XFS Bug**

Okay, so I'm looking at this memory corruption issue and immediately my mind focuses on the buffer size. The reported `xfs_buf_log_item` is 2176 bits, which is, conveniently, 272 bytes. Now, the crucial part here is the buggy address – it's located 104 bytes into this freed region. A quick mental calculation tells me that 104 bytes is equivalent to 832 bits. This screams "off-by-one" type of error. We are seeing corruption at 832 bits within a 2176 bit block. Now, I need to understand the structure. My next step is to drill down into the layout of the `xfs_log_item` itself. I need to visualize what's residing where within that 272 byte chunk to pinpoint how this 104-byte offset is leading to the corruption. Let's see...



13/2 2026/09/19 00:45 tool codesearch-struct-layout
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_log_item]

Results:
map[Fields:[map[Name:li_ail OffsetBits:0 SizeBits:128] map[Name:li_trans OffsetBits:128 SizeBits:128] map[Name:li_lsn OffsetBits:256 SizeBits:64] map[Name:li_log OffsetBits:320 SizeBits:64] map[Name:li_ailp OffsetBits:384 SizeBits:64] map[Name:li_type OffsetBits:448 SizeBits:32] map[Name:li_flags OffsetBits:512 SizeBits:64] map[Name:li_buf OffsetBits:576 SizeBits:64] map[Name:li_bio_list OffsetBits:640 SizeBits:128] map[Name:li_ops OffsetBits:768 SizeBits:64] map[Name:li_cil OffsetBits:832 SizeBits:128] map[Name:li_lv OffsetBits:960 SizeBits:64] map[Name:li_lv_shadow OffsetBits:1024 SizeBits:64] map[Name:li_seq OffsetBits:1088 SizeBits:64] map[Name:li_order_id OffsetBits:1152 SizeBits:32]]]

14/2 2026/09/19 00:45 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 12661
							output: 47
							thoughts: 585
						

Thoughts:
**Analyzing a Potential Use-After-Free Vulnerability in XFS**

Okay, so I'm looking at this memory corruption issue and immediately my mind jumps to the specifics. Offset 832 bits, which translates to 16 bytes, is where `li_cil` resides. This is a `struct list_head`, so that 8-byte write is definitely touching the `next` or `prev` pointer of `li_cil`.  That sparks an immediate association: `list_splice_init`! That's a classic function for manipulating list heads. 

Digging deeper, in `xlog_cil_push_pcp_aggregate`, I see:

```c
		if (!list_empty(&cilpcp->log_items))
			list_splice_init(&cilpcp->log_items, &ctx->log_items);
```

Right, `list_splice_init` takes `list` and `head`. Let's refresh the details:

```c
static inline void list_splice_init(struct list_head *list,
				    struct list_head *head)
{
	if (!list_empty(list)) {
		__list_splice(list, head->prev, head);
		INIT_LIST_HEAD(list);
	}
}
```

The key operation is in `__list_splice`. It's modifying `list->prev->next = head;` and `list->next->prev = head->prev;`.  So, `list` in this case is `&cilpcp->log_items`.  A lightbulb flashes! If anything in `&cilpcp->log_items` has been freed, then either `list->prev` or `list->next` could be pointing to a freed element. And when `__list_splice` executes that write, we're writing to freed memory! Bingo!

The freed element in question appears to be an `xfs_buf_log_item`. And it was freed by task 5944. It looks like it was freed as a result of a call to `xfs_ioc_setlabel`:

```
 xfs_buf_ioend+0x235/0x790 fs/xfs/xfs_buf.c:1167
 xfs_buf_iowait+0x133/0x420 fs/xfs/xfs_buf.c:1336
 xfs_bwrite+0x5f/0xe0 fs/xfs/xfs_buf.c:1239
 xfs_sync_sb_buf+0x172/0x290 fs/xfs/libxfs/xfs_sb.c:1489
 xfs_ioc_setlabel+0x1d7/0x340 fs/xfs/xfs_ioctl.c:1081
```

Okay, `xfs_ioc_setlabel` is calling `xfs_sync_sb_buf`, which is where the freeing happens. I should take a closer look at `xfs_sync_sb_buf` to understand how the buffer gets freed in the first place and if there are any opportunities for a race condition there.



15/2 2026/09/19 00:45 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/libxfs/xfs_sb.c Name:xfs_sync_sb_buf]

Results:
map[SourceCode:1463:	/*
1464:	 * Same behavior as xfs_sync_sb, except that it is always synchronous and it
1465:	 * also writes the superblock buffer to disk sector 0 immediately.
1466:	 */
1467:	int
1468:	xfs_sync_sb_buf(
1469:		struct xfs_mount	*mp,
1470:		bool			update_rtsb)
1471:	{
1472:		struct xfs_trans	*tp;
1473:		int			error;
1474:	
1475:		error = xfs_trans_alloc(mp, &M_RES(mp)->tr_sb, 0, 0, 0, &tp);
1476:		if (error)
1477:			return error;
1478:	
1479:		xfs_log_sb(tp);
1480:		if (update_rtsb)
1481:			xfs_log_rtsb(tp, xfs_trans_getsb(tp));
1482:		xfs_trans_set_sync(tp);
1483:		error = xfs_trans_commit(tp);
1484:		if (error)
1485:			return error;
1486:	
1487:		/* Re-acquire and write the sb and rtsb to disk. */
1488:		xfs_buf_lock(mp->m_sb_bp);
1489:		error = xfs_bwrite(mp->m_sb_bp);
1490:		xfs_buf_unlock(mp->m_sb_bp);
1491:		if (error)
1492:			return error;
1493:	
1494:		if (update_rtsb && mp->m_rtsb_bp) {
1495:			xfs_buf_lock(mp->m_rtsb_bp);
1496:			error = xfs_bwrite(mp->m_rtsb_bp);
1497:			xfs_buf_unlock(mp->m_rtsb_bp);
1498:		}
1499:	
1500:		return error;
1501:	}
 SourceFile:fs/xfs/libxfs/xfs_sb.c]

16/2 2026/09/19 00:45 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 14656
							output: 42
							thoughts: 178
						

Thoughts:
**My Analysis of the XFS Superblock Sync Process**

Okay, let me break this down. So, `xfs_sync_sb_buf`… right, it sets up a transaction, which is pretty standard. And then it *logs* the superblock. Good, that's expected. Transaction commit, which makes sense. Makes sure everything is consistent. Then, the superblock buffer is written *directly* using `xfs_bwrite(mp->m_sb_bp)`. That's a direct write *after* the commit.

The commit, `xfs_trans_commit`, this adds the log item to the CIL, the Committed Item List. That's how it tracks what's been committed, and how it'll be recovered in the event of an issue, makes sense. And as part of that CIL addition, the `li_cil` is linked into `cilpcp->log_items`. Got it. Transaction commit returns.

Now, here's where it gets interesting: *then* we call `xfs_bwrite` on the buffer. This writes it *synchronously*. So, it's a synchronous write to disk. This means `xfs_sync_sb_buf` is effectively blocking until the I/O completes. Okay, so that means we're waiting for the write to finish before returning from the sync operation. This seems like a reasonable approach to ensure data consistency, the write is not going to error, or be lost.

Once the I/O completes, `xfs_buf_ioend` is called. Okay, I need to see exactly what `xfs_buf_ioend` does in this context, because that's the final piece of the puzzle here. What does the completion process look like?



17/2 2026/09/19 00:45 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf.c Name:xfs_buf_ioend]

Results:
map[SourceCode:1122:	/*
1123:	 * Complete a buffer read or write.
1124:	 *
1125:	 * Releases the buffer if the I/O was asynchronous.
1126:	 */
1127:	static void
1128:	xfs_buf_ioend(
1129:		struct xfs_buf	*bp)
1130:	{
1131:		bool		async = bp->b_flags & XBF_ASYNC;
1132:	
1133:		trace_xfs_buf_iodone(bp, _RET_IP_);
1134:	
1135:		if (bp->b_flags & XBF_READ) {
1136:			if (!bp->b_error && is_vmalloc_addr(bp->b_addr))
1137:				invalidate_kernel_vmap_range(bp->b_addr,
1138:					roundup(BBTOB(bp->b_length), PAGE_SIZE));
1139:			if (!bp->b_error && bp->b_ops)
1140:				bp->b_ops->verify_read(bp);
1141:			if (!bp->b_error)
1142:				xfs_buf_set_flags(bp, XBF_DONE);
1143:			if (bp->b_flags & XBF_READ_AHEAD)
1144:				percpu_counter_dec(&bp->b_target->bt_readahead_count);
1145:		} else {
1146:			if (unlikely(bp->b_error)) {
1147:				if (xfs_buf_ioend_handle_error(bp)) {
1148:					ASSERT(async);
1149:					return;
1150:				}
1151:			} else {
1152:				xfs_buf_clear_flags(bp, XBF_WRITE_FAIL);
1153:				xfs_buf_set_flags(bp, XBF_DONE);
1154:			}
1155:	
1156:			/* clear the retry state */
1157:			bp->b_last_error = 0;
1158:			bp->b_retries = 0;
1159:			bp->b_first_retry_time = 0;
1160:	
1161:			/*
1162:			 * Note that for things like remote attribute buffers, there may
1163:			 * not be a buffer log item here, so processing the buffer log
1164:			 * item must remain optional.
1165:			 */
1166:			if (bp->b_log_item)
1167:				xfs_buf_item_done(bp);
1168:	
1169:			if (bp->b_iodone)
1170:				bp->b_iodone(bp);
1171:		}
1172:	
1173:		xfs_buf_clear_flags(bp, XBF_READ | XBF_WRITE | XBF_READ_AHEAD);
1174:		if (async)
1175:			xfs_buf_relse(bp);
1176:	}
 SourceFile:fs/xfs/xfs_buf.c]

18/2 2026/09/19 00:45 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 16137
							output: 45
							thoughts: 23
						

Thoughts:
Here's my attempt at summarizing the thought process, tailored for an expert audience:

**Diving into `xfs_buf_item_done`**

Okay, so I'm seeing a call to `xfs_buf_item_done`. Right, that's the signal to complete an item associated with a buffer. My first instinct is, let's just trace through what *exactly* happens when this function gets called. I need to understand the implications here. What state changes occur? Does it signal anything else? What kind of cleanup is triggered, and is it what I expect based on the context? I need to get a clear picture of its behavior.



19/2 2026/09/19 00:45 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_item_done]

Results:
map[SourceCode:1065:	void
1066:	xfs_buf_item_done(
1067:		struct xfs_buf		*bp)
1068:	{
1069:		struct xfs_buf_log_item	*bip = bp->b_log_item;
1070:	
1071:		/*
1072:		 * If we are forcibly shutting down, this may well be off the AIL
1073:		 * already. That's because we simulate the log-committed callbacks to
1074:		 * unpin these buffers. Or we may never have put this item on AIL
1075:		 * because of the transaction was aborted forcibly.
1076:		 * xfs_trans_ail_delete() takes care of these.
1077:		 *
1078:		 * Either way, AIL is useless if we're forcing a shutdown.
1079:		 *
1080:		 * Note that log recovery writes might have buffer items that are not on
1081:		 * the AIL even when the file system is not shut down.
1082:		 */
1083:		xfs_trans_ail_delete(&bip->bli_item,
1084:				     xlog_in_recovery(bip->bli_item.li_log) ?
1085:				     0 : SHUTDOWN_CORRUPT_INCORE);
1086:		xfs_buf_item_relse(bip);
1087:	}
 SourceFile:fs/xfs/xfs_buf_item.c]

20/2 2026/09/19 00:45 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 16768
							output: 45
							thoughts: 22
						

Thoughts:
Here's my take on those thoughts, from my perspective as an expert:

**Reflecting on `xfs_buf_item_relse`**

Okay, so I'm looking at `xfs_buf_item_relse`. Right, it's pretty straightforward, it's that function responsible for *releasing* the `xfs_buf_log_item`. This is a crucial piece of the XFS puzzle, as it is the final step in the lifecycle of a buffer's logging information. Essentially, it's the unregister function, allowing a buffer that was previously logged to be marked as no longer needing to be journaled. I want to keep an eye on this function, as its execution needs to be precise for performance and data integrity.



21/2 2026/09/19 00:45 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_item_relse]

Results:
map[SourceCode:  71:	/*
  72:	 * xfs_buf_item_relse() is called when the buf log item is no longer needed.
  73:	 */
  74:	static void
  75:	xfs_buf_item_relse(
  76:		struct xfs_buf_log_item	*bip)
  77:	{
  78:		struct xfs_buf		*bp = bip->bli_buf;
  79:	
  80:		trace_xfs_buf_item_relse(bp, _RET_IP_);
  81:	
  82:		ASSERT(!test_bit(XFS_LI_IN_AIL, &bip->bli_item.li_flags));
  83:		ASSERT(atomic_read(&bip->bli_refcount) == 0);
  84:	
  85:		bp->b_log_item = NULL;
  86:		xfs_buf_rele(bp);
  87:		xfs_buf_item_free(bip);
  88:	}
 SourceFile:fs/xfs/xfs_buf_item.c]

22/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 17303
							output: 45
							thoughts: 228
						

Thoughts:
**The Curious Case of the Freed Log Item**

Okay, hold on a second. I'm following this code path, and something doesn't feel right. `xfs_buf_item_relse` is responsible for freeing the `xfs_buf_log_item`, but... wait a minute... that log item *might* still be lingering on the CIL list! That's the problem here. I'm tracking how `xfs_sync_sb_buf` works, and I recall that it can commit a transaction, and as part of that, the log item is added to the CIL. Then, `xfs_sync_sb_buf` directly kicks off `xfs_bwrite` on the buffer.

Now, here's where it gets interesting. Once `xfs_bwrite` completes, `xfs_buf_ioend` is called, which in turn calls `xfs_buf_item_done`. And here's the kicker: `xfs_buf_item_done` then calls `xfs_buf_item_relse`, which... *frees* the `xfs_buf_log_item`. But, but, but the log item *should* still be on the CIL list! Why isn't it removed?

It's clear that `xfs_trans_commit` added it to the CIL initially, but what's the mechanism for removing it? It looks like the issue is that it's being freed before it's removed! Does `xfs_trans_ail_delete` handle that removal? Let me check `xfs_trans_ail_delete` real quick to make sure I haven't missed something.



23/2 2026/09/19 00:46 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_trans_ail.c Name:xfs_trans_ail_delete]

Results:
map[SourceCode: 918:	void
 919:	xfs_trans_ail_delete(
 920:		struct xfs_log_item	*lip,
 921:		int			shutdown_type)
 922:	{
 923:		struct xfs_ail		*ailp = lip->li_ailp;
 924:		struct xlog		*log = ailp->ail_log;
 925:		xfs_lsn_t		tail_lsn;
 926:	
 927:		spin_lock(&ailp->ail_lock);
 928:		if (!test_bit(XFS_LI_IN_AIL, &lip->li_flags)) {
 929:			spin_unlock(&ailp->ail_lock);
 930:			if (shutdown_type && !xlog_is_shutdown(log)) {
 931:				xfs_alert_tag(log->l_mp, XFS_PTAG_AILDELETE,
 932:		"%s: attempting to delete a log item that is not in the AIL",
 933:						__func__);
 934:				xlog_force_shutdown(log, shutdown_type);
 935:			}
 936:			return;
 937:		}
 938:	
 939:		clear_bit(XFS_LI_FAILED, &lip->li_flags);
 940:		tail_lsn = xfs_ail_delete_one(ailp, lip);
 941:		xfs_ail_update_finish(ailp, tail_lsn);	/* drops the AIL lock */
 942:	}
 SourceFile:fs/xfs/xfs_trans_ail.c]

24/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 18410
							output: 47
							thoughts: 80
						

Thoughts:
Okay, let me think this through.

**Analyzing XFS Transaction Management**

Right, so `xfs_trans_ail_delete` is only pulling the item from the AIL, it's not actually freeing it from the CIL. That immediately rings an alarm bell. Hold on, if something's still sitting in the CIL, it *shouldn't* be eligible for being freed, right? That's the whole point of the CIL – commit log integrity! I need to understand how this isn't causing corruption. So, how on earth is `xfs_sync_sb_buf` working without hitting this issue? I need to go back and take another hard look at that code path and figure out where the disconnect is. This needs to be understood thoroughly; potential data integrity issues are not to be taken lightly.



25/2 2026/09/19 00:46 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/libxfs/xfs_sb.c Name:xfs_sync_sb_buf]

Results:
map[SourceCode:1463:	/*
1464:	 * Same behavior as xfs_sync_sb, except that it is always synchronous and it
1465:	 * also writes the superblock buffer to disk sector 0 immediately.
1466:	 */
1467:	int
1468:	xfs_sync_sb_buf(
1469:		struct xfs_mount	*mp,
1470:		bool			update_rtsb)
1471:	{
1472:		struct xfs_trans	*tp;
1473:		int			error;
1474:	
1475:		error = xfs_trans_alloc(mp, &M_RES(mp)->tr_sb, 0, 0, 0, &tp);
1476:		if (error)
1477:			return error;
1478:	
1479:		xfs_log_sb(tp);
1480:		if (update_rtsb)
1481:			xfs_log_rtsb(tp, xfs_trans_getsb(tp));
1482:		xfs_trans_set_sync(tp);
1483:		error = xfs_trans_commit(tp);
1484:		if (error)
1485:			return error;
1486:	
1487:		/* Re-acquire and write the sb and rtsb to disk. */
1488:		xfs_buf_lock(mp->m_sb_bp);
1489:		error = xfs_bwrite(mp->m_sb_bp);
1490:		xfs_buf_unlock(mp->m_sb_bp);
1491:		if (error)
1492:			return error;
1493:	
1494:		if (update_rtsb && mp->m_rtsb_bp) {
1495:			xfs_buf_lock(mp->m_rtsb_bp);
1496:			error = xfs_bwrite(mp->m_rtsb_bp);
1497:			xfs_buf_unlock(mp->m_rtsb_bp);
1498:		}
1499:	
1500:		return error;
1501:	}
 SourceFile:fs/xfs/libxfs/xfs_sb.c]

26/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 19354
							output: 41
							thoughts: 28
						

Thoughts:
Here's my summary, as though I'm thinking through this process:

**Transaction Synchronization Checkpoint**

Okay, so I see `xfs_trans_set_sync(tp)` has been called. That's the signal to get the transaction `tp` synchronized. Let me shift my mental gears and start looking at what happens next. The obvious follow-up is `xfs_trans_commit`. That's where all the magic happens. Let's see what the commit does, step by step. Is this a forced sync? What are the implications? Are there any specific flags set on `tp`? I need to understand the relationship between this `set_sync` call and the ultimate commit to fully grasp the synchronization behavior. This is crucial for performance and data integrity, so I need to make sure I understand it well. Let's dig in.



27/2 2026/09/19 00:46 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_trans.c Name:xfs_trans_commit]

Results:
map[SourceCode: 908:	int
 909:	xfs_trans_commit(
 910:		struct xfs_trans	*tp)
 911:	{
 912:		/*
 913:		 * Finish deferred items on final commit. Only permanent transactions
 914:		 * should ever have deferred ops.
 915:		 */
 916:		WARN_ON_ONCE(!list_empty(&tp->t_dfops) &&
 917:			     !(tp->t_flags & XFS_TRANS_PERM_LOG_RES));
 918:		if (tp->t_flags & XFS_TRANS_PERM_LOG_RES) {
 919:			int error = xfs_defer_finish_noroll(&tp);
 920:			if (error) {
 921:				xfs_trans_cancel(tp);
 922:				return error;
 923:			}
 924:		}
 925:	
 926:		return __xfs_trans_commit(tp, false);
 927:	}
 SourceFile:fs/xfs/xfs_trans.c]

28/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 19926
							output: 42
							thoughts: 13
						

Thoughts:
Here's my summary, as though I'm thinking through it:

**Diving into `__xfs_trans_commit`**

Okay, time to get into this. I'm taking a look at `__xfs_trans_commit`. This is a critical function; it's the linchpin for transaction completion in XFS, so I need to understand it cold. This is where the rubber meets the road. It's the point where all the dirty data and metadata are finally written out and the transaction is made permanent. I need to make sure I understand the precise ordering of operations, the error handling, and how it interacts with the journaling layer. Let's see how well it's managing the block allocation. Any flaws here can be catastrophic. I need to review the concurrency aspects, too, how it interacts with other transactions. Let's go through the code step-by-step and make sure it's all solid. Let's see if there are any subtle race conditions, particularly around the log flushes or metadata updates.



29/2 2026/09/19 00:46 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_trans.c Name:__xfs_trans_commit]

Results:
map[SourceCode: 808:	/*
 809:	 * Commit the given transaction to the log.
 810:	 *
 811:	 * XFS disk error handling mechanism is not based on a typical
 812:	 * transaction abort mechanism. Logically after the filesystem
 813:	 * gets marked 'SHUTDOWN', we can't let any new transactions
 814:	 * be durable - ie. committed to disk - because some metadata might
 815:	 * be inconsistent. In such cases, this returns an error, and the
 816:	 * caller may assume that all locked objects joined to the transaction
 817:	 * have already been unlocked as if the commit had succeeded.
 818:	 * Do not reference the transaction structure after this call.
 819:	 */
 820:	static int
 821:	__xfs_trans_commit(
 822:		struct xfs_trans	*tp,
 823:		bool			regrant)
 824:	{
 825:		struct xfs_mount	*mp = tp->t_mountp;
 826:		struct xlog		*log = mp->m_log;
 827:		xfs_csn_t		commit_seq = 0;
 828:		int			error = 0;
 829:		int			sync = tp->t_flags & XFS_TRANS_SYNC;
 830:	
 831:		trace_xfs_trans_commit(tp, _RET_IP_);
 832:	
 833:		/*
 834:		 * Commit per-transaction changes that are not already tracked through
 835:		 * log items.  This can add dirty log items to the transaction.
 836:		 */
 837:		if (tp->t_flags & XFS_TRANS_SB_DIRTY)
 838:			xfs_trans_apply_sb_deltas(tp);
 839:		xfs_trans_apply_dquot_deltas(tp);
 840:	
 841:		error = xfs_trans_run_precommits(tp);
 842:		if (error)
 843:			goto out_unreserve;
 844:	
 845:		/*
 846:		 * If there is nothing to be logged by the transaction,
 847:		 * then unlock all of the items associated with the
 848:		 * transaction and free the transaction structure.
 849:		 * Also make sure to return any reserved blocks to
 850:		 * the free pool.
 851:		 */
 852:		if (!(tp->t_flags & XFS_TRANS_DIRTY))
 853:			goto out_unreserve;
 854:	
 855:		/*
 856:		 * We must check against log shutdown here because we cannot abort log
 857:		 * items and leave them dirty, inconsistent and unpinned in memory while
 858:		 * the log is active. This leaves them open to being written back to
 859:		 * disk, and that will lead to on-disk corruption.
 860:		 */
 861:		if (xlog_is_shutdown(log)) {
 862:			error = -EIO;
 863:			goto out_unreserve;
 864:		}
 865:	
 866:		ASSERT(tp->t_ticket != NULL);
 867:	
 868:		xlog_cil_commit(log, tp, &commit_seq, regrant);
 869:	
 870:		xfs_trans_free(tp);
 871:	
 872:		/*
 873:		 * If the transaction needs to be synchronous, then force the
 874:		 * log out now and wait for it.
 875:		 */
 876:		if (sync) {
 877:			error = xfs_log_force_seq(mp, commit_seq, XFS_LOG_SYNC, NULL);
 878:			XFS_STATS_INC(mp, xs_trans_sync);
 879:		} else {
 880:			XFS_STATS_INC(mp, xs_trans_async);
 881:		}
 882:	
 883:		return error;
 884:	
 885:	out_unreserve:
 886:		xfs_trans_unreserve_and_mod_sb(tp);
 887:	
 888:		/*
 889:		 * It is indeed possible for the transaction to be not dirty but
 890:		 * the dqinfo portion to be.  All that means is that we have some
 891:		 * (non-persistent) quota reservations that need to be unreserved.
 892:		 */
 893:		xfs_trans_unreserve_and_mod_dquots(tp, true);
 894:		if (tp->t_ticket) {
 895:			if (regrant && !xlog_is_shutdown(log))
 896:				xfs_log_ticket_regrant(log, tp->t_ticket);
 897:			else
 898:				xfs_log_ticket_ungrant(log, tp->t_ticket);
 899:			tp->t_ticket = NULL;
 900:		}
 901:		xfs_trans_free_items(tp, !!error);
 902:		xfs_trans_free(tp);
 903:	
 904:		XFS_STATS_INC(mp, xs_trans_empty);
 905:		return error;
 906:	}
 SourceFile:fs/xfs/xfs_trans.c]

30/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 21735
							output: 43
							thoughts: 89
						

Thoughts:
Here's my understanding, as if I were thinking it through:

**Analyzing the Transaction Commit Process in XFS**

Okay, so `xlog_cil_commit` is the function that actually gets the log entries added to the CIL – that makes sense. Now, because `xfs_trans_set_sync` was triggered, `sync` is true, and that means we're going to call `xfs_log_force_seq`.  Wait a minute... right, `xfs_log_force_seq` is the function that's going to *force* the log out to stable storage and, crucially, *wait* for the I/O to complete. Given that this is a critical stage, let me take a closer look at `xfs_log_force_seq` to confirm my understanding of its mechanisms and any potential implications for performance or data integrity.



31/2 2026/09/19 00:46 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log.c Name:xfs_log_force_seq]

Results:
map[SourceCode:2986:	/*
2987:	 * Force the log to a specific checkpoint sequence.
2988:	 *
2989:	 * First force the CIL so that all the required changes have been flushed to the
2990:	 * iclogs. If the CIL force completed it will return a commit LSN that indicates
2991:	 * the iclog that needs to be flushed to stable storage. If the caller needs
2992:	 * a synchronous log force, we will wait on the iclog with the LSN returned by
2993:	 * xlog_cil_force_seq() to be completed.
2994:	 */
2995:	int
2996:	xfs_log_force_seq(
2997:		struct xfs_mount	*mp,
2998:		xfs_csn_t		seq,
2999:		uint			flags,
3000:		int			*log_flushed)
3001:	{
3002:		struct xlog		*log = mp->m_log;
3003:		xfs_lsn_t		lsn;
3004:		int			ret;
3005:		ASSERT(seq != 0);
3006:	
3007:		XFS_STATS_INC(mp, xs_log_force);
3008:		trace_xfs_log_force(mp, seq, _RET_IP_);
3009:	
3010:		lsn = xlog_cil_force_seq(log, seq);
3011:		if (lsn == NULLCOMMITLSN)
3012:			return 0;
3013:	
3014:		ret = xlog_force_lsn(log, lsn, flags, log_flushed, false);
3015:		if (ret == -EAGAIN) {
3016:			XFS_STATS_INC(mp, xs_log_force_sleep);
3017:			ret = xlog_force_lsn(log, lsn, flags, log_flushed, true);
3018:		}
3019:		return ret;
3020:	}
 SourceFile:fs/xfs/xfs_log.c]

32/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 22654
							output: 45
							thoughts: 30
						

Thoughts:
Here's my take on those thoughts, from an expert's perspective:

**Diving into CIL Sequencing**

Okay, so we're talking about `xlog_cil_force_seq`. My initial thought is that this is the mechanism that we use to explicitly control or override the default sequencing of CIL (Command Interpretation Language) operations within the XLOG (Write-Ahead Log) system. It's a key control point and needs to be handled with care.

My next step, naturally, is to examine how this function works. I want to see how it operates within the broader context of XLOG management. What are the implications of invoking `xlog_cil_force_seq`? Does it have performance implications? Does it impact concurrency? I'll probably be thinking about edge cases and potential race conditions too. My assumption is that the use of this probably has a very good reason to exist, and now I just need to figure out why, and how it works. I'll need to go deeper into the source code and documentation.



33/2 2026/09/19 00:46 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_force_seq]

Results:
map[SourceCode:1898:	/*
1899:	 * Conditionally push the CIL based on the sequence passed in.
1900:	 *
1901:	 * We only need to push if we haven't already pushed the sequence number given.
1902:	 * Hence the only time we will trigger a push here is if the push sequence is
1903:	 * the same as the current context.
1904:	 *
1905:	 * We return the current commit lsn to allow the callers to determine if a
1906:	 * iclog flush is necessary following this call.
1907:	 */
1908:	xfs_lsn_t
1909:	xlog_cil_force_seq(
1910:		struct xlog	*log,
1911:		xfs_csn_t	sequence)
1912:	{
1913:		struct xfs_cil		*cil = log->l_cilp;
1914:		struct xfs_cil_ctx	*ctx;
1915:		xfs_lsn_t		commit_lsn = NULLCOMMITLSN;
1916:	
1917:		ASSERT(sequence <= cil->xc_current_sequence);
1918:	
1919:		if (!sequence)
1920:			sequence = cil->xc_current_sequence;
1921:		trace_xfs_log_force(log->l_mp, sequence, _RET_IP_);
1922:	
1923:		/*
1924:		 * check to see if we need to force out the current context.
1925:		 * xlog_cil_push() handles racing pushes for the same sequence,
1926:		 * so no need to deal with it here.
1927:		 */
1928:	restart:
1929:		xlog_cil_push_now(log, sequence, false);
1930:	
1931:		/*
1932:		 * See if we can find a previous sequence still committing.
1933:		 * We need to wait for all previous sequence commits to complete
1934:		 * before allowing the force of push_seq to go ahead. Hence block
1935:		 * on commits for those as well.
1936:		 */
1937:		spin_lock(&cil->xc_push_lock);
1938:		list_for_each_entry(ctx, &cil->xc_committing, committing) {
1939:			/*
1940:			 * Avoid getting stuck in this loop because we were woken by the
1941:			 * shutdown, but then went back to sleep once already in the
1942:			 * shutdown state.
1943:			 */
1944:			if (xlog_is_shutdown(log))
1945:				goto out_shutdown;
1946:			if (ctx->sequence > sequence)
1947:				continue;
1948:			if (!ctx->commit_lsn) {
1949:				/*
1950:				 * It is still being pushed! Wait for the push to
1951:				 * complete, then start again from the beginning.
1952:				 */
1953:				XFS_STATS_INC(log->l_mp, xs_log_force_sleep);
1954:				xlog_wait(&cil->xc_commit_wait, &cil->xc_push_lock);
1955:				goto restart;
1956:			}
1957:			if (ctx->sequence != sequence)
1958:				continue;
1959:			/* found it! */
1960:			commit_lsn = ctx->commit_lsn;
1961:		}
1962:	
1963:		/*
1964:		 * The call to xlog_cil_push_now() executes the push in the background.
1965:		 * Hence by the time we have got here it our sequence may not have been
1966:		 * pushed yet. This is true if the current sequence still matches the
1967:		 * push sequence after the above wait loop and the CIL still contains
1968:		 * dirty objects. This is guaranteed by the push code first adding the
1969:		 * context to the committing list before emptying the CIL.
1970:		 *
1971:		 * Hence if we don't find the context in the committing list and the
1972:		 * current sequence number is unchanged then the CIL contents are
1973:		 * significant.  If the CIL is empty, if means there was nothing to push
1974:		 * and that means there is nothing to wait for. If the CIL is not empty,
1975:		 * it means we haven't yet started the push, because if it had started
1976:		 * we would have found the context on the committing list.
1977:		 */
1978:		if (sequence == cil->xc_current_sequence &&
1979:		    !test_bit(XLOG_CIL_EMPTY, &cil->xc_flags)) {
1980:			spin_unlock(&cil->xc_push_lock);
1981:			goto restart;
1982:		}
1983:	
1984:		spin_unlock(&cil->xc_push_lock);
1985:		return commit_lsn;
1986:	
1987:		/*
1988:		 * We detected a shutdown in progress. We need to trigger the log force
1989:		 * to pass through it's iclog state machine error handling, even though
1990:		 * we are already in a shutdown state. Hence we can't return
1991:		 * NULLCOMMITLSN here as that has special meaning to log forces (i.e.
1992:		 * LSN is already stable), so we return a zero LSN instead.
1993:		 */
1994:	out_shutdown:
1995:		spin_unlock(&cil->xc_push_lock);
1996:		return 0;
1997:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

34/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 24567
							output: 45
							thoughts: 163
						

Thoughts:
**My Analysis of the CIL Push Process**

Okay, so I'm looking at how this CIL pushing works and I'm starting to piece it together. `xlog_cil_push_now` *initiates* the background push by queuing `xlog_cil_push_work` onto a workqueue, got it. It's asynchronous. And then, `xlog_cil_force_seq` is the function that actually waits for this push to finish, right?

But, hold on a second... it doesn't directly wait on the workqueue itself. Instead, it seems to be using `cil->xc_commit_wait`. Okay, yeah, makes sense, it's a condition variable, so it waits for a *state* change. Now, I see... `xlog_cil_force_seq` actually waits on `ctx->commit_lsn` to get set. This is a crucial detail. I need to understand when and where this `commit_lsn` is set, as that indicates completion.

Aha! It's set within `xlog_cil_push_work`! But, even more telling, *after* `xlog_cil_push_pcp_aggregate` is called. That makes sense. I need to dive deeper into `xlog_cil_push_work` to fully grasp the commit sequence. I'll need to understand what `xlog_cil_push_pcp_aggregate` is doing in relation to the LSN and the completion signal. Time to dissect that function.



35/2 2026/09/19 00:46 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_push_work]

Results:
map[SourceCode:1355:	/*
1356:	 * Push the Committed Item List to the log.
1357:	 *
1358:	 * If the current sequence is the same as xc_push_seq we need to do a flush. If
1359:	 * xc_push_seq is less than the current sequence, then it has already been
1360:	 * flushed and we don't need to do anything - the caller will wait for it to
1361:	 * complete if necessary.
1362:	 *
1363:	 * xc_push_seq is checked unlocked against the sequence number for a match.
1364:	 * Hence we can allow log forces to run racily and not issue pushes for the
1365:	 * same sequence twice.  If we get a race between multiple pushes for the same
1366:	 * sequence they will block on the first one and then abort, hence avoiding
1367:	 * needless pushes.
1368:	 *
1369:	 * This runs from a workqueue so it does not inherent any specific memory
1370:	 * allocation context. However, we do not want to block on memory reclaim
1371:	 * recursing back into the filesystem because this push may have been triggered
1372:	 * by memory reclaim itself. Hence we really need to run under full GFP_NOFS
1373:	 * contraints here.
1374:	 */
1375:	static void
1376:	xlog_cil_push_work(
1377:		struct work_struct	*work)
1378:	{
1379:		unsigned int		nofs_flags = memalloc_nofs_save();
1380:		struct xfs_cil_ctx	*ctx =
1381:			container_of(work, struct xfs_cil_ctx, push_work);
1382:		struct xfs_cil		*cil = ctx->cil;
1383:		struct xlog		*log = cil->xc_log;
1384:		struct xfs_cil_ctx	*new_ctx;
1385:		int			num_iovecs = 0;
1386:		int			num_bytes = 0;
1387:		int			error = 0;
1388:		struct xlog_cil_trans_hdr thdr;
1389:		struct xfs_log_vec	lvhdr = {};
1390:		xfs_csn_t		push_seq;
1391:		bool			push_commit_stable;
1392:		LIST_HEAD		(whiteouts);
1393:		struct xlog_ticket	*ticket;
1394:	
1395:		new_ctx = xlog_cil_ctx_alloc();
1396:		new_ctx->ticket = xlog_cil_ticket_alloc(log);
1397:	
1398:		down_write(&cil->xc_ctx_lock);
1399:	
1400:		spin_lock(&cil->xc_push_lock);
1401:		push_seq = cil->xc_push_seq;
1402:		ASSERT(push_seq <= ctx->sequence);
1403:		push_commit_stable = cil->xc_push_commit_stable;
1404:		cil->xc_push_commit_stable = false;
1405:	
1406:		/*
1407:		 * As we are about to switch to a new, empty CIL context, we no longer
1408:		 * need to throttle tasks on CIL space overruns. Wake any waiters that
1409:		 * the hard push throttle may have caught so they can start committing
1410:		 * to the new context. The ctx->xc_push_lock provides the serialisation
1411:		 * necessary for safely using the lockless waitqueue_active() check in
1412:		 * this context.
1413:		 */
1414:		if (waitqueue_active(&cil->xc_push_wait))
1415:			wake_up_all(&cil->xc_push_wait);
1416:	
1417:		xlog_cil_push_pcp_aggregate(cil, ctx);
1418:	
1419:		/*
1420:		 * Check if we've anything to push. If there is nothing, then we don't
1421:		 * move on to a new sequence number and so we have to be able to push
1422:		 * this sequence again later.
1423:		 */
1424:		if (test_bit(XLOG_CIL_EMPTY, &cil->xc_flags)) {
1425:			cil->xc_push_seq = 0;
1426:			spin_unlock(&cil->xc_push_lock);
1427:			goto out_skip;
1428:		}
1429:	
1430:	
1431:		/* check for a previously pushed sequence */
1432:		if (push_seq < ctx->sequence) {
1433:			spin_unlock(&cil->xc_push_lock);
1434:			goto out_skip;
1435:		}
1436:	
1437:		/*
1438:		 * We are now going to push this context, so add it to the committing
1439:		 * list before we do anything else. This ensures that anyone waiting on
1440:		 * this push can easily detect the difference between a "push in
1441:		 * progress" and "CIL is empty, nothing to do".
1442:		 *
1443:		 * IOWs, a wait loop can now check for:
1444:		 *	the current sequence not being found on the committing list;
1445:		 *	an empty CIL; and
1446:		 *	an unchanged sequence number
1447:		 * to detect a push that had nothing to do and therefore does not need
1448:		 * waiting on. If the CIL is not empty, we get put on the committing
1449:		 * list before emptying the CIL and bumping the sequence number. Hence
1450:		 * an empty CIL and an unchanged sequence number means we jumped out
1451:		 * above after doing nothing.
1452:		 *
1453:		 * Hence the waiter will either find the commit sequence on the
1454:		 * committing list or the sequence number will be unchanged and the CIL
1455:		 * still dirty. In that latter case, the push has not yet started, and
1456:		 * so the waiter will have to continue trying to check the CIL
1457:		 * committing list until it is found. In extreme cases of delay, the
1458:		 * sequence may fully commit between the attempts the wait makes to wait
1459:		 * on the commit sequence.
1460:		 */
1461:		list_add(&ctx->committing, &cil->xc_committing);
1462:		spin_unlock(&cil->xc_push_lock);
1463:	
1464:		xlog_cil_build_lv_chain(ctx, &whiteouts, &num_iovecs, &num_bytes);
1465:	
1466:		/*
1467:		 * Switch the contexts so we can drop the context lock and move out
1468:		 * of a shared context. We can't just go straight to the commit record,
1469:		 * though - we need to synchronise with previous and future commits so
1470:		 * that the commit records are correctly ordered in the log to ensure
1471:		 * that we process items during log IO completion in the correct order.
1472:		 *
1473:		 * For example, if we get an EFI in one checkpoint and the EFD in the
1474:		 * next (e.g. due to log forces), we do not want the checkpoint with
1475:		 * the EFD to be committed before the checkpoint with the EFI.  Hence
1476:		 * we must strictly order the commit records of the checkpoints so
1477:		 * that: a) the checkpoint callbacks are attached to the iclogs in the
1478:		 * correct order; and b) the checkpoints are replayed in correct order
1479:		 * in log recovery.
1480:		 *
1481:		 * Hence we need to add this context to the committing context list so
1482:		 * that higher sequences will wait for us to write out a commit record
1483:		 * before they do.
1484:		 *
1485:		 * xfs_log_force_seq requires us to mirror the new sequence into the cil
1486:		 * structure atomically with the addition of this sequence to the
1487:		 * committing list. This also ensures that we can do unlocked checks
1488:		 * against the current sequence in log forces without risking
1489:		 * deferencing a freed context pointer.
1490:		 */
1491:		spin_lock(&cil->xc_push_lock);
1492:		xlog_cil_ctx_switch(cil, new_ctx);
1493:		spin_unlock(&cil->xc_push_lock);
1494:		up_write(&cil->xc_ctx_lock);
1495:	
1496:		/*
1497:		 * Sort the log vector chain before we add the transaction headers.
1498:		 * This ensures we always have the transaction headers at the start
1499:		 * of the chain.
1500:		 */
1501:		list_sort(NULL, &ctx->lv_chain, xlog_cil_order_cmp);
1502:	
1503:		/*
1504:		 * Build a checkpoint transaction header and write it to the log to
1505:		 * begin the transaction. We need to account for the space used by the
1506:		 * transaction header here as it is not accounted for in xlog_write().
1507:		 * Add the lvhdr to the head of the lv chain we pass to xlog_write() so
1508:		 * it gets written into the iclog first.
1509:		 */
1510:		xlog_cil_build_trans_hdr(ctx, &thdr, &lvhdr, num_iovecs);
1511:		num_bytes += lvhdr.lv_bytes;
1512:		list_add(&lvhdr.lv_list, &ctx->lv_chain);
1513:	
1514:		/*
1515:		 * Take the lvhdr back off the lv_chain immediately after calling
1516:		 * xlog_cil_write_chain() as it should not be passed to log IO
1517:		 * completion.
1518:		 */
1519:		error = xlog_cil_write_chain(ctx, num_bytes);
1520:		list_del(&lvhdr.lv_list);
1521:		if (error)
1522:			goto out_abort_free_ticket;
1523:	
1524:		error = xlog_cil_write_commit_record(ctx);
1525:		if (error)
1526:			goto out_abort_free_ticket;
1527:	
1528:		/*
1529:		 * Grab the ticket from the ctx so we can ungrant it after releasing the
1530:		 * commit_iclog. The ctx may be freed by the time we return from
1531:		 * releasing the commit_iclog (i.e. checkpoint has been completed and
1532:		 * callback run) so we can't reference the ctx after the call to
1533:		 * xlog_state_release_iclog().
1534:		 */
1535:		ticket = ctx->ticket;
1536:	
1537:		/*
1538:		 * If the checkpoint spans multiple iclogs, wait for all previous iclogs
1539:		 * to complete before we submit the commit_iclog. We can't use state
1540:		 * checks for this - ACTIVE can be either a past completed iclog or a
1541:		 * future iclog being filled, while WANT_SYNC through SYNC_DONE can be a
1542:		 * past or future iclog awaiting IO or ordered IO completion to be run.
1543:		 * In the latter case, if it's a future iclog and we wait on it, the we
1544:		 * will hang because it won't get processed through to ic_force_wait
1545:		 * wakeup until this commit_iclog is written to disk.  Hence we use the
1546:		 * iclog header lsn and compare it to the commit lsn to determine if we
1547:		 * need to wait on iclogs or not.
1548:		 */
1549:		spin_lock(&log->l_icloglock);
1550:		if (ctx->start_lsn != ctx->commit_lsn) {
1551:			xfs_lsn_t	plsn = be64_to_cpu(
1552:				ctx->commit_iclog->ic_prev->ic_header->h_lsn);
1553:	
1554:			if (plsn && XFS_LSN_CMP(plsn, ctx->commit_lsn) < 0) {
1555:				/*
1556:				 * Waiting on ic_force_wait orders the completion of
1557:				 * iclogs older than ic_prev. Hence we only need to wait
1558:				 * on the most recent older iclog here.
1559:				 */
1560:				xlog_wait_on_iclog(log, ctx->commit_iclog->ic_prev);
1561:				spin_lock(&log->l_icloglock);
1562:			}
1563:	
1564:			/*
1565:			 * We need to issue a pre-flush so that the ordering for this
1566:			 * checkpoint is correctly preserved down to stable storage.
1567:			 */
1568:			ctx->commit_iclog->ic_flags |= XLOG_ICL_NEED_FLUSH;
1569:		}
1570:	
1571:		/*
1572:		 * The commit iclog must be written to stable storage to guarantee
1573:		 * journal IO vs metadata writeback IO is correctly ordered on stable
1574:		 * storage.
1575:		 *
1576:		 * If the push caller needs the commit to be immediately stable and the
1577:		 * commit_iclog is not yet marked as XLOG_STATE_WANT_SYNC to indicate it
1578:		 * will be written when released, switch it's state to WANT_SYNC right
1579:		 * now.
1580:		 */
1581:		ctx->commit_iclog->ic_flags |= XLOG_ICL_NEED_FUA;
1582:		if (push_commit_stable &&
1583:		    ctx->commit_iclog->ic_state == XLOG_STATE_ACTIVE)
1584:			xlog_state_switch_iclogs(log, ctx->commit_iclog, 0);
1585:		ticket = ctx->ticket;
1586:		xlog_state_release_iclog(log, ctx->commit_iclog, ticket);
1587:	
1588:		/* Not safe to reference ctx now! */
1589:	
1590:		spin_unlock(&log->l_icloglock);
1591:		xlog_cil_cleanup_whiteouts(&whiteouts);
1592:		xfs_log_ticket_ungrant(log, ticket);
1593:		memalloc_nofs_restore(nofs_flags);
1594:		return;
1595:	
1596:	out_skip:
1597:		up_write(&cil->xc_ctx_lock);
1598:		xfs_log_ticket_put(new_ctx->ticket);
1599:		kfree(new_ctx);
1600:		memalloc_nofs_restore(nofs_flags);
1601:		return;
1602:	
1603:	out_abort_free_ticket:
1604:		ASSERT(xlog_is_shutdown(log));
1605:		xlog_cil_cleanup_whiteouts(&whiteouts);
1606:		if (!ctx->commit_iclog) {
1607:			xfs_log_ticket_ungrant(log, ctx->ticket);
1608:			xlog_cil_committed(ctx);
1609:			memalloc_nofs_restore(nofs_flags);
1610:			return;
1611:		}
1612:		spin_lock(&log->l_icloglock);
1613:		ticket = ctx->ticket;
1614:		xlog_state_release_iclog(log, ctx->commit_iclog, ticket);
1615:		/* Not safe to reference ctx now! */
1616:		spin_unlock(&log->l_icloglock);
1617:		xfs_log_ticket_ungrant(log, ticket);
1618:		memalloc_nofs_restore(nofs_flags);
1619:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

36/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 29662
							output: 47
							thoughts: 445
						

Thoughts:
**Debugging a Tricky XFS Crash**

Okay, here's what I'm seeing. The crash is happening within `xlog_cil_push_pcp_aggregate`, and it looks like that function gets called by `xlog_cil_push_work`, which is itself kicked off asynchronously from `xlog_cil_push_work` at line 1417. That's our entry point.

The problem, as I understand it, seems to be a timing issue stemming from `xfs_sync_sb_buf`. It's calling `xfs_trans_commit` which, as we know, adds a log item to the CIL. Then, immediately afterwards, `xfs_sync_sb_buf` calls `xfs_bwrite(mp->m_sb_bp)`. That's where things go sideways. `xfs_bwrite` *completes* and the `xfs_buf_ioend` frees the associated `xfs_buf_log_item`. But, and here's the crucial bit, the log item is still sitting in the CIL! It's still waiting to be pushed! I have to ask myself, why did `xfs_sync_sb_buf` call `xfs_bwrite` without ensuring the CIL had been flushed?

Aha! Now I see what's happening. `xfs_sync_sb_buf` is calling `xfs_trans_set_sync(tp)`. `xfs_trans_commit` then calls `xfs_log_force_seq(mp, commit_seq, XFS_LOG_SYNC, NULL)`. `xfs_log_force_seq` is calling `xlog_cil_force_seq(log, seq)`. And *that* function is where the magic happens. `xlog_cil_force_seq` calls `xlog_cil_push_now(log, sequence, false)` which queues `xlog_cil_push_work`. So, we *are* forcing the CIL push, but it's asynchronous.

Crucially, `xlog_cil_force_seq` *waits* for `ctx->commit_lsn` to be set. It blocks. This means `xlog_cil_force_seq` is actually waiting for `xlog_cil_push_work` to *complete* `xlog_cil_push_pcp_aggregate` and `xlog_cil_write_commit_record`. So, it *should* be safe.

I'm thinking I need to understand what's happening within `xlog_cil_write_commit_record` to see if it's the culprit. Let's start there.



37/2 2026/09/19 00:46 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_write_commit_record]

Results:
map[SourceCode:1179:	/*
1180:	 * Write out the commit record of a checkpoint transaction to close off a
1181:	 * running log write. These commit records are strictly ordered in ascending CIL
1182:	 * sequence order so that log recovery will always replay the checkpoints in the
1183:	 * correct order.
1184:	 */
1185:	static int
1186:	xlog_cil_write_commit_record(
1187:		struct xfs_cil_ctx	*ctx)
1188:	{
1189:		struct xlog		*log = ctx->cil->xc_log;
1190:		struct xlog_op_header	ophdr = {
1191:			.oh_clientid = XFS_TRANSACTION,
1192:			.oh_tid = cpu_to_be32(ctx->ticket->t_tid),
1193:			.oh_flags = XLOG_COMMIT_TRANS,
1194:		};
1195:		struct xfs_log_iovec	reg = {
1196:			.i_addr = &ophdr,
1197:			.i_len = sizeof(struct xlog_op_header),
1198:			.i_type = XLOG_REG_TYPE_COMMIT,
1199:		};
1200:		int			error;
1201:	
1202:		if (xlog_is_shutdown(log))
1203:			return -EIO;
1204:	
1205:		error = xlog_cil_order_write(ctx->cil, ctx->sequence, _COMMIT_RECORD);
1206:		if (error)
1207:			return error;
1208:		error = xlog_write_one_vec(log, ctx, &reg, ctx->ticket);
1209:		if (error)
1210:			xlog_force_shutdown(log, SHUTDOWN_LOG_IO_ERROR);
1211:		return error;
1212:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

38/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 31319
							output: 38
							thoughts: 43
						

Thoughts:
Okay, here's my take on those thoughts, framed as an expert's internal monologue:

**Tracking Down the Commit LSN**

Alright, hang on a second... I'm looking at this code and something's bugging me. Where *exactly* is `ctx->commit_lsn` being initialized? It's crucial for understanding the log sequence number tracking, and I don't see it explicitly set here. Time to dig in. Let's get down to the nitty-gritty and jump into the `xfs_log_cil.c` file. I'll need to do a quick search for any assignments to that variable - something like `commit_lsn =`. That should lead me right to the heart of where that value is being handled. I need to understand the lifecycle of that LSN.



39/2 2026/09/19 00:46 tool grepper
0m Args:
map[Expression:commit_lsn = PathPrefix:fs/xfs/xfs_log_cil.c]

Results:
map[Output:fs/xfs/xfs_log_cil.c=1036=xlog_cil_set_ctx_write_state(
--
fs/xfs/xfs_log_cil.c-1094-	ctx->commit_iclog = iclog;
fs/xfs/xfs_log_cil.c:1095:	ctx->commit_lsn = lsn;
fs/xfs/xfs_log_cil.c-1096-	wake_up_all(&cil->xc_commit_wait);
--
fs/xfs/xfs_log_cil.c=1909=xlog_cil_force_seq(
--
fs/xfs/xfs_log_cil.c-1914-	struct xfs_cil_ctx	*ctx;
fs/xfs/xfs_log_cil.c:1915:	xfs_lsn_t		commit_lsn = NULLCOMMITLSN;
fs/xfs/xfs_log_cil.c-1916-
--
fs/xfs/xfs_log_cil.c-1959-		/* found it! */
fs/xfs/xfs_log_cil.c:1960:		commit_lsn = ctx->commit_lsn;
fs/xfs/xfs_log_cil.c-1961-	}
]

40/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 31928
							output: 49
							thoughts: 44
						

Thoughts:
Here's my take on the thought process, as if it were my own:

**Investigating `ctx->commit_lsn` Setting**

Okay, so I'm looking at how `ctx->commit_lsn` is getting its value. The code comments point me toward `xlog_cil_set_ctx_write_state`, that's where the critical setting happens. Let's delve into that function, shall we? It's time to confirm and understand the exact mechanism and any potential implications of that assignment, I'll review how it's being handled in `xlog_cil_set_ctx_write_state`



41/2 2026/09/19 00:46 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_set_ctx_write_state]

Results:
map[SourceCode:1029:	/*
1030:	* Record the LSN of the iclog we were just granted space to start writing into.
1031:	* If the context doesn't have a start_lsn recorded, then this iclog will
1032:	* contain the start record for the checkpoint. Otherwise this write contains
1033:	* the commit record for the checkpoint.
1034:	*/
1035:	void
1036:	xlog_cil_set_ctx_write_state(
1037:		struct xfs_cil_ctx	*ctx,
1038:		struct xlog_in_core	*iclog)
1039:	{
1040:		struct xfs_cil		*cil = ctx->cil;
1041:		xfs_lsn_t		lsn = be64_to_cpu(iclog->ic_header->h_lsn);
1042:	
1043:		ASSERT(!ctx->commit_lsn);
1044:		if (!ctx->start_lsn) {
1045:			spin_lock(&cil->xc_push_lock);
1046:			/*
1047:			 * The LSN we need to pass to the log items on transaction
1048:			 * commit is the LSN reported by the first log vector write, not
1049:			 * the commit lsn. If we use the commit record lsn then we can
1050:			 * move the grant write head beyond the tail LSN and overwrite
1051:			 * it.
1052:			 */
1053:			ctx->start_lsn = lsn;
1054:			wake_up_all(&cil->xc_start_wait);
1055:			spin_unlock(&cil->xc_push_lock);
1056:	
1057:			/*
1058:			 * Flush the write cache before writing the start record so that
1059:			 * the metadata we are about to overwrite in the log and the
1060:			 * data that new allocations in this context refer to are
1061:			 * persisted to stable storage before this iclog is written.
1062:			 */
1063:			spin_lock(&cil->xc_log->l_icloglock);
1064:			iclog->ic_flags |= XLOG_ICL_NEED_FLUSH;
1065:			spin_unlock(&cil->xc_log->l_icloglock);
1066:			return;
1067:		}
1068:	
1069:		/*
1070:		 * Take a reference to the iclog for the context so that we still hold
1071:		 * it when xlog_write is done and has released it. This means the
1072:		 * context controls when the iclog is released for IO.
1073:		 */
1074:		atomic_inc(&iclog->ic_refcnt);
1075:	
1076:		/*
1077:		 * xlog_state_get_iclog_space() guarantees there is enough space in the
1078:		 * iclog for an entire commit record, so we can attach the context
1079:		 * callbacks now.  This needs to be done before we make the commit_lsn
1080:		 * visible to waiters so that checkpoints with commit records in the
1081:		 * same iclog order their IO completion callbacks in the same order that
1082:		 * the commit records appear in the iclog.
1083:		 */
1084:		spin_lock(&cil->xc_log->l_icloglock);
1085:		list_add_tail(&ctx->iclog_entry, &iclog->ic_callbacks);
1086:		spin_unlock(&cil->xc_log->l_icloglock);
1087:	
1088:		/*
1089:		 * Now we can record the commit LSN and wake anyone waiting for this
1090:		 * sequence to have the ordered commit record assigned to a physical
1091:		 * location in the log.
1092:		 */
1093:		spin_lock(&cil->xc_push_lock);
1094:		ctx->commit_iclog = iclog;
1095:		ctx->commit_lsn = lsn;
1096:		wake_up_all(&cil->xc_commit_wait);
1097:		spin_unlock(&cil->xc_push_lock);
1098:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

42/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 33361
							output: 37
							thoughts: 56
						

Thoughts:
Here's my take on the thought process:

**Tracing the Write State in XLOG Operations**

Okay, so I'm trying to figure out where `xlog_cil_set_ctx_write_state` is being called within the XLOG write path. My initial hunch is that it's probably triggered from either `xlog_write_one_vec` or the main `xlog_write` function, but I need to confirm that. Time to dig in and do a quick code search for that specific function. Let's see what the call graph reveals. This should be a pretty straightforward exercise, given my familiarity with the codebase. I just need to get a clear picture of the data flow and how the write state is being managed during XLOG writes.



43/2 2026/09/19 00:46 tool grepper
0m Args:
map[Expression:xlog_cil_set_ctx_write_state PathPrefix:fs/xfs/]

Results:
map[Output:fs/xfs/xfs_log.c=2151=xlog_write(
--
fs/xfs/xfs_log.c-2184-	if (ctx)
fs/xfs/xfs_log.c:2185:		xlog_cil_set_ctx_write_state(ctx, data.iclog);
fs/xfs/xfs_log.c-2186-
--
fs/xfs/xfs_log_cil.c=1035=void
fs/xfs/xfs_log_cil.c:1036:xlog_cil_set_ctx_write_state(
fs/xfs/xfs_log_cil.c-1037-	struct xfs_cil_ctx	*ctx,
--
fs/xfs/xfs_log_priv.h=570=void	xlog_cil_commit(struct xlog *log, struct xfs_trans *tp,
fs/xfs/xfs_log_priv.h-571-			xfs_csn_t *commit_seq, bool regrant);
fs/xfs/xfs_log_priv.h:572:void	xlog_cil_set_ctx_write_state(struct xfs_cil_ctx *ctx,
fs/xfs/xfs_log_priv.h-573-			struct xlog_in_core *iclog);
]

44/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 33977
							output: 43
							thoughts: 579
						

Thoughts:
**My Analysis of the XFS Logging Path**

Okay, let me trace this through. We're looking at a scenario where a log item is getting accessed at the wrong time, likely after it's been freed. It all starts with `xlog_write`, which is called from both `xlog_cil_write_chain` and `xlog_write_one_vec`. The crucial point is `ctx->commit_lsn` is set when `xlog_cil_write_commit_record` calls `xlog_write_one_vec`. I know that happens *after* `xlog_cil_push_pcp_aggregate`.

So, `xlog_cil_force_seq` is waiting for `ctx->commit_lsn` to be set, meaning it's dependent on `xlog_cil_push_pcp_aggregate` to complete. If `xlog_cil_force_seq` is waiting, then `xfs_log_force_seq` also waits. And if *that* waits, `xfs_trans_commit` is also dependent. Which in turn means `xfs_sync_sb_buf` waits for `xfs_trans_commit`, meaning it waits for everything before it, and then calls `xfs_bwrite`.

Therefore, the `xfs_bwrite` call *should* happen after `xlog_cil_push_pcp_aggregate` has finished. And if that's the case, then by the time `xfs_bwrite` executes, the log item should have already been spliced from `cilpcp->log_items` to `ctx->log_items`, and then freed by `xfs_buf_ioend`.

Here's the problem: why is `xlog_cil_push_pcp_aggregate` accessing the log item *after* it should be gone? Am I missing something in the control flow here? Could it be that `xfs_sync_sb_buf` commits the transaction, and the log item gets added to the CIL, but for the *next* sequence?

Okay, let's step through `xfs_trans_commit`. It calls `xlog_cil_commit`, which adds the log item to the CIL. *Then* it calls `xfs_log_force_seq(mp, commit_seq, XFS_LOG_SYNC, NULL)`. `xfs_log_force_seq` forces the log up to `commit_seq`.  If `commit_seq` is already pushed, then `xlog_cil_force_seq` returns immediately. Hmm, I have a feeling I need to carefully check `xlog_cil_commit`. I need to understand exactly how the log item is added there and whether this is a timing issue or the source of the item being accessed after it's freed.



45/2 2026/09/19 00:46 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_commit]

Results:
map[SourceCode:1806:	/*
1807:	 * Commit a transaction with the given vector to the Committed Item List.
1808:	 *
1809:	 * To do this, we need to format the item, pin it in memory if required and
1810:	 * account for the space used by the transaction. Once we have done that we
1811:	 * need to release the unused reservation for the transaction, attach the
1812:	 * transaction to the checkpoint context so we carry the busy extents through
1813:	 * to checkpoint completion, and then unlock all the items in the transaction.
1814:	 *
1815:	 * Called with the context lock already held in read mode to lock out
1816:	 * background commit, returns without it held once background commits are
1817:	 * allowed again.
1818:	 */
1819:	void
1820:	xlog_cil_commit(
1821:		struct xlog		*log,
1822:		struct xfs_trans	*tp,
1823:		xfs_csn_t		*commit_seq,
1824:		bool			regrant)
1825:	{
1826:		struct xfs_cil		*cil = log->l_cilp;
1827:		struct xfs_log_item	*lip, *next;
1828:		uint32_t		released_space = 0;
1829:	
1830:		/*
1831:		 * Do all necessary memory allocation before we lock the CIL.
1832:		 * This ensures the allocation does not deadlock with a CIL
1833:		 * push in memory reclaim (e.g. from kswapd).
1834:		 */
1835:		xlog_cil_alloc_shadow_bufs(log, tp);
1836:	
1837:		/* lock out background commit */
1838:		down_read(&cil->xc_ctx_lock);
1839:	
1840:		if (tp->t_flags & XFS_TRANS_HAS_INTENT_DONE)
1841:			released_space = xlog_cil_process_intents(cil, tp);
1842:	
1843:		xlog_cil_insert_items(log, tp, released_space);
1844:	
1845:		if (regrant && !xlog_is_shutdown(log))
1846:			xfs_log_ticket_regrant(log, tp->t_ticket);
1847:		else
1848:			xfs_log_ticket_ungrant(log, tp->t_ticket);
1849:		tp->t_ticket = NULL;
1850:		xfs_trans_unreserve_and_mod_sb(tp);
1851:	
1852:		/*
1853:		 * Once all the items of the transaction have been copied to the CIL,
1854:		 * the items can be unlocked and possibly freed.
1855:		 *
1856:		 * This needs to be done before we drop the CIL context lock because we
1857:		 * have to update state in the log items and unlock them before they go
1858:		 * to disk. If we don't, then the CIL checkpoint can race with us and
1859:		 * we can run checkpoint completion before we've updated and unlocked
1860:		 * the log items. This affects (at least) processing of stale buffers,
1861:		 * inodes and EFIs.
1862:		 */
1863:		trace_xfs_trans_commit_items(tp, _RET_IP_);
1864:		list_for_each_entry_safe(lip, next, &tp->t_items, li_trans) {
1865:			xfs_trans_del_item(lip);
1866:			if (lip->li_ops->iop_committing)
1867:				lip->li_ops->iop_committing(lip, cil->xc_ctx->sequence);
1868:		}
1869:		if (commit_seq)
1870:			*commit_seq = cil->xc_ctx->sequence;
1871:	
1872:		/* xlog_cil_push_background() releases cil->xc_ctx_lock */
1873:		xlog_cil_push_background(log);
1874:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

46/2 2026/09/19 00:46 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 36408
							output: 45
							thoughts: 33
						

Thoughts:
Here's my summary, as though I'm thinking through this process:

**Diving into CIL Insertion**

Okay, so I'm looking at how we're integrating these items into the CIL. The function responsible for that insertion, as I understand it, is `xlog_cil_insert_items`. It makes sense; the name is pretty descriptive. Now, I need to take a closer look at `xlog_cil_insert_items` itself to verify precisely how it's handling the addition process. I want to confirm the nuances and specifics of its implementation. Let's see what's happening under the hood.



47/2 2026/09/19 00:47 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_insert_items]

Results:
map[SourceCode: 625:	/*
 626:	 * Insert the log items into the CIL and calculate the difference in space
 627:	 * consumed by the item. Add the space to the checkpoint ticket and calculate
 628:	 * if the change requires additional log metadata. If it does, take that space
 629:	 * as well. Remove the amount of space we added to the checkpoint ticket from
 630:	 * the current transaction ticket so that the accounting works out correctly.
 631:	 */
 632:	static void
 633:	xlog_cil_insert_items(
 634:		struct xlog		*log,
 635:		struct xfs_trans	*tp,
 636:		uint32_t		released_space)
 637:	{
 638:		struct xfs_cil		*cil = log->l_cilp;
 639:		struct xfs_cil_ctx	*ctx = cil->xc_ctx;
 640:		struct xfs_log_item	*lip;
 641:		int			len = 0;
 642:		int			iovhdr_res = 0, split_res = 0, ctx_res = 0;
 643:		int			space_used;
 644:		int			order;
 645:		unsigned int		cpu_nr;
 646:		struct xlog_cil_pcp	*cilpcp;
 647:	
 648:		ASSERT(tp);
 649:	
 650:		/*
 651:		 * We can do this safely because the context can't checkpoint until we
 652:		 * are done so it doesn't matter exactly how we update the CIL.
 653:		 */
 654:		xlog_cil_insert_format_items(log, tp, &len);
 655:	
 656:		/*
 657:		 * Subtract the space released by intent cancelation from the space we
 658:		 * consumed so that we remove it from the CIL space and add it back to
 659:		 * the current transaction reservation context.
 660:		 */
 661:		len -= released_space;
 662:	
 663:		/*
 664:		 * Grab the per-cpu pointer for the CIL before we start any accounting.
 665:		 * That ensures that we are running with pre-emption disabled and so we
 666:		 * can't be scheduled away between split sample/update operations that
 667:		 * are done without outside locking to serialise them.
 668:		 */
 669:		cpu_nr = get_cpu();
 670:		cilpcp = this_cpu_ptr(cil->xc_pcp);
 671:	
 672:		/* Tell the future push that there was work added by this CPU. */
 673:		if (!cpumask_test_cpu(cpu_nr, &ctx->cil_pcpmask))
 674:			cpumask_test_and_set_cpu(cpu_nr, &ctx->cil_pcpmask);
 675:	
 676:		/*
 677:		 * We need to take the CIL checkpoint unit reservation on the first
 678:		 * commit into the CIL. Test the XLOG_CIL_EMPTY bit first so we don't
 679:		 * unnecessarily do an atomic op in the fast path here. We can clear the
 680:		 * XLOG_CIL_EMPTY bit as we are under the xc_ctx_lock here and that
 681:		 * needs to be held exclusively to reset the XLOG_CIL_EMPTY bit.
 682:		 */
 683:		if (test_bit(XLOG_CIL_EMPTY, &cil->xc_flags) &&
 684:		    test_and_clear_bit(XLOG_CIL_EMPTY, &cil->xc_flags))
 685:			ctx_res = ctx->ticket->t_unit_res;
 686:	
 687:		/*
 688:		 * Check if we need to steal iclog headers. atomic_read() is not a
 689:		 * locked atomic operation, so we can check the value before we do any
 690:		 * real atomic ops in the fast path. If we've already taken the CIL unit
 691:		 * reservation from this commit, we've already got one iclog header
 692:		 * space reserved so we have to account for that otherwise we risk
 693:		 * overrunning the reservation on this ticket.
 694:		 *
 695:		 * If the CIL is already at the hard limit, we might need more header
 696:		 * space that originally reserved. So steal more header space from every
 697:		 * commit that occurs once we are over the hard limit to ensure the CIL
 698:		 * push won't run out of reservation space.
 699:		 *
 700:		 * This can steal more than we need, but that's OK.
 701:		 *
 702:		 * The cil->xc_ctx_lock provides the serialisation necessary for safely
 703:		 * calling xlog_cil_over_hard_limit() in this context.
 704:		 */
 705:		space_used = atomic_read(&ctx->space_used) + cilpcp->space_used + len;
 706:		if (atomic_read(&cil->xc_iclog_hdrs) > 0 ||
 707:		    xlog_cil_over_hard_limit(log, space_used)) {
 708:			split_res = log->l_iclog_hsize +
 709:						sizeof(struct xlog_op_header);
 710:			if (ctx_res)
 711:				ctx_res += split_res * (tp->t_ticket->t_iclog_hdrs - 1);
 712:			else
 713:				ctx_res = split_res * tp->t_ticket->t_iclog_hdrs;
 714:			atomic_sub(tp->t_ticket->t_iclog_hdrs, &cil->xc_iclog_hdrs);
 715:		}
 716:		cilpcp->space_reserved += ctx_res;
 717:	
 718:		/*
 719:		 * Accurately account when over the soft limit, otherwise fold the
 720:		 * percpu count into the global count if over the per-cpu threshold.
 721:		 */
 722:		if (!test_bit(XLOG_CIL_PCP_SPACE, &cil->xc_flags)) {
 723:			atomic_add(len, &ctx->space_used);
 724:		} else if (cilpcp->space_used + len >
 725:				(XLOG_CIL_SPACE_LIMIT(log) / num_online_cpus())) {
 726:			space_used = atomic_add_return(cilpcp->space_used + len,
 727:							&ctx->space_used);
 728:			cilpcp->space_used = 0;
 729:	
 730:			/*
 731:			 * If we just transitioned over the soft limit, we need to
 732:			 * transition to the global atomic counter.
 733:			 */
 734:			if (space_used >= XLOG_CIL_SPACE_LIMIT(log))
 735:				xlog_cil_insert_pcp_aggregate(cil, ctx);
 736:		} else {
 737:			cilpcp->space_used += len;
 738:		}
 739:		/* attach the transaction to the CIL if it has any busy extents */
 740:		if (!list_empty(&tp->t_busy))
 741:			list_splice_init(&tp->t_busy, &cilpcp->busy_extents);
 742:	
 743:		/*
 744:		 * Now update the order of everything modified in the transaction
 745:		 * and insert items into the CIL if they aren't already there.
 746:		 * We do this here so we only need to take the CIL lock once during
 747:		 * the transaction commit.
 748:		 */
 749:		order = atomic_inc_return(&ctx->order_id);
 750:		list_for_each_entry(lip, &tp->t_items, li_trans) {
 751:			/* Skip items which aren't dirty in this transaction. */
 752:			if (!test_bit(XFS_LI_DIRTY, &lip->li_flags))
 753:				continue;
 754:	
 755:			lip->li_order_id = order;
 756:			if (!list_empty(&lip->li_cil))
 757:				continue;
 758:			list_add_tail(&lip->li_cil, &cilpcp->log_items);
 759:		}
 760:		put_cpu();
 761:	
 762:		/*
 763:		 * If we've overrun the reservation, dump the tx details before we move
 764:		 * the log items. Shutdown is imminent...
 765:		 */
 766:		tp->t_ticket->t_curr_res -= ctx_res + len;
 767:		if (WARN_ON(tp->t_ticket->t_curr_res < 0)) {
 768:			xfs_warn(log->l_mp, "Transaction log reservation overrun:");
 769:			xfs_warn(log->l_mp,
 770:				 "  log items: %d bytes (iov hdrs: %d bytes)",
 771:				 len, iovhdr_res);
 772:			xfs_warn(log->l_mp, "  split region headers: %d bytes",
 773:				 split_res);
 774:			xfs_warn(log->l_mp, "  ctx ticket: %d bytes", ctx_res);
 775:			xlog_print_trans(tp);
 776:			xlog_force_shutdown(log, SHUTDOWN_LOG_IO_ERROR);
 777:		}
 778:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

48/2 2026/09/19 00:47 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 39382
							output: 47
							thoughts: 3188
						

Thoughts:
**Debugging a Concurrent Data Race in XFS Logging**

Okay, so I'm diving deep into this XFS logging issue. It seems like the core problem revolves around concurrent access to the per-CPU log item lists (`cilpcp->log_items`) during transaction commits. Let's break this down:

First, an item gets added to the per-CPU list via `list_add_tail`. It seems pretty straightforward, then `xfs_trans_commit` triggers the log force sequence. That in turn, queues work to push the CIL, `xlog_cil_push_work`. But the key is that `xlog_cil_force_seq` waits until `ctx->commit_lsn` is set, indicating the push is complete. So `xlog_cil_push_work` must have *already* called the aggregate function before returning.

The `xlog_cil_push_work` function calls `xlog_cil_push_pcp_aggregate`. This function is supposed to splice the per-CPU lists into the context's main list (`ctx->log_items`), so after it runs, the `cilpcp->log_items` should be empty. But, here's where it gets interesting: I'm seeing a crash in `list_splice_init` during the next transaction, meaning `cilpcp->log_items` *isn't* empty when it should be!

I need to understand *why* `xlog_cil_push_pcp_aggregate` wouldn't splice the items in a previous transaction. I see a check: the splice only happens if the CPU is in `ctx->cil_pcpmask`. This mask is set in `xlog_cil_insert_items` by `cpumask_test_and_set_cpu`, which I've checked is atomic. So the CPU should be set in the mask.

I'm thinking: Could `xlog_cil_push_work` be running concurrently with `xlog_cil_insert_items` and miss the `cpu` in `ctx->cil_pcpmask`? Nope, the context lock ensures they can't run together.

Then, there's the possibility that `xlog_cil_insert_items` adds an item to `cilpcp->log_items` *before* the push happens. In that case, `xlog_cil_push_work` will see the item in `cilpcp->log_items`, and the `cpu` will be in `ctx->cil_pcpmask`. The function will proceed to splice items.

So if the splice fails, the item *must* have been freed!

My thought: Could an item get on `cilpcp->log_items`, but *not* be spliced?
I've got a clue! The critical part is here:

```c
		list_for_each_entry(lip, &tp->t_items, li_trans) {
			// Skip items which aren't dirty in this transaction.
			if (!test_bit(XFS_LI_DIRTY, &lip->li_flags))
				continue;
	
			lip->li_order_id = order;
			if (!list_empty(&lip->li_cil))
				continue;
			list_add_tail(&lip->li_cil, &cilpcp->log_items);
		}
```

If `!list_empty(&lip->li_cil)` is true, the `list_add_tail` is skipped! This happens if an item is already on the CIL. If the item is already *committed* to the current context, this is fine, but if it is on a *previous* CIL, there could be a race here! I think I'm onto something. XFS is skipping adding an item that is ALREADY on the CIL.

If the item gets modified in transaction 1, it's added to CIL context 1. If it's modified again in transaction 2, and context 1 hasn't pushed yet, it stays in context 1? Yes, that's what seems to be happening. *I think this is it!*

`xlog_cil_insert_items` sees `!list_empty(&lip->li_cil)` and skips adding it to `cilpcp->log_items`. BUT, it is left on `old_ctx->log_items`! This is where the race happens.



49/2 2026/09/19 00:47 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_insert_format_items]

Results:
map[SourceCode: 508:	/*
 509:	 * Format log item into a flat buffers
 510:	 *
 511:	 * For delayed logging, we need to hold a formatted buffer containing all the
 512:	 * changes on the log item. This enables us to relog the item in memory and
 513:	 * write it out asynchronously without needing to relock the object that was
 514:	 * modified at the time it gets written into the iclog.
 515:	 *
 516:	 * This function takes the prepared log vectors attached to each log item, and
 517:	 * formats the changes into the log vector buffer. The buffer it uses is
 518:	 * dependent on the current state of the vector in the CIL - the shadow lv is
 519:	 * guaranteed to be large enough for the current modification, but we will only
 520:	 * use that if we can't reuse the existing lv. If we can't reuse the existing
 521:	 * lv, then simple swap it out for the shadow lv. We don't free it - that is
 522:	 * done lazily either by th enext modification or the freeing of the log item.
 523:	 *
 524:	 * We don't set up region headers during this process; we simply copy the
 525:	 * regions into the flat buffer. We can do this because we still have to do a
 526:	 * formatting step to write the regions into the iclog buffer.  Writing the
 527:	 * ophdrs during the iclog write means that we can support splitting large
 528:	 * regions across iclog boundares without needing a change in the format of the
 529:	 * item/region encapsulation.
 530:	 *
 531:	 * Hence what we need to do now is change the rewrite the vector array to point
 532:	 * to the copied region inside the buffer we just allocated. This allows us to
 533:	 * format the regions into the iclog as though they are being formatted
 534:	 * directly out of the objects themselves.
 535:	 */
 536:	static void
 537:	xlog_cil_insert_format_items(
 538:		struct xlog		*log,
 539:		struct xfs_trans	*tp,
 540:		int			*diff_len)
 541:	{
 542:		struct xfs_log_item	*lip;
 543:	
 544:		/* Bail out if we didn't find a log item.  */
 545:		if (list_empty(&tp->t_items)) {
 546:			ASSERT(0);
 547:			return;
 548:		}
 549:	
 550:		list_for_each_entry(lip, &tp->t_items, li_trans) {
 551:			struct xfs_log_vec *lv = lip->li_lv;
 552:			struct xfs_log_vec *shadow = lip->li_lv_shadow;
 553:			struct xlog_format_buf lfb = { };
 554:	
 555:			/* Skip items which aren't dirty in this transaction. */
 556:			if (!test_bit(XFS_LI_DIRTY, &lip->li_flags))
 557:				continue;
 558:	
 559:			/*
 560:			 * The formatting size information is already attached to
 561:			 * the shadow lv on the log item.
 562:			 */
 563:			if (shadow->lv_buf_used == XFS_LOG_VEC_ORDERED) {
 564:				if (!lv) {
 565:					lv = shadow;
 566:					lv->lv_item = lip;
 567:				}
 568:				ASSERT(shadow->lv_alloc_size == lv->lv_alloc_size);
 569:				xfs_cil_prepare_item(log, lip, lv, diff_len);
 570:				continue;
 571:			}
 572:	
 573:			/* Skip items that do not have any vectors for writing */
 574:			if (!shadow->lv_niovecs)
 575:				continue;
 576:	
 577:			/* compare to existing item size */
 578:			if (lv && shadow->lv_alloc_size <= lv->lv_alloc_size) {
 579:				/* same or smaller, optimise common overwrite case */
 580:	
 581:				/*
 582:				 * set the item up as though it is a new insertion so
 583:				 * that the space reservation accounting is correct.
 584:				 */
 585:				*diff_len -= lv->lv_bytes;
 586:	
 587:				/* Ensure the lv is set up according to ->iop_size */
 588:				lv->lv_niovecs = shadow->lv_niovecs;
 589:	
 590:				/* reset the lv buffer information for new formatting */
 591:				lv->lv_buf_used = 0;
 592:				lv->lv_bytes = 0;
 593:				lv->lv_buf = (char *)lv +
 594:						xlog_cil_iovec_space(lv->lv_niovecs);
 595:			} else {
 596:				/* switch to shadow buffer! */
 597:				lv = shadow;
 598:				lv->lv_item = lip;
 599:			}
 600:	
 601:			lfb.lv = lv;
 602:			ASSERT(IS_ALIGNED((unsigned long)lv->lv_buf, sizeof(uint64_t)));
 603:			lip->li_ops->iop_format(lip, &lfb);
 604:			xfs_cil_prepare_item(log, lip, lv, diff_len);
 605:		}
 606:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

50/2 2026/09/19 00:47 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 45227
							output: 43
							thoughts: 673
						

Thoughts:
**Analyzing the Concurrency of XFS CIL Item Insertion**

Okay, so I'm looking at how `xlog_cil_insert_items` handles transaction items, and there's a potential race condition that's got me thinking. It appears that `xlog_cil_insert_items` iterates through a transaction's items and adds "dirty" ones to a context's log items list, specifically `cilpcp->log_items`. The core of the issue is in this snippet:

```c
		if (!list_empty(&lip->li_cil))
			continue;
		list_add_tail(&lip->li_cil, &cilpcp->log_items);
```

Basically, if an item is *already* on `lip->li_cil`, it's skipped. My initial reaction was that if the item was on an old context and that old context was currently committing, then that old context would process and log stale data. My first thought was that perhaps XFS moved the item over to the new transaction context; however, `xlog_cil_insert_items` definitely doesn't do that.

But wait a minute, how does it all work? I recall that `xlog_cil_insert_items` is called with a read lock on the context lock (`down_read(&cil->xc_ctx_lock)`), and `xlog_cil_push_work` later takes a *write* lock (`down_write(&cil->xc_ctx_lock)`) before switching contexts using `xlog_cil_ctx_switch(cil, new_ctx)`. So the result of that logic is that `xlog_cil_insert_items` will add items to either the old OR the new context, depending on the timing of when `xlog_cil_push_work` runs.

Now it's starting to come together. If `xlog_cil_insert_items` runs *before* `xlog_cil_push_work` acquires the write lock, it sees the old context and adds the item to the old context's `cilpcp->log_items`. Then, `xlog_cil_push_work` aggregates these items into the `old_ctx->log_items` list. If it runs *after* the write lock is taken, it'll add items to the new context's list. That seems like an acceptable solution.

But, circling back to the original concern, consider an item *already* present in the old context from a previous transaction. The `!list_empty(&lip->li_cil)` condition would be true. In this case, `xlog_cil_insert_items` doesn't re-add it. So, `xlog_cil_push_work` will correctly process the existing item in the `old_ctx->log_items` and write it to the log during the commit process. Then `xlog_cil_push_work` calls `xlog_cil_committed(ctx)` or `xlog_cil_write_commit_record`.

The main outstanding question is when these items are removed from the `ctx->log_items` lists; I'll need to check the code in `xlog_cil_committed` to fully understand the item lifecycle.



51/2 2026/09/19 00:47 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_committed]

Results:
map[SourceCode: 969:	/*
 970:	 * Mark all items committed and clear busy extents. We free the log vector
 971:	 * chains in a separate pass so that we unpin the log items as quickly as
 972:	 * possible.
 973:	 */
 974:	static void
 975:	xlog_cil_committed(
 976:		struct xfs_cil_ctx	*ctx)
 977:	{
 978:		struct xfs_mount	*mp = ctx->cil->xc_log->l_mp;
 979:		bool			abort = xlog_is_shutdown(ctx->cil->xc_log);
 980:	
 981:		/*
 982:		 * If the I/O failed, we're aborting the commit and already shutdown.
 983:		 * Wake any commit waiters before aborting the log items so we don't
 984:		 * block async log pushers on callbacks. Async log pushers explicitly do
 985:		 * not wait on log force completion because they may be holding locks
 986:		 * required to unpin items.
 987:		 */
 988:		if (abort) {
 989:			spin_lock(&ctx->cil->xc_push_lock);
 990:			wake_up_all(&ctx->cil->xc_start_wait);
 991:			wake_up_all(&ctx->cil->xc_commit_wait);
 992:			spin_unlock(&ctx->cil->xc_push_lock);
 993:		}
 994:	
 995:		xlog_cil_ail_insert(ctx, abort);
 996:	
 997:		xfs_extent_busy_sort(&ctx->busy_extents.extent_list);
 998:		xfs_extent_busy_clear(&ctx->busy_extents.extent_list,
 999:				      xfs_has_discard(mp) && !abort);
1000:	
1001:		spin_lock(&ctx->cil->xc_push_lock);
1002:		list_del(&ctx->committing);
1003:		spin_unlock(&ctx->cil->xc_push_lock);
1004:	
1005:		xlog_cil_free_logvec(&ctx->lv_chain);
1006:	
1007:		if (!list_empty(&ctx->busy_extents.extent_list)) {
1008:			ctx->busy_extents.owner = ctx;
1009:			xfs_discard_extents(mp, &ctx->busy_extents);
1010:			return;
1011:		}
1012:	
1013:		kfree(ctx);
1014:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

52/2 2026/09/19 00:47 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 47421
							output: 45
							thoughts: 18
						

Thoughts:
Okay, here's my attempt at summarizing the thought process, as if it were my own, assuming the user is an expert.

**My Thinking on AIL Insertion**

Alright, so the core of this operation, `xlog_cil_ail_insert`, boils down to efficiently integrating these items into the Active Item List (AIL). My first consideration, given my deep understanding of the logging architecture, is how this insertion impacts the overall consistency and recoverability. I'm immediately thinking about concurrency control – how are we handling potential conflicts if multiple processes are trying to modify the AIL concurrently? That's paramount.

Next, I'm analyzing the item itself. What are we actually inserting? Is it a data modification, a control record, or something else entirely? The type of item will dictate the optimal insertion strategy. Do we need to check for existing entries related to the same data before insertion?

Beyond the mechanics, I'm thinking about performance. Is this a frequent operation? If so, the insertion method needs to be lightning fast. Do we need to optimize for sequential insertion, or can we handle random access efficiently? Cache coherency and minimizing contention would be critical here. I'm also considering how this insertion impacts the size of the AIL and how that influences flushing to disk.

Finally, I'm checking for error conditions. What if the AIL is full? What if memory allocation fails during the insertion process? Are we handling all of these edge cases gracefully, ensuring data integrity even in failure scenarios? Proper error handling is absolutely non-negotiable here. I need to review the related code paths to ensure nothing is missed.



53/2 2026/09/19 00:47 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_ail_insert]

Results:
map[SourceCode: 802:	/*
 803:	 * Take the checkpoint's log vector chain of items and insert the attached log
 804:	 * items into the AIL. This uses bulk insertion techniques to minimise AIL lock
 805:	 * traffic.
 806:	 *
 807:	 * The AIL tracks log items via the start record LSN of the checkpoint,
 808:	 * not the commit record LSN. This is because we can pipeline multiple
 809:	 * checkpoints, and so the start record of checkpoint N+1 can be
 810:	 * written before the commit record of checkpoint N. i.e:
 811:	 *
 812:	 *   start N			commit N
 813:	 *	+-------------+------------+----------------+
 814:	 *		  start N+1			commit N+1
 815:	 *
 816:	 * The tail of the log cannot be moved to the LSN of commit N when all
 817:	 * the items of that checkpoint are written back, because then the
 818:	 * start record for N+1 is no longer in the active portion of the log
 819:	 * and recovery will fail/corrupt the filesystem.
 820:	 *
 821:	 * Hence when all the log items in checkpoint N are written back, the
 822:	 * tail of the log most now only move as far forwards as the start LSN
 823:	 * of checkpoint N+1.
 824:	 *
 825:	 * If we are called with the aborted flag set, it is because a log write during
 826:	 * a CIL checkpoint commit has failed. In this case, all the items in the
 827:	 * checkpoint have already gone through iop_committed and iop_committing, which
 828:	 * means that checkpoint commit abort handling is treated exactly the same as an
 829:	 * iclog write error even though we haven't started any IO yet. Hence in this
 830:	 * case all we need to do is iop_committed processing, followed by an
 831:	 * iop_unpin(aborted) call.
 832:	 *
 833:	 * The AIL cursor is used to optimise the insert process. If commit_lsn is not
 834:	 * at the end of the AIL, the insert cursor avoids the need to walk the AIL to
 835:	 * find the insertion point on every xfs_log_item_batch_insert() call. This
 836:	 * saves a lot of needless list walking and is a net win, even though it
 837:	 * slightly increases that amount of AIL lock traffic to set it up and tear it
 838:	 * down.
 839:	 */
 840:	static void
 841:	xlog_cil_ail_insert(
 842:		struct xfs_cil_ctx	*ctx,
 843:		bool			aborted)
 844:	{
 845:	#define LOG_ITEM_BATCH_SIZE	32
 846:		struct xfs_ail		*ailp = ctx->cil->xc_log->l_ailp;
 847:		struct xfs_log_item	*log_items[LOG_ITEM_BATCH_SIZE];
 848:		struct xfs_log_vec	*lv;
 849:		struct xfs_ail_cursor	cur;
 850:		xfs_lsn_t		old_head;
 851:		int			i = 0;
 852:	
 853:		/*
 854:		 * Update the AIL head LSN with the commit record LSN of this
 855:		 * checkpoint. As iclogs are always completed in order, this should
 856:		 * always be the same (as iclogs can contain multiple commit records) or
 857:		 * higher LSN than the current head. We do this before insertion of the
 858:		 * items so that log space checks during insertion will reflect the
 859:		 * space that this checkpoint has already consumed.  We call
 860:		 * xfs_ail_update_finish() so that tail space and space-based wakeups
 861:		 * will be recalculated appropriately.
 862:		 */
 863:		ASSERT(XFS_LSN_CMP(ctx->commit_lsn, ailp->ail_head_lsn) >= 0 ||
 864:				aborted);
 865:		spin_lock(&ailp->ail_lock);
 866:		xfs_trans_ail_cursor_last(ailp, &cur, ctx->start_lsn);
 867:		old_head = ailp->ail_head_lsn;
 868:		ailp->ail_head_lsn = ctx->commit_lsn;
 869:		/* xfs_ail_update_finish() drops the ail_lock */
 870:		xfs_ail_update_finish(ailp, NULLCOMMITLSN);
 871:	
 872:		/*
 873:		 * We move the AIL head forwards to account for the space used in the
 874:		 * log before we remove that space from the grant heads. This prevents a
 875:		 * transient condition where reservation space appears to become
 876:		 * available on return, only for it to disappear again immediately as
 877:		 * the AIL head update accounts in the log tail space.
 878:		 */
 879:		smp_wmb();	/* paired with smp_rmb in xlog_grant_space_left */
 880:		xlog_grant_return_space(ailp->ail_log, old_head, ailp->ail_head_lsn);
 881:	
 882:		/* unpin all the log items */
 883:		list_for_each_entry(lv, &ctx->lv_chain, lv_list) {
 884:			struct xfs_log_item	*lip = lv->lv_item;
 885:			xfs_lsn_t		item_lsn;
 886:	
 887:			if (aborted) {
 888:				trace_xlog_ail_insert_abort(lip);
 889:				set_bit(XFS_LI_ABORTED, &lip->li_flags);
 890:			}
 891:	
 892:			if (lip->li_ops->flags & XFS_ITEM_RELEASE_WHEN_COMMITTED) {
 893:				lip->li_ops->iop_release(lip);
 894:				continue;
 895:			}
 896:	
 897:			if (lip->li_ops->iop_committed)
 898:				item_lsn = lip->li_ops->iop_committed(lip,
 899:						ctx->start_lsn);
 900:			else
 901:				item_lsn = ctx->start_lsn;
 902:	
 903:			/* item_lsn of -1 means the item needs no further processing */
 904:			if (XFS_LSN_CMP(item_lsn, (xfs_lsn_t)-1) == 0)
 905:				continue;
 906:	
 907:			/*
 908:			 * if we are aborting the operation, no point in inserting the
 909:			 * object into the AIL as we are in a shutdown situation.
 910:			 */
 911:			if (aborted) {
 912:				ASSERT(xlog_is_shutdown(ailp->ail_log));
 913:				if (lip->li_ops->iop_unpin)
 914:					lip->li_ops->iop_unpin(lip, 1);
 915:				continue;
 916:			}
 917:	
 918:			if (item_lsn != ctx->start_lsn) {
 919:	
 920:				/*
 921:				 * Not a bulk update option due to unusual item_lsn.
 922:				 * Push into AIL immediately, rechecking the lsn once
 923:				 * we have the ail lock. Then unpin the item. This does
 924:				 * not affect the AIL cursor the bulk insert path is
 925:				 * using.
 926:				 */
 927:				spin_lock(&ailp->ail_lock);
 928:				if (XFS_LSN_CMP(item_lsn, lip->li_lsn) > 0)
 929:					xfs_trans_ail_update(ailp, lip, item_lsn);
 930:				else
 931:					spin_unlock(&ailp->ail_lock);
 932:				if (lip->li_ops->iop_unpin)
 933:					lip->li_ops->iop_unpin(lip, 0);
 934:				continue;
 935:			}
 936:	
 937:			/* Item is a candidate for bulk AIL insert.  */
 938:			log_items[i++] = lv->lv_item;
 939:			if (i >= LOG_ITEM_BATCH_SIZE) {
 940:				xlog_cil_ail_insert_batch(ailp, &cur, log_items,
 941:						LOG_ITEM_BATCH_SIZE, ctx->start_lsn);
 942:				i = 0;
 943:			}
 944:		}
 945:	
 946:		/* make sure we insert the remainder! */
 947:		if (i)
 948:			xlog_cil_ail_insert_batch(ailp, &cur, log_items, i,
 949:					ctx->start_lsn);
 950:	
 951:		spin_lock(&ailp->ail_lock);
 952:		xfs_trans_ail_cursor_done(&cur);
 953:		spin_unlock(&ailp->ail_lock);
 954:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

54/2 2026/09/19 00:47 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 50528
							output: 47
							thoughts: 98
						

Thoughts:
**My Analysis of the Cilium XLog Insertion Process**

Okay, hold on a second! I need to re-evaluate how this works. I was just reviewing the `xlog_cil_ail_insert` function, and it's suddenly clear: it's iterating over the `ctx->lv_chain` and not `ctx->log_items` directly. That's a crucial distinction. Now, the question is where is the `ctx->log_items` structure actually cleared or handled? It must be getting built into that linked chain.

Aha! It's starting to click. I'm recalling now that `xlog_cil_build_lv_chain` seems to be responsible for building `ctx->lv_chain` *from* `ctx->log_items`. That makes sense. Therefore, the processing pipeline likely involves populating `ctx->log_items`, then having `xlog_cil_build_lv_chain` create the chain used by `xlog_cil_ail_insert`. I'm going to jump into reviewing `xlog_cil_build_lv_chain` now to confirm this.



55/2 2026/09/19 00:47 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_build_lv_chain]

Results:
map[SourceCode:1298:	/*
1299:	 * Pull all the log vectors off the items in the CIL, and remove the items from
1300:	 * the CIL. We don't need the CIL lock here because it's only needed on the
1301:	 * transaction commit side which is currently locked out by the flush lock.
1302:	 *
1303:	 * If a log item is marked with a whiteout, we do not need to write it to the
1304:	 * journal and so we just move them to the whiteout list for the caller to
1305:	 * dispose of appropriately.
1306:	 */
1307:	static void
1308:	xlog_cil_build_lv_chain(
1309:		struct xfs_cil_ctx	*ctx,
1310:		struct list_head	*whiteouts,
1311:		uint32_t		*num_iovecs,
1312:		uint32_t		*num_bytes)
1313:	{
1314:		while (!list_empty(&ctx->log_items)) {
1315:			struct xfs_log_item	*item;
1316:			struct xfs_log_vec	*lv;
1317:	
1318:			item = list_first_entry(&ctx->log_items,
1319:						struct xfs_log_item, li_cil);
1320:	
1321:			if (test_bit(XFS_LI_WHITEOUT, &item->li_flags)) {
1322:				list_move(&item->li_cil, whiteouts);
1323:				trace_xfs_cil_whiteout_skip(item);
1324:				continue;
1325:			}
1326:	
1327:			lv = item->li_lv;
1328:			lv->lv_order_id = item->li_order_id;
1329:	
1330:			/* we don't write ordered log vectors */
1331:			if (lv->lv_buf_used != XFS_LOG_VEC_ORDERED)
1332:				*num_bytes += lv->lv_bytes;
1333:			*num_iovecs += lv->lv_niovecs;
1334:			list_add_tail(&lv->lv_list, &ctx->lv_chain);
1335:	
1336:			list_del_init(&item->li_cil);
1337:			item->li_order_id = 0;
1338:			item->li_lv = NULL;
1339:		}
1340:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

56/2 2026/09/19 00:47 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 51659
							output: 45
							thoughts: 1896
						

Thoughts:
**Analyzing a Potential XFS Log Item Leak**

Okay, so I'm tracing this XFS code and I've got a handle on the interaction between `xlog_cil_build_lv_chain`, `xlog_cil_insert_items`, and context switching in the CIL. Initially, my thought process went like this: `xlog_cil_build_lv_chain` empties `item->li_cil` by removing it from `ctx->log_items`, essentially re-initializing it.  This seemed problematic, because if `xlog_cil_insert_items` runs *after* this, it'll see an empty list and incorrectly add the item to the *new* context's log. I considered the function call order: `xlog_cil_push_pcp_aggregate` splices `cilpcp->log_items` to `ctx->log_items`, then `xlog_cil_build_lv_chain` removes things, and *then* the context switch happens. But, `xlog_cil_build_lv_chain` happens *before* the switch.  Since the write lock `cil->xc_ctx_lock` is held, I figured it was safe because `xlog_cil_insert_items` couldn't run concurrently. This seemed okay, `xlog_cil_insert_items` gets the *new* context and should add to the right list. All good, right?

But then, I hit a snag. The log item is freed by `xfs_buf_ioend`, but somehow, the item is *still* on the new context's `cilpcp->log_items` list! This is wrong! It seemed like a race condition where the log push happened *after* the item was freed. But, the sync flag is set. That should push it, making sure it happens before the free!

Okay, so, `xfs_trans_commit` calls `xfs_log_force_seq`, which in turn calls `xlog_cil_force_seq`. `xlog_cil_force_seq` *should* be pushing the new context, and blocking until it's written. The key is that `xlog_cil_force_seq` *must* push the new context and wait for it to complete before `xfs_trans_commit` returns. If that's true, then the log push should be done, and the item's list entry should be cleaned up before the buf is freed.

So, I drilled down into `xlog_cil_force_seq`. It queues `xlog_cil_push_work`, and *then* waits for the context to commit. I traced the execution flow, step by step, which looks good. My thinking was that after pushing it, it waits for `ctx->commit_lsn` to be set, which it should do.  The problem, however, is that this entire process depends on whether a sync is actually *enforced*.

Then it dawned on me. What if `xfs_log_force_seq` returns *early*? I started to look at where `xlog_cil_force_seq` can return `NULLCOMMITLSN`, as this leads to `xfs_log_force_seq` returning immediately. This is the point of the bug: if `xlog_cil_force_seq` receives a sequence that is *less than* the current sequence, it exits early with `NULLCOMMITLSN`. This indicates that the context might *already* be pushed. This means that we don't know the `commit_lsn`. So what if we can't wait?

This is where the problem lies. The CIL context *has* been pushed. However, since the sequence check in `xlog_cil_force_seq` results in early return, we have no guarantees that it has completed! Consequently, `xfs_log_force_seq` returns immediately. Then, `xfs_trans_commit` returns, and the buffer is freed. But we never pushed the changes to the list, potentially resulting in the item being incorrectly left on the `cilpcp->log_items` list.  This could lead to a use-after-free scenario. This needs further investigation. It *appears* to be a subtle race condition related to premature returns from `xlog_cil_force_seq`.



57/2 2026/09/19 00:48 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_force_seq]

Results:
map[SourceCode:1898:	/*
1899:	 * Conditionally push the CIL based on the sequence passed in.
1900:	 *
1901:	 * We only need to push if we haven't already pushed the sequence number given.
1902:	 * Hence the only time we will trigger a push here is if the push sequence is
1903:	 * the same as the current context.
1904:	 *
1905:	 * We return the current commit lsn to allow the callers to determine if a
1906:	 * iclog flush is necessary following this call.
1907:	 */
1908:	xfs_lsn_t
1909:	xlog_cil_force_seq(
1910:		struct xlog	*log,
1911:		xfs_csn_t	sequence)
1912:	{
1913:		struct xfs_cil		*cil = log->l_cilp;
1914:		struct xfs_cil_ctx	*ctx;
1915:		xfs_lsn_t		commit_lsn = NULLCOMMITLSN;
1916:	
1917:		ASSERT(sequence <= cil->xc_current_sequence);
1918:	
1919:		if (!sequence)
1920:			sequence = cil->xc_current_sequence;
1921:		trace_xfs_log_force(log->l_mp, sequence, _RET_IP_);
1922:	
1923:		/*
1924:		 * check to see if we need to force out the current context.
1925:		 * xlog_cil_push() handles racing pushes for the same sequence,
1926:		 * so no need to deal with it here.
1927:		 */
1928:	restart:
1929:		xlog_cil_push_now(log, sequence, false);
1930:	
1931:		/*
1932:		 * See if we can find a previous sequence still committing.
1933:		 * We need to wait for all previous sequence commits to complete
1934:		 * before allowing the force of push_seq to go ahead. Hence block
1935:		 * on commits for those as well.
1936:		 */
1937:		spin_lock(&cil->xc_push_lock);
1938:		list_for_each_entry(ctx, &cil->xc_committing, committing) {
1939:			/*
1940:			 * Avoid getting stuck in this loop because we were woken by the
1941:			 * shutdown, but then went back to sleep once already in the
1942:			 * shutdown state.
1943:			 */
1944:			if (xlog_is_shutdown(log))
1945:				goto out_shutdown;
1946:			if (ctx->sequence > sequence)
1947:				continue;
1948:			if (!ctx->commit_lsn) {
1949:				/*
1950:				 * It is still being pushed! Wait for the push to
1951:				 * complete, then start again from the beginning.
1952:				 */
1953:				XFS_STATS_INC(log->l_mp, xs_log_force_sleep);
1954:				xlog_wait(&cil->xc_commit_wait, &cil->xc_push_lock);
1955:				goto restart;
1956:			}
1957:			if (ctx->sequence != sequence)
1958:				continue;
1959:			/* found it! */
1960:			commit_lsn = ctx->commit_lsn;
1961:		}
1962:	
1963:		/*
1964:		 * The call to xlog_cil_push_now() executes the push in the background.
1965:		 * Hence by the time we have got here it our sequence may not have been
1966:		 * pushed yet. This is true if the current sequence still matches the
1967:		 * push sequence after the above wait loop and the CIL still contains
1968:		 * dirty objects. This is guaranteed by the push code first adding the
1969:		 * context to the committing list before emptying the CIL.
1970:		 *
1971:		 * Hence if we don't find the context in the committing list and the
1972:		 * current sequence number is unchanged then the CIL contents are
1973:		 * significant.  If the CIL is empty, if means there was nothing to push
1974:		 * and that means there is nothing to wait for. If the CIL is not empty,
1975:		 * it means we haven't yet started the push, because if it had started
1976:		 * we would have found the context on the committing list.
1977:		 */
1978:		if (sequence == cil->xc_current_sequence &&
1979:		    !test_bit(XLOG_CIL_EMPTY, &cil->xc_flags)) {
1980:			spin_unlock(&cil->xc_push_lock);
1981:			goto restart;
1982:		}
1983:	
1984:		spin_unlock(&cil->xc_push_lock);
1985:		return commit_lsn;
1986:	
1987:		/*
1988:		 * We detected a shutdown in progress. We need to trigger the log force
1989:		 * to pass through it's iclog state machine error handling, even though
1990:		 * we are already in a shutdown state. Hence we can't return
1991:		 * NULLCOMMITLSN here as that has special meaning to log forces (i.e.
1992:		 * LSN is already stable), so we return a zero LSN instead.
1993:		 */
1994:	out_shutdown:
1995:		spin_unlock(&cil->xc_push_lock);
1996:		return 0;
1997:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

58/2 2026/09/19 00:48 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 56161
							output: 30
							thoughts: 1902
						

Thoughts:
**Debugging a Potential XFS Crash**

Okay, let's break this down. If `commit_lsn` is `NULLCOMMITLSN`, then `xfs_log_force_seq` returns 0. That much is clear. But if `xlog_cil_force_seq` returns `NULLCOMMITLSN`, it implies the sequence has been pushed, committed, and removed from `cil->xc_committing`. The question is *when* is it removed? Ah, `xlog_cil_committed` does the removal: within that, the list deletion happens under `ctx->cil->xc_push_lock`’s protection. This function is called when the iclog IO completes. So, the data is on disk. We don't need to block waiting for iclog IO to complete, so returning 0 is correct if the iclog IO has completed because it is already on disk. That means `xlog_cil_committed` has run.

If `xlog_cil_committed` has run, it calls `xlog_cil_ail_insert`, which unpins the log items. When unpinned, they can be written to disk either by the AIL or by `xfs_bwrite`, which should be safe. However, the problem is that `xlog_cil_push_pcp_aggregate` is crashing on a freed item. That function accesses `cilpcp->log_items`. So, the item *must* have been added to `cilpcp->log_items` and then freed *before* `xlog_cil_push_pcp_aggregate` runs. How can that happen? Perhaps if `xfs_sync_sb_buf` calls `xfs_bwrite` before `xlog_cil_push_pcp_aggregate`.

But `xfs_sync_sb_buf` calls `xfs_trans_commit`, which calls `xfs_log_force_seq`. `xfs_log_force_seq` waits for `xlog_cil_push_pcp_aggregate` to complete because `xlog_cil_force_seq` waits for `ctx->commit_lsn` which is set after `xlog_cil_push_pcp_aggregate` executes. Therefore, `xfs_log_force_seq` cannot return before `xlog_cil_push_pcp_aggregate` runs! What if it returns `NULLCOMMITLSN` *before* `xlog_cil_push_pcp_aggregate`? That means if `sequence < cil->xc_current_sequence` and it’s *not* in `cil->xc_committing`. The `sequence` is the `commit_seq`, which is set during `xlog_cil_commit`. `xlog_cil_commit` sets `commit_seq`, calls `xlog_cil_push_background`, and then `xfs_trans_commit` calls `xfs_log_force_seq`. If `commit_seq == cil->xc_current_sequence`, then `xlog_cil_force_seq` will call `xlog_cil_push_now`, and it *will* wait.

If `commit_seq < cil->xc_current_sequence`, another thread has *already* pushed the CIL and switched the context. So the work for `commit_seq` has *already* started. And if that's the case, then `xlog_cil_push_pcp_aggregate` *must* have already been called. That's because it's called *before* `xlog_cil_ctx_switch`. So, if `commit_seq < cil->xc_current_sequence`, then `xlog_cil_ctx_switch` has *already* been called for that `commit_seq`. Thus, `xlog_cil_push_pcp_aggregate` is *finished*. The item must already be spliced from `cilpcp->log_items`. Why isn't it?

What if the item was added to `cilpcp->log_items` *after* `xlog_cil_push_pcp_aggregate` but *before* `xlog_cil_ctx_switch`? Let’s check `xlog_cil_push_work`. `xlog_cil_push_work` holds `down_write(&cil->xc_ctx_lock)` from before `xlog_cil_push_pcp_aggregate` until after `xlog_cil_ctx_switch`. `xlog_cil_insert_items` holds `down_read(&cil->xc_ctx_lock)`. Therefore, `xlog_cil_insert_items` can *not* run concurrently with `xlog_cil


59/2 2026/09/19 00:48 tool grepper
0m Args:
map[Expression:cil_pcpmask PathPrefix:fs/xfs/]

Results:
map[Output:fs/xfs/xfs_log_cil.c=119=xlog_cil_push_pcp_aggregate(
--
fs/xfs/xfs_log_cil.c-125-
fs/xfs/xfs_log_cil.c:126:	for_each_cpu(cpu, &ctx->cil_pcpmask) {
fs/xfs/xfs_log_cil.c-127-		cilpcp = per_cpu_ptr(cil->xc_pcp, cpu);
--
fs/xfs/xfs_log_cil.c=155=xlog_cil_insert_pcp_aggregate(
--
fs/xfs/xfs_log_cil.c-166-	/*
fs/xfs/xfs_log_cil.c:167:	 * We can race with other cpus setting cil_pcpmask.  However, we've
fs/xfs/xfs_log_cil.c-168-	 * atomically cleared PCP_SPACE which forces other threads to add to
fs/xfs/xfs_log_cil.c:169:	 * the global space used count.  cil_pcpmask is a superset of cilpcp
fs/xfs/xfs_log_cil.c-170-	 * structures that could have a nonzero space_used.
fs/xfs/xfs_log_cil.c-171-	 */
fs/xfs/xfs_log_cil.c:172:	for_each_cpu(cpu, &ctx->cil_pcpmask) {
fs/xfs/xfs_log_cil.c-173-		struct xlog_cil_pcp	*cilpcp = per_cpu_ptr(cil->xc_pcp, cpu);
--
fs/xfs/xfs_log_cil.c=633=xlog_cil_insert_items(
--
fs/xfs/xfs_log_cil.c-672-	/* Tell the future push that there was work added by this CPU. */
fs/xfs/xfs_log_cil.c:673:	if (!cpumask_test_cpu(cpu_nr, &ctx->cil_pcpmask))
fs/xfs/xfs_log_cil.c:674:		cpumask_test_and_set_cpu(cpu_nr, &ctx->cil_pcpmask);
fs/xfs/xfs_log_cil.c-675-
--
fs/xfs/xfs_log_priv.h=235=struct xfs_cil_ctx {
--
fs/xfs/xfs_log_priv.h-254-	 */
fs/xfs/xfs_log_priv.h:255:	struct cpumask		cil_pcpmask;
fs/xfs/xfs_log_priv.h-256-};
]

60/2 2026/09/19 00:48 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 59846
							output: 45
							thoughts: 2409
						

Thoughts:
**The Root of the Issue: Concurrent Modification and Delayed Log Force**

Okay, so I'm looking at this crash in the XFS logging code, a slab-use-after-free within `xlog_cil_push_pcp_aggregate`. It seems I'm dealing with a buffer log item (`xfs_buf_log_item`) that's been freed prematurely, but is still lingering on a list. Let me walk through the sequence of events as I understand them.

Initially, I'm fairly certain the `cpu` is inside `ctx->cil_pcpmask`. The core is in `xlog_cil_push_pcp_aggregate`, which iterates over the `cilpcp->log_items` list, splices its items, and ideally, leaves the list empty. But it's crashing during that splice operation, indicating a corrupted list. My initial suspicion was that somehow a list element was freed before the splice, but this doesn't quite make sense given the call graph: `xlog_cil_push_pcp_aggregate` is called from `xlog_cil_push_work`, which is supposed to run *after* the item is put there.

The crash happens because `cilpcp->log_items` somehow *contains* a freed item. Now, the `xfs_buf_log_item` is freed in the `xfs_buf_item_relse`, which is called by `xfs_buf_item_done`, which is triggered by `xfs_buf_ioend`, which happens *after* the buffer write completes, specifically `xfs_bwrite` completes. But, `xfs_bwrite` is called by `xfs_sync_sb_buf` *after* a `xfs_trans_commit`, which commits the transaction that uses this `xfs_buf_log_item`. Here's the catch: the commit calls `xfs_log_force_seq`, which should *wait* for the log to be pushed. But does this *always* happen?

If `xfs_log_force_seq` returns early (due to a sequence mismatch), it could return 0. This suggests that `xlog_cil_push_work` *has* already run and completed for the log sequence. If so, `xlog_cil_push_pcp_aggregate` should have *already* executed and spliced the items. So the item should *not* be on the `cilpcp->log_items` list, and the crash should not happen here.

The breakthrough comes when I consider the possibility of *concurrent* modification. Suppose the freed item is on the `cilpcp->log_items` list of a *different* context, a later sequence. Here's a possible scenario:

1.  A transaction modifies a buffer and adds an item to `cilpcp->log_items` for sequence N.
2.  `xfs_log_force_seq` is called for sequence N, ensuring it's pushed and committed.
3.  `xfs_sync_sb_buf` calls `xfs_bwrite` on the buffer. Since sequence N is pushed, the `xfs_buf_log_item` is spliced from `cilpcp->log_items`, but also unpinned at this point.
4.  The buffer write completes, and the buffer item is freed.
5.  *Another* transaction (sequence N+1) then *also* modifies the same buffer, adding the *same* item to the new `cilpcp->log_items` list. This other transaction *does not* force the log.
6.  The original transaction finishes but not before calling `xfs_bwrite` on the same buffer, and the buffer gets freed by `xfs_buf_ioend`. The item is now freed.
7.  Later, the log for sequence N+1 is pushed.
8.  `xlog_cil_push_pcp_aggregate` attempts to splice `cilpcp->log_items`, which *still* contains the freed item. Crash!

So it's not the current context, but a subsequent transaction concurrently modifying the *same* buffer, adding the freed item back to the list of log items. This means two transactions are acting on the same buffer, and because the log isn't being forced by the second transaction, the item from the first transaction is unpinned and freed, while also being added back into the log.

Now, to verify, let me trace through a possible event sequence: Thread A and Thread B, modifying the same superblock buffer. Thread A forces the log. Thread B does not force. Then Thread A writes the buffer. After the write has completed, the item is freed.


61/2 2026/09/19 00:48 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_item_done]

Results:
map[SourceCode:1065:	void
1066:	xfs_buf_item_done(
1067:		struct xfs_buf		*bp)
1068:	{
1069:		struct xfs_buf_log_item	*bip = bp->b_log_item;
1070:	
1071:		/*
1072:		 * If we are forcibly shutting down, this may well be off the AIL
1073:		 * already. That's because we simulate the log-committed callbacks to
1074:		 * unpin these buffers. Or we may never have put this item on AIL
1075:		 * because of the transaction was aborted forcibly.
1076:		 * xfs_trans_ail_delete() takes care of these.
1077:		 *
1078:		 * Either way, AIL is useless if we're forcing a shutdown.
1079:		 *
1080:		 * Note that log recovery writes might have buffer items that are not on
1081:		 * the AIL even when the file system is not shut down.
1082:		 */
1083:		xfs_trans_ail_delete(&bip->bli_item,
1084:				     xlog_in_recovery(bip->bli_item.li_log) ?
1085:				     0 : SHUTDOWN_CORRUPT_INCORE);
1086:		xfs_buf_item_relse(bip);
1087:	}
 SourceFile:fs/xfs/xfs_buf_item.c]

62/2 2026/09/19 00:48 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 63747
							output: 45
							thoughts: 636
						

Thoughts:
**Analyzing a Potential Use-After-Free in XFS**

Okay, let's break this down. My initial thought is that `xfs_buf_item_done` calls `xfs_trans_ail_delete`. I know that if the item isn't in the Active Intent Log (AIL), then `xfs_trans_ail_delete` will trigger a shutdown if the `shutdown_type` is non-zero.  Here's the critical bit of code...

```c
	if (!test_bit(XFS_LI_IN_AIL, &lip->li_flags)) {
		spin_unlock(&ailp->ail_lock);
		if (shutdown_type && !xlog_is_shutdown(log)) {
			xfs_alert_tag(log->l_mp, XFS_PTAG_AILDELETE,
	"%s: attempting to delete a log item that is not in the AIL",
					__func__);
			xlog_force_shutdown(log, shutdown_type);
		}
		return;
	}
```

In the scenario we're considering, where Thread B has committed the transaction, the item is in the Commit Intent Log (CIL), but *not* in the AIL. That's because it hasn't been pushed and committed to the log yet. That makes me think this is where the issue lies. If the item isn't in the AIL, `xfs_trans_ail_delete` will call `xlog_force_shutdown(log, SHUTDOWN_CORRUPT_INCORE)`! That's a huge flag.

Now, let's see what's happening in the bug report. While the report doesn't explicitly state a shutdown, it's a KASAN report, so the filesystem *might* have shut down just before the crash. This is important to understand if it prevents the UAF. If it shuts down, `xlog_force_shutdown` sets the shutdown flag. Then, `xfs_buf_item_relse` gets called. Now, let's look at this part of the code, as this is where it's freed:

```c
	static void
	xfs_buf_item_relse(
		struct xfs_buf_log_item	*bip)
	{
		struct xfs_buf		*bp = bip->bli_buf;
	
		trace_xfs_buf_item_relse(bp, _RET_IP_);
	
		ASSERT(!test_bit(XFS_LI_IN_AIL, &bip->bli_item.li_flags));
		ASSERT(atomic_read(&bip->bli_refcount) == 0);
	
		bp->b_log_item = NULL;
		xfs_buf_rele(bp);
		xfs_buf_item_free(bip);
	}
```

Okay, *yes*, `xfs_buf_item_relse` frees the item! That's the smoking gun!

So, the critical question becomes: does the CIL push still run? Even if the filesystem is shutting down, `xlog_cil_push_work` might *still* be running or scheduled! That's where I need to focus my attention now; what happens to `xlog_cil_push_work` on shutdown? I need to analyze its behavior under those circumstances to understand the potential use-after-free.



63/2 2026/09/19 00:48 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_push_work]

Results:
map[SourceCode:1355:	/*
1356:	 * Push the Committed Item List to the log.
1357:	 *
1358:	 * If the current sequence is the same as xc_push_seq we need to do a flush. If
1359:	 * xc_push_seq is less than the current sequence, then it has already been
1360:	 * flushed and we don't need to do anything - the caller will wait for it to
1361:	 * complete if necessary.
1362:	 *
1363:	 * xc_push_seq is checked unlocked against the sequence number for a match.
1364:	 * Hence we can allow log forces to run racily and not issue pushes for the
1365:	 * same sequence twice.  If we get a race between multiple pushes for the same
1366:	 * sequence they will block on the first one and then abort, hence avoiding
1367:	 * needless pushes.
1368:	 *
1369:	 * This runs from a workqueue so it does not inherent any specific memory
1370:	 * allocation context. However, we do not want to block on memory reclaim
1371:	 * recursing back into the filesystem because this push may have been triggered
1372:	 * by memory reclaim itself. Hence we really need to run under full GFP_NOFS
1373:	 * contraints here.
1374:	 */
1375:	static void
1376:	xlog_cil_push_work(
1377:		struct work_struct	*work)
1378:	{
1379:		unsigned int		nofs_flags = memalloc_nofs_save();
1380:		struct xfs_cil_ctx	*ctx =
1381:			container_of(work, struct xfs_cil_ctx, push_work);
1382:		struct xfs_cil		*cil = ctx->cil;
1383:		struct xlog		*log = cil->xc_log;
1384:		struct xfs_cil_ctx	*new_ctx;
1385:		int			num_iovecs = 0;
1386:		int			num_bytes = 0;
1387:		int			error = 0;
1388:		struct xlog_cil_trans_hdr thdr;
1389:		struct xfs_log_vec	lvhdr = {};
1390:		xfs_csn_t		push_seq;
1391:		bool			push_commit_stable;
1392:		LIST_HEAD		(whiteouts);
1393:		struct xlog_ticket	*ticket;
1394:	
1395:		new_ctx = xlog_cil_ctx_alloc();
1396:		new_ctx->ticket = xlog_cil_ticket_alloc(log);
1397:	
1398:		down_write(&cil->xc_ctx_lock);
1399:	
1400:		spin_lock(&cil->xc_push_lock);
1401:		push_seq = cil->xc_push_seq;
1402:		ASSERT(push_seq <= ctx->sequence);
1403:		push_commit_stable = cil->xc_push_commit_stable;
1404:		cil->xc_push_commit_stable = false;
1405:	
1406:		/*
1407:		 * As we are about to switch to a new, empty CIL context, we no longer
1408:		 * need to throttle tasks on CIL space overruns. Wake any waiters that
1409:		 * the hard push throttle may have caught so they can start committing
1410:		 * to the new context. The ctx->xc_push_lock provides the serialisation
1411:		 * necessary for safely using the lockless waitqueue_active() check in
1412:		 * this context.
1413:		 */
1414:		if (waitqueue_active(&cil->xc_push_wait))
1415:			wake_up_all(&cil->xc_push_wait);
1416:	
1417:		xlog_cil_push_pcp_aggregate(cil, ctx);
1418:	
1419:		/*
1420:		 * Check if we've anything to push. If there is nothing, then we don't
1421:		 * move on to a new sequence number and so we have to be able to push
1422:		 * this sequence again later.
1423:		 */
1424:		if (test_bit(XLOG_CIL_EMPTY, &cil->xc_flags)) {
1425:			cil->xc_push_seq = 0;
1426:			spin_unlock(&cil->xc_push_lock);
1427:			goto out_skip;
1428:		}
1429:	
1430:	
1431:		/* check for a previously pushed sequence */
1432:		if (push_seq < ctx->sequence) {
1433:			spin_unlock(&cil->xc_push_lock);
1434:			goto out_skip;
1435:		}
1436:	
1437:		/*
1438:		 * We are now going to push this context, so add it to the committing
1439:		 * list before we do anything else. This ensures that anyone waiting on
1440:		 * this push can easily detect the difference between a "push in
1441:		 * progress" and "CIL is empty, nothing to do".
1442:		 *
1443:		 * IOWs, a wait loop can now check for:
1444:		 *	the current sequence not being found on the committing list;
1445:		 *	an empty CIL; and
1446:		 *	an unchanged sequence number
1447:		 * to detect a push that had nothing to do and therefore does not need
1448:		 * waiting on. If the CIL is not empty, we get put on the committing
1449:		 * list before emptying the CIL and bumping the sequence number. Hence
1450:		 * an empty CIL and an unchanged sequence number means we jumped out
1451:		 * above after doing nothing.
1452:		 *
1453:		 * Hence the waiter will either find the commit sequence on the
1454:		 * committing list or the sequence number will be unchanged and the CIL
1455:		 * still dirty. In that latter case, the push has not yet started, and
1456:		 * so the waiter will have to continue trying to check the CIL
1457:		 * committing list until it is found. In extreme cases of delay, the
1458:		 * sequence may fully commit between the attempts the wait makes to wait
1459:		 * on the commit sequence.
1460:		 */
1461:		list_add(&ctx->committing, &cil->xc_committing);
1462:		spin_unlock(&cil->xc_push_lock);
1463:	
1464:		xlog_cil_build_lv_chain(ctx, &whiteouts, &num_iovecs, &num_bytes);
1465:	
1466:		/*
1467:		 * Switch the contexts so we can drop the context lock and move out
1468:		 * of a shared context. We can't just go straight to the commit record,
1469:		 * though - we need to synchronise with previous and future commits so
1470:		 * that the commit records are correctly ordered in the log to ensure
1471:		 * that we process items during log IO completion in the correct order.
1472:		 *
1473:		 * For example, if we get an EFI in one checkpoint and the EFD in the
1474:		 * next (e.g. due to log forces), we do not want the checkpoint with
1475:		 * the EFD to be committed before the checkpoint with the EFI.  Hence
1476:		 * we must strictly order the commit records of the checkpoints so
1477:		 * that: a) the checkpoint callbacks are attached to the iclogs in the
1478:		 * correct order; and b) the checkpoints are replayed in correct order
1479:		 * in log recovery.
1480:		 *
1481:		 * Hence we need to add this context to the committing context list so
1482:		 * that higher sequences will wait for us to write out a commit record
1483:		 * before they do.
1484:		 *
1485:		 * xfs_log_force_seq requires us to mirror the new sequence into the cil
1486:		 * structure atomically with the addition of this sequence to the
1487:		 * committing list. This also ensures that we can do unlocked checks
1488:		 * against the current sequence in log forces without risking
1489:		 * deferencing a freed context pointer.
1490:		 */
1491:		spin_lock(&cil->xc_push_lock);
1492:		xlog_cil_ctx_switch(cil, new_ctx);
1493:		spin_unlock(&cil->xc_push_lock);
1494:		up_write(&cil->xc_ctx_lock);
1495:	
1496:		/*
1497:		 * Sort the log vector chain before we add the transaction headers.
1498:		 * This ensures we always have the transaction headers at the start
1499:		 * of the chain.
1500:		 */
1501:		list_sort(NULL, &ctx->lv_chain, xlog_cil_order_cmp);
1502:	
1503:		/*
1504:		 * Build a checkpoint transaction header and write it to the log to
1505:		 * begin the transaction. We need to account for the space used by the
1506:		 * transaction header here as it is not accounted for in xlog_write().
1507:		 * Add the lvhdr to the head of the lv chain we pass to xlog_write() so
1508:		 * it gets written into the iclog first.
1509:		 */
1510:		xlog_cil_build_trans_hdr(ctx, &thdr, &lvhdr, num_iovecs);
1511:		num_bytes += lvhdr.lv_bytes;
1512:		list_add(&lvhdr.lv_list, &ctx->lv_chain);
1513:	
1514:		/*
1515:		 * Take the lvhdr back off the lv_chain immediately after calling
1516:		 * xlog_cil_write_chain() as it should not be passed to log IO
1517:		 * completion.
1518:		 */
1519:		error = xlog_cil_write_chain(ctx, num_bytes);
1520:		list_del(&lvhdr.lv_list);
1521:		if (error)
1522:			goto out_abort_free_ticket;
1523:	
1524:		error = xlog_cil_write_commit_record(ctx);
1525:		if (error)
1526:			goto out_abort_free_ticket;
1527:	
1528:		/*
1529:		 * Grab the ticket from the ctx so we can ungrant it after releasing the
1530:		 * commit_iclog. The ctx may be freed by the time we return from
1531:		 * releasing the commit_iclog (i.e. checkpoint has been completed and
1532:		 * callback run) so we can't reference the ctx after the call to
1533:		 * xlog_state_release_iclog().
1534:		 */
1535:		ticket = ctx->ticket;
1536:	
1537:		/*
1538:		 * If the checkpoint spans multiple iclogs, wait for all previous iclogs
1539:		 * to complete before we submit the commit_iclog. We can't use state
1540:		 * checks for this - ACTIVE can be either a past completed iclog or a
1541:		 * future iclog being filled, while WANT_SYNC through SYNC_DONE can be a
1542:		 * past or future iclog awaiting IO or ordered IO completion to be run.
1543:		 * In the latter case, if it's a future iclog and we wait on it, the we
1544:		 * will hang because it won't get processed through to ic_force_wait
1545:		 * wakeup until this commit_iclog is written to disk.  Hence we use the
1546:		 * iclog header lsn and compare it to the commit lsn to determine if we
1547:		 * need to wait on iclogs or not.
1548:		 */
1549:		spin_lock(&log->l_icloglock);
1550:		if (ctx->start_lsn != ctx->commit_lsn) {
1551:			xfs_lsn_t	plsn = be64_to_cpu(
1552:				ctx->commit_iclog->ic_prev->ic_header->h_lsn);
1553:	
1554:			if (plsn && XFS_LSN_CMP(plsn, ctx->commit_lsn) < 0) {
1555:				/*
1556:				 * Waiting on ic_force_wait orders the completion of
1557:				 * iclogs older than ic_prev. Hence we only need to wait
1558:				 * on the most recent older iclog here.
1559:				 */
1560:				xlog_wait_on_iclog(log, ctx->commit_iclog->ic_prev);
1561:				spin_lock(&log->l_icloglock);
1562:			}
1563:	
1564:			/*
1565:			 * We need to issue a pre-flush so that the ordering for this
1566:			 * checkpoint is correctly preserved down to stable storage.
1567:			 */
1568:			ctx->commit_iclog->ic_flags |= XLOG_ICL_NEED_FLUSH;
1569:		}
1570:	
1571:		/*
1572:		 * The commit iclog must be written to stable storage to guarantee
1573:		 * journal IO vs metadata writeback IO is correctly ordered on stable
1574:		 * storage.
1575:		 *
1576:		 * If the push caller needs the commit to be immediately stable and the
1577:		 * commit_iclog is not yet marked as XLOG_STATE_WANT_SYNC to indicate it
1578:		 * will be written when released, switch it's state to WANT_SYNC right
1579:		 * now.
1580:		 */
1581:		ctx->commit_iclog->ic_flags |= XLOG_ICL_NEED_FUA;
1582:		if (push_commit_stable &&
1583:		    ctx->commit_iclog->ic_state == XLOG_STATE_ACTIVE)
1584:			xlog_state_switch_iclogs(log, ctx->commit_iclog, 0);
1585:		ticket = ctx->ticket;
1586:		xlog_state_release_iclog(log, ctx->commit_iclog, ticket);
1587:	
1588:		/* Not safe to reference ctx now! */
1589:	
1590:		spin_unlock(&log->l_icloglock);
1591:		xlog_cil_cleanup_whiteouts(&whiteouts);
1592:		xfs_log_ticket_ungrant(log, ticket);
1593:		memalloc_nofs_restore(nofs_flags);
1594:		return;
1595:	
1596:	out_skip:
1597:		up_write(&cil->xc_ctx_lock);
1598:		xfs_log_ticket_put(new_ctx->ticket);
1599:		kfree(new_ctx);
1600:		memalloc_nofs_restore(nofs_flags);
1601:		return;
1602:	
1603:	out_abort_free_ticket:
1604:		ASSERT(xlog_is_shutdown(log));
1605:		xlog_cil_cleanup_whiteouts(&whiteouts);
1606:		if (!ctx->commit_iclog) {
1607:			xfs_log_ticket_ungrant(log, ctx->ticket);
1608:			xlog_cil_committed(ctx);
1609:			memalloc_nofs_restore(nofs_flags);
1610:			return;
1611:		}
1612:		spin_lock(&log->l_icloglock);
1613:		ticket = ctx->ticket;
1614:		xlog_state_release_iclog(log, ctx->commit_iclog, ticket);
1615:		/* Not safe to reference ctx now! */
1616:		spin_unlock(&log->l_icloglock);
1617:		xfs_log_ticket_ungrant(log, ticket);
1618:		memalloc_nofs_restore(nofs_flags);
1619:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

64/2 2026/09/19 00:48 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 69748
							output: 42
							thoughts: 1435
						

Thoughts:
**Analyzing a Potential Use-After-Free in XFS CIL Handling**

Okay, let me break this down. My initial thought was that a crash within `xlog_cil_write_chain` or `xlog_cil_write_commit_record` would lead to `out_abort_free_ticket` and ultimately to `xlog_cil_ail_insert`. This path should unpin the items, preventing a subsequent crash in `xlog_cil_push_pcp_aggregate`. But then I realized that if the commit is *aborted*, the aggregate push will *already* have run, so no issue, the items are gone. So that eliminates a race in that case.

But wait a minute…what if the problem occurs when pushing a *later* context? If `xlog_cil_push_pcp_aggregate` crashes on an item added in the next context, that's added to the `cilpcp->log_items` list. If the filesystem shuts down *before* that next context is pushed, then `xfs_buf_item_relse` is called, which frees the item. However, the item *remains* on `cilpcp->log_items` in the *next* context!

The critical question here is whether the "next" context gets pushed even after shutdown. I need to check `xlog_cil_push_work` in a shutdown scenario. Surprisingly, `xlog_cil_push_work` *doesn't* check for `xlog_is_shutdown(log)` at the beginning. It just calls `xlog_cil_push_pcp_aggregate` directly, no matter what!

So, if a shutdown happens and a CIL push is scheduled, it's going to call `xlog_cil_push_pcp_aggregate` with a freed item on the list. That's the bug.

Here's the summary of the bug:

1.  A transaction writes to a buffer, commits it, and its `xfs_buf_log_item` is added to `cilpcp->log_items` of the *current* CIL context.
2.  The filesystem shuts down. This can be due to an error, an external event or forced shutdown.
3.  `xfs_buf_item_done` is called.
4.  Because the FS is shutdown, `xfs_trans_ail_delete` is called which handles removing it from the AIL, and returns.
5.  `xfs_buf_item_done` calls `xfs_buf_item_relse` which *frees* the `xfs_buf_log_item`.
6.  *Crucially*, the item is still on the `cilpcp->log_items` list for the *next* context because it hasn't been pushed yet.
7.  Later, the CIL context gets pushed (e.g., via background worker).
8.  `xlog_cil_push_work` calls `xlog_cil_push_pcp_aggregate`.
9.  `xlog_cil_push_pcp_aggregate` iterates through `cilpcp->log_items` and calls `list_splice_init`
10. `list_splice_init` accesses the `next` and `prev` pointers of the *freed* `xfs_buf_log_item`, triggering a KASAN use-after-free!

Is this exploitable? Absolutely. The UAF is in `__list_splice`, specifically:

```c
	first->prev = prev;
	prev->next = first;

	last->next = next;
	next->prev = last;
```

Here, `first` and `last` are derived from the freed item's `li_cil` list head. If an attacker can control the contents of this freed item (e.g., via reallocating the memory with attacker-controlled data), they can control `first` and `last`. The write `first->prev = prev` is an *arbitrary write* primitive! The attacker can write the address of `prev` (which is a kernel address) to an attacker-controlled address! This can corrupt linked list data structures or overwrite critical function pointers. This is a classic list-corruption primitive that can be leveraged for privilege escalation.

Can an unprivileged user trigger this? It requires a filesystem shutdown while an item is in the CIL. Shutdowns are not that uncommon - corrupted file system, I/O errors from USB, or similar. An unprivileged user could create a malicious file system and trigger an I/O error or exploit some other shutdown vector. The stack trace shows `xfs_ioc_setlabel


65/2 2026/09/19 00:49 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_ioctl.c Name:xfs_ioc_setlabel]

Results:
map[SourceCode:1038:	static int
1039:	xfs_ioc_setlabel(
1040:		struct file		*filp,
1041:		struct xfs_mount	*mp,
1042:		char			__user *newlabel)
1043:	{
1044:		struct xfs_sb		*sbp = &mp->m_sb;
1045:		char			label[XFSLABEL_MAX + 1];
1046:		size_t			len;
1047:		int			error;
1048:	
1049:		if (!capable(CAP_SYS_ADMIN))
1050:			return -EPERM;
1051:		/*
1052:		 * The generic ioctl allows up to FSLABEL_MAX chars, but XFS is much
1053:		 * smaller, at 12 bytes.  We copy one more to be sure we find the
1054:		 * (required) NULL character to test the incoming label length.
1055:		 * NB: The on disk label doesn't need to be null terminated.
1056:		 */
1057:		if (copy_from_user(label, newlabel, XFSLABEL_MAX + 1))
1058:			return -EFAULT;
1059:		len = strnlen(label, XFSLABEL_MAX + 1);
1060:		if (len > sizeof(sbp->sb_fname))
1061:			return -EINVAL;
1062:	
1063:		error = mnt_want_write_file(filp);
1064:		if (error)
1065:			return error;
1066:	
1067:		spin_lock(&mp->m_sb_lock);
1068:		memset(sbp->sb_fname, 0, sizeof(sbp->sb_fname));
1069:		memcpy(sbp->sb_fname, label, len);
1070:		spin_unlock(&mp->m_sb_lock);
1071:	
1072:		/*
1073:		 * Now we do several things to satisfy userspace.
1074:		 * In addition to normal logging of the primary superblock, we also
1075:		 * immediately write these changes to sector zero for the primary, then
1076:		 * update all backup supers (as xfs_db does for a label change), then
1077:		 * invalidate the block device page cache.  This is so that any prior
1078:		 * buffered reads from userspace (i.e. from blkid) are invalidated,
1079:		 * and userspace will see the newly-written label.
1080:		 */
1081:		error = xfs_sync_sb_buf(mp, true);
1082:		if (error)
1083:			goto out;
1084:		/*
1085:		 * growfs also updates backup supers so lock against that.
1086:		 */
1087:		mutex_lock(&mp->m_growlock);
1088:		error = xfs_update_secondary_sbs(mp);
1089:		mutex_unlock(&mp->m_growlock);
1090:	
1091:		invalidate_bdev(mp->m_ddev_targp->bt_bdev);
1092:		if (xfs_has_rtsb(mp) && mp->m_rtdev_targp)
1093:			invalidate_bdev(mp->m_rtdev_targp->bt_bdev);
1094:	
1095:	out:
1096:		mnt_drop_write_file(filp);
1097:		return error;
1098:	}
 SourceFile:fs/xfs/xfs_ioctl.c]

66/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 73275
							output: 40
							thoughts: 851
						

Thoughts:
**Analyzing the XFS Bug**

Okay, so `xfs_ioc_setlabel` needs `CAP_SYS_ADMIN`, and `capable()` checks the initial user namespace, meaning it's not accessible from a regular user namespace. It requires global root, that much is clear. However, the reported bug seems to be in `xlog_cil_push_pcp_aggregate` and `xfs_buf_item_relse`, which suggests that we don't *need* `xfs_ioc_setlabel` to trigger the problem. Any transaction that modifies a buffer, commits, and then the buffer is freed before the CIL is pushed could do it.

Now, normally, buffers shouldn't be freed while they're still in the CIL. `xfs_buf_item_relse` is called when a buffer is no longer needed. Usually, `xfs_buf_item_done` is called when I/O completes. I/O only gets submitted for a buffer if it's been written to disk, which is usually handled by the AIL after the buffer is pushed from the CIL and written to the iclog. So, the normal flow doesn't write a buffer to disk while it's in the CIL.

But then, `xfs_sync_sb_buf` writes it to disk while it's in the CIL because it calls `xfs_bwrite` *immediately* after `xfs_trans_commit`. And `xfs_sync_sb_buf` calls `xfs_trans_commit`, which calls `xfs_log_force_seq`. `xfs_log_force_seq` waits for the CIL to be pushed, right? So, normally the CIL *is* pushed before `xfs_bwrite` is called.

So then, why did the syzkaller report show a problem? Let's check the report again. The call stack shows: `xfs_buf_ioend`, `xfs_buf_iowait`, `xfs_bwrite`, `xfs_sync_sb_buf`, `xfs_ioc_setlabel`. `xfs_sync_sb_buf` calls `xfs_bwrite`, which then calls `xfs_buf_iowait`, which calls `xfs_buf_ioend`. `xfs_buf_iowait` *waits* for I/O completion, so `xfs_buf_ioend` must be called when the I/O *completes*. If `xfs_bwrite` is called, it submits the I/O and then waits. But, wait, if there's an I/O error on the buffer, could `xfs_bwrite` call `xfs_buf_ioend` directly? I need to check `xfs_bwrite`.



67/2 2026/09/19 00:49 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf.c Name:xfs_bwrite]

Results:
map[SourceCode:1226:	int
1227:	xfs_bwrite(
1228:		struct xfs_buf		*bp)
1229:	{
1230:		int			error;
1231:	
1232:		ASSERT(xfs_buf_islocked(bp));
1233:	
1234:		xfs_buf_set_flags(bp, XBF_WRITE);
1235:		xfs_buf_clear_flags(bp, XBF_ASYNC | XBF_READ | _XBF_DELWRI_Q |
1236:					XBF_DONE);
1237:	
1238:		xfs_buf_submit(bp);
1239:		error = xfs_buf_iowait(bp);
1240:		if (error)
1241:			xfs_force_shutdown(bp->b_mount, SHUTDOWN_META_IO_ERROR);
1242:		return error;
1243:	}
 SourceFile:fs/xfs/xfs_buf.c]

68/2 2026/09/19 00:49 llm expert-compressor
0m Model:
gemini-3.8-flash

Reply:
### 1. Approaches Tried and Results

- **Crash Analysis**:
  - The bug is a slab-use-after-free (UAF) write of size 8 at offset 104 (`0x68`) within an `xfs_buf_log_item` object (size 272 bytes, cache `xfs_buf_item`).
  - Stack trace for the crash:
    - Worker thread running `xlog_cil_push_work` -> `xlog_cil_push_pcp_aggregate` -> `list_splice_init(&cilpcp->log_items, &ctx->log_items)` -> `__list_splice` at `include/linux/list.h:580`.
  - Stack trace for allocation:
    - Task 5944 (ioctl call `xfs_ioc_setlabel` -> `xfs_sync_sb_buf` -> `xfs_log_sb` -> `__xfs_trans_getsb` -> `_xfs_trans_bjoin` -> `xfs_buf_item_init`).
  - Stack trace for free:
    - Task 5944 (same ioctl `xfs_ioc_setlabel` -> `xfs_sync_sb_buf` -> `xfs_bwrite` -> `xfs_buf_iowait` -> `xfs_buf_ioend` -> `xfs_buf_item_done` -> `xfs_buf_item_relse` -> `xfs_buf_item_free`).
  - Struct layout examination:
    - `struct xfs_buf_log_item` starts with `struct xfs_log_item bli_item` at offset 0.
    - Inside `struct xfs_log_item`, `li_cil` is at offset 832 bits = 104 bytes, size 128 bits (16 bytes, a `struct list_head`).
    - The write of 8 bytes at offset 104 is an update to `item->li_cil.next` or `item->li_cil.prev` during list manipulation in `__list_splice` or `list_splice_init`.

- **Tracing the Execution Flow**:
  - In `xfs_sync_sb_buf`:
    ```c
    error = xfs_trans_alloc(mp, &M_RES(mp)->tr_sb, 0, 0, 0, &tp);
    xfs_log_sb(tp);
    if (update_rtsb)
        xfs_log_rtsb(tp, xfs_trans_getsb(tp));
    xfs_trans_set_sync(tp);
    error = xfs_trans_commit(tp);
    xfs_buf_lock(mp->m_sb_bp);
    error = xfs_bwrite(mp->m_sb_bp);
    xfs_buf_unlock(mp->m_sb_bp);
    ```
  - In `xfs_trans_commit` -> `__xfs_trans_commit`:
    - Calls `xlog_cil_commit(log, tp, &commit_seq, regrant)`.
    - If `tp->t_flags & XFS_TRANS_SYNC`, calls `xfs_log_force_seq(mp, commit_seq, XFS_LOG_SYNC, NULL)`.
  - In `xlog_cil_commit`:
    - Takes `down_read(&cil->xc_ctx_lock)`.
    - Inserts items via `xlog_cil_insert_items(log, tp, released_space)`, where:
      ```c
      list_for_each_entry(lip, &tp->t_items, li_trans) {
          if (!test_bit(XFS_LI_DIRTY, &lip->li_flags))
              continue;
          lip->li_order_id = order;
          if (!list_empty(&lip->li_cil))
              continue;
          list_add_tail(&lip->li_cil, &cilpcp->log_items);
      }
      ```
    - Records `*commit_seq = cil->xc_ctx->sequence`.
    - Releases `xc_ctx_lock` via `xlog_cil_push_background(log)`.
  - In `xfs_log_force_seq`:
    - Calls `xlog_cil_force_seq(log, seq)`.
    - Calls `xlog_force_lsn(log, lsn, flags, log_flushed, ...)`.
  - In `xfs_sync_sb_buf` after commit:
    - Calls `xfs_bwrite(mp->m_sb_bp)`.
    - `xfs_bwrite` performs write I/O and calls `xfs_buf_iowait(bp)`.
    - Upon completion, `xfs_buf_ioend` calls `xfs_buf_item_done(bp)` -> `xfs_trans_ail_delete(&bip->bli_item, ...)` -> `xfs_buf_item_relse(bip)` -> `xfs_buf_item_free(bip)`.
    - Note that `xfs_buf_item_done` frees the `xfs_buf_log_item`!
  - Meanwhile, in the CIL background worker `xlog_cil_push_work`:
    - Calls `xlog_cil_push_pcp_aggregate(cil, ctx)`:
      ```c
      for_each_cpu(cpu, &ctx->cil_pcpmask) {
          cilpcp = per_cpu_ptr(cil->xc_pcp, cpu);
          ...
          if (!list_empty(&cilpcp->log_items))
              list_splice_init(&cilpcp->log_items, &ctx->log_items);
          ...
      }
      ```
    - The crash happens because `cilpcp->log_items` still contains `&bip->bli_item.li_cil`, but `bip` was already freed by `xfs_bwrite`!

---

### 2. Hypotheses and Active Lines of Investigation

- **Why was `bip` freed while still in `cilpcp->log_items`?**
  1. *Hypothesis A (Preemption / CPU mismatch / Race in CIL push vs force)*:
     - Did `xlog_cil_force_seq` actually wait for the CIL context to finish push before returning?
     - Look at `xlog_cil_force_seq`:
       ```c
       if (ctx->sequence != sequence)
           continue;
       commit_lsn = ctx->commit_lsn;
       ```
       If `ctx->commit_lsn` is non-zero, it gets `commit_lsn`. But wait! Does `xlog_cil_force_seq` wait for `xlog_cil_push_work` of *this* context, or could it see something already pushed or miss the current context if another push raced?
     - What if `xfs_sync_sb_buf` added the sb buffer to the CIL, but `mp->m_sb_bp` already had an older or concurrent write in flight, or `xfs_buf_item_done` was called on a buffer whose log item hadn't gone through AIL insertion yet?
     - Notice in `xfs_buf_item_done`:
       ```c
       xfs_trans_ail_delete(&bip->bli_item,
                    xlog_in_recovery(bip->bli_item.li_log) ?
                    0 : SHUTDOWN_CORRUPT_INCORE);
       xfs_buf_item_relse(bip);
       ```
       Wait! `xfs_trans_ail_delete` checks:
       ```c
       if (!test_bit(XFS_LI_IN_AIL, &lip->li_flags)) {
           spin_unlock(&ailp->ail_lock);
           if (shutdown_type && !xlog_is_shutdown(log)) {
               xfs_alert_tag(... "attempting to delete a log item that is not in the AIL");
               xlog_force_shutdown(log, shutdown_type);
           }
           return;
       }
       ```
       If it wasn't in the AIL, it forces shutdown and then immediately proceeds to `xfs_buf_item_relse(bip)` which frees `bip`!
       Why would `bip` not be in the AIL? Because `xfs_bwrite` was called before the CIL checkpoint committed items to the AIL! Or `xfs_bwrite` completes before `xlog_cil_ail_insert` ran!
     - Wait, in `xfs_sync_sb_buf`, why is `xfs_bwrite(mp->m_sb_bp)` called directly right after `xfs_trans_commit(tp)`?
       Let's check git history of `xfs_sync_sb_buf` or commits around `xfs_sync_sb_buf` and `xfs_bwrite`.
  2. *Hypothesis B (Superblock buffer log item lifecycle)*:
     - When `xfs_log_sb` logs the superblock, it attaches an `xfs_buf_log_item` to `mp->m_sb_bp`.
     - `xfs_sync_sb_buf` logs the sb and then immediately calls `xfs_bwrite(mp->m_sb_bp)`.
     - But `mp->m_sb_bp->b_log_item` is still attached!
     - When `xfs_bwrite` finishes, `xfs_buf_ioend` is invoked.
     - Because `bp->b_log_item` is non-NULL (`if (bp->b_log_item) xfs_buf_item_done(bp);`), it calls `xfs_buf_item_done(bp)`!
     - And `xfs_buf_item_done` unconditionally calls `xfs_buf_item_relse(bip)`, which sets `bp->b_log_item = NULL` and frees `bip`!
     - BUT `bip` is STILL in the CIL (`cilpcp->log_items` or `ctx->log_items`) waiting for `xlog_cil_push_work` to format and write it to disk!
     - When `xlog_cil_push_work` subsequently runs, it touches `bip->bli_item.li_cil` in `xlog_cil_push_pcp_aggregate`, resulting in UAF!

- **Key Question to Verify via Git History**:
  - Is `xfs_sync_sb_buf` or `xfs_ioc_setlabel` new or recently modified?
  - Search git log for `xfs_sync_sb_buf`, `xfs_ioc_setlabel`, or `xfs_buf_item_done` / `xfs_buf_item_relse`.
  - Is there a commit fixing this UAF?

---

### 3. Critical Files, Functions, and Layouts

- **Files & Functions**:
  - `fs/xfs/libxfs/xfs_sb.c`: `xfs_sync_sb_buf`
    - Commits transaction with `xfs_trans_set_sync(tp); xfs_trans_commit(tp);`
    - Immediately acquires lock and calls `xfs_bwrite(mp->m_sb_bp)`.
  - `fs/xfs/xfs_buf.c`: `xfs_buf_ioend`
    - Line 1166: `if (bp->b_log_item) xfs_buf_item_done(bp);`
  - `fs/xfs/xfs_buf_item.c`:
    - `xfs_buf_item_done`: calls `xfs_trans_ail_delete` and `xfs_buf_item_relse(bip)`.
    - `xfs_buf_item_relse`: clears `bp->b_log_item = NULL;` and frees `bip` via `xfs_buf_item_free(bip)`.
  - `fs/xfs/xfs_log_cil.c`:
    - `xlog_cil_push_pcp_aggregate`: splices `cilpcp->log_items` into `ctx->log_items`.
    - `xlog_cil_push_work`: runs in workqueue `xfs-cil/...`.
    - `xlog_cil_insert_items`: adds `lip->li_cil` into `cilpcp->log_items`.
  - `fs/xfs/xfs_ioctl.c`:
    - Line 1081: `xfs_ioc_setlabel` calls `xfs_sync_sb_buf`.
    - Line 1238: `xfs_file_ioctl`.

- **Struct Offsets**:
  - `struct xfs_buf_log_item`:
    - `bli_item`: offset 0, size 1216 bits (152 bytes)
  - `struct xfs_log_item`:
    - `li_cil`: offset 832 bits (104 bytes = 0x68), size 128 bits (16 bytes, `struct list_head`)
  - Buggy address: offset 104 in freed slab object of `xfs_buf_item` cache (size 272 bytes).

---

### 4. Next Steps & Instructions

- Use `git-log` or grep git history to inspect recent commits touching `xfs_sync_sb_buf` or `xfs_ioc_setlabel` or `xfs_buf_item_done`.
- Check permissions for `xfs_ioc_setlabel` (e.g. `CAP_SYS_ADMIN`? `capable()` vs `ns_capable()`).
  - Does `xfs_ioc_setlabel` require `capable(CAP_SYS_ADMIN)` or can an unprivileged user or user in a user namespace call `XFS_IOC_SETLABEL`?
  - Does mounting a malicious filesystem trigger it?
  - Can unprivileged processes reach `xfs_ioc_setlabel` or is it restricted?
  - Is it exploitable (UAF write of list pointers)? Denial of Service?
- Avoid repetitive layout checks; proceed directly to permission analysis and git commit context.

Tokens:
							input: 50070
							output: 3330
							thoughts: 0
						

69/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 24909
							output: 47
							thoughts: 0
						

70/2 2026/09/19 00:49 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/libxfs/xfs_sb.c Name:xfs_sync_sb_buf]

Results:
map[SourceCode:1463:	/*
1464:	 * Same behavior as xfs_sync_sb, except that it is always synchronous and it
1465:	 * also writes the superblock buffer to disk sector 0 immediately.
1466:	 */
1467:	int
1468:	xfs_sync_sb_buf(
1469:		struct xfs_mount	*mp,
1470:		bool			update_rtsb)
1471:	{
1472:		struct xfs_trans	*tp;
1473:		int			error;
1474:	
1475:		error = xfs_trans_alloc(mp, &M_RES(mp)->tr_sb, 0, 0, 0, &tp);
1476:		if (error)
1477:			return error;
1478:	
1479:		xfs_log_sb(tp);
1480:		if (update_rtsb)
1481:			xfs_log_rtsb(tp, xfs_trans_getsb(tp));
1482:		xfs_trans_set_sync(tp);
1483:		error = xfs_trans_commit(tp);
1484:		if (error)
1485:			return error;
1486:	
1487:		/* Re-acquire and write the sb and rtsb to disk. */
1488:		xfs_buf_lock(mp->m_sb_bp);
1489:		error = xfs_bwrite(mp->m_sb_bp);
1490:		xfs_buf_unlock(mp->m_sb_bp);
1491:		if (error)
1492:			return error;
1493:	
1494:		if (update_rtsb && mp->m_rtsb_bp) {
1495:			xfs_buf_lock(mp->m_rtsb_bp);
1496:			error = xfs_bwrite(mp->m_rtsb_bp);
1497:			xfs_buf_unlock(mp->m_rtsb_bp);
1498:		}
1499:	
1500:		return error;
1501:	}
 SourceFile:fs/xfs/libxfs/xfs_sb.c]

71/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 25595
							output: 41
							thoughts: 0
						

72/2 2026/09/19 00:49 tool git-log
0m Args:
map[CodeRegexp:xfs_sync_sb_buf Count:10 PathPrefix:fs/xfs/]

Results:
map[Output:238650ef6c7c Merge tag 'powerpc-7.3-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
]

73/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 25696
							output: 48
							thoughts: 0
						

74/2 2026/09/19 00:49 tool git-log
0m Args:
map[CodeRegexp:xfs_sync_sb_buf Count:10 PathPrefix:fs/xfs/ Since:3 years]

Results:
map[Output:238650ef6c7c Merge tag 'powerpc-7.3-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
]

75/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 25804
							output: 48
							thoughts: 0
						

76/2 2026/09/19 00:49 tool git-log
0m Args:
map[CodeRegexp:xfs_sync_sb_buf Count:10 PathPrefix:fs/xfs/ Since:5 years]

Results:
map[Output:238650ef6c7c Merge tag 'powerpc-7.3-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
]

77/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 25912
							output: 49
							thoughts: 0
						

78/2 2026/09/19 00:49 tool git-log
0m Args:
map[CodeRegexp:xfs_sync_sb_buf Count:10 PathPrefix:fs/xfs/ Since:10 years]

Results:
map[Output:238650ef6c7c Merge tag 'powerpc-7.3-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
]

79/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 26021
							output: 49
							thoughts: 0
						

80/2 2026/09/19 00:49 tool git-log
0m Args:
map[CodeRegexp:xfs_sync_sb_buf Count:10 PathPrefix:fs/xfs/ Since:20 years]

Results:
map[Output:238650ef6c7c Merge tag 'powerpc-7.3-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
]

81/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 26130
							output: 50
							thoughts: 0
						

82/2 2026/09/19 00:49 tool git-log
0m Args:
map[CodeRegexp:xfs_sync_sb_buf Count:10 PathPrefix:fs/xfs/ Since:100 years]

Results:
map[Output:]

83/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 26193
							output: 50
							thoughts: 56
						

Thoughts:
Okay, here's my take on those thoughts, framed as my own mental process:

**Troubleshooting a Git Log Issue**

Alright, that's strange. `git log` is either coming back empty, or I'm seeing something really weird like a merge commit I don't expect. Time to narrow this down and make sure I'm querying the log correctly. Given the context, I think I'll try filtering the `git log` output more precisely. I need to be more specific with my search terms and target the right code. Let's see... I'll use the `SymbolName` parameter with the function `xfs_sync_sb_buf`, and pair that with the `SourcePath` parameter to target the correct file, which I'm pretty sure is `fs/xfs/libxfs/xfs_sb.c`. That should give me a much more focused and helpful set of results. Hopefully this will reveal the history I'm actually interested in.



84/2 2026/09/19 00:49 tool git-log
0m Args:
map[Count:10 SourcePath:fs/xfs/libxfs/xfs_sb.c SymbolName:xfs_sync_sb_buf]

Results:
map[Output:238650ef6c7c Merge tag 'powerpc-7.3-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux
]

85/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 26570
							output: 45
							thoughts: 60
						

Thoughts:
Okay, here's my take on those thoughts, tailored for an expert audience:

**Debugging a Stubborn Git History**

Alright, hang on a second... `git log` is only showing the merge commit? That's not what I expected at all. I need to dig deeper. Let's see... the easiest way to get an overview of *what's* in that merge is to use `git show HEAD` right away. That will give me a snapshot of the changes introduced at the current head, and should illuminate the content.

If that doesn't reveal enough context, I'll switch gears and try a more granular approach. Given that I suspect a problem in the XFS superblock handling, I'll try a `git blame` on `fs/xfs/libxfs/xfs_sb.c`. That should show me the lines of code and the specific commits that last touched them, highlighting the changes and the timeline of edits around the code in question, allowing me to isolate the root cause.



86/2 2026/09/19 00:49 tool git-blame
0m Args:
map[End:1501 File:fs/xfs/libxfs/xfs_sb.c Start:1463]

Results:
map[Output:^238650ef6c7c 1463) /*
^238650ef6c7c 1464)  * Same behavior as xfs_sync_sb, except that it is always synchronous and it
^238650ef6c7c 1465)  * also writes the superblock buffer to disk sector 0 immediately.
^238650ef6c7c 1466)  */
^238650ef6c7c 1467) int
^238650ef6c7c 1468) xfs_sync_sb_buf(
^238650ef6c7c 1469) 	struct xfs_mount	*mp,
^238650ef6c7c 1470) 	bool			update_rtsb)
^238650ef6c7c 1471) {
^238650ef6c7c 1472) 	struct xfs_trans	*tp;
^238650ef6c7c 1473) 	int			error;
^238650ef6c7c 1474) 
^238650ef6c7c 1475) 	error = xfs_trans_alloc(mp, &M_RES(mp)->tr_sb, 0, 0, 0, &tp);
^238650ef6c7c 1476) 	if (error)
^238650ef6c7c 1477) 		return error;
^238650ef6c7c 1478) 
^238650ef6c7c 1479) 	xfs_log_sb(tp);
^238650ef6c7c 1480) 	if (update_rtsb)
^238650ef6c7c 1481) 		xfs_log_rtsb(tp, xfs_trans_getsb(tp));
^238650ef6c7c 1482) 	xfs_trans_set_sync(tp);
^238650ef6c7c 1483) 	error = xfs_trans_commit(tp);
^238650ef6c7c 1484) 	if (error)
^238650ef6c7c 1485) 		return error;
^238650ef6c7c 1486) 
^238650ef6c7c 1487) 	/* Re-acquire and write the sb and rtsb to disk. */
^238650ef6c7c 1488) 	xfs_buf_lock(mp->m_sb_bp);
^238650ef6c7c 1489) 	error = xfs_bwrite(mp->m_sb_bp);
^238650ef6c7c 1490) 	xfs_buf_unlock(mp->m_sb_bp);
^238650ef6c7c 1491) 	if (error)
^238650ef6c7c 1492) 		return error;
^238650ef6c7c 1493) 
^238650ef6c7c 1494) 	if (update_rtsb && mp->m_rtsb_bp) {
^238650ef6c7c 1495) 		xfs_buf_lock(mp->m_rtsb_bp);
^238650ef6c7c 1496) 		error = xfs_bwrite(mp->m_rtsb_bp);
^238650ef6c7c 1497) 		xfs_buf_unlock(mp->m_rtsb_bp);
^238650ef6c7c 1498) 	}
^238650ef6c7c 1499) 
^238650ef6c7c 1500) 	return error;
^238650ef6c7c 1501) }
]

87/2 2026/09/19 00:49 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 28034
							output: 65
							thoughts: 226
						

Thoughts:
**Analyzing a Potential Security Vulnerability**

Okay, so this commit `^238650ef6c7c`... that means it's pretty ancient, probably predates the shallow clone I'm working with. The `^` signifies the boundary commit, so this is critical context. Right, I need to look into permissions, specifically for `xfs_ioc_setlabel`. Let me see...

```c
	if (!capable(CAP_SYS_ADMIN))
		return -EPERM;
```

Ah, it requires `CAP_SYS_ADMIN`. That's important. And `capable()` checks against `init_user_ns`, right? I need to make sure I have that straight. Yes, it confirms the check is within the initial user namespace. So, it's not accessible to unprivileged processes or user namespaces.

Okay, so I'm thinking... could a malicious filesystem, mounted, somehow trigger this vulnerability? That's the angle I need to investigate. I need to see if `xfs_sync_sb_buf` is called anywhere else. It is important to know if this functionality is used in a context that may allow escalation of privileges.



88/2 2026/09/19 00:50 tool codesearch-find-references
0m Args:
map[ContextFile:fs/xfs/libxfs/xfs_sb.c IncludeSnippetLines:0 Name:xfs_sync_sb_buf SourceTreePrefix:fs/xfs/]

Results:
map[References:[map[ReferenceKind:calls ReferencingEntityKind:function ReferencingEntityName:xfs_ioc_setlabel SourceFile:fs/xfs/xfs_ioctl.c SourceLine:1081]] TruncatedOutput:false]

89/2 2026/09/19 00:50 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 28656
							output: 58
							thoughts: 87
						

Thoughts:
Here's my thought process, as an expert in this area:

**Analyzing the Call Path of a Data Modification Function**

Okay, so I'm looking at something that appears to be triggered exclusively through `xfs_ioc_setlabel`. But is that *really* the only path? I need to be absolutely certain. The immediate concern is whether this is the sole entry point, so I'm going to dig a little deeper.

My first thought is, is `xfs_bwrite` on a buffer that has a log item common? Is it a usual occurrence? If it is, then there is more to explore, as it would mean that whatever functionality is being called here isn't triggered just by `xfs_ioc_setlabel`.

Right, let's confirm my suspicions. Let me see where `xfs_bwrite` is called from. I'll need to trace the references to understand the full scope of how this function is used. The goal here is to determine if this piece of code is more broadly applicable, or if it is indeed very specific to this ioctl call. I'll check the source for every place it's referenced, to get a clear picture.



90/2 2026/09/19 00:50 tool codesearch-find-references
0m Args:
map[ContextFile:fs/xfs/xfs_buf.c IncludeSnippetLines:0 Name:xfs_bwrite SourceTreePrefix:fs/xfs/]

Results:
map[References:[map[ReferenceKind:calls ReferencingEntityKind:function ReferencingEntityName:xfs_add_incompat_log_feature SourceFile:fs/xfs/xfs_mount.c SourceLine:1608] map[ReferenceKind:calls ReferencingEntityKind:function ReferencingEntityName:xfs_attr_rmtval_set_value SourceFile:fs/xfs/libxfs/xfs_attr_remote.c SourceLine:546] map[ReferenceKind:calls ReferencingEntityKind:function ReferencingEntityName:xfs_growfs_rt_init_rtsb SourceFile:fs/xfs/xfs_rtalloc.c SourceLine:852] map[ReferenceKind:calls ReferencingEntityKind:function ReferencingEntityName:xfs_qm_dqpurge SourceFile:fs/xfs/xfs_qm.c SourceLine:170] map[ReferenceKind:calls ReferencingEntityKind:function ReferencingEntityName:xfs_sync_sb_buf SourceFile:fs/xfs/libxfs/xfs_sb.c SourceLine:1489] map[ReferenceKind:calls ReferencingEntityKind:function ReferencingEntityName:xfs_sync_sb_buf SourceFile:fs/xfs/libxfs/xfs_sb.c SourceLine:1496] map[ReferenceKind:calls ReferencingEntityKind:function ReferencingEntityName:xlog_recover_buf_commit_pass2 SourceFile:fs/xfs/xfs_buf_item_recover.c SourceLine:1162]] TruncatedOutput:false]

91/2 2026/09/19 00:50 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 29503
							output: 46
							thoughts: 17
						

Thoughts:
Okay, let's dive into this. Here's how I'd approach summarizing the "thoughts" you've described, from my perspective as an expert:

**Investigating `xfs_add_incompat_log_feature`**

Alright, so the focus is on `xfs_add_incompat_log_feature`. Just the name itself hints at some interesting functionality related to XFS journaling. My initial thought is to quickly mentally catalogue what I already know about it, what the implications might be for compatibility, and what corner cases I should immediately consider. I'll automatically start by thinking about how this feature might influence existing XFS filesystems, particularly those on older kernels or with different mount options. A "log_feature" addition usually means some new on-disk structure, which raises questions about versioning and potential upgrade/downgrade scenarios. I need to understand if this is a feature that's generally safe to add or if it requires careful consideration before activating. Is it related to the online journaling work? Could it have performance implications? I'll probably have a mental checklist forming:

*   What's the *incompat* part about? Is it truly *incompatible*, or are we dealing with a "feature flag" kind of incompatibility (i.e., gracefully handled by older kernels)?
*   How is it triggered? Is it enabled at filesystem creation, mount time, or through some utility?
*   What does the log contain/change? Is it purely metadata, or potentially file data as well?
*   Any implications for `xfsdump` and `xfsrestore`? This is *always* a consideration.
*   Does it relate to anything like checksums, transaction logging, or specific durability guarantees?

Essentially, I'm thinking, this is a call for an investigation into a potentially new feature of XFS. My mind immediately begins to generate questions based on my years of expertise. I'm going to quickly check the relevant XFS code and documentation for a better understanding, beginning with the source itself.



92/2 2026/09/19 00:50 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_mount.c Name:xfs_add_incompat_log_feature]

Results:
map[SourceCode:1559:	/*
1560:	 * Enable a log incompat feature flag in the primary superblock.  The caller
1561:	 * cannot have any other transactions in progress.
1562:	 */
1563:	int
1564:	xfs_add_incompat_log_feature(
1565:		struct xfs_mount	*mp,
1566:		uint32_t		feature)
1567:	{
1568:		struct xfs_dsb		*dsb;
1569:		int			error;
1570:	
1571:		ASSERT(hweight32(feature) == 1);
1572:		ASSERT(!(feature & XFS_SB_FEAT_INCOMPAT_LOG_UNKNOWN));
1573:	
1574:		/*
1575:		 * Force the log to disk and kick the background AIL thread to reduce
1576:		 * the chances that the bwrite will stall waiting for the AIL to unpin
1577:		 * the primary superblock buffer.  This isn't a data integrity
1578:		 * operation, so we don't need a synchronous push.
1579:		 */
1580:		error = xfs_log_force(mp, XFS_LOG_SYNC);
1581:		if (error)
1582:			return error;
1583:		xfs_ail_push_all(mp->m_ail);
1584:	
1585:		/*
1586:		 * Lock the primary superblock buffer to serialize all callers that
1587:		 * are trying to set feature bits.
1588:		 */
1589:		xfs_buf_lock(mp->m_sb_bp);
1590:		xfs_buf_hold(mp->m_sb_bp);
1591:	
1592:		if (xfs_is_shutdown(mp)) {
1593:			error = -EIO;
1594:			goto rele;
1595:		}
1596:	
1597:		if (xfs_sb_has_incompat_log_feature(&mp->m_sb, feature))
1598:			goto rele;
1599:	
1600:		/*
1601:		 * Write the primary superblock to disk immediately, because we need
1602:		 * the log_incompat bit to be set in the primary super now to protect
1603:		 * the log items that we're going to commit later.
1604:		 */
1605:		dsb = mp->m_sb_bp->b_addr;
1606:		xfs_sb_to_disk(dsb, &mp->m_sb);
1607:		dsb->sb_features_log_incompat |= cpu_to_be32(feature);
1608:		error = xfs_bwrite(mp->m_sb_bp);
1609:		if (error)
1610:			goto shutdown;
1611:	
1612:		/*
1613:		 * Add the feature bits to the incore superblock before we unlock the
1614:		 * buffer.
1615:		 */
1616:		xfs_sb_add_incompat_log_features(&mp->m_sb, feature);
1617:		xfs_buf_relse(mp->m_sb_bp);
1618:	
1619:		/* Log the superblock to disk. */
1620:		return xfs_sync_sb(mp, false);
1621:	shutdown:
1622:		xfs_force_shutdown(mp, SHUTDOWN_META_IO_ERROR);
1623:	rele:
1624:		xfs_buf_relse(mp->m_sb_bp);
1625:		return error;
1626:	}
 SourceFile:fs/xfs/xfs_mount.c]

93/2 2026/09/19 00:50 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 31051
							output: 45
							thoughts: 354
						

Thoughts:
**Analyzing a Potential XFS Superblock Update Issue**

Okay, so I'm looking at this `xfs_add_incompat_log_feature` function and immediately I see it calling `xfs_log_force` and `xfs_ail_push_all`. Standard, gets the log synced and the AIL flushed. Then it does an `xfs_bwrite` on the superblock buffer, `mp->m_sb_bp`. Wait a minute... if that superblock buffer *has* a log item attached, that `xfs_bwrite` is going to trigger `xfs_buf_ioend`, which goes to `xfs_buf_item_done`, and then `xfs_buf_item_relse`.

Hmm, can `mp->m_sb_bp` actually have a log item attached? Of course it can! It's the primary superblock buffer, so it *often* has log items associated with it. This is where it gets interesting...

`xfs_buf_item_done` contains the following:

```c
	xfs_trans_ail_delete(&bip->bli_item,
			     xlog_in_recovery(bip->bli_item.li_log) ?
			     0 : SHUTDOWN_CORRUPT_INCORE);
	xfs_buf_item_relse(bip);
```

Okay, so `xfs_trans_ail_delete` is called. If the item is in the AIL, it's removed. But what if the item is in the CIL? This is the core issue! If it's in the CIL, `xfs_trans_ail_delete` will determine that it's NOT in the AIL, so it likely won't do anything to clean up the CIL item, potentially leading to inconsistencies. I need to dig into `xfs_trans_ail_delete` and see how it handles items that are only in the CIL.



94/2 2026/09/19 00:50 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_trans_ail_delete]

Results:
map[SourceCode: 918:	void
 919:	xfs_trans_ail_delete(
 920:		struct xfs_log_item	*lip,
 921:		int			shutdown_type)
 922:	{
 923:		struct xfs_ail		*ailp = lip->li_ailp;
 924:		struct xlog		*log = ailp->ail_log;
 925:		xfs_lsn_t		tail_lsn;
 926:	
 927:		spin_lock(&ailp->ail_lock);
 928:		if (!test_bit(XFS_LI_IN_AIL, &lip->li_flags)) {
 929:			spin_unlock(&ailp->ail_lock);
 930:			if (shutdown_type && !xlog_is_shutdown(log)) {
 931:				xfs_alert_tag(log->l_mp, XFS_PTAG_AILDELETE,
 932:		"%s: attempting to delete a log item that is not in the AIL",
 933:						__func__);
 934:				xlog_force_shutdown(log, shutdown_type);
 935:			}
 936:			return;
 937:		}
 938:	
 939:		clear_bit(XFS_LI_FAILED, &lip->li_flags);
 940:		tail_lsn = xfs_ail_delete_one(ailp, lip);
 941:		xfs_ail_update_finish(ailp, tail_lsn);	/* drops the AIL lock */
 942:	}
 SourceFile:fs/xfs/xfs_trans_ail.c]

95/2 2026/09/19 00:50 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 32350
							output: 43
							thoughts: 992
						

Thoughts:
**Analyzing a Potential XFS Log Corruption Scenario**

Okay, so I'm looking at this code path, and it looks like if an item isn't in the AIL, and the `shutdown_type` is non-zero (specifically, `SHUTDOWN_CORRUPT_INCORE`), a forced shutdown is triggered. I need to clarify: did the bug report explicitly mention a shutdown? The report doesn't have a shutdown message, but it's still possible it happened. 

Now, let's trace this through. In `xfs_sync_sb_buf`, the transaction is committed using `xfs_trans_commit`, and critically, this is a synchronous commit. This means it calls `xfs_log_force_seq` with `XFS_LOG_SYNC`. `xfs_log_force_seq`, in turn, waits for the CIL to be pushed and the internal log (`iclog`) to be written to disk. The important thing here is when the CIL "pushes," items *should* be moved to the AIL. Hmm... but isn't `xlog_cil_push_work` the routine responsible for moving the CIL items to the AIL? No, that's not quite right. `xlog_cil_push_work` writes the CIL to the iclog. It's when the iclog I/O completes that `xlog_state_do_callback` gets called, which in turn leads to `xlog_cil_committed`, then `xlog_cil_ail_insert`, which *finally* inserts the items into the AIL! 

So, `xfs_log_force_seq` (with the sync flag) is essentially waiting for the iclog I/O to complete. By the time `xfs_trans_commit` returns, these items *should* be in the AIL. If they are in the AIL, then `xfs_trans_ail_delete` should successfully remove them. That will be followed by `xfs_buf_item_relse`, which should free the `xfs_buf_log_item`.

But here's the kicker: The bug report shows a *use-after-free* error in `xlog_cil_push_work` and related functions: `__list_splice`, `list_splice_init`, and `xlog_cil_push_pcp_aggregate`. This indicates that `xlog_cil_push_work` is accessing a freed `xfs_buf_log_item`. How can that be? How is `xlog_cil_push_work` still running *after* `xfs_trans_commit` has returned, and *still* finding the item in `cilpcp->log_items`?

Okay, let's step through the transaction commit more carefully. `xfs_trans_commit` actually calls `xlog_cil_commit`. `xlog_cil_commit` adds the item to `cilpcp->log_items` and then calls `xlog_cil_push_background(log)`. And then, if the commit is synchronous (which it is, because of the `XFS_TRANS_SYNC` flag), it calls `xfs_log_force_seq`. `xfs_log_force_seq` then waits for the CIL push to complete. But, could there be a concurrency issue here?

If `xlog_cil_push_work` is running concurrently, it will splice items from `cilpcp->log_items`. Wait a second, `xlog_cil_push_pcp_aggregate` splices `cilpcp->log_items` to `ctx->log_items`. If `xfs_trans_commit` returns, that means `xfs_log_force_seq` has finished. How can `xfs_log_force_seq` complete *before* `xlog_cil_push_work` even has a chance to splice `cilpcp->log_items`? I need to check `xfs_log_force_seq` more carefully.



96/2 2026/09/19 00:50 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log.c Name:xfs_log_force_seq]

Results:
map[SourceCode:2986:	/*
2987:	 * Force the log to a specific checkpoint sequence.
2988:	 *
2989:	 * First force the CIL so that all the required changes have been flushed to the
2990:	 * iclogs. If the CIL force completed it will return a commit LSN that indicates
2991:	 * the iclog that needs to be flushed to stable storage. If the caller needs
2992:	 * a synchronous log force, we will wait on the iclog with the LSN returned by
2993:	 * xlog_cil_force_seq() to be completed.
2994:	 */
2995:	int
2996:	xfs_log_force_seq(
2997:		struct xfs_mount	*mp,
2998:		xfs_csn_t		seq,
2999:		uint			flags,
3000:		int			*log_flushed)
3001:	{
3002:		struct xlog		*log = mp->m_log;
3003:		xfs_lsn_t		lsn;
3004:		int			ret;
3005:		ASSERT(seq != 0);
3006:	
3007:		XFS_STATS_INC(mp, xs_log_force);
3008:		trace_xfs_log_force(mp, seq, _RET_IP_);
3009:	
3010:		lsn = xlog_cil_force_seq(log, seq);
3011:		if (lsn == NULLCOMMITLSN)
3012:			return 0;
3013:	
3014:		ret = xlog_force_lsn(log, lsn, flags, log_flushed, false);
3015:		if (ret == -EAGAIN) {
3016:			XFS_STATS_INC(mp, xs_log_force_sleep);
3017:			ret = xlog_force_lsn(log, lsn, flags, log_flushed, true);
3018:		}
3019:		return ret;
3020:	}
 SourceFile:fs/xfs/xfs_log.c]

97/2 2026/09/19 00:50 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 34871
							output: 45
							thoughts: 14
						

Thoughts:
Okay, here's my attempt at summarizing that thought process, tailored for an expert audience:

**Checking `xlog_cil_force_seq`**

Alright, time to get to it. Let's dig in and take a look at that `xlog_cil_force_seq` variable. I need to understand its current state and how it's behaving. Specifically, I'm thinking about its implications for... well, whatever specific situation I'm currently dealing with. The specifics are key here; depending on the context of what I'm doing, this variable's effect could be subtle or catastrophic. The devil is always in the details with these parameters. Let's see what we can find. I’m expecting to uncover something specific that I can analyze. I need to ensure there are no surprises in the current environment.



98/2 2026/09/19 00:50 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_force_seq]

Results:
map[SourceCode:1898:	/*
1899:	 * Conditionally push the CIL based on the sequence passed in.
1900:	 *
1901:	 * We only need to push if we haven't already pushed the sequence number given.
1902:	 * Hence the only time we will trigger a push here is if the push sequence is
1903:	 * the same as the current context.
1904:	 *
1905:	 * We return the current commit lsn to allow the callers to determine if a
1906:	 * iclog flush is necessary following this call.
1907:	 */
1908:	xfs_lsn_t
1909:	xlog_cil_force_seq(
1910:		struct xlog	*log,
1911:		xfs_csn_t	sequence)
1912:	{
1913:		struct xfs_cil		*cil = log->l_cilp;
1914:		struct xfs_cil_ctx	*ctx;
1915:		xfs_lsn_t		commit_lsn = NULLCOMMITLSN;
1916:	
1917:		ASSERT(sequence <= cil->xc_current_sequence);
1918:	
1919:		if (!sequence)
1920:			sequence = cil->xc_current_sequence;
1921:		trace_xfs_log_force(log->l_mp, sequence, _RET_IP_);
1922:	
1923:		/*
1924:		 * check to see if we need to force out the current context.
1925:		 * xlog_cil_push() handles racing pushes for the same sequence,
1926:		 * so no need to deal with it here.
1927:		 */
1928:	restart:
1929:		xlog_cil_push_now(log, sequence, false);
1930:	
1931:		/*
1932:		 * See if we can find a previous sequence still committing.
1933:		 * We need to wait for all previous sequence commits to complete
1934:		 * before allowing the force of push_seq to go ahead. Hence block
1935:		 * on commits for those as well.
1936:		 */
1937:		spin_lock(&cil->xc_push_lock);
1938:		list_for_each_entry(ctx, &cil->xc_committing, committing) {
1939:			/*
1940:			 * Avoid getting stuck in this loop because we were woken by the
1941:			 * shutdown, but then went back to sleep once already in the
1942:			 * shutdown state.
1943:			 */
1944:			if (xlog_is_shutdown(log))
1945:				goto out_shutdown;
1946:			if (ctx->sequence > sequence)
1947:				continue;
1948:			if (!ctx->commit_lsn) {
1949:				/*
1950:				 * It is still being pushed! Wait for the push to
1951:				 * complete, then start again from the beginning.
1952:				 */
1953:				XFS_STATS_INC(log->l_mp, xs_log_force_sleep);
1954:				xlog_wait(&cil->xc_commit_wait, &cil->xc_push_lock);
1955:				goto restart;
1956:			}
1957:			if (ctx->sequence != sequence)
1958:				continue;
1959:			/* found it! */
1960:			commit_lsn = ctx->commit_lsn;
1961:		}
1962:	
1963:		/*
1964:		 * The call to xlog_cil_push_now() executes the push in the background.
1965:		 * Hence by the time we have got here it our sequence may not have been
1966:		 * pushed yet. This is true if the current sequence still matches the
1967:		 * push sequence after the above wait loop and the CIL still contains
1968:		 * dirty objects. This is guaranteed by the push code first adding the
1969:		 * context to the committing list before emptying the CIL.
1970:		 *
1971:		 * Hence if we don't find the context in the committing list and the
1972:		 * current sequence number is unchanged then the CIL contents are
1973:		 * significant.  If the CIL is empty, if means there was nothing to push
1974:		 * and that means there is nothing to wait for. If the CIL is not empty,
1975:		 * it means we haven't yet started the push, because if it had started
1976:		 * we would have found the context on the committing list.
1977:		 */
1978:		if (sequence == cil->xc_current_sequence &&
1979:		    !test_bit(XLOG_CIL_EMPTY, &cil->xc_flags)) {
1980:			spin_unlock(&cil->xc_push_lock);
1981:			goto restart;
1982:		}
1983:	
1984:		spin_unlock(&cil->xc_push_lock);
1985:		return commit_lsn;
1986:	
1987:		/*
1988:		 * We detected a shutdown in progress. We need to trigger the log force
1989:		 * to pass through it's iclog state machine error handling, even though
1990:		 * we are already in a shutdown state. Hence we can't return
1991:		 * NULLCOMMITLSN here as that has special meaning to log forces (i.e.
1992:		 * LSN is already stable), so we return a zero LSN instead.
1993:		 */
1994:	out_shutdown:
1995:		spin_unlock(&cil->xc_push_lock);
1996:		return 0;
1997:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

99/2 2026/09/19 00:50 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 36724
							output: 47
							thoughts: 143
						

Thoughts:
**Tracing the Commit LSN in the XLOG CIL Process**

Okay, so I'm digging into this `xlog_cil_force_seq` function and it's calling `xlog_cil_push_now`. That's the first clue. Now, I see it's waiting for `ctx->commit_lsn` to be non-zero. That's the key, right? I need to understand when and how this `ctx->commit_lsn` gets populated.

Alright, let's trace this. Where is it set? The flow seems to point to `xlog_cil_push_work`. So, let's look there. Ah, `xlog_cil_push_work` calls `xlog_cil_write_commit_record(ctx)`. Bingo! This looks like where the magic happens.

So, *this* is where `ctx->commit_lsn` is likely being set – in `xlog_cil_write_commit_record`. Now, I need to verify that; so let's jump in and check `xlog_cil_write_commit_record` directly. That's the next logical step.



100/2 2026/09/19 00:50 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_write_commit_record]

Results:
map[SourceCode:1179:	/*
1180:	 * Write out the commit record of a checkpoint transaction to close off a
1181:	 * running log write. These commit records are strictly ordered in ascending CIL
1182:	 * sequence order so that log recovery will always replay the checkpoints in the
1183:	 * correct order.
1184:	 */
1185:	static int
1186:	xlog_cil_write_commit_record(
1187:		struct xfs_cil_ctx	*ctx)
1188:	{
1189:		struct xlog		*log = ctx->cil->xc_log;
1190:		struct xlog_op_header	ophdr = {
1191:			.oh_clientid = XFS_TRANSACTION,
1192:			.oh_tid = cpu_to_be32(ctx->ticket->t_tid),
1193:			.oh_flags = XLOG_COMMIT_TRANS,
1194:		};
1195:		struct xfs_log_iovec	reg = {
1196:			.i_addr = &ophdr,
1197:			.i_len = sizeof(struct xlog_op_header),
1198:			.i_type = XLOG_REG_TYPE_COMMIT,
1199:		};
1200:		int			error;
1201:	
1202:		if (xlog_is_shutdown(log))
1203:			return -EIO;
1204:	
1205:		error = xlog_cil_order_write(ctx->cil, ctx->sequence, _COMMIT_RECORD);
1206:		if (error)
1207:			return error;
1208:		error = xlog_write_one_vec(log, ctx, &reg, ctx->ticket);
1209:		if (error)
1210:			xlog_force_shutdown(log, SHUTDOWN_LOG_IO_ERROR);
1211:		return error;
1212:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

101/2 2026/09/19 00:50 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 37742
							output: 43
							thoughts: 244
						

Thoughts:
**Digging into the LSN Assignment**

Okay, so I'm trying to figure out where this `ctx->commit_lsn` is being set. My initial thought was that it was happening in `xlog_write_one_vec`, but I need to confirm that. I'm going to double-check `xlog_cil_push_work` first, as I thought I'd seen something there.

Alright, here's what's happening in `xlog_cil_push_work`: it calls `xlog_cil_write_commit_record`. Then, it grabs a `ticket` from the context (`ctx`). The comment there is important - it seems like the context might get freed later. It explicitly states it can't be referenced *after* `xlog_state_release_iclog()`. So, I'll need to remember that. However, I still need to know where `ctx->commit_lsn` is actually set. I'm going to go back and verify it isn't in `xlog_write_one_vec` after all. Time to dig in there.



102/2 2026/09/19 00:50 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log.c Name:xlog_write_one_vec]

Results:
map[SourceCode: 807:	int
 808:	xlog_write_one_vec(
 809:		struct xlog		*log,
 810:		struct xfs_cil_ctx	*ctx,
 811:		struct xfs_log_iovec	*reg,
 812:		struct xlog_ticket	*ticket)
 813:	{
 814:		struct xfs_log_vec	lv = {
 815:			.lv_niovecs	= 1,
 816:			.lv_iovecp	= reg,
 817:			.lv_bytes	= reg->i_len,
 818:		};
 819:		LIST_HEAD		(lv_chain);
 820:	
 821:		/* account for space used by record data */
 822:		ticket->t_curr_res -= lv.lv_bytes;
 823:	
 824:		list_add(&lv.lv_list, &lv_chain);
 825:		return xlog_write(log, ctx, &lv_chain, ticket, lv.lv_bytes);
 826:	}
 SourceFile:fs/xfs/xfs_log.c]

103/2 2026/09/19 00:50 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 38612
							output: 39
							thoughts: 10
						

Thoughts:
Okay, here's my attempt at summarizing the thought process, as if it were my own, assuming I'm an expert in the field:

**Diving into `xlog_write`**

Alright, time to dig into this `xlog_write` function. This is critical – it's the bedrock of our WAL (Write-Ahead Logging) implementation. I need to refresh my understanding of its current behavior and look for potential bottlenecks or areas for optimization. Before I do anything, let's step through the key aspects of its functionality. I'll need to remember the locking that protects the process, and what the overall structure of the writing entails. This impacts how efficiently we're logging transactions and how quickly we can recover from crashes. I need to make sure I don't overlook anything that could introduce performance regressions. I know that, in many ways, `xlog_write` is a point of contention for people working on a variety of database projects, and I want to make sure I fully understand it.



104/2 2026/09/19 00:50 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log.c Name:xlog_write]

Results:
map[SourceCode:2110:	/*
2111:	 * Write some region out to in-core log
2112:	 *
2113:	 * This will be called when writing externally provided regions or when
2114:	 * writing out a commit record for a given transaction.
2115:	 *
2116:	 * General algorithm:
2117:	 *	1. Find total length of this write.  This may include adding to the
2118:	 *		lengths passed in.
2119:	 *	2. Check whether we violate the tickets reservation.
2120:	 *	3. While writing to this iclog
2121:	 *	    A. Reserve as much space in this iclog as can get
2122:	 *	    B. If this is first write, save away start lsn
2123:	 *	    C. While writing this region:
2124:	 *		1. If first write of transaction, write start record
2125:	 *		2. Write log operation header (header per region)
2126:	 *		3. Find out if we can fit entire region into this iclog
2127:	 *		4. Potentially, verify destination memcpy ptr
2128:	 *		5. Memcpy (partial) region
2129:	 *		6. If partial copy, release iclog; otherwise, continue
2130:	 *			copying more regions into current iclog
2131:	 *	4. Mark want sync bit (in simulation mode)
2132:	 *	5. Release iclog for potential flush to on-disk log.
2133:	 *
2134:	 * ERRORS:
2135:	 * 1.	Panic if reservation is overrun.  This should never happen since
2136:	 *	reservation amounts are generated internal to the filesystem.
2137:	 * NOTES:
2138:	 * 1. Tickets are single threaded data structures.
2139:	 * 2. The XLOG_END_TRANS & XLOG_CONTINUE_TRANS flags are passed down to the
2140:	 *	syncing routine.  When a single log_write region needs to span
2141:	 *	multiple in-core logs, the XLOG_CONTINUE_TRANS bit should be set
2142:	 *	on all log operation writes which don't contain the end of the
2143:	 *	region.  The XLOG_END_TRANS bit is used for the in-core log
2144:	 *	operation which contains the end of the continued log_write region.
2145:	 * 3. When xlog_state_get_iclog_space() grabs the rest of the current iclog,
2146:	 *	we don't really know exactly how much space will be used.  As a result,
2147:	 *	we don't update ic_offset until the end when we know exactly how many
2148:	 *	bytes have been written out.
2149:	 */
2150:	int
2151:	xlog_write(
2152:		struct xlog		*log,
2153:		struct xfs_cil_ctx	*ctx,
2154:		struct list_head	*lv_chain,
2155:		struct xlog_ticket	*ticket,
2156:		uint32_t		len)
2157:	
2158:	{
2159:		struct xfs_log_vec	*lv;
2160:		struct xlog_write_data	data = {
2161:			.ticket		= ticket,
2162:			.bytes_left	= len,
2163:		};
2164:		int			error;
2165:	
2166:		if (ticket->t_curr_res < 0) {
2167:			xfs_alert_tag(log->l_mp, XFS_PTAG_LOGRES,
2168:			     "ctx ticket reservation ran out. Need to up reservation");
2169:			xlog_print_tic_res(log->l_mp, ticket);
2170:			xlog_force_shutdown(log, SHUTDOWN_LOG_IO_ERROR);
2171:		}
2172:	
2173:		error = xlog_state_get_iclog_space(log, &data);
2174:		if (error)
2175:			return error;
2176:	
2177:		ASSERT(xlog_write_space_left(&data) > 0);
2178:	
2179:		/*
2180:		 * If we have a context pointer, pass it the first iclog we are
2181:		 * writing to so it can record state needed for iclog write
2182:		 * ordering.
2183:		 */
2184:		if (ctx)
2185:			xlog_cil_set_ctx_write_state(ctx, data.iclog);
2186:	
2187:		list_for_each_entry(lv, lv_chain, lv_list) {
2188:			/*
2189:			 * If the entire log vec does not fit in the iclog, punt it to
2190:			 * the partial copy loop which can handle this case.
2191:			 */
2192:			if (lv->lv_niovecs &&
2193:			    lv->lv_bytes > xlog_write_space_left(&data)) {
2194:				error = xlog_write_partial(lv, &data);
2195:				if (error) {
2196:					/*
2197:					 * We have no iclog to release, so just return
2198:					 * the error immediately.
2199:					 */
2200:					return error;
2201:				}
2202:			} else {
2203:				xlog_write_full(lv, &data);
2204:			}
2205:		}
2206:		ASSERT(data.bytes_left == 0);
2207:	
2208:		/*
2209:		 * We've already been guaranteed that the last writes will fit inside
2210:		 * the current iclog, and hence it will already have the space used by
2211:		 * those writes accounted to it. Hence we do not need to update the
2212:		 * iclog with the number of bytes written here.
2213:		 */
2214:		spin_lock(&log->l_icloglock);
2215:		xlog_state_finish_copy(log, data.iclog, data.record_cnt, 0);
2216:		error = xlog_state_release_iclog(log, data.iclog, ticket);
2217:		spin_unlock(&log->l_icloglock);
2218:	
2219:		return error;
2220:	}
 SourceFile:fs/xfs/xfs_log.c]

105/2 2026/09/19 00:50 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 40727
							output: 49
							thoughts: 24
						

Thoughts:
Okay, here's my interpretation of that thought process, tailored for an expert audience, and written in the first person:

**My Deep Dive into Context Write State**

Right, so `xlog_cil_set_ctx_write_state(ctx, data.iclog)`... that's a key function call. Let me break down what's running through my head: I'm immediately recognizing that we're talking about setting the write state within a specific context, likely related to transaction logging, specifically the CIL (Conditional Index Logging) or a related structure. The arguments, `ctx` and `data.iclog` give me important information on context and data being written.

My focus goes immediately to how these elements are interacting. `ctx` is, of course, the *context* or handle associated with the operation and how it relates to the larger transaction processing flow. This is a critical point that dictates how the logging is handled. And `data.iclog`... *that* is the key. Is this an instance of a larger struct? Is this structure holding the information being written, perhaps some sort of "intent log" information? I'm assessing what exactly `iclog` contains, especially the critical details that are being written. Is it the actual data, is it metadata for the log entry, or both?

The implication here is that we're ensuring the correct write state is synchronized at this point. Am I dealing with a critical section, locking, or some other concurrency control mechanism? This could also be a state transition, indicating that the write operation is starting, has completed, or has encountered an error. The context is critical. Is it a persistent transaction log, an in-memory buffer, or something else?

Ultimately, this function call is absolutely crucial for the integrity of the logging system and transaction durability. A misconfiguration here could cause serious data loss or corruption, so I'm analyzing this with great care.



106/2 2026/09/19 00:51 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_set_ctx_write_state]

Results:
map[SourceCode:1029:	/*
1030:	* Record the LSN of the iclog we were just granted space to start writing into.
1031:	* If the context doesn't have a start_lsn recorded, then this iclog will
1032:	* contain the start record for the checkpoint. Otherwise this write contains
1033:	* the commit record for the checkpoint.
1034:	*/
1035:	void
1036:	xlog_cil_set_ctx_write_state(
1037:		struct xfs_cil_ctx	*ctx,
1038:		struct xlog_in_core	*iclog)
1039:	{
1040:		struct xfs_cil		*cil = ctx->cil;
1041:		xfs_lsn_t		lsn = be64_to_cpu(iclog->ic_header->h_lsn);
1042:	
1043:		ASSERT(!ctx->commit_lsn);
1044:		if (!ctx->start_lsn) {
1045:			spin_lock(&cil->xc_push_lock);
1046:			/*
1047:			 * The LSN we need to pass to the log items on transaction
1048:			 * commit is the LSN reported by the first log vector write, not
1049:			 * the commit lsn. If we use the commit record lsn then we can
1050:			 * move the grant write head beyond the tail LSN and overwrite
1051:			 * it.
1052:			 */
1053:			ctx->start_lsn = lsn;
1054:			wake_up_all(&cil->xc_start_wait);
1055:			spin_unlock(&cil->xc_push_lock);
1056:	
1057:			/*
1058:			 * Flush the write cache before writing the start record so that
1059:			 * the metadata we are about to overwrite in the log and the
1060:			 * data that new allocations in this context refer to are
1061:			 * persisted to stable storage before this iclog is written.
1062:			 */
1063:			spin_lock(&cil->xc_log->l_icloglock);
1064:			iclog->ic_flags |= XLOG_ICL_NEED_FLUSH;
1065:			spin_unlock(&cil->xc_log->l_icloglock);
1066:			return;
1067:		}
1068:	
1069:		/*
1070:		 * Take a reference to the iclog for the context so that we still hold
1071:		 * it when xlog_write is done and has released it. This means the
1072:		 * context controls when the iclog is released for IO.
1073:		 */
1074:		atomic_inc(&iclog->ic_refcnt);
1075:	
1076:		/*
1077:		 * xlog_state_get_iclog_space() guarantees there is enough space in the
1078:		 * iclog for an entire commit record, so we can attach the context
1079:		 * callbacks now.  This needs to be done before we make the commit_lsn
1080:		 * visible to waiters so that checkpoints with commit records in the
1081:		 * same iclog order their IO completion callbacks in the same order that
1082:		 * the commit records appear in the iclog.
1083:		 */
1084:		spin_lock(&cil->xc_log->l_icloglock);
1085:		list_add_tail(&ctx->iclog_entry, &iclog->ic_callbacks);
1086:		spin_unlock(&cil->xc_log->l_icloglock);
1087:	
1088:		/*
1089:		 * Now we can record the commit LSN and wake anyone waiting for this
1090:		 * sequence to have the ordered commit record assigned to a physical
1091:		 * location in the log.
1092:		 */
1093:		spin_lock(&cil->xc_push_lock);
1094:		ctx->commit_iclog = iclog;
1095:		ctx->commit_lsn = lsn;
1096:		wake_up_all(&cil->xc_commit_wait);
1097:		spin_unlock(&cil->xc_push_lock);
1098:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

107/2 2026/09/19 00:51 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 42408
							output: 45
							thoughts: 3135
						

Thoughts:
**Understanding the XFS Buffer UAF Bug**

Alright, let's break this down. My initial thought process revolves around tracing the path of `ctx->commit_lsn`. I realize it's set during the commit record write within `xlog_cil_set_ctx_write_state`, triggered by `xlog_write`, which itself is called from `xlog_cil_write_commit_record`. Crucially, this all happens within `xlog_cil_push_work`. I followed the sequence - push aggregate, build level-value chain, write chain, write commit record (which sets the LSN). The first realization is that `xlog_cil_push_pcp_aggregate` executes before the LSN is set. This leads me to conclude `xlog_cil_force_seq` will wait on `xc_commit_wait` until the `ctx->commit_lsn` becomes available. This is important: `xlog_cil_force_seq` cannot return until the aggregate is done. This, in turn, means that `xfs_trans_commit`, which relies on `xfs_log_force_seq`, can't return until the iclog is written to disk. And that means `xfs_sync_sb_buf` can't call `xfs_bwrite` until the iclog is written.

Then I shifted to the AIL (Active Inode Log) and the I/O completion callback `xlog_state_do_callback`. That calls `xlog_cil_committed`, which adds items to the AIL through `xlog_cil_ail_insert`. Logically, the `xfs_trans_ail_delete` in `xfs_buf_item_done` should remove these items. `xfs_buf_item_relse` should then free them. But... the bug report says there's a problem with `xlog_cil_push_pcp_aggregate` accessing a *freed* item! That's the crux.

I had to rethink the timing. If `xlog_cil_push_pcp_aggregate` runs before `xfs_trans_commit` returns, and `xfs_bwrite` can't run before the commit, how is a `bwrite` on a *freed* buffer even possible? Could the `bwrite` be from another thread? The stack trace reveals that the thread that calls `xfs_trans_commit` is the same one calling `xfs_bwrite`, and freeing the item. How can `xlog_cil_push_work` (which includes `xlog_cil_push_pcp_aggregate`) access a freed item when the transaction for that same call has completed? I thought the item was added to the CIL *again* after freeing, or by *another* transaction!

The answer lies in the interaction with the superblock buffer (`mp->m_sb_bp`), which is shared. `xfs_sync_sb_buf` commits a transaction, logs it, and then *unconditionally* acquires a lock on that buffer *after* the transaction commit, and then writes it to disk. Now, another thread can jump in between `xfs_trans_commit` and `xfs_buf_lock`, modify the superblock, commit its transaction and add the item to the CIL, and then *release* the lock on the shared buffer. My thread then locks the superblock buffer, and *then* writes it. `xfs_bwrite` triggers the I/O completion, `xfs_buf_ioend`, which in turn calls `xfs_buf_item_done`, and this is where the real problem happens. The item is added back to the AIL. But that call frees the item! The items are freed before the CIL is pushed by the other thread! Then, when the *other* thread's CIL push runs, the freed memory is accessed, leading to the UAF.

So the sequence is this: Task A (say, an `xfs_ioc_setlabel` call) calls `xfs_sync_sb_buf`, commits a transaction, pushes to CIL. Then it tries to write the Superblock. Task B jumps in, modifies SB, commits transaction, and adds the SB buffer to the CIL. Task A writes the Superblock. The critical issue is `xfs_bwrite`'s unconditional calling of `xfs_buf_item_done`, that frees memory of an element still in CIL, leading to the use-after-free. The buffer is being written by `xfs_bwrite` that expects a buffer *not* to be in the CIL. The solution must be some guard around `xfs_bwrite`.



108/2 2026/09/19 00:51 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_item_done]

Results:
map[SourceCode:1065:	void
1066:	xfs_buf_item_done(
1067:		struct xfs_buf		*bp)
1068:	{
1069:		struct xfs_buf_log_item	*bip = bp->b_log_item;
1070:	
1071:		/*
1072:		 * If we are forcibly shutting down, this may well be off the AIL
1073:		 * already. That's because we simulate the log-committed callbacks to
1074:		 * unpin these buffers. Or we may never have put this item on AIL
1075:		 * because of the transaction was aborted forcibly.
1076:		 * xfs_trans_ail_delete() takes care of these.
1077:		 *
1078:		 * Either way, AIL is useless if we're forcing a shutdown.
1079:		 *
1080:		 * Note that log recovery writes might have buffer items that are not on
1081:		 * the AIL even when the file system is not shut down.
1082:		 */
1083:		xfs_trans_ail_delete(&bip->bli_item,
1084:				     xlog_in_recovery(bip->bli_item.li_log) ?
1085:				     0 : SHUTDOWN_CORRUPT_INCORE);
1086:		xfs_buf_item_relse(bip);
1087:	}
 SourceFile:fs/xfs/xfs_buf_item.c]

109/2 2026/09/19 00:51 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 47031
							output: 42
							thoughts: 38
						

Thoughts:
Here's my take on those thoughts:

**Analyzing `xfs_buf_ioend`'s Callers**

Okay, so I'm thinking about the XFS buffer code. I need to understand the relationship between `xfs_buf_item_done` and `xfs_buf_ioend`. The note says `xfs_buf_item_done` is called from `xfs_buf_ioend`. That makes sense; it implies `xfs_buf_ioend` is likely the IO completion handler for the buffer, which would then trigger the item completion. I'm going to dig into the `xfs_buf_ioend` function definition now. Let's see exactly how this chain works, what conditions lead to the call, and whether there are any subtleties in the sequencing of the related structures. I need to grasp the control flow here perfectly to understand its implications for performance and, more importantly, correctness. I'm especially interested in concurrency concerns related to these calls.



110/2 2026/09/19 00:51 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf.c Name:xfs_buf_ioend]

Results:
map[SourceCode:1122:	/*
1123:	 * Complete a buffer read or write.
1124:	 *
1125:	 * Releases the buffer if the I/O was asynchronous.
1126:	 */
1127:	static void
1128:	xfs_buf_ioend(
1129:		struct xfs_buf	*bp)
1130:	{
1131:		bool		async = bp->b_flags & XBF_ASYNC;
1132:	
1133:		trace_xfs_buf_iodone(bp, _RET_IP_);
1134:	
1135:		if (bp->b_flags & XBF_READ) {
1136:			if (!bp->b_error && is_vmalloc_addr(bp->b_addr))
1137:				invalidate_kernel_vmap_range(bp->b_addr,
1138:					roundup(BBTOB(bp->b_length), PAGE_SIZE));
1139:			if (!bp->b_error && bp->b_ops)
1140:				bp->b_ops->verify_read(bp);
1141:			if (!bp->b_error)
1142:				xfs_buf_set_flags(bp, XBF_DONE);
1143:			if (bp->b_flags & XBF_READ_AHEAD)
1144:				percpu_counter_dec(&bp->b_target->bt_readahead_count);
1145:		} else {
1146:			if (unlikely(bp->b_error)) {
1147:				if (xfs_buf_ioend_handle_error(bp)) {
1148:					ASSERT(async);
1149:					return;
1150:				}
1151:			} else {
1152:				xfs_buf_clear_flags(bp, XBF_WRITE_FAIL);
1153:				xfs_buf_set_flags(bp, XBF_DONE);
1154:			}
1155:	
1156:			/* clear the retry state */
1157:			bp->b_last_error = 0;
1158:			bp->b_retries = 0;
1159:			bp->b_first_retry_time = 0;
1160:	
1161:			/*
1162:			 * Note that for things like remote attribute buffers, there may
1163:			 * not be a buffer log item here, so processing the buffer log
1164:			 * item must remain optional.
1165:			 */
1166:			if (bp->b_log_item)
1167:				xfs_buf_item_done(bp);
1168:	
1169:			if (bp->b_iodone)
1170:				bp->b_iodone(bp);
1171:		}
1172:	
1173:		xfs_buf_clear_flags(bp, XBF_READ | XBF_WRITE | XBF_READ_AHEAD);
1174:		if (async)
1175:			xfs_buf_relse(bp);
1176:	}
 SourceFile:fs/xfs/xfs_buf.c]

111/2 2026/09/19 00:51 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 48207
							output: 45
							thoughts: 251
						

Thoughts:
**My Analysis of XFS Buffer Handling and Log Item Management**

Okay, let's break this down. My initial observation is that `xfs_buf_item_done` only gets called if `bp->b_log_item` isn't null. And, without question, `xfs_buf_item_done` always calls `xfs_buf_item_relse(bip)`. That part seems straightforward. But then, I have to consider the write path. `xfsaild` writes a buffer using `xfs_buf_delwri_submit`, which eventually calls `xfs_bwrite` or something similar, right?

When that write completes, we hit `xfs_buf_ioend`, and *that* calls `xfs_buf_item_done`. And then... bam! The log item is freed. Wait a second, is that actually correct? Yes, it seems like once a buffer gets written to disk, its associated log item is freed. Okay, that makes sense.

But then, the follow-up question hits me: what if that buffer is *still* in the CIL? Meaning, it's been modified by a new transaction? If it's in the CIL, it means it's been modified by a later transaction. And if it's been modified by a new transaction... shouldn't it be pinned? Yeah, that's it! It has to be pinned to prevent freeing the log item prematurely! Okay, I think I'm onto something here. *xfs_buf_item_pin*! That's the function I need to look at.

When a transaction commits, it pins the log items, preventing them from being prematurely released. That makes perfect sense. I think I'm going to dig into the details of `xfs_buf_item_pin` to be absolutely certain.



112/2 2026/09/19 00:51 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_item_pin]

Results:
map[SourceCode: 407:	/*
 408:	 * This is called to pin the buffer associated with the buf log item in memory
 409:	 * so it cannot be written out.
 410:	 *
 411:	 * We take a reference to the buffer log item here so that the BLI life cycle
 412:	 * extends at least until the buffer is unpinned via xfs_buf_item_unpin() and
 413:	 * inserted into the AIL.
 414:	 *
 415:	 * We also need to take a reference to the buffer itself as the BLI unpin
 416:	 * processing requires accessing the buffer after the BLI has dropped the final
 417:	 * BLI reference. See xfs_buf_item_unpin() for an explanation.
 418:	 * If unpins race to drop the final BLI reference and only the
 419:	 * BLI owns a reference to the buffer, then the loser of the race can have the
 420:	 * buffer fgreed from under it (e.g. on shutdown). Taking a buffer reference per
 421:	 * pin count ensures the life cycle of the buffer extends for as
 422:	 * long as we hold the buffer pin reference in xfs_buf_item_unpin().
 423:	 */
 424:	STATIC void
 425:	xfs_buf_item_pin(
 426:		struct xfs_log_item	*lip)
 427:	{
 428:		struct xfs_buf_log_item	*bip = BUF_ITEM(lip);
 429:	
 430:		ASSERT(atomic_read(&bip->bli_refcount) > 0);
 431:		ASSERT((bip->bli_flags & XFS_BLI_LOGGED) ||
 432:		       (bip->bli_flags & XFS_BLI_ORDERED) ||
 433:		       (bip->bli_flags & XFS_BLI_STALE));
 434:	
 435:		trace_xfs_buf_item_pin(bip);
 436:	
 437:		xfs_buf_hold(bip->bli_buf);
 438:		atomic_inc(&bip->bli_refcount);
 439:		atomic_inc(&bip->bli_buf->b_pin_count);
 440:	}
 SourceFile:fs/xfs/xfs_buf_item.c]

113/2 2026/09/19 00:51 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 49569
							output: 40
							thoughts: 51
						

Thoughts:
Okay, here's my interpretation of those thoughts, crafted with the expectation that I'm discussing this with a fellow expert:

**Investigating Buffer Pinning and Write Operations in XFS**

Hmm, let me see... I'm tracing through this `xfs_buf_item_pin` function and it's bumping the `b_pin_count` field within the buffer's `bli_buf` structure, right? So, if a buffer's "pinned," that fundamentally means something is actively *relying* on its current contents. That brings me to a critical question: Can a buffer be written to while it's in a pinned state? This feels like a potential race condition or data integrity issue if the write operation were to modify data that a pinner still expects to be consistent. I need to dig into the `xfs_bwrite` function to understand the interaction. How does it handle this pinned state? Does it wait, error out, or maybe even implicitly unpin or manage the pin count within the write path? Knowing this is vital to understanding the overall integrity and concurrency behavior of the XFS buffer management system. It's a key question when dealing with journaling or crash recovery, for sure.



114/2 2026/09/19 00:51 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf.c Name:xfs_bwrite]

Results:
map[SourceCode:1226:	int
1227:	xfs_bwrite(
1228:		struct xfs_buf		*bp)
1229:	{
1230:		int			error;
1231:	
1232:		ASSERT(xfs_buf_islocked(bp));
1233:	
1234:		xfs_buf_set_flags(bp, XBF_WRITE);
1235:		xfs_buf_clear_flags(bp, XBF_ASYNC | XBF_READ | _XBF_DELWRI_Q |
1236:					XBF_DONE);
1237:	
1238:		xfs_buf_submit(bp);
1239:		error = xfs_buf_iowait(bp);
1240:		if (error)
1241:			xfs_force_shutdown(bp->b_mount, SHUTDOWN_META_IO_ERROR);
1242:		return error;
1243:	}
 SourceFile:fs/xfs/xfs_buf.c]

115/2 2026/09/19 00:51 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 50216
							output: 41
							thoughts: 46
						

Thoughts:
Okay, here's the summary of those thoughts, tailored for an expert audience, and written as if they are my own internal monologue:

**A Concerning Oversight in Buffer Handling**

Wait a second... *xfs_bwrite* doesn't seem to be validating whether the buffer it's working with is actually pinned! That's a potential landmine. It just dives straight into calling `xfs_buf_submit(bp)`.  That's... not ideal.  It's bypassing a crucial safety check.  I need to drill down into `xfs_buf_submit` right now. This could have serious implications for data integrity and could easily lead to some unexpected issues, depending on how `xfs_buf_submit` handles unpinned buffers. Gotta figure out what's going on underneath this... quickly.



116/2 2026/09/19 00:51 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf.c Name:xfs_buf_submit]

Results:
map[SourceCode:1370:	/*
1371:	 * Buffer I/O submission path, read or write. Asynchronous submission transfers
1372:	 * the buffer lock ownership and the current reference to the IO. It is not
1373:	 * safe to reference the buffer after a call to this function unless the caller
1374:	 * holds an additional reference itself.
1375:	 */
1376:	static void
1377:	xfs_buf_submit(
1378:		struct xfs_buf	*bp)
1379:	{
1380:		trace_xfs_buf_submit(bp, _RET_IP_);
1381:	
1382:		ASSERT(!(bp->b_flags & _XBF_DELWRI_Q));
1383:	
1384:		/*
1385:		 * On log shutdown we stale and complete the buffer immediately. We can
1386:		 * be called to read the superblock before the log has been set up, so
1387:		 * be careful checking the log state.
1388:		 *
1389:		 * Checking the mount shutdown state here can result in the log tail
1390:		 * moving inappropriately on disk as the log may not yet be shut down.
1391:		 * i.e. failing this buffer on mount shutdown can remove it from the AIL
1392:		 * and move the tail of the log forwards without having written this
1393:		 * buffer to disk. This corrupts the log tail state in memory, and
1394:		 * because the log may not be shut down yet, it can then be propagated
1395:		 * to disk before the log is shutdown. Hence we check log shutdown
1396:		 * state here rather than mount state to avoid corrupting the log tail
1397:		 * on shutdown.
1398:		 */
1399:		if (bp->b_mount->m_log && xlog_is_shutdown(bp->b_mount->m_log)) {
1400:			xfs_buf_ioerror(bp, -EIO);
1401:			goto ioerror;
1402:		}
1403:	
1404:		if (bp->b_flags & XBF_WRITE)
1405:			xfs_buf_wait_unpin(bp);
1406:	
1407:		/*
1408:		 * Make sure we capture only current IO errors rather than stale errors
1409:		 * left over from previous use of the buffer (e.g. failed readahead).
1410:		 */
1411:		bp->b_error = 0;
1412:	
1413:		if ((bp->b_flags & XBF_WRITE) && !xfs_buf_verify_write(bp)) {
1414:			/* ->verify_write should have set b_error already */
1415:			xfs_force_shutdown(bp->b_mount, SHUTDOWN_CORRUPT_INCORE);
1416:			goto ioerror;
1417:		}
1418:	
1419:		/* In-memory targets are directly mapped, no I/O required. */
1420:		if (xfs_buftarg_is_mem(bp->b_target))
1421:			goto end_io;
1422:	
1423:		xfs_buf_submit_bio(bp);
1424:		return;
1425:	
1426:	ioerror:
1427:		xfs_buf_clear_flags(bp, XBF_DONE);
1428:		xfs_buf_stale(bp);
1429:	end_io:
1430:		if (bp->b_flags & XBF_ASYNC)
1431:			xfs_buf_ioend(bp);
1432:		else
1433:			complete(&bp->b_iowait);
1434:	}
 SourceFile:fs/xfs/xfs_buf.c]

117/2 2026/09/19 00:51 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 51549
							output: 44
							thoughts: 48
						

Thoughts:
**Diving into xfs_buf_submit and xfs_buf_wait_unpin**

Right, so `xfs_buf_submit`... a crucial function, no doubt. My immediate thought is, when dealing with `XBF_WRITE` buffers within it, we're invoking `xfs_buf_wait_unpin(bp)`.  That's the key connection. Therefore, my next step is clear. Time to delve into the workings of `xfs_buf_wait_unpin`. I need to fully understand its behaviour in this context. What's it doing? How's it interacting with the buffer? And, most importantly, what are the implications of this unpin operation *after* a write? Let's get to it.



118/2 2026/09/19 00:51 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf.c Name:xfs_buf_wait_unpin]

Results:
map[SourceCode: 968:	STATIC void
 969:	xfs_buf_wait_unpin(
 970:		struct xfs_buf		*bp)
 971:	{
 972:		DECLARE_WAITQUEUE	(wait, current);
 973:	
 974:		if (atomic_read(&bp->b_pin_count) == 0)
 975:			return;
 976:	
 977:		add_wait_queue(&bp->b_waiters, &wait);
 978:		for (;;) {
 979:			set_current_state(TASK_UNINTERRUPTIBLE);
 980:			if (atomic_read(&bp->b_pin_count) == 0)
 981:				break;
 982:			io_schedule();
 983:		}
 984:		remove_wait_queue(&bp->b_waiters, &wait);
 985:		set_current_state(TASK_RUNNING);
 986:	}
 SourceFile:fs/xfs/xfs_buf.c]

119/2 2026/09/19 00:51 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 52112
							output: 46
							thoughts: 655
						

Thoughts:
**My XFS Buffer Puzzlement**

Okay, so `xfs_buf_submit` is *waiting* for the buffer to be unpinned. That much is clear. But when *exactly* does this unpinning happen? I'm tracing it out... the transaction commits to the iclog, the iclog hits disk, and `xlog_state_do_callback` gets called. From there, it's `xlog_cil_committed`, which triggers `xlog_cil_ail_insert`. That inserts items into the AIL, and THEN... aha! It calls `xfs_buf_item_unpin`.

Wait a minute... so the unpinning happens *after* the CIL push is done and the iclog is safely on disk! That means `xfs_bwrite` *cannot* proceed until the CIL push has finished. That's a critical dependency. This implies that if the CIL push is done, `xlog_cil_push_pcp_aggregate` must have completed, right?

But then, if `xlog_cil_push_pcp_aggregate` is *done*, how in the world is it accessing the freed item? That's what the bug report is screaming about. Let's re-read those KASAN errors:

```
BUG: KASAN: slab-use-after-free in __list_splice include/linux/list.h:580 [inline]
BUG: KASAN: slab-use-after-free in list_splice_init include/linux/list.h:619 [inline]
BUG: KASAN: slab-use-after-free in xlog_cil_push_pcp_aggregate fs/xfs/xfs_log_cil.c:137 [inline]
BUG: KASAN: slab-use-after-free in xlog_cil_push_work+0x9b6/0x2a90 fs/xfs/xfs_log_cil.c:1417
```

Okay, it's clear: `xlog_cil_push_pcp_aggregate` is messing with `cilpcp->log_items`. That's where the corruption is happening.

If the buffer *was* pinned, `xfs_bwrite` would correctly wait for the unpin. But what if it *wasn't*? When would a buffer NOT be pinned? The answer lies in `xfs_trans_log_buf`, which gets called when a transaction modifies a buffer. That sets `XFS_BLI_LOGGED` on the buffer log item.

When the transaction commits, `xlog_cil_commit` calls `xlog_cil_insert_items`. That function in turn calls `IOP_COMMITTING(lip, ctx->sequence)`. And for a buffer log item, that expands to `xfs_buf_item_committing`. Now I need to see what's happening inside `xfs_buf_item_committing`. I feel like I'm on the right track; the flow from `xfs_trans_log_buf` to `xfs_buf_item_committing` is key, and the unpin is possibly premature.



120/2 2026/09/19 00:52 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_item_committing]

Results:
map[SourceCode: 762:	STATIC void
 763:	xfs_buf_item_committing(
 764:		struct xfs_log_item	*lip,
 765:		xfs_csn_t		seq)
 766:	{
 767:		return xfs_buf_item_release(lip);
 768:	}
 SourceFile:fs/xfs/xfs_buf_item.c]

121/2 2026/09/19 00:52 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 53657
							output: 45
							thoughts: 40
						

Thoughts:
Okay, here we go. Here's a summary of that thought process, assuming I'm already deep in the weeds of XFS buffer management:

**Digging into XFS Buffer Release**

Hmm, hold on a second. It just hit me - `xfs_buf_item_committing` is actually calling `xfs_buf_item_release`? That's a connection I need to verify. Let's see... I've got to double-check that interaction. Time to quickly jump into the source code for `xfs_buf_item_release`. Need to understand *exactly* how those two functions relate and what the implications are for buffer state transitions during commit operations. This could be critical for pinpointing that elusive performance bottleneck I've been chasing, or maybe even a subtle race condition. Better confirm my understanding and make sure it's correct.



122/2 2026/09/19 00:52 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_item_release]

Results:
map[SourceCode: 647:	/*
 648:	 * Release the buffer associated with the buf log item.  If there is no dirty
 649:	 * logged data associated with the buffer recorded in the buf log item, then
 650:	 * free the buf log item and remove the reference to it in the buffer.
 651:	 *
 652:	 * This call ignores the recursion count.  It is only called when the buffer
 653:	 * should REALLY be unlocked, regardless of the recursion count.
 654:	 *
 655:	 * We unconditionally drop the transaction's reference to the log item. If the
 656:	 * item was logged, then another reference was taken when it was pinned, so we
 657:	 * can safely drop the transaction reference now.  This also allows us to avoid
 658:	 * potential races with the unpin code freeing the bli by not referencing the
 659:	 * bli after we've dropped the reference count.
 660:	 *
 661:	 * If the XFS_BLI_HOLD flag is set in the buf log item, then free the log item
 662:	 * if necessary but do not unlock the buffer.  This is for support of
 663:	 * xfs_trans_bhold(). Make sure the XFS_BLI_HOLD field is cleared if we don't
 664:	 * free the item.
 665:	 *
 666:	 * If the XFS_BLI_STALE flag is set, the last reference to the BLI *must*
 667:	 * perform a completion abort of any objects attached to the buffer for IO
 668:	 * tracking purposes. This generally only happens in shutdown situations,
 669:	 * normally xfs_buf_item_unpin() will drop the last BLI reference and perform
 670:	 * completion processing. However, because transaction completion can race with
 671:	 * checkpoint completion during a shutdown, this release context may end up
 672:	 * being the last active reference to the BLI and so needs to perform this
 673:	 * cleanup.
 674:	 */
 675:	STATIC void
 676:	xfs_buf_item_release(
 677:		struct xfs_log_item	*lip)
 678:	{
 679:		struct xfs_buf_log_item	*bip = BUF_ITEM(lip);
 680:		struct xfs_buf		*bp = bip->bli_buf;
 681:		bool			hold = bip->bli_flags & XFS_BLI_HOLD;
 682:		bool			stale = bip->bli_flags & XFS_BLI_STALE;
 683:		bool			aborted = test_bit(XFS_LI_ABORTED,
 684:							   &lip->li_flags);
 685:		bool			dirty = bip->bli_flags & XFS_BLI_DIRTY;
 686:	#if defined(DEBUG) || defined(XFS_WARN)
 687:		bool			ordered = bip->bli_flags & XFS_BLI_ORDERED;
 688:	#endif
 689:	
 690:		trace_xfs_buf_item_release(bip);
 691:	
 692:		ASSERT(xfs_buf_islocked(bp));
 693:	
 694:		/*
 695:		 * The bli dirty state should match whether the blf has logged segments
 696:		 * except for ordered buffers, where only the bli should be dirty.
 697:		 */
 698:		ASSERT((!ordered && dirty == xfs_buf_item_dirty_format(bip)) ||
 699:		       (ordered && dirty && !xfs_buf_item_dirty_format(bip)));
 700:		ASSERT(!stale || (bip->__bli_format.blf_flags & XFS_BLF_CANCEL));
 701:	
 702:		/*
 703:		 * Clear the buffer's association with this transaction and
 704:		 * per-transaction state from the bli, which has been copied above.
 705:		 */
 706:		bp->b_transp = NULL;
 707:		bip->bli_flags &= ~(XFS_BLI_LOGGED | XFS_BLI_HOLD | XFS_BLI_ORDERED);
 708:	
 709:		/* If there are other references, then we have nothing to do. */
 710:		if (!atomic_dec_and_test(&bip->bli_refcount))
 711:			goto out_release;
 712:	
 713:		/*
 714:		 * Stale buffer completion frees the BLI, unlocks and releases the
 715:		 * buffer. Neither the BLI or buffer are safe to reference after this
 716:		 * call, so there's nothing more we need to do here.
 717:		 *
 718:		 * If we get here with a stale buffer and references to the BLI remain,
 719:		 * we must not unlock the buffer as the last BLI reference owns lock
 720:		 * context, not us.
 721:		 */
 722:		if (stale) {
 723:			xfs_buf_item_finish_stale(bip);
 724:			xfs_buf_relse(bp);
 725:			ASSERT(!hold);
 726:			return;
 727:		}
 728:	
 729:		/*
 730:		 * Dirty or clean, aborted items are done and need to be removed from
 731:		 * the AIL and released. This frees the BLI, but leaves the buffer
 732:		 * locked and referenced.
 733:		 */
 734:		if (aborted || xlog_is_shutdown(lip->li_log)) {
 735:			ASSERT(list_empty(&bip->bli_buf->b_li_list));
 736:			xfs_buf_item_done(bp);
 737:			goto out_release;
 738:		}
 739:	
 740:		/*
 741:		 * Clean, unreferenced BLIs can be immediately freed, leaving the buffer
 742:		 * locked and referenced.
 743:		 *
 744:		 * Dirty, unreferenced BLIs *must* be in the AIL awaiting writeback.
 745:		 */
 746:		if (!dirty)
 747:			xfs_buf_item_relse(bip);
 748:		else
 749:			ASSERT(test_bit(XFS_LI_IN_AIL, &lip->li_flags));
 750:	
 751:		/* Not safe to reference the BLI from here */
 752:	out_release:
 753:		/*
 754:		 * If we get here with a stale buffer, we must not unlock the
 755:		 * buffer as the last BLI reference owns lock context, not us.
 756:		 */
 757:		if (stale || hold)
 758:			return;
 759:		xfs_buf_relse(bp);
 760:	}
 SourceFile:fs/xfs/xfs_buf_item.c]

123/2 2026/09/19 00:52 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 55882
							output: 41
							thoughts: 1185
						

Thoughts:
**Analyzing a Potential Race Condition in XFS Buffer Handling**

Okay, let's break this down. My initial thought process is centered around how buffers are handled within the XFS filesystem, particularly with regard to pinning, unpinning, and how they interact with the CIL (Commit Intent Log) push. I see that `xfs_buf_item_release` clears flags, decrements the reference count, and then releases the buffer if the count hits zero. But there's a crucial point: if the item was pinned, the reference count was *incremented*. This implies a scenario where `atomic_dec_and_test` will return `false`, leading to the buffer being released *while* it's pinned!

That immediately sets off alarm bells. `xfs_buf_relse` unlocks the buffer, meaning another thread could potentially lock it and trigger `xfs_bwrite`, which, critically, *waits* for the buffer to be unpinned via `xfs_buf_wait_unpin`. This wait implies the CIL push must complete, which means the iclog should be written, `xlog_cil_ail_insert` called, the buffer unpinned via `xfs_buf_item_unpin`, and *then* `xfs_bwrite` can proceed. And when it completes, `xfs_buf_item_done` is called which does trans cleanup and frees the item.

But if `xfs_bwrite` is waiting for unpin, then the CIL push must have completed. If that's the case, then `xlog_cil_push_pcp_aggregate` must have finished. So how could it be accessing the freed item? That's the core of the puzzle.

Now, I'm going back to the bug report. Okay, *KASAN slab-use-after-free* and importantly `PREEMPT_{RT,(full)}` are mentioned. That changes everything. It suggests that the CIL push work might be preempted. If it's preempted *within* `xlog_cil_push_pcp_aggregate`, it hasn't finished splicing the list! But wait... If the list isn't spliced, then the buffer can't be unpinned, because that's done *after* the commit record is written, right?

The buffer unpin happens in `xlog_cil_ail_insert`, which occurs *after* the iclog I/O is complete, which is after `xlog_cil_push_work` writes the commit record. So `xlog_cil_push_work` *must* finish the aggregate *before* it can write the commit record and unpin the buffer. If it *hasn't* finished, the iclog *cannot* be written, the buffer *cannot* be unpinned, `xfs_bwrite` *cannot* proceed, `xfs_buf_item_done` *cannot* be called, and therefore the item *cannot* be freed! It doesn't make sense.

I need to re-evaluate. Is there a scenario where `xfs_bwrite` *doesn't* wait? I need to look closer at `xfs_buf_submit` again. There's a fundamental assumption here that I am missing.



124/2 2026/09/19 00:52 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf.c Name:xfs_buf_submit]

Results:
map[SourceCode:1370:	/*
1371:	 * Buffer I/O submission path, read or write. Asynchronous submission transfers
1372:	 * the buffer lock ownership and the current reference to the IO. It is not
1373:	 * safe to reference the buffer after a call to this function unless the caller
1374:	 * holds an additional reference itself.
1375:	 */
1376:	static void
1377:	xfs_buf_submit(
1378:		struct xfs_buf	*bp)
1379:	{
1380:		trace_xfs_buf_submit(bp, _RET_IP_);
1381:	
1382:		ASSERT(!(bp->b_flags & _XBF_DELWRI_Q));
1383:	
1384:		/*
1385:		 * On log shutdown we stale and complete the buffer immediately. We can
1386:		 * be called to read the superblock before the log has been set up, so
1387:		 * be careful checking the log state.
1388:		 *
1389:		 * Checking the mount shutdown state here can result in the log tail
1390:		 * moving inappropriately on disk as the log may not yet be shut down.
1391:		 * i.e. failing this buffer on mount shutdown can remove it from the AIL
1392:		 * and move the tail of the log forwards without having written this
1393:		 * buffer to disk. This corrupts the log tail state in memory, and
1394:		 * because the log may not be shut down yet, it can then be propagated
1395:		 * to disk before the log is shutdown. Hence we check log shutdown
1396:		 * state here rather than mount state to avoid corrupting the log tail
1397:		 * on shutdown.
1398:		 */
1399:		if (bp->b_mount->m_log && xlog_is_shutdown(bp->b_mount->m_log)) {
1400:			xfs_buf_ioerror(bp, -EIO);
1401:			goto ioerror;
1402:		}
1403:	
1404:		if (bp->b_flags & XBF_WRITE)
1405:			xfs_buf_wait_unpin(bp);
1406:	
1407:		/*
1408:		 * Make sure we capture only current IO errors rather than stale errors
1409:		 * left over from previous use of the buffer (e.g. failed readahead).
1410:		 */
1411:		bp->b_error = 0;
1412:	
1413:		if ((bp->b_flags & XBF_WRITE) && !xfs_buf_verify_write(bp)) {
1414:			/* ->verify_write should have set b_error already */
1415:			xfs_force_shutdown(bp->b_mount, SHUTDOWN_CORRUPT_INCORE);
1416:			goto ioerror;
1417:		}
1418:	
1419:		/* In-memory targets are directly mapped, no I/O required. */
1420:		if (xfs_buftarg_is_mem(bp->b_target))
1421:			goto end_io;
1422:	
1423:		xfs_buf_submit_bio(bp);
1424:		return;
1425:	
1426:	ioerror:
1427:		xfs_buf_clear_flags(bp, XBF_DONE);
1428:		xfs_buf_stale(bp);
1429:	end_io:
1430:		if (bp->b_flags & XBF_ASYNC)
1431:			xfs_buf_ioend(bp);
1432:		else
1433:			complete(&bp->b_iowait);
1434:	}
 SourceFile:fs/xfs/xfs_buf.c]

125/2 2026/09/19 00:52 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 58885
							output: 45
							thoughts: 178
						

Thoughts:
**Investigating a Potential Pinning Issue in XFS Buffer Handling**

Okay, let's think this through. I see `xfs_buf_submit` calling `xfs_buf_wait_unpin(bp)` if it's a write operation (`XBF_WRITE`). Now, a red flag pops up: could there be a scenario where `bp->b_pin_count` is zero, meaning the buffer isn't supposedly pinned, yet the buffer is still lingering in the CIL (Commit Intent Log)? That would be a problem. So, I need to understand when that `b_pin_count` is incremented. Ah, right, that's handled by `xfs_buf_item_pin`.

The next question: when is `xfs_buf_item_pin` actually called? Tracing back from `xfs_trans_commit`, through `xlog_cil_commit` and then `xlog_cil_insert_items` leads me to `IOP_PIN(lip)`. Wait a minute... *`xlog_cil_insert_items` itself* calls `IOP_PIN(lip)`! So, it's during the insertion of items into the CIL that the pinning happens. That's a crucial piece of the puzzle. I'd better double check that `xlog_cil_insert_items` function now and make sure it is doing what it needs to.



126/2 2026/09/19 00:52 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_insert_items]

Results:
map[SourceCode: 625:	/*
 626:	 * Insert the log items into the CIL and calculate the difference in space
 627:	 * consumed by the item. Add the space to the checkpoint ticket and calculate
 628:	 * if the change requires additional log metadata. If it does, take that space
 629:	 * as well. Remove the amount of space we added to the checkpoint ticket from
 630:	 * the current transaction ticket so that the accounting works out correctly.
 631:	 */
 632:	static void
 633:	xlog_cil_insert_items(
 634:		struct xlog		*log,
 635:		struct xfs_trans	*tp,
 636:		uint32_t		released_space)
 637:	{
 638:		struct xfs_cil		*cil = log->l_cilp;
 639:		struct xfs_cil_ctx	*ctx = cil->xc_ctx;
 640:		struct xfs_log_item	*lip;
 641:		int			len = 0;
 642:		int			iovhdr_res = 0, split_res = 0, ctx_res = 0;
 643:		int			space_used;
 644:		int			order;
 645:		unsigned int		cpu_nr;
 646:		struct xlog_cil_pcp	*cilpcp;
 647:	
 648:		ASSERT(tp);
 649:	
 650:		/*
 651:		 * We can do this safely because the context can't checkpoint until we
 652:		 * are done so it doesn't matter exactly how we update the CIL.
 653:		 */
 654:		xlog_cil_insert_format_items(log, tp, &len);
 655:	
 656:		/*
 657:		 * Subtract the space released by intent cancelation from the space we
 658:		 * consumed so that we remove it from the CIL space and add it back to
 659:		 * the current transaction reservation context.
 660:		 */
 661:		len -= released_space;
 662:	
 663:		/*
 664:		 * Grab the per-cpu pointer for the CIL before we start any accounting.
 665:		 * That ensures that we are running with pre-emption disabled and so we
 666:		 * can't be scheduled away between split sample/update operations that
 667:		 * are done without outside locking to serialise them.
 668:		 */
 669:		cpu_nr = get_cpu();
 670:		cilpcp = this_cpu_ptr(cil->xc_pcp);
 671:	
 672:		/* Tell the future push that there was work added by this CPU. */
 673:		if (!cpumask_test_cpu(cpu_nr, &ctx->cil_pcpmask))
 674:			cpumask_test_and_set_cpu(cpu_nr, &ctx->cil_pcpmask);
 675:	
 676:		/*
 677:		 * We need to take the CIL checkpoint unit reservation on the first
 678:		 * commit into the CIL. Test the XLOG_CIL_EMPTY bit first so we don't
 679:		 * unnecessarily do an atomic op in the fast path here. We can clear the
 680:		 * XLOG_CIL_EMPTY bit as we are under the xc_ctx_lock here and that
 681:		 * needs to be held exclusively to reset the XLOG_CIL_EMPTY bit.
 682:		 */
 683:		if (test_bit(XLOG_CIL_EMPTY, &cil->xc_flags) &&
 684:		    test_and_clear_bit(XLOG_CIL_EMPTY, &cil->xc_flags))
 685:			ctx_res = ctx->ticket->t_unit_res;
 686:	
 687:		/*
 688:		 * Check if we need to steal iclog headers. atomic_read() is not a
 689:		 * locked atomic operation, so we can check the value before we do any
 690:		 * real atomic ops in the fast path. If we've already taken the CIL unit
 691:		 * reservation from this commit, we've already got one iclog header
 692:		 * space reserved so we have to account for that otherwise we risk
 693:		 * overrunning the reservation on this ticket.
 694:		 *
 695:		 * If the CIL is already at the hard limit, we might need more header
 696:		 * space that originally reserved. So steal more header space from every
 697:		 * commit that occurs once we are over the hard limit to ensure the CIL
 698:		 * push won't run out of reservation space.
 699:		 *
 700:		 * This can steal more than we need, but that's OK.
 701:		 *
 702:		 * The cil->xc_ctx_lock provides the serialisation necessary for safely
 703:		 * calling xlog_cil_over_hard_limit() in this context.
 704:		 */
 705:		space_used = atomic_read(&ctx->space_used) + cilpcp->space_used + len;
 706:		if (atomic_read(&cil->xc_iclog_hdrs) > 0 ||
 707:		    xlog_cil_over_hard_limit(log, space_used)) {
 708:			split_res = log->l_iclog_hsize +
 709:						sizeof(struct xlog_op_header);
 710:			if (ctx_res)
 711:				ctx_res += split_res * (tp->t_ticket->t_iclog_hdrs - 1);
 712:			else
 713:				ctx_res = split_res * tp->t_ticket->t_iclog_hdrs;
 714:			atomic_sub(tp->t_ticket->t_iclog_hdrs, &cil->xc_iclog_hdrs);
 715:		}
 716:		cilpcp->space_reserved += ctx_res;
 717:	
 718:		/*
 719:		 * Accurately account when over the soft limit, otherwise fold the
 720:		 * percpu count into the global count if over the per-cpu threshold.
 721:		 */
 722:		if (!test_bit(XLOG_CIL_PCP_SPACE, &cil->xc_flags)) {
 723:			atomic_add(len, &ctx->space_used);
 724:		} else if (cilpcp->space_used + len >
 725:				(XLOG_CIL_SPACE_LIMIT(log) / num_online_cpus())) {
 726:			space_used = atomic_add_return(cilpcp->space_used + len,
 727:							&ctx->space_used);
 728:			cilpcp->space_used = 0;
 729:	
 730:			/*
 731:			 * If we just transitioned over the soft limit, we need to
 732:			 * transition to the global atomic counter.
 733:			 */
 734:			if (space_used >= XLOG_CIL_SPACE_LIMIT(log))
 735:				xlog_cil_insert_pcp_aggregate(cil, ctx);
 736:		} else {
 737:			cilpcp->space_used += len;
 738:		}
 739:		/* attach the transaction to the CIL if it has any busy extents */
 740:		if (!list_empty(&tp->t_busy))
 741:			list_splice_init(&tp->t_busy, &cilpcp->busy_extents);
 742:	
 743:		/*
 744:		 * Now update the order of everything modified in the transaction
 745:		 * and insert items into the CIL if they aren't already there.
 746:		 * We do this here so we only need to take the CIL lock once during
 747:		 * the transaction commit.
 748:		 */
 749:		order = atomic_inc_return(&ctx->order_id);
 750:		list_for_each_entry(lip, &tp->t_items, li_trans) {
 751:			/* Skip items which aren't dirty in this transaction. */
 752:			if (!test_bit(XFS_LI_DIRTY, &lip->li_flags))
 753:				continue;
 754:	
 755:			lip->li_order_id = order;
 756:			if (!list_empty(&lip->li_cil))
 757:				continue;
 758:			list_add_tail(&lip->li_cil, &cilpcp->log_items);
 759:		}
 760:		put_cpu();
 761:	
 762:		/*
 763:		 * If we've overrun the reservation, dump the tx details before we move
 764:		 * the log items. Shutdown is imminent...
 765:		 */
 766:		tp->t_ticket->t_curr_res -= ctx_res + len;
 767:		if (WARN_ON(tp->t_ticket->t_curr_res < 0)) {
 768:			xfs_warn(log->l_mp, "Transaction log reservation overrun:");
 769:			xfs_warn(log->l_mp,
 770:				 "  log items: %d bytes (iov hdrs: %d bytes)",
 771:				 len, iovhdr_res);
 772:			xfs_warn(log->l_mp, "  split region headers: %d bytes",
 773:				 split_res);
 774:			xfs_warn(log->l_mp, "  ctx ticket: %d bytes", ctx_res);
 775:			xlog_print_trans(tp);
 776:			xlog_force_shutdown(log, SHUTDOWN_LOG_IO_ERROR);
 777:		}
 778:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

127/2 2026/09/19 00:52 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 62174
							output: 43
							thoughts: 48
						

Thoughts:
**Investigating the IOP_PIN Call**

Okay, hold on a second. I was under the impression that `xlog_cil_insert_items` was responsible for pinning those log items, but it doesn't appear to be calling `IOP_PIN(lip)` at all. That's unexpected. This means I need to retrace my steps and figure out where this crucial pinning operation *is* actually happening. Where in the commit flow is this performed?

Alright, let's switch gears and focus on `xlog_cil_commit`. My money is on the pinning happening during the commit phase, so let's start there. Let's see if that function is the culprit.



128/2 2026/09/19 00:52 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_commit]

Results:
map[SourceCode:1806:	/*
1807:	 * Commit a transaction with the given vector to the Committed Item List.
1808:	 *
1809:	 * To do this, we need to format the item, pin it in memory if required and
1810:	 * account for the space used by the transaction. Once we have done that we
1811:	 * need to release the unused reservation for the transaction, attach the
1812:	 * transaction to the checkpoint context so we carry the busy extents through
1813:	 * to checkpoint completion, and then unlock all the items in the transaction.
1814:	 *
1815:	 * Called with the context lock already held in read mode to lock out
1816:	 * background commit, returns without it held once background commits are
1817:	 * allowed again.
1818:	 */
1819:	void
1820:	xlog_cil_commit(
1821:		struct xlog		*log,
1822:		struct xfs_trans	*tp,
1823:		xfs_csn_t		*commit_seq,
1824:		bool			regrant)
1825:	{
1826:		struct xfs_cil		*cil = log->l_cilp;
1827:		struct xfs_log_item	*lip, *next;
1828:		uint32_t		released_space = 0;
1829:	
1830:		/*
1831:		 * Do all necessary memory allocation before we lock the CIL.
1832:		 * This ensures the allocation does not deadlock with a CIL
1833:		 * push in memory reclaim (e.g. from kswapd).
1834:		 */
1835:		xlog_cil_alloc_shadow_bufs(log, tp);
1836:	
1837:		/* lock out background commit */
1838:		down_read(&cil->xc_ctx_lock);
1839:	
1840:		if (tp->t_flags & XFS_TRANS_HAS_INTENT_DONE)
1841:			released_space = xlog_cil_process_intents(cil, tp);
1842:	
1843:		xlog_cil_insert_items(log, tp, released_space);
1844:	
1845:		if (regrant && !xlog_is_shutdown(log))
1846:			xfs_log_ticket_regrant(log, tp->t_ticket);
1847:		else
1848:			xfs_log_ticket_ungrant(log, tp->t_ticket);
1849:		tp->t_ticket = NULL;
1850:		xfs_trans_unreserve_and_mod_sb(tp);
1851:	
1852:		/*
1853:		 * Once all the items of the transaction have been copied to the CIL,
1854:		 * the items can be unlocked and possibly freed.
1855:		 *
1856:		 * This needs to be done before we drop the CIL context lock because we
1857:		 * have to update state in the log items and unlock them before they go
1858:		 * to disk. If we don't, then the CIL checkpoint can race with us and
1859:		 * we can run checkpoint completion before we've updated and unlocked
1860:		 * the log items. This affects (at least) processing of stale buffers,
1861:		 * inodes and EFIs.
1862:		 */
1863:		trace_xfs_trans_commit_items(tp, _RET_IP_);
1864:		list_for_each_entry_safe(lip, next, &tp->t_items, li_trans) {
1865:			xfs_trans_del_item(lip);
1866:			if (lip->li_ops->iop_committing)
1867:				lip->li_ops->iop_committing(lip, cil->xc_ctx->sequence);
1868:		}
1869:		if (commit_seq)
1870:			*commit_seq = cil->xc_ctx->sequence;
1871:	
1872:		/* xlog_cil_push_background() releases cil->xc_ctx_lock */
1873:		xlog_cil_push_background(log);
1874:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

129/2 2026/09/19 00:52 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 63604
							output: 45
							thoughts: 102
						

Thoughts:
**Pinning the Buffer in xfs_buf_item_release**

Okay, so `xlog_cil_commit` is calling `lip->li_ops->iop_committing`. That's the entry point, naturally. And, in the case of a buffer log item, `iop_committing` is going to resolve to `xfs_buf_item_committing`, which is exactly what I expected. The next step, then, is `xfs_buf_item_release`. But wait a minute... I distinctly remember that function *not* doing any buffer pinning. This seems... odd. I was sure that was handled there. This warrants a double-check. So, if not there, then where the hell is the buffer getting pinned? Time to thoroughly vet the `xfs_buf_item_ops` structure. I need to understand the complete buffer lifecycle here.



130/2 2026/09/19 00:52 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_item_ops]

Results:
map[SourceCode: 832:	static const struct xfs_item_ops xfs_buf_item_ops = {
 833:		.iop_size	= xfs_buf_item_size,
 834:		.iop_precommit	= xfs_buf_item_precommit,
 835:		.iop_format	= xfs_buf_item_format,
 836:		.iop_pin	= xfs_buf_item_pin,
 837:		.iop_unpin	= xfs_buf_item_unpin,
 838:		.iop_release	= xfs_buf_item_release,
 839:		.iop_committing	= xfs_buf_item_committing,
 840:		.iop_committed	= xfs_buf_item_committed,
 841:		.iop_push	= xfs_buf_item_push,
 842:	};
 SourceFile:fs/xfs/xfs_buf_item.c]

131/2 2026/09/19 00:52 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 64214
							output: 58
							thoughts: 20
						

Thoughts:
**Pinpoint Pursuit: Tracing the `iop_pin` Function Calls**

Okay, so I need to understand the lifecycle of this `iop_pin` function. My immediate thought is, where is it actually *used*? That's the crucial question. Time to dive into the codebase and search for every instance of `iop_pin`. I need to see where it's called, how it's being passed arguments, and in what context it's operating. This initial search is the bedrock; it will define my understanding of its purpose within the larger system.



132/2 2026/09/19 00:52 tool codesearch-find-references
0m Error:
log-in to see details

Args:
map[ContextFile:fs/xfs/xfs_buf_item.c IncludeSnippetLines:0 Name:iop_pin SourceTreePrefix:fs/xfs/]

Results:
map[References:<nil> TruncatedOutput:false]

133/2 2026/09/19 00:52 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 64433
							output: 29
							thoughts: 19
						

Thoughts:
Okay, here's my take on those thoughts, tailored for an expert audience, and written as if they were my own:

**Navigating the Landscape: Targeting `->iop_pin`**

Alright, a new problem, or perhaps just a new angle on an existing one. My initial instinct is to treat this as a field to be explored. Let's see... a field, yes. The mental checklist is running: dependencies, potential points of entry, the overall architecture... But before I get lost in the weeds of context, I need a specific starting point, a well-defined target. The goal is to move beyond the high-level, I need to look closer.

My immediate focus sharpens: let's jump straight into the code. The objective is clear. I'll search for `->iop_pin`. That's where I need to start. From there, I'll be able to trace its usage, see how it's initialized, manipulated, and ultimately, how it fits into the broader picture. I anticipate that this will be the thread I need to pull to start untangling the problem.



134/2 2026/09/19 00:52 tool grepper
0m Args:
map[Expression:->iop_pin PathPrefix:fs/xfs/]

Results:
map[Output:fs/xfs/xfs_log_cil.c=371=xfs_cil_prepare_item(
--
fs/xfs/xfs_log_cil.c-388-	if (!lip->li_lv) {
fs/xfs/xfs_log_cil.c:389:		if (lv->lv_item->li_ops->iop_pin)
fs/xfs/xfs_log_cil.c:390:			lv->lv_item->li_ops->iop_pin(lv->lv_item);
fs/xfs/xfs_log_cil.c-391-		lv->lv_item->li_lv_shadow = NULL;
]

135/2 2026/09/19 00:52 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 64897
							output: 45
							thoughts: 34
						

Thoughts:
Here's my take on the thought process, as requested:

**XFS CIL Item Preparation & IO Pinning - A Quick Investigation**

Alright, that's interesting. I see that `xfs_cil_prepare_item` is calling `iop_pin`. Now, *that* warrants a closer look. I need to understand why this function, part of the XFS CIL (Checkpoint In-flight Log) system, is triggering the IO pinning mechanism. I know they're related, but I need to quickly refresh the exact details of this function. Let's dig into `xfs_cil_prepare_item` and dissect this interaction between log management and IO operations. It's time to trace the control flow and reason about the implications of pinning data within this specific context.



136/2 2026/09/19 00:52 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xfs_cil_prepare_item]

Results:
map[SourceCode: 366:	/*
 367:	 * Prepare the log item for insertion into the CIL. Calculate the difference in
 368:	 * log space it will consume, and if it is a new item pin it as well.
 369:	 */
 370:	STATIC void
 371:	xfs_cil_prepare_item(
 372:		struct xlog		*log,
 373:		struct xfs_log_item	*lip,
 374:		struct xfs_log_vec	*lv,
 375:		int			*diff_len)
 376:	{
 377:		/* Account for the new LV being passed in */
 378:		if (lv->lv_buf_used != XFS_LOG_VEC_ORDERED)
 379:			*diff_len += lv->lv_bytes;
 380:	
 381:		/*
 382:		 * If there is no old LV, this is the first time we've seen the item in
 383:		 * this CIL context and so we need to pin it. If we are replacing the
 384:		 * old lv, then remove the space it accounts for and make it the shadow
 385:		 * buffer for later freeing. In both cases we are now switching to the
 386:		 * shadow buffer, so update the pointer to it appropriately.
 387:		 */
 388:		if (!lip->li_lv) {
 389:			if (lv->lv_item->li_ops->iop_pin)
 390:				lv->lv_item->li_ops->iop_pin(lv->lv_item);
 391:			lv->lv_item->li_lv_shadow = NULL;
 392:		} else if (lip->li_lv != lv) {
 393:			ASSERT(lv->lv_buf_used != XFS_LOG_VEC_ORDERED);
 394:	
 395:			*diff_len -= lip->li_lv->lv_bytes;
 396:			lv->lv_item->li_lv_shadow = lip->li_lv;
 397:		}
 398:	
 399:		/* attach new log vector to log item */
 400:		lv->lv_item->li_lv = lv;
 401:	
 402:		/*
 403:		 * If this is the first time the item is being committed to the
 404:		 * CIL, store the sequence number on the log item so we can
 405:		 * tell in future commits whether this is the first checkpoint
 406:		 * the item is being committed into.
 407:		 */
 408:		if (!lv->lv_item->li_seq)
 409:			lv->lv_item->li_seq = log->l_cilp->xc_ctx->sequence;
 410:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

137/2 2026/09/19 00:52 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 65939
							output: 63
							thoughts: 14
						

Thoughts:
Here's my thought process, as if I were considering this question:

**Tracing the Callers of `xfs_cil_prepare_item`**

Alright, so the task at hand is to understand where the function `xfs_cil_prepare_item` is invoked within the XFS filesystem code. This isn't a particularly complex question, but it's crucial for understanding how data is prepared for journaling in XFS.

My initial approach would be, naturally, to leverage the source code. I'd begin by using `grep` or a similar tool to pinpoint every instance where `xfs_cil_prepare_item` appears in the XFS source tree. Given my experience, I'd probably use a more sophisticated approach than a simple `grep` - perhaps source code indexing or cross-referencing capabilities within my IDE to get a quick and comprehensive list. I'd be looking for both direct calls and any indirect calls through function pointers if there are any.

Once I have the list of call sites, I'd want to quickly filter out false positives. This would involve examining each call in context, ensuring that I understand the code that executes around that call. I know the XFS codebase pretty well, so I'm already anticipating the typical patterns for CIL (Commit Intent Log) operations. I'd look for areas related to transaction management, metadata updates, and data block allocation/deallocation, since these are all prime candidates for where this function would be used.

Ultimately, I expect to see `xfs_cil_prepare_item` being called within the context of transaction preparation. It would likely be part of a larger workflow that prepares data for journaling and ensures the atomicity of file system operations. I might want to then dive into the callers of these functions to understand the contexts within which these transaction preparations are being performed. I need to be sure I understand the complete workflow that this is a part of to understand where in the system the function is being used.



138/2 2026/09/19 00:52 tool codesearch-find-references
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c IncludeSnippetLines:0 Name:xfs_cil_prepare_item SourceTreePrefix:fs/xfs/]

Results:
map[References:[map[ReferenceKind:calls ReferencingEntityKind:function ReferencingEntityName:xlog_cil_insert_format_items SourceFile:fs/xfs/xfs_log_cil.c SourceLine:569] map[ReferenceKind:calls ReferencingEntityKind:function ReferencingEntityName:xlog_cil_insert_format_items SourceFile:fs/xfs/xfs_log_cil.c SourceLine:604]] TruncatedOutput:false]

139/2 2026/09/19 00:52 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 66571
							output: 46
							thoughts: 1394
						

Thoughts:
**Analyzing the Potential for Freed Item Access in XFS CIL**

Okay, here's what's running through my head. `xlog_cil_insert_format_items` is called from `xlog_cil_insert_items`.  Alright, so that confirms that `xlog_cil_insert_items` does indeed pin the buffer.  If it pins the buffer, `bp->b_pin_count` is incremented. That means that `xfs_buf_submit` will definitely wait for the buffer to be unpinned, which means that `xfs_bwrite` will wait too. And if `xfs_bwrite` waits, then `xfs_buf_item_done` won't be called until the buffer is unpinned.

Now, if the buffer *is* unpinned, that *should* mean the CIL push is done and the iclog is on disk. That *should* mean that `xlog_cil_push_pcp_aggregate` has finished. So why am I seeing a potential access to a freed item? Where am I going wrong?

Wait, is it possible that `xfs_buf_item_release` unpins the buffer? I need to double-check that. Let's look at the code:

```c
	/* If there are other references, then we have nothing to do. */
	if (!atomic_dec_and_test(&bip->bli_refcount))
		goto out_release;
```

Ah! The `atomic_dec_and_test(&bip->bli_refcount)`! When `xfs_buf_item_pin` is called, it does this:

```c
	xfs_buf_hold(bip->bli_buf);
	atomic_inc(&bip->bli_refcount);
	atomic_inc(&bip->bli_buf->b_pin_count);
```

So `bip->bli_refcount` *is* incremented, and when `xfs_buf_item_release` is called, it decrements it. Since `bip->bli_refcount` was incremented by `xfs_buf_item_pin`, `atomic_dec_and_test` will return FALSE, which means the buffer is *not* freed, *not* unpinned, and we go to `out_release`. Thus, the buffer *remains* pinned!

So, `xfs_bwrite` *will* wait. This is a problem since `xfs_sync_sb_buf` calls `xfs_trans_commit`, which will call `xlog_cil_commit`. So the buffer *is* pinned before `xfs_trans_commit` returns. But, `xfs_sync_sb_buf` uses `XFS_TRANS_SYNC`. `xfs_trans_commit` with `XFS_TRANS_SYNC` calls `xfs_log_force_seq`, which waits for the iclog to be written. `xlog_cil_ail_insert` is called when the iclog is written and it does the unpinning! So, by the time `xfs_trans_commit` returns, the buffer *is* unpinned!

Okay, if the buffer is unpinned, then `xfs_bwrite` won't wait. It *will* write the buffer, and when it's done, `xfs_buf_item_done` is called. That in turn calls `xfs_trans_ail_delete` and `xfs_buf_item_relse`. And `xfs_buf_item_relse` *frees* the item. But wait. If the buffer *was* unpinned, the CIL push for *that* transaction should be complete, and `xlog_cil_push_pcp_aggregate` for that transaction *should* be finished.

So... why am I seeing a freed item being accessed? Could *another* transaction have modified the buffer after it was unpinned, but before `xfs_bwrite` was actually called? Let's walk through it:

1.  Task A calls `xfs_sync_sb_buf`.
2.  Task A commits a SYNC transaction.
3.  Task A's transaction is pushed to CIL, the iclog is written, the buffer is UNPINNED, and inserted into the AIL.
4.  Task A's `xfs_trans_commit` returns.
5.  Task A is about to call `xfs_buf_lock(mp->m_sb_bp)`.
6.  *Now*, Task B starts a transaction, locks `mp->m_sb_bp


140/2 2026/09/19 00:53 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_item_unpin]

Results:
map[SourceCode: 478:	/*
 479:	 * This is called to unpin the buffer associated with the buf log item which was
 480:	 * previously pinned with a call to xfs_buf_item_pin().  We enter this function
 481:	 * with a buffer pin count, a buffer reference and a BLI reference.
 482:	 *
 483:	 * We must drop the BLI reference before we unpin the buffer because the AIL
 484:	 * doesn't acquire a BLI reference whenever it accesses it. Therefore if the
 485:	 * refcount drops to zero, the bli could still be AIL resident and the buffer
 486:	 * submitted for I/O at any point before we return. This can result in IO
 487:	 * completion freeing the buffer while we are still trying to access it here.
 488:	 * This race condition can also occur in shutdown situations where we abort and
 489:	 * unpin buffers from contexts other that journal IO completion.
 490:	 *
 491:	 * Hence we have to hold a buffer reference per pin count to ensure that the
 492:	 * buffer cannot be freed until we have finished processing the unpin operation.
 493:	 * The reference is taken in xfs_buf_item_pin(), and we must hold it until we
 494:	 * are done processing the buffer state. In the case of an abort (remove =
 495:	 * true) then we re-use the current pin reference as the IO reference we hand
 496:	 * off to IO failure handling.
 497:	 */
 498:	STATIC void
 499:	xfs_buf_item_unpin(
 500:		struct xfs_log_item	*lip,
 501:		int			remove)
 502:	{
 503:		struct xfs_buf_log_item	*bip = BUF_ITEM(lip);
 504:		struct xfs_buf		*bp = bip->bli_buf;
 505:		int			stale = bip->bli_flags & XFS_BLI_STALE;
 506:		int			freed;
 507:	
 508:		ASSERT(bp->b_log_item == bip);
 509:		ASSERT(atomic_read(&bip->bli_refcount) > 0);
 510:	
 511:		trace_xfs_buf_item_unpin(bip);
 512:	
 513:		freed = atomic_dec_and_test(&bip->bli_refcount);
 514:		if (atomic_dec_and_test(&bp->b_pin_count))
 515:			wake_up_all(&bp->b_waiters);
 516:	
 517:		/*
 518:		 * Nothing to do but drop the buffer pin reference if the BLI is
 519:		 * still active.
 520:		 */
 521:		if (!freed) {
 522:			xfs_buf_rele(bp);
 523:			return;
 524:		}
 525:	
 526:		if (stale) {
 527:			trace_xfs_buf_item_unpin_stale(bip);
 528:	
 529:			/*
 530:			 * The buffer has been locked and referenced since it was marked
 531:			 * stale so we own both lock and reference exclusively here. We
 532:			 * do not need the pin reference any more, so drop it now so
 533:			 * that we only have one reference to drop once item completion
 534:			 * processing is complete.
 535:			 */
 536:			xfs_buf_rele(bp);
 537:			xfs_buf_item_finish_stale(bip);
 538:			xfs_buf_relse(bp);
 539:			return;
 540:		}
 541:	
 542:		if (remove) {
 543:			/*
 544:			 * We need to simulate an async IO failures here to ensure that
 545:			 * the correct error completion is run on this buffer. This
 546:			 * requires a reference to the buffer and for the buffer to be
 547:			 * locked. We can safely pass ownership of the pin reference to
 548:			 * the IO to ensure that nothing can free the buffer while we
 549:			 * wait for the lock and then run the IO failure completion.
 550:			 */
 551:			xfs_buf_lock(bp);
 552:			xfs_buf_fail(bp);
 553:			return;
 554:		}
 555:	
 556:		/*
 557:		 * BLI has no more active references - it will be moved to the AIL to
 558:		 * manage the remaining BLI/buffer life cycle. There is nothing left for
 559:		 * us to do here so drop the pin reference to the buffer.
 560:		 */
 561:		xfs_buf_rele(bp);
 562:	}
 SourceFile:fs/xfs/xfs_buf_item.c]

141/2 2026/09/19 00:53 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 70442
							output: 45
							thoughts: 54
						

Thoughts:
**My Investigation into xfs_buf_item_unpin and li_lv**

Okay, hold on a second. I was under the impression that `xfs_buf_item_unpin` handled setting `lip->li_lv` to `NULL`. The documentation, or perhaps some past code review, led me to believe that. But looking at the implementation now, it's clear that it *doesn't* do that. So, where, in the chain of events, *does* `lip->li_lv` actually get set to `NULL`? I need to track down the responsible function. Let me see... I'll start by checking `xlog_cil_ail_insert`. That seems like a logical place to start digging into how `lip->li_lv` is managed within the logging system. I expect that I will likely find the answer within that function or functions it calls.



142/2 2026/09/19 00:53 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_ail_insert]

Results:
map[SourceCode: 802:	/*
 803:	 * Take the checkpoint's log vector chain of items and insert the attached log
 804:	 * items into the AIL. This uses bulk insertion techniques to minimise AIL lock
 805:	 * traffic.
 806:	 *
 807:	 * The AIL tracks log items via the start record LSN of the checkpoint,
 808:	 * not the commit record LSN. This is because we can pipeline multiple
 809:	 * checkpoints, and so the start record of checkpoint N+1 can be
 810:	 * written before the commit record of checkpoint N. i.e:
 811:	 *
 812:	 *   start N			commit N
 813:	 *	+-------------+------------+----------------+
 814:	 *		  start N+1			commit N+1
 815:	 *
 816:	 * The tail of the log cannot be moved to the LSN of commit N when all
 817:	 * the items of that checkpoint are written back, because then the
 818:	 * start record for N+1 is no longer in the active portion of the log
 819:	 * and recovery will fail/corrupt the filesystem.
 820:	 *
 821:	 * Hence when all the log items in checkpoint N are written back, the
 822:	 * tail of the log most now only move as far forwards as the start LSN
 823:	 * of checkpoint N+1.
 824:	 *
 825:	 * If we are called with the aborted flag set, it is because a log write during
 826:	 * a CIL checkpoint commit has failed. In this case, all the items in the
 827:	 * checkpoint have already gone through iop_committed and iop_committing, which
 828:	 * means that checkpoint commit abort handling is treated exactly the same as an
 829:	 * iclog write error even though we haven't started any IO yet. Hence in this
 830:	 * case all we need to do is iop_committed processing, followed by an
 831:	 * iop_unpin(aborted) call.
 832:	 *
 833:	 * The AIL cursor is used to optimise the insert process. If commit_lsn is not
 834:	 * at the end of the AIL, the insert cursor avoids the need to walk the AIL to
 835:	 * find the insertion point on every xfs_log_item_batch_insert() call. This
 836:	 * saves a lot of needless list walking and is a net win, even though it
 837:	 * slightly increases that amount of AIL lock traffic to set it up and tear it
 838:	 * down.
 839:	 */
 840:	static void
 841:	xlog_cil_ail_insert(
 842:		struct xfs_cil_ctx	*ctx,
 843:		bool			aborted)
 844:	{
 845:	#define LOG_ITEM_BATCH_SIZE	32
 846:		struct xfs_ail		*ailp = ctx->cil->xc_log->l_ailp;
 847:		struct xfs_log_item	*log_items[LOG_ITEM_BATCH_SIZE];
 848:		struct xfs_log_vec	*lv;
 849:		struct xfs_ail_cursor	cur;
 850:		xfs_lsn_t		old_head;
 851:		int			i = 0;
 852:	
 853:		/*
 854:		 * Update the AIL head LSN with the commit record LSN of this
 855:		 * checkpoint. As iclogs are always completed in order, this should
 856:		 * always be the same (as iclogs can contain multiple commit records) or
 857:		 * higher LSN than the current head. We do this before insertion of the
 858:		 * items so that log space checks during insertion will reflect the
 859:		 * space that this checkpoint has already consumed.  We call
 860:		 * xfs_ail_update_finish() so that tail space and space-based wakeups
 861:		 * will be recalculated appropriately.
 862:		 */
 863:		ASSERT(XFS_LSN_CMP(ctx->commit_lsn, ailp->ail_head_lsn) >= 0 ||
 864:				aborted);
 865:		spin_lock(&ailp->ail_lock);
 866:		xfs_trans_ail_cursor_last(ailp, &cur, ctx->start_lsn);
 867:		old_head = ailp->ail_head_lsn;
 868:		ailp->ail_head_lsn = ctx->commit_lsn;
 869:		/* xfs_ail_update_finish() drops the ail_lock */
 870:		xfs_ail_update_finish(ailp, NULLCOMMITLSN);
 871:	
 872:		/*
 873:		 * We move the AIL head forwards to account for the space used in the
 874:		 * log before we remove that space from the grant heads. This prevents a
 875:		 * transient condition where reservation space appears to become
 876:		 * available on return, only for it to disappear again immediately as
 877:		 * the AIL head update accounts in the log tail space.
 878:		 */
 879:		smp_wmb();	/* paired with smp_rmb in xlog_grant_space_left */
 880:		xlog_grant_return_space(ailp->ail_log, old_head, ailp->ail_head_lsn);
 881:	
 882:		/* unpin all the log items */
 883:		list_for_each_entry(lv, &ctx->lv_chain, lv_list) {
 884:			struct xfs_log_item	*lip = lv->lv_item;
 885:			xfs_lsn_t		item_lsn;
 886:	
 887:			if (aborted) {
 888:				trace_xlog_ail_insert_abort(lip);
 889:				set_bit(XFS_LI_ABORTED, &lip->li_flags);
 890:			}
 891:	
 892:			if (lip->li_ops->flags & XFS_ITEM_RELEASE_WHEN_COMMITTED) {
 893:				lip->li_ops->iop_release(lip);
 894:				continue;
 895:			}
 896:	
 897:			if (lip->li_ops->iop_committed)
 898:				item_lsn = lip->li_ops->iop_committed(lip,
 899:						ctx->start_lsn);
 900:			else
 901:				item_lsn = ctx->start_lsn;
 902:	
 903:			/* item_lsn of -1 means the item needs no further processing */
 904:			if (XFS_LSN_CMP(item_lsn, (xfs_lsn_t)-1) == 0)
 905:				continue;
 906:	
 907:			/*
 908:			 * if we are aborting the operation, no point in inserting the
 909:			 * object into the AIL as we are in a shutdown situation.
 910:			 */
 911:			if (aborted) {
 912:				ASSERT(xlog_is_shutdown(ailp->ail_log));
 913:				if (lip->li_ops->iop_unpin)
 914:					lip->li_ops->iop_unpin(lip, 1);
 915:				continue;
 916:			}
 917:	
 918:			if (item_lsn != ctx->start_lsn) {
 919:	
 920:				/*
 921:				 * Not a bulk update option due to unusual item_lsn.
 922:				 * Push into AIL immediately, rechecking the lsn once
 923:				 * we have the ail lock. Then unpin the item. This does
 924:				 * not affect the AIL cursor the bulk insert path is
 925:				 * using.
 926:				 */
 927:				spin_lock(&ailp->ail_lock);
 928:				if (XFS_LSN_CMP(item_lsn, lip->li_lsn) > 0)
 929:					xfs_trans_ail_update(ailp, lip, item_lsn);
 930:				else
 931:					spin_unlock(&ailp->ail_lock);
 932:				if (lip->li_ops->iop_unpin)
 933:					lip->li_ops->iop_unpin(lip, 0);
 934:				continue;
 935:			}
 936:	
 937:			/* Item is a candidate for bulk AIL insert.  */
 938:			log_items[i++] = lv->lv_item;
 939:			if (i >= LOG_ITEM_BATCH_SIZE) {
 940:				xlog_cil_ail_insert_batch(ailp, &cur, log_items,
 941:						LOG_ITEM_BATCH_SIZE, ctx->start_lsn);
 942:				i = 0;
 943:			}
 944:		}
 945:	
 946:		/* make sure we insert the remainder! */
 947:		if (i)
 948:			xlog_cil_ail_insert_batch(ailp, &cur, log_items, i,
 949:					ctx->start_lsn);
 950:	
 951:		spin_lock(&ailp->ail_lock);
 952:		xfs_trans_ail_cursor_done(&cur);
 953:		spin_unlock(&ailp->ail_lock);
 954:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

143/2 2026/09/19 00:53 llm expert-compressor
0m Model:
gemini-3.8-flash

Reply:
### 1. Approaches Tried and Results

- **Crash Details**:
  - Report: `BUG: KASAN: slab-use-after-free in __list_splice include/linux/list.h:580` / `list_splice_init include/linux/list.h:619` / `xlog_cil_push_pcp_aggregate fs/xfs/xfs_log_cil.c:137` / `xlog_cil_push_work+0x9b6/0x2a90`.
  - Buggy address: offset 104 (`0x68`) within `xfs_buf_log_item` (`struct xfs_log_item li_cil` member, size 16 bytes: `next` and `prev` pointers). Cache `xfs_buf_item`, size 272 bytes.
  - Allocation stack: Task 5944 running `xfs_ioc_setlabel` -> `xfs_sync_sb_buf` -> `xfs_log_sb` -> `__xfs_trans_getsb` -> `_xfs_trans_bjoin` -> `xfs_buf_item_init`.
  - Free stack: Task 5944 running `xfs_ioc_setlabel` -> `xfs_sync_sb_buf` -> `xfs_bwrite` -> `xfs_buf_iowait` -> `xfs_buf_ioend` -> `xfs_buf_item_done` -> `xfs_buf_item_relse` -> `xfs_buf_item_free`.

- **Source Code Investigation**:
  - `fs/xfs/libxfs/xfs_sb.c:xfs_sync_sb_buf`:
    - Allocates transaction `tp`.
    - Logs superblock: `xfs_log_sb(tp)`.
    - Sets sync commit: `xfs_trans_set_sync(tp); error = xfs_trans_commit(tp);`.
    - Immediately acquires buffer lock and writes: `xfs_buf_lock(mp->m_sb_bp); error = xfs_bwrite(mp->m_sb_bp); xfs_buf_unlock(mp->m_sb_bp);`.
  - `fs/xfs/xfs_ioctl.c:xfs_ioc_setlabel`:
    - Checks `if (!capable(CAP_SYS_ADMIN)) return -EPERM;`.
    - Explicitly uses `capable(CAP_SYS_ADMIN)`, which checks the initial namespace, NOT `ns_capable()`.
  - `fs/xfs/xfs_buf.c:xfs_bwrite` & `xfs_buf_submit`:
    - `xfs_bwrite` marks `XBF_WRITE`, clears `XBF_ASYNC | XBF_READ | _XBF_DELWRI_Q | XBF_DONE`, calls `xfs_buf_submit(bp)` and waits on `xfs_buf_iowait(bp)`.
    - `xfs_buf_submit`: checks if pinned via `if (bp->b_flags & XBF_WRITE) xfs_buf_wait_unpin(bp);`.
    - Upon I/O completion, `xfs_buf_ioend` is called:
      ```c
      if (bp->b_log_item)
          xfs_buf_item_done(bp);
      ```
    - `xfs_buf_item_done`:
      ```c
      xfs_trans_ail_delete(&bip->bli_item,
                   xlog_in_recovery(bip->bli_item.li_log) ?
                   0 : SHUTDOWN_CORRUPT_INCORE);
      xfs_buf_item_relse(bip);
      ```
    - `xfs_buf_item_relse` sets `bp->b_log_item = NULL;` and frees `bip` via `xfs_buf_item_free(bip);`.

- **CIL & Transaction Mechanism**:
  - When `tp` commits in `xfs_trans_commit`, `xlog_cil_commit` adds dirty log items to per-CPU list `cilpcp->log_items`.
  - If `XFS_TRANS_SYNC` is set, `xfs_log_force_seq` is called.
  - `xlog_cil_force_seq` triggers `xlog_cil_push_now` and waits for `ctx->commit_lsn`.
  - Background work `xlog_cil_push_work` runs:
    - Runs `xlog_cil_push_pcp_aggregate(cil, ctx)`:
      ```c
      for_each_cpu(cpu, &ctx->cil_pcpmask) {
          cilpcp = per_cpu_ptr(cil->xc_pcp, cpu);
          if (!list_empty(&cilpcp->log_items))
              list_splice_init(&cilpcp->log_items, &ctx->log_items);
      }
      ```
    - Builds log vector chain, switches context, and writes commit record via `xlog_cil_write_commit_record` -> sets `ctx->commit_lsn`.
    - Only after iclog write completion, callbacks execute (`xlog_cil_committed`) -> `xlog_cil_ail_insert` -> items inserted into AIL and unpinned.

- **Git Inspection**:
  - `git-log` / `git-blame` shows shallow repository boundary (`^238650ef6c7c`) for these paths.
  - Search for references to `xfs_sync_sb_buf`: only referenced in `xfs_ioc_setlabel` in `fs/xfs/xfs_ioctl.c`.

---

### 2. Hypotheses and Current Analysis

- **Mechanism of the Bug**:
  - `xfs_sync_sb_buf` commits a transaction logging `mp->m_sb_bp`, then immediately calls `xfs_bwrite(mp->m_sb_bp)`.
  - If `mp->m_sb_bp` is modified again concurrently by another transaction or CIL sequence (or if another transaction modifies `m_sb_bp` before the CIL push aggregates or while `m_sb_bp` is being handled), or if an error / shutdown occurs:
    - When `xfs_bwrite` completes, `xfs_buf_ioend` is invoked on `mp->m_sb_bp`.
    - `xfs_buf_ioend` sees `bp->b_log_item` is set and calls `xfs_buf_item_done(bp)`.
    - `xfs_buf_item_done` deletes the item from the AIL (or handles shutdown) and calls `xfs_buf_item_relse(bip)`, which immediately frees `bip` (`xfs_buf_item_free(bip)`).
    - However, if the item was queued into `cilpcp->log_items` for the next/current CIL push context that has not yet completed `xlog_cil_push_pcp_aggregate`, `bip->bli_item.li_cil` remains on `cilpcp->log_items`.
    - When `xlog_cil_push_work` runs `xlog_cil_push_pcp_aggregate`, it executes `list_splice_init(&cilpcp->log_items, &ctx->log_items)`, attempting to unlink/splice `bip->bli_item.li_cil`, touching the freed slab memory (UAF write).

- **Exploitability & Dimensions**:
  - **Exploitable**: Yes (slab-use-after-free write of pointers in list manipulation `__list_splice`, can corrupt slab metadata or overwrite pointers).
  - **Denial of Service**: Yes (crash / panic).
  - **Accessible from Unprivileged Processes**: No. Entry point in report is `xfs_ioc_setlabel` (`XFS_IOC_SETLABEL`), which contains `if (!capable(CAP_SYS_ADMIN)) return -EPERM;`.
  - **Accessible from User Namespaces**: No. Uses `capable(CAP_SYS_ADMIN)` (checking initial user namespace `init_user_ns`), not `ns_capable()`. User namespaces cannot call this ioctl. Furthermore, unprivileged users cannot mount XFS filesystems in user namespaces (XFS does not have `FS_USERNS_MOUNT`).
  - **Malicious Filesystem Trigger**: `xfs_sync_sb_buf` is not executed during mount. Check references to `xfs_sync_sb_buf` - only called from `xfs_ioc_setlabel`. (Other callers of `xfs_bwrite` like `xfs_add_incompat_log_feature` are also admin operations).
  - **Remote / Peripheral / VM Triggers**: Not reachable via network, peripheral (without mount/admin actions), or hypervisor interfaces.

---

### 3. Critical Code & Files

- `fs/xfs/xfs_ioctl.c`:
  ```c
  static int
  xfs_ioc_setlabel(struct file *filp, struct xfs_mount *mp, char __user *newlabel)
  {
      ...
      if (!capable(CAP_SYS_ADMIN))
          return -EPERM;
      ...
      error = xfs_sync_sb_buf(mp, true);
      ...
  }
  ```
- `fs/xfs/libxfs/xfs_sb.c`:
  ```c
  int xfs_sync_sb_buf(struct xfs_mount *mp, bool update_rtsb)
  {
      ...
      error = xfs_trans_commit(tp);
      ...
      xfs_buf_lock(mp->m_sb_bp);
      error = xfs_bwrite(mp->m_sb_bp);
      xfs_buf_unlock(mp->m_sb_bp);
      ...
  }
  ```
- `fs/xfs/xfs_buf.c:xfs_buf_ioend`:
  ```c
  if (bp->b_log_item)
      xfs_buf_item_done(bp);
  ```
- `fs/xfs/xfs_buf_item.c:xfs_buf_item_done` and `xfs_buf_item_relse`:
  ```c
  void xfs_buf_item_done(struct xfs_buf *bp) {
      struct xfs_buf_log_item *bip = bp->b_log_item;
      xfs_trans_ail_delete(&bip->bli_item, ...);
      xfs_buf_item_relse(bip);
  }
  ```
- `fs/xfs/xfs_log_cil.c:xlog_cil_push_pcp_aggregate`:
  ```c
  list_splice_init(&cilpcp->log_items, &ctx->log_items);
  ```

---

### 4. Watchouts / Notes for Final Assessment

- Do not get stuck re-checking struct layout or git history; the shallow git history only goes back to `238650ef6c7c`.
- The capability check `capable(CAP_SYS_ADMIN)` strictly gates `xfs_ioc_setlabel`.
- Check if any other trigger exists for `xfs_sync_sb_buf` (none; codesearch confirmed `xfs_ioc_setlabel` is the only caller).
- Prepare to invoke `set-results` and provide the final answer.

Tokens:
							input: 46196
							output: 2676
							thoughts: 0
						

144/2 2026/09/19 00:53 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 30664
							output: 45
							thoughts: 0
						

145/2 2026/09/19 00:53 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_buf_item.c Name:xfs_buf_item_pin]

Results:
map[SourceCode: 407:	/*
 408:	 * This is called to pin the buffer associated with the buf log item in memory
 409:	 * so it cannot be written out.
 410:	 *
 411:	 * We take a reference to the buffer log item here so that the BLI life cycle
 412:	 * extends at least until the buffer is unpinned via xfs_buf_item_unpin() and
 413:	 * inserted into the AIL.
 414:	 *
 415:	 * We also need to take a reference to the buffer itself as the BLI unpin
 416:	 * processing requires accessing the buffer after the BLI has dropped the final
 417:	 * BLI reference. See xfs_buf_item_unpin() for an explanation.
 418:	 * If unpins race to drop the final BLI reference and only the
 419:	 * BLI owns a reference to the buffer, then the loser of the race can have the
 420:	 * buffer fgreed from under it (e.g. on shutdown). Taking a buffer reference per
 421:	 * pin count ensures the life cycle of the buffer extends for as
 422:	 * long as we hold the buffer pin reference in xfs_buf_item_unpin().
 423:	 */
 424:	STATIC void
 425:	xfs_buf_item_pin(
 426:		struct xfs_log_item	*lip)
 427:	{
 428:		struct xfs_buf_log_item	*bip = BUF_ITEM(lip);
 429:	
 430:		ASSERT(atomic_read(&bip->bli_refcount) > 0);
 431:		ASSERT((bip->bli_flags & XFS_BLI_LOGGED) ||
 432:		       (bip->bli_flags & XFS_BLI_ORDERED) ||
 433:		       (bip->bli_flags & XFS_BLI_STALE));
 434:	
 435:		trace_xfs_buf_item_pin(bip);
 436:	
 437:		xfs_buf_hold(bip->bli_buf);
 438:		atomic_inc(&bip->bli_refcount);
 439:		atomic_inc(&bip->bli_buf->b_pin_count);
 440:	}
 SourceFile:fs/xfs/xfs_buf_item.c]

146/2 2026/09/19 00:53 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 31374
							output: 45
							thoughts: 0
						

147/2 2026/09/19 00:53 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_push_work]

Results:
map[SourceCode:1355:	/*
1356:	 * Push the Committed Item List to the log.
1357:	 *
1358:	 * If the current sequence is the same as xc_push_seq we need to do a flush. If
1359:	 * xc_push_seq is less than the current sequence, then it has already been
1360:	 * flushed and we don't need to do anything - the caller will wait for it to
1361:	 * complete if necessary.
1362:	 *
1363:	 * xc_push_seq is checked unlocked against the sequence number for a match.
1364:	 * Hence we can allow log forces to run racily and not issue pushes for the
1365:	 * same sequence twice.  If we get a race between multiple pushes for the same
1366:	 * sequence they will block on the first one and then abort, hence avoiding
1367:	 * needless pushes.
1368:	 *
1369:	 * This runs from a workqueue so it does not inherent any specific memory
1370:	 * allocation context. However, we do not want to block on memory reclaim
1371:	 * recursing back into the filesystem because this push may have been triggered
1372:	 * by memory reclaim itself. Hence we really need to run under full GFP_NOFS
1373:	 * contraints here.
1374:	 */
1375:	static void
1376:	xlog_cil_push_work(
1377:		struct work_struct	*work)
1378:	{
1379:		unsigned int		nofs_flags = memalloc_nofs_save();
1380:		struct xfs_cil_ctx	*ctx =
1381:			container_of(work, struct xfs_cil_ctx, push_work);
1382:		struct xfs_cil		*cil = ctx->cil;
1383:		struct xlog		*log = cil->xc_log;
1384:		struct xfs_cil_ctx	*new_ctx;
1385:		int			num_iovecs = 0;
1386:		int			num_bytes = 0;
1387:		int			error = 0;
1388:		struct xlog_cil_trans_hdr thdr;
1389:		struct xfs_log_vec	lvhdr = {};
1390:		xfs_csn_t		push_seq;
1391:		bool			push_commit_stable;
1392:		LIST_HEAD		(whiteouts);
1393:		struct xlog_ticket	*ticket;
1394:	
1395:		new_ctx = xlog_cil_ctx_alloc();
1396:		new_ctx->ticket = xlog_cil_ticket_alloc(log);
1397:	
1398:		down_write(&cil->xc_ctx_lock);
1399:	
1400:		spin_lock(&cil->xc_push_lock);
1401:		push_seq = cil->xc_push_seq;
1402:		ASSERT(push_seq <= ctx->sequence);
1403:		push_commit_stable = cil->xc_push_commit_stable;
1404:		cil->xc_push_commit_stable = false;
1405:	
1406:		/*
1407:		 * As we are about to switch to a new, empty CIL context, we no longer
1408:		 * need to throttle tasks on CIL space overruns. Wake any waiters that
1409:		 * the hard push throttle may have caught so they can start committing
1410:		 * to the new context. The ctx->xc_push_lock provides the serialisation
1411:		 * necessary for safely using the lockless waitqueue_active() check in
1412:		 * this context.
1413:		 */
1414:		if (waitqueue_active(&cil->xc_push_wait))
1415:			wake_up_all(&cil->xc_push_wait);
1416:	
1417:		xlog_cil_push_pcp_aggregate(cil, ctx);
1418:	
1419:		/*
1420:		 * Check if we've anything to push. If there is nothing, then we don't
1421:		 * move on to a new sequence number and so we have to be able to push
1422:		 * this sequence again later.
1423:		 */
1424:		if (test_bit(XLOG_CIL_EMPTY, &cil->xc_flags)) {
1425:			cil->xc_push_seq = 0;
1426:			spin_unlock(&cil->xc_push_lock);
1427:			goto out_skip;
1428:		}
1429:	
1430:	
1431:		/* check for a previously pushed sequence */
1432:		if (push_seq < ctx->sequence) {
1433:			spin_unlock(&cil->xc_push_lock);
1434:			goto out_skip;
1435:		}
1436:	
1437:		/*
1438:		 * We are now going to push this context, so add it to the committing
1439:		 * list before we do anything else. This ensures that anyone waiting on
1440:		 * this push can easily detect the difference between a "push in
1441:		 * progress" and "CIL is empty, nothing to do".
1442:		 *
1443:		 * IOWs, a wait loop can now check for:
1444:		 *	the current sequence not being found on the committing list;
1445:		 *	an empty CIL; and
1446:		 *	an unchanged sequence number
1447:		 * to detect a push that had nothing to do and therefore does not need
1448:		 * waiting on. If the CIL is not empty, we get put on the committing
1449:		 * list before emptying the CIL and bumping the sequence number. Hence
1450:		 * an empty CIL and an unchanged sequence number means we jumped out
1451:		 * above after doing nothing.
1452:		 *
1453:		 * Hence the waiter will either find the commit sequence on the
1454:		 * committing list or the sequence number will be unchanged and the CIL
1455:		 * still dirty. In that latter case, the push has not yet started, and
1456:		 * so the waiter will have to continue trying to check the CIL
1457:		 * committing list until it is found. In extreme cases of delay, the
1458:		 * sequence may fully commit between the attempts the wait makes to wait
1459:		 * on the commit sequence.
1460:		 */
1461:		list_add(&ctx->committing, &cil->xc_committing);
1462:		spin_unlock(&cil->xc_push_lock);
1463:	
1464:		xlog_cil_build_lv_chain(ctx, &whiteouts, &num_iovecs, &num_bytes);
1465:	
1466:		/*
1467:		 * Switch the contexts so we can drop the context lock and move out
1468:		 * of a shared context. We can't just go straight to the commit record,
1469:		 * though - we need to synchronise with previous and future commits so
1470:		 * that the commit records are correctly ordered in the log to ensure
1471:		 * that we process items during log IO completion in the correct order.
1472:		 *
1473:		 * For example, if we get an EFI in one checkpoint and the EFD in the
1474:		 * next (e.g. due to log forces), we do not want the checkpoint with
1475:		 * the EFD to be committed before the checkpoint with the EFI.  Hence
1476:		 * we must strictly order the commit records of the checkpoints so
1477:		 * that: a) the checkpoint callbacks are attached to the iclogs in the
1478:		 * correct order; and b) the checkpoints are replayed in correct order
1479:		 * in log recovery.
1480:		 *
1481:		 * Hence we need to add this context to the committing context list so
1482:		 * that higher sequences will wait for us to write out a commit record
1483:		 * before they do.
1484:		 *
1485:		 * xfs_log_force_seq requires us to mirror the new sequence into the cil
1486:		 * structure atomically with the addition of this sequence to the
1487:		 * committing list. This also ensures that we can do unlocked checks
1488:		 * against the current sequence in log forces without risking
1489:		 * deferencing a freed context pointer.
1490:		 */
1491:		spin_lock(&cil->xc_push_lock);
1492:		xlog_cil_ctx_switch(cil, new_ctx);
1493:		spin_unlock(&cil->xc_push_lock);
1494:		up_write(&cil->xc_ctx_lock);
1495:	
1496:		/*
1497:		 * Sort the log vector chain before we add the transaction headers.
1498:		 * This ensures we always have the transaction headers at the start
1499:		 * of the chain.
1500:		 */
1501:		list_sort(NULL, &ctx->lv_chain, xlog_cil_order_cmp);
1502:	
1503:		/*
1504:		 * Build a checkpoint transaction header and write it to the log to
1505:		 * begin the transaction. We need to account for the space used by the
1506:		 * transaction header here as it is not accounted for in xlog_write().
1507:		 * Add the lvhdr to the head of the lv chain we pass to xlog_write() so
1508:		 * it gets written into the iclog first.
1509:		 */
1510:		xlog_cil_build_trans_hdr(ctx, &thdr, &lvhdr, num_iovecs);
1511:		num_bytes += lvhdr.lv_bytes;
1512:		list_add(&lvhdr.lv_list, &ctx->lv_chain);
1513:	
1514:		/*
1515:		 * Take the lvhdr back off the lv_chain immediately after calling
1516:		 * xlog_cil_write_chain() as it should not be passed to log IO
1517:		 * completion.
1518:		 */
1519:		error = xlog_cil_write_chain(ctx, num_bytes);
1520:		list_del(&lvhdr.lv_list);
1521:		if (error)
1522:			goto out_abort_free_ticket;
1523:	
1524:		error = xlog_cil_write_commit_record(ctx);
1525:		if (error)
1526:			goto out_abort_free_ticket;
1527:	
1528:		/*
1529:		 * Grab the ticket from the ctx so we can ungrant it after releasing the
1530:		 * commit_iclog. The ctx may be freed by the time we return from
1531:		 * releasing the commit_iclog (i.e. checkpoint has been completed and
1532:		 * callback run) so we can't reference the ctx after the call to
1533:		 * xlog_state_release_iclog().
1534:		 */
1535:		ticket = ctx->ticket;
1536:	
1537:		/*
1538:		 * If the checkpoint spans multiple iclogs, wait for all previous iclogs
1539:		 * to complete before we submit the commit_iclog. We can't use state
1540:		 * checks for this - ACTIVE can be either a past completed iclog or a
1541:		 * future iclog being filled, while WANT_SYNC through SYNC_DONE can be a
1542:		 * past or future iclog awaiting IO or ordered IO completion to be run.
1543:		 * In the latter case, if it's a future iclog and we wait on it, the we
1544:		 * will hang because it won't get processed through to ic_force_wait
1545:		 * wakeup until this commit_iclog is written to disk.  Hence we use the
1546:		 * iclog header lsn and compare it to the commit lsn to determine if we
1547:		 * need to wait on iclogs or not.
1548:		 */
1549:		spin_lock(&log->l_icloglock);
1550:		if (ctx->start_lsn != ctx->commit_lsn) {
1551:			xfs_lsn_t	plsn = be64_to_cpu(
1552:				ctx->commit_iclog->ic_prev->ic_header->h_lsn);
1553:	
1554:			if (plsn && XFS_LSN_CMP(plsn, ctx->commit_lsn) < 0) {
1555:				/*
1556:				 * Waiting on ic_force_wait orders the completion of
1557:				 * iclogs older than ic_prev. Hence we only need to wait
1558:				 * on the most recent older iclog here.
1559:				 */
1560:				xlog_wait_on_iclog(log, ctx->commit_iclog->ic_prev);
1561:				spin_lock(&log->l_icloglock);
1562:			}
1563:	
1564:			/*
1565:			 * We need to issue a pre-flush so that the ordering for this
1566:			 * checkpoint is correctly preserved down to stable storage.
1567:			 */
1568:			ctx->commit_iclog->ic_flags |= XLOG_ICL_NEED_FLUSH;
1569:		}
1570:	
1571:		/*
1572:		 * The commit iclog must be written to stable storage to guarantee
1573:		 * journal IO vs metadata writeback IO is correctly ordered on stable
1574:		 * storage.
1575:		 *
1576:		 * If the push caller needs the commit to be immediately stable and the
1577:		 * commit_iclog is not yet marked as XLOG_STATE_WANT_SYNC to indicate it
1578:		 * will be written when released, switch it's state to WANT_SYNC right
1579:		 * now.
1580:		 */
1581:		ctx->commit_iclog->ic_flags |= XLOG_ICL_NEED_FUA;
1582:		if (push_commit_stable &&
1583:		    ctx->commit_iclog->ic_state == XLOG_STATE_ACTIVE)
1584:			xlog_state_switch_iclogs(log, ctx->commit_iclog, 0);
1585:		ticket = ctx->ticket;
1586:		xlog_state_release_iclog(log, ctx->commit_iclog, ticket);
1587:	
1588:		/* Not safe to reference ctx now! */
1589:	
1590:		spin_unlock(&log->l_icloglock);
1591:		xlog_cil_cleanup_whiteouts(&whiteouts);
1592:		xfs_log_ticket_ungrant(log, ticket);
1593:		memalloc_nofs_restore(nofs_flags);
1594:		return;
1595:	
1596:	out_skip:
1597:		up_write(&cil->xc_ctx_lock);
1598:		xfs_log_ticket_put(new_ctx->ticket);
1599:		kfree(new_ctx);
1600:		memalloc_nofs_restore(nofs_flags);
1601:		return;
1602:	
1603:	out_abort_free_ticket:
1604:		ASSERT(xlog_is_shutdown(log));
1605:		xlog_cil_cleanup_whiteouts(&whiteouts);
1606:		if (!ctx->commit_iclog) {
1607:			xfs_log_ticket_ungrant(log, ctx->ticket);
1608:			xlog_cil_committed(ctx);
1609:			memalloc_nofs_restore(nofs_flags);
1610:			return;
1611:		}
1612:		spin_lock(&log->l_icloglock);
1613:		ticket = ctx->ticket;
1614:		xlog_state_release_iclog(log, ctx->commit_iclog, ticket);
1615:		/* Not safe to reference ctx now! */
1616:		spin_unlock(&log->l_icloglock);
1617:		xfs_log_ticket_ungrant(log, ticket);
1618:		memalloc_nofs_restore(nofs_flags);
1619:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

148/2 2026/09/19 00:53 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 35972
							output: 43
							thoughts: 0
						

149/2 2026/09/19 00:53 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_committed]

Results:
map[SourceCode: 969:	/*
 970:	 * Mark all items committed and clear busy extents. We free the log vector
 971:	 * chains in a separate pass so that we unpin the log items as quickly as
 972:	 * possible.
 973:	 */
 974:	static void
 975:	xlog_cil_committed(
 976:		struct xfs_cil_ctx	*ctx)
 977:	{
 978:		struct xfs_mount	*mp = ctx->cil->xc_log->l_mp;
 979:		bool			abort = xlog_is_shutdown(ctx->cil->xc_log);
 980:	
 981:		/*
 982:		 * If the I/O failed, we're aborting the commit and already shutdown.
 983:		 * Wake any commit waiters before aborting the log items so we don't
 984:		 * block async log pushers on callbacks. Async log pushers explicitly do
 985:		 * not wait on log force completion because they may be holding locks
 986:		 * required to unpin items.
 987:		 */
 988:		if (abort) {
 989:			spin_lock(&ctx->cil->xc_push_lock);
 990:			wake_up_all(&ctx->cil->xc_start_wait);
 991:			wake_up_all(&ctx->cil->xc_commit_wait);
 992:			spin_unlock(&ctx->cil->xc_push_lock);
 993:		}
 994:	
 995:		xlog_cil_ail_insert(ctx, abort);
 996:	
 997:		xfs_extent_busy_sort(&ctx->busy_extents.extent_list);
 998:		xfs_extent_busy_clear(&ctx->busy_extents.extent_list,
 999:				      xfs_has_discard(mp) && !abort);
1000:	
1001:		spin_lock(&ctx->cil->xc_push_lock);
1002:		list_del(&ctx->committing);
1003:		spin_unlock(&ctx->cil->xc_push_lock);
1004:	
1005:		xlog_cil_free_logvec(&ctx->lv_chain);
1006:	
1007:		if (!list_empty(&ctx->busy_extents.extent_list)) {
1008:			ctx->busy_extents.owner = ctx;
1009:			xfs_discard_extents(mp, &ctx->busy_extents);
1010:			return;
1011:		}
1012:	
1013:		kfree(ctx);
1014:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

150/2 2026/09/19 00:53 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 36786
							output: 48
							thoughts: 0
						

151/2 2026/09/19 00:53 tool codesearch-definition-source
0m Args:
map[ContextFile:fs/xfs/xfs_log_cil.c Name:xlog_cil_push_pcp_aggregate]

Results:
map[SourceCode: 112:	/*
 113:	 * Aggregate the CIL per cpu structures into global counts, lists, etc and
 114:	 * clear the percpu state ready for the next context to use. This is called
 115:	 * from the push code with the context lock held exclusively, hence nothing else
 116:	 * will be accessing or modifying the per-cpu counters.
 117:	 */
 118:	static void
 119:	xlog_cil_push_pcp_aggregate(
 120:		struct xfs_cil		*cil,
 121:		struct xfs_cil_ctx	*ctx)
 122:	{
 123:		struct xlog_cil_pcp	*cilpcp;
 124:		int			cpu;
 125:	
 126:		for_each_cpu(cpu, &ctx->cil_pcpmask) {
 127:			cilpcp = per_cpu_ptr(cil->xc_pcp, cpu);
 128:	
 129:			ctx->ticket->t_curr_res += cilpcp->space_reserved;
 130:			cilpcp->space_reserved = 0;
 131:	
 132:			if (!list_empty(&cilpcp->busy_extents)) {
 133:				list_splice_init(&cilpcp->busy_extents,
 134:						&ctx->busy_extents.extent_list);
 135:			}
 136:			if (!list_empty(&cilpcp->log_items))
 137:				list_splice_init(&cilpcp->log_items, &ctx->log_items);
 138:	
 139:			/*
 140:			 * We're in the middle of switching cil contexts.  Reset the
 141:			 * counter we use to detect when the current context is nearing
 142:			 * full.
 143:			 */
 144:			cilpcp->space_used = 0;
 145:		}
 146:	}
 SourceFile:fs/xfs/xfs_log_cil.c]

152/2 2026/09/19 00:53 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 37420
							output: 66
							thoughts: 0
						

153/2 2026/09/19 00:53 tool set-results
0m Args:
map[DenialOfService:true Exploitable:true FilesystemTrigger:false NetworkTrigger:false PeripheralTrigger:false RemoteTrigger:false Unprivileged:false UserNamespace:false VMGuestTrigger:false VMHostTrigger:false]

Results:
map[DenialOfService:true Exploitable:true FilesystemTrigger:false NetworkTrigger:false PeripheralTrigger:false RemoteTrigger:false Unprivileged:false UserNamespace:false VMGuestTrigger:false VMHostTrigger:false]

154/2 2026/09/19 00:53 llm expert
0m Model:
gemini-3.1-pro-preview

Tokens:
							input: 37550
							output: 562
							thoughts: 421
						

Thoughts:
**My Analysis of the XFS Slab-Use-After-Free Bug**

Okay, so I've been digging into this XFS bug and here's what I've got: It's a nasty use-after-free vulnerability, specifically within the `xlog_cil_push_pcp_aggregate` function. The core issue lies in how the `cilpcp->log_items` list is handled, and it's a classic case of freeing a buffer item while it's still actively referenced.

The root cause is `xfs_buf_item_relse`, which, crucially, frees the `xfs_buf_log_item` before it's been properly aggregated by the CIL push mechanism. This happens during a transaction commit, specifically when `xfs_sync_sb_buf` is called. The superblock buffer I/O completes, `xfs_buf_ioend` kicks in, and `xfs_buf_item_done` removes the item from the AIL, and importantly, calls `xfs_buf_item_relse`. The problem? This item was *just* added to the per-CPU log items list during the transaction commit but hasn't been aggregated by the CIL push yet. Boom. Freeing the item prematurely.

In terms of exploitability, it's a slab-use-after-free, a write due to the list manipulation, which means it’s ripe for memory corruption. We're looking at potentially arbitrary code execution if an attacker can control the freed memory region and how it's reallocated. Even without full control, the crash is definitely a denial-of-service vector.

Now, about reachability. The trigger is the `xfs_ioc_setlabel` ioctl, which in turn calls `xfs_sync_sb_buf`. However, this ioctl is gated behind `capable(CAP_SYS_ADMIN)`. This is where it gets interesting, since the capability check is done in the initial user namespace. This restricts access to privileged users in that namespace, meaning this isn't reachable from unprivileged processes or user namespaces. It's also not triggered by network, peripherals, remote inputs, or automatically when mounting a malicious filesystem. So, at least for now, it seems this is isolated to root users within the initial user namespace who are explicitly calling this ioctl. It doesn't appear to be a wormable or easily triggered remote issue, but still a serious vulnerability.



155/1 2026/09/19 00:53 action format-explanation
0m Results:
map[Explanation:**Bug Mechanism and Impact**
The bug is a slab-use-after-free write in the XFS filesystem's Committed Item
List (CIL) push worker. It occurs when `xfs_sync_sb_buf` commits a transaction
that logs the superblock buffer and then immediately issues a synchronous write
(`xfs_bwrite`) on the same buffer.

When the transaction commits, the buffer's log item is added to a per-CPU list
(`cilpcp->log_items`) to be processed by a background CIL push. However, the
immediate `xfs_bwrite` causes the buffer's I/O completion routine
(`xfs_buf_ioend`) to run. This routine sees the attached log item, removes it
from the Active Item List (AIL), and releases it (`xfs_buf_item_relse`), which
frees the `xfs_buf_log_item` structure back to the slab allocator.

Later, when the background CIL push worker (`xlog_cil_push_work`) aggregates the
per-CPU lists via `xlog_cil_push_pcp_aggregate`, it attempts to splice the freed
log item's `li_cil` list node (`list_splice_init`), resulting in a
use-after-free write.

Because this is a use-after-free write involving linked list pointers
(`__list_splice`), it can be used to corrupt slab metadata or overwrite
arbitrary kernel pointers, making it theoretically **Exploitable** for privilege
escalation or arbitrary code execution. It also trivially causes a kernel panic,
leading to a **Denial of Service**.

**Reachability Analysis**
Despite the severe memory corruption, the bug is highly restricted in its
reachability:
- The only caller of `xfs_sync_sb_buf` in the kernel is the `XFS_IOC_SETLABEL`
ioctl (`xfs_ioc_setlabel`).
- The `xfs_ioc_setlabel` function explicitly enforces a capability check at its
entry point: `if (!capable(CAP_SYS_ADMIN)) return -EPERM;`.
- The `capable()` function checks for capabilities in the *initial* user
namespace (unlike `ns_capable()`).
- Therefore, this bug is **not accessible from unprivileged processes** and
**not accessible from user namespaces**.
- The bug requires an explicit ioctl call from a highly privileged process (root
in the init namespace) and is not triggered automatically during mount, meaning
it cannot be exploited via a **Malicious Filesystem Trigger**.
- It is not exposed to **Network**, **Remote**, or **Peripheral** attack
vectors.]

LLM Calls Summary:
Total Calls Total Tokens Avg Tokens Total Duration (Seconds) Avg Duration (Seconds)
Tool Calls Summary:
Total Calls Total Duration (Seconds) Avg Duration (Seconds)