ID Workflow Result Correct Bug Created Started Finished Revision
05f5e79f assessment-security DenialOfService: ❌ Exploitable: ❌ FilesystemTrigger: ❌ FuzzingArtifact: ❌ MemoryCorruption: ❌ NetworkNeedsSetup: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: βœ… UserNamespace: βœ… VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ KCSAN: data-race in dentry_kill / lockref_get_not_dead 2026/11/17 06:13 2026/11/17 06:13 2026/11/17 06:22 a3e64cfc
Agent: prod-syz-agent-5
External Bug ID: ---

Inputs:
BaseBranch master
BaseCommit RC
BaseRepository git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
BugTitle KCSAN: data-race in dentry_kill / lockref_get_not_dead
CrashCommit 666539eecdf4db623f5e3c3e55cf9f2dfad24aa4
CrashLogID 4767864663310336
CrashReportID 6521910881419264
KernelCommit 666539eecdf4db623f5e3c3e55cf9f2dfad24aa4
KernelConfig
Show (266103 bytes)
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 syzkaller Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="Debian clang version 22.1.8 (1~deb13u4)"
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_OPT_ZERO_INIT_PADDING_BITS=""
CONFIG_CC_OPT_NO_ADDRSIG="-fno-addrsig"
CONFIG_CC_OPT_DIAGNOSTICS_SHOW_CONTEXT=""
CONFIG_CC_OPT_DIAGNOSTICS_SHOW_INLINING_CHAIN=""
CONFIG_CC_OPT_STRICT_FLEX_ARRAYS="-fstrict-flex-arrays=3"
CONFIG_CC_OPT_ALLOW_STORE_DATA_RACES_PARAM=""
CONFIG_CC_OPT_NO_ALLOW_STORE_DATA_RACES=""
CONFIG_LD_OPT_FORCE_GROUP_ALLOCATION="--force-group-allocation"
CONFIG_LD_OPT_NO_WARN_RWX_SEGMENTS=""
CONFIG_CC_OPT_WNO_ADDRESS_OF_PACKED_MEMBER="-Wno-address-of-packed-member"
CONFIG_CC_OPT_WNO_FORMAT_OVERFLOW_NON_KPRINTF="-Wno-format-overflow-non-kprintf"
CONFIG_CC_OPT_WNO_FORMAT_TRUNCATION_NON_KPRINTF="-Wno-format-truncation-non-kprintf"
CONFIG_CC_OPT_WNO_DEFAULT_CONST_INIT_UNSAFE="-Wno-default-const-init-unsafe"
CONFIG_CC_OPT_WNO_DANGLING_POINTER=""
CONFIG_CC_OPT_WVLA_LARGER_THAN=""
CONFIG_CC_OPT_WNO_UNTERMINATED_STRING_INITIALIZATION="-Wno-unterminated-string-initialization"
CONFIG_CC_OPT_WERROR_DESIGNATED_INIT=""
CONFIG_CC_OPT_WENUM_CONVERSION="-Wenum-conversion"
CONFIG_CC_OPT_WNO_PACKED_NOT_ALIGNED=""
CONFIG_CC_OPT_WNO_FORMAT_OVERFLOW="-Wno-format-overflow"
CONFIG_CC_OPT_WNO_STRINGOP_TRUNCATION=""
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_CC_OPT_INLINE_MEMSET="-mllvm -max-store-memset=4294967294"
CONFIG_LD_CAN_USE_KEEP_IN_OVERLAY=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 is not set
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_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
# CONFIG_POSIX_AUX_CLOCKS is not set
# end of Timers subsystem

CONFIG_BPF=y
CONFIG_HAVE_EBPF_JIT=y
CONFIG_HAVE_EBPF_JIT_KASAN=y
CONFIG_ARCH_WANT_DEFAULT_BPF_JIT=y

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

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

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
# CONFIG_PSI 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_DEFER=y
# end of RCU Subsystem

# CONFIG_IKCONFIG is not set
# 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
# CONFIG_SCHED_PROXY_EXEC 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_NUMA_BALANCING is not set
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_FAIR_GROUP_SCHED=y
# CONFIG_CFS_BANDWIDTH is not set
# 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 is not set
# 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 is not set
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 is not set
CONFIG_ADVISE_SYSCALLS=y
CONFIG_MEMBARRIER=y
CONFIG_KCMP=y
CONFIG_RSEQ=y
# CONFIG_RSEQ_SLICE_EXTENSION is not set
# 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

#
# 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_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_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 is not set
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_RUSTC_HAS_APXF=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_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_PROC_KCORE_TEXT=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
# CONFIG_X86_PMEM_LEGACY is not set
CONFIG_X86_CHECK_BIOS_CORRUPTION=y
CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y
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 is not set
# CONFIG_X86_USER_SHADOW_STACK 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"
# 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_CC_OPT_INDIRECT_BRANCH_CS_PREFIX="-mindirect-branch-cs-prefix"
CONFIG_CC_OPT_CF_PROTECTION_NONE="-fcf-protection=none"
CONFIG_CC_OPT_CF_PROTECTION_BRANCH="-fcf-protection=branch -fno-jump-tables"
CONFIG_CC_OPT_FALIGN_JUMPS=""
CONFIG_CC_OPT_FALIGN_LOOPS="-falign-loops=1"
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_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_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_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 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 is not set
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_VIRTUALIZATION=y
# CONFIG_KVM is not set
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_SYSFAST32=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_ENQCMD=y
CONFIG_X86_DISABLED_FEATURE_SGX=y
CONFIG_X86_DISABLED_FEATURE_XENPV=y
CONFIG_X86_DISABLED_FEATURE_TDX_GUEST=y
CONFIG_X86_DISABLED_FEATURE_USER_SHSTK=y
CONFIG_X86_DISABLED_FEATURE_FRED=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_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_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_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_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_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_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 is not set
# CONFIG_MODULE_SIG is not set
# 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_DEV_BSG_COMMON=y
CONFIG_BLK_DEV_BSGLIB=y
# CONFIG_BLK_DEV_INTEGRITY is not set
# CONFIG_BLK_DEV_WRITE_MOUNTED is not set
# CONFIG_BLK_DEV_ZONED is not set
# CONFIG_BLK_DEV_THROTTLING is not set
# CONFIG_BLK_WBT is not set
CONFIG_BLK_CGROUP_IOLATENCY=y
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 is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_EFI_PARTITION=y
# 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 is not set
# end of IO Schedulers

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_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 is not set

#
# 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_VMEMMAP_OPTIMIZATION=y
CONFIG_ARCH_WANT_OPTIMIZE_DAX_VMEMMAP=y
CONFIG_ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP=y
CONFIG_HAVE_GUP_FAST=y
CONFIG_EXCLUSIVE_SYSTEM_RAM=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
# CONFIG_MEMORY_HOTPLUG is not set
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_COMPACTION=y
CONFIG_COMPACT_UNEVICTABLE_DEFAULT=1
# CONFIG_PAGE_REPORTING is not set
CONFIG_NUMA_MIGRATION=y
CONFIG_MIGRATION=y
CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=y
CONFIG_PCP_BATCH_SCALE_MAX=5
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_MMU_NOTIFIER=y
# CONFIG_KSM is not set
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_TRANSPARENT_HUGEPAGE is not set
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 is not set
CONFIG_PAGE_BLOCK_MAX_ORDER=10
CONFIG_GENERIC_EARLY_IOREMAP=y
# CONFIG_DEFERRED_STRUCT_PAGE_INIT is not set
# 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_HMM_MIRROR=y
CONFIG_VMAP_PFN=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 is not set
# CONFIG_GUP_TEST is not set
# CONFIG_DMAPOOL_TEST is not set
CONFIG_ARCH_HAS_PTE_SPECIAL=y
CONFIG_MEMFD_CREATE=y
CONFIG_SECRETMEM=y
# CONFIG_ANON_VMA_NAME is not set
# CONFIG_USERFAULTFD is not set
CONFIG_LRU_GEN=y
CONFIG_LRU_GEN_ENABLED=y
# CONFIG_LRU_GEN_STATS is not set
CONFIG_LRU_GEN_WALKS_MMU=y
CONFIG_LOCK_MM_AND_FIND_VMA=y
CONFIG_IOMMU_MM_DATA=y
CONFIG_EXECMEM=y
CONFIG_NUMA_MEMBLKS=y
# CONFIG_NUMA_EMU is not set
CONFIG_PT_RECLAIM=y
CONFIG_ARCH_HAS_CHECK_WX=y
CONFIG_CHECK_WX=y
CONFIG_ARCH_HAS_PTDUMP=y
CONFIG_PTDUMP=y

#
# Data Access Monitoring
#
# CONFIG_DAMON 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_ROCCET is not set
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
CONFIG_NETFILTER_XTABLES_LEGACY=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=y
CONFIG_NETFILTER_XT_TARGET_DSCP=y
CONFIG_NETFILTER_XT_TARGET_HL=y
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=y
CONFIG_NETFILTER_XT_TARGET_NFLOG=y
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=y
CONFIG_NETFILTER_XT_TARGET_NOTRACK=y
CONFIG_NETFILTER_XT_TARGET_RATEEST=y
CONFIG_NETFILTER_XT_TARGET_REDIRECT=y
CONFIG_NETFILTER_XT_TARGET_MASQUERADE=y
CONFIG_NETFILTER_XT_TARGET_TEE=y
CONFIG_NETFILTER_XT_TARGET_TPROXY=y
CONFIG_NETFILTER_XT_TARGET_TRACE=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_IP_NF_IPTABLES_LEGACY=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_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_SYNPROXY=y
CONFIG_IP_NF_NAT=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
CONFIG_IP_NF_TARGET_NETMAP=y
CONFIG_IP_NF_TARGET_REDIRECT=y
CONFIG_IP_NF_MANGLE=y
CONFIG_IP_NF_TARGET_ECN=y
CONFIG_IP_NF_TARGET_TTL=y
CONFIG_IP_NF_RAW=y
CONFIG_IP_NF_SECURITY=y
CONFIG_IP_NF_ARPTABLES=y
CONFIG_NFT_COMPAT_ARP=y
CONFIG_IP_NF_ARPFILTER=y
CONFIG_IP_NF_ARP_MANGLE=y
# end of IP: Netfilter Configuration

#
# IPv6: Netfilter Configuration
#
CONFIG_IP6_NF_IPTABLES_LEGACY=y
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_HL=y
CONFIG_IP6_NF_FILTER=y
CONFIG_IP6_NF_TARGET_REJECT=y
CONFIG_IP6_NF_TARGET_SYNPROXY=y
CONFIG_IP6_NF_MANGLE=y
CONFIG_IP6_NF_RAW=y
CONFIG_IP6_NF_SECURITY=y
CONFIG_IP6_NF_NAT=y
CONFIG_IP6_NF_TARGET_MASQUERADE=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_LEGACY=y
CONFIG_BRIDGE_NF_EBTABLES=y
CONFIG_BRIDGE_EBT_BROUTE=y
CONFIG_BRIDGE_EBT_T_FILTER=y
CONFIG_BRIDGE_EBT_T_NAT=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_KS8995 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_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_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_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_NET_RX_BUSY_POLL=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 is not set
# CONFIG_BT_BNEP is not set
CONFIG_BT_HIDP=y
# CONFIG_BT_LE is not set
# CONFIG_BT_LEDS is not set
# CONFIG_BT_MSFTEXT is not set
# CONFIG_BT_AOSPEXT is not set
# CONFIG_BT_DEBUGFS is not set
# CONFIG_BT_SELFTEST is not set
# CONFIG_BT_FEATURE_DEBUG is not set

#
# Bluetooth device drivers
#
CONFIG_BT_INTEL=y
CONFIG_BT_BCM=y
CONFIG_BT_RTL=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_HCIBTUSB_QCOM is not set
# 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 is not set
# CONFIG_BT_HCIUART_ATH3K is not set
# CONFIG_BT_HCIUART_LL is not set
# CONFIG_BT_HCIUART_3WIRE is not set
# CONFIG_BT_HCIUART_INTEL is not set
# CONFIG_BT_HCIUART_RTL is not set
# CONFIG_BT_HCIUART_QCA is not set
# CONFIG_BT_HCIUART_AG6XX is not set
# CONFIG_BT_HCIUART_MRVL is not set
# 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 is not set
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_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 is not set
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 is not set
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_VSOCK is not set
# 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 is not set
# CONFIG_PCIEAER 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_PTM is not set
CONFIG_PCI_MSI=y
CONFIG_PCI_QUIRKS=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not set
CONFIG_PCI_ATS=y
CONFIG_PCI_IDE=y
CONFIG_PCI_TSM=y
CONFIG_PCI_DOE=y
CONFIG_PCI_ECAM=y
CONFIG_PCI_LOCKLESS_CONFIG=y
# CONFIG_PCI_IOV is not set
# CONFIG_PCI_NPEM is not set
CONFIG_PCI_PRI=y
CONFIG_PCI_PASID=y
# CONFIG_PCIE_TPH 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
# 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
# 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 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_EXTRA_FIRMWARE=""
# CONFIG_FW_LOADER_USER_HELPER is not set
# CONFIG_FW_LOADER_COMPRESS 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 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_SIMPLEFB is not set
# CONFIG_COREBOOT_FIRMWARE is not set

#
# Qualcomm firmware drivers
#
# 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 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 is not set
# CONFIG_BLK_DEV_FD is not set
CONFIG_CDROM=y
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
# CONFIG_ZRAM is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_VIRTIO_BLK=y
# CONFIG_BLK_DEV_RBD is not set
# CONFIG_BLK_DEV_UBLK is not set
# CONFIG_BLK_DEV_RNBD_CLIENT is not set

#
# NVME Support
#
# CONFIG_BLK_DEV_NVME is not set
# CONFIG_NVME_RDMA is not set
# CONFIG_NVME_FC is not set
# CONFIG_NVME_TCP is not set
# CONFIG_NVME_TARGET 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_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_GSC is not set
# CONFIG_INTEL_MEI_CSC is not set
# CONFIG_INTEL_MEI_VSC_HW is not set
# CONFIG_INTEL_MEI_HDCP is not set
# CONFIG_INTEL_MEI_PXP is not set
# CONFIG_INTEL_MEI_GSC_PROXY is not set
# CONFIG_VMWARE_VMCI is not set
# 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 is not set
CONFIG_SCSI_COMMON=y
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
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 is not set
# CONFIG_SCSI_SCAN_ASYNC is not set

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
# CONFIG_SCSI_FC_ATTRS is not set
CONFIG_SCSI_ISCSI_ATTRS=y
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS 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 is not set
# 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_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_ISCSI 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_VIRTIO=y
# 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_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 is not set
# 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 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_BCACHE is not set
CONFIG_BLK_DEV_DM_BUILTIN=y
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
# CONFIG_DM_UNSTRIPED is not set
# CONFIG_DM_CRYPT is not set
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_THIN_PROVISIONING is not set
# CONFIG_DM_CACHE is not set
# CONFIG_DM_WRITECACHE is not set
# CONFIG_DM_EBS is not set
# CONFIG_DM_ERA is not set
# CONFIG_DM_CLONE is not set
CONFIG_DM_MIRROR=y
# CONFIG_DM_LOG_USERSPACE is not set
# CONFIG_DM_RAID is not set
CONFIG_DM_ZERO=y
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_DUST is not set
# CONFIG_DM_INIT is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_DM_FLAKEY is not set
# CONFIG_DM_VERITY is not set
# CONFIG_DM_SWITCH is not set
# CONFIG_DM_LOG_WRITES is not set
# CONFIG_DM_INTEGRITY is not set
# CONFIG_DM_AUDIT is not set
# 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_REMOTE_TARGET is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_FIREWIRE_NOSY is not set
# end of IEEE 1394 (FireWire) support

CONFIG_MACINTOSH_DRIVERS=y
CONFIG_MAC_EMUMOUSEBTN=y
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_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_YT921X 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
# 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_MPNIC 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_NEBULA_MATRIX=y
# CONFIG_NBL 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_XPOWERS_ACX00_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=y
# 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_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 is not set
# CONFIG_ATH9K_AHB is not set
CONFIG_ATH9K_DEBUGFS=y
# CONFIG_ATH9K_STATION_STATISTICS is not set
# CONFIG_ATH9K_DYNACK is not set
# CONFIG_ATH9K_WOW is not set
# CONFIG_ATH9K_RFKILL is not set
# CONFIG_ATH9K_CHANNEL_CONTEXT is not set
# CONFIG_ATH9K_PCOEM 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 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 is not set
# CONFIG_ATH12K is not set
CONFIG_WLAN_VENDOR_ATMEL=y
CONFIG_AT76C50X_USB=y
CONFIG_WLAN_VENDOR_BROADCOM=y
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
CONFIG_BRCMUTIL=y
# CONFIG_BRCMSMAC is not set
CONFIG_BRCMFMAC=y
CONFIG_BRCMFMAC_PROTO_BCDC=y
# CONFIG_BRCMFMAC_SDIO is not set
CONFIG_BRCMFMAC_USB=y
# CONFIG_BRCMFMAC_PCIE is not set
# CONFIG_BRCM_TRACING is not set
# CONFIG_BRCMDBG is not set
CONFIG_WLAN_VENDOR_INTEL=y
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_IWL4965 is not set
# CONFIG_IWL3945 is not set
# CONFIG_IWLWIFI is not set
CONFIG_WLAN_VENDOR_INTERSIL=y
CONFIG_P54_COMMON=y
CONFIG_P54_USB=y
# CONFIG_P54_PCI is not set
# CONFIG_P54_SPI is not set
CONFIG_P54_LEDS=y
CONFIG_WLAN_VENDOR_MARVELL=y
CONFIG_LIBERTAS=y
CONFIG_LIBERTAS_USB=y
CONFIG_LIBERTAS_SDIO=y
CONFIG_LIBERTAS_SPI=y
# CONFIG_LIBERTAS_DEBUG is not set
CONFIG_LIBERTAS_MESH=y
CONFIG_LIBERTAS_THINFIRM=y
# CONFIG_LIBERTAS_THINFIRM_DEBUG is not set
CONFIG_LIBERTAS_THINFIRM_USB=y
CONFIG_MWIFIEX=y
# CONFIG_MWIFIEX_SDIO is not set
# CONFIG_MWIFIEX_PCIE is not set
CONFIG_MWIFIEX_USB=y
# CONFIG_MWL8K is not set
CONFIG_WLAN_VENDOR_MEDIATEK=y
CONFIG_MT7601U=y
CONFIG_MT76_CORE=y
CONFIG_MT76_LEDS=y
CONFIG_MT76_USB=y
CONFIG_MT76x02_LIB=y
CONFIG_MT76x02_USB=y
CONFIG_MT76_CONNAC_LIB=y
CONFIG_MT792x_LIB=y
CONFIG_MT792x_USB=y
CONFIG_MT76x0_COMMON=y
CONFIG_MT76x0U=y
# CONFIG_MT76x0E is not set
CONFIG_MT76x2_COMMON=y
# CONFIG_MT76x2E is not set
CONFIG_MT76x2U=y
# CONFIG_MT7603E is not set
CONFIG_MT7615_COMMON=y
# CONFIG_MT7615E is not set
CONFIG_MT7663_USB_SDIO_COMMON=y
CONFIG_MT7663U=y
# CONFIG_MT7663S is not set
# CONFIG_MT7915E is not set
CONFIG_MT7921_COMMON=y
# CONFIG_MT7921E is not set
# CONFIG_MT7921S is not set
CONFIG_MT7921U=y
# CONFIG_MT7996E is not set
CONFIG_MT7925_COMMON=y
# CONFIG_MT7925E is not set
CONFIG_MT7925U=y
CONFIG_WLAN_VENDOR_MICROCHIP=y
CONFIG_WILC1000=y
CONFIG_WILC1000_SDIO=y
# CONFIG_WILC1000_SPI is not set
# CONFIG_WILC1000_HW_OOB_INTR 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=y
CONFIG_RT2X00=y
# CONFIG_RT2400PCI is not set
# CONFIG_RT2500PCI is not set
# CONFIG_RT61PCI is not set
# CONFIG_RT2800PCI is not set
CONFIG_RT2500USB=y
CONFIG_RT73USB=y
CONFIG_RT2800USB=y
CONFIG_RT2800USB_RT33XX=y
CONFIG_RT2800USB_RT35XX=y
CONFIG_RT2800USB_RT3573=y
CONFIG_RT2800USB_RT53XX=y
CONFIG_RT2800USB_RT55XX=y
CONFIG_RT2800USB_UNKNOWN=y
CONFIG_RT2800_LIB=y
CONFIG_RT2X00_LIB_USB=y
CONFIG_RT2X00_LIB=y
CONFIG_RT2X00_LIB_FIRMWARE=y
CONFIG_RT2X00_LIB_CRYPTO=y
CONFIG_RT2X00_LIB_LEDS=y
# CONFIG_RT2X00_LIB_DEBUGFS is not set
# CONFIG_RT2X00_DEBUG is not set
CONFIG_WLAN_VENDOR_REALTEK=y
# CONFIG_RTL8180 is not set
CONFIG_RTL8187=y
CONFIG_RTL8187_LEDS=y
CONFIG_RTL_CARDS=y
CONFIG_RTL8192CE=y
CONFIG_RTL8192SE=y
CONFIG_RTL8192DE=y
CONFIG_RTL8723AE=y
CONFIG_RTL8723BE=y
CONFIG_RTL8188EE=y
CONFIG_RTL8192EE=y
CONFIG_RTL8821AE=y
CONFIG_RTL8192CU=y
# CONFIG_RTL8192DU is not set
CONFIG_RTLWIFI=y
CONFIG_RTLWIFI_PCI=y
CONFIG_RTLWIFI_USB=y
# CONFIG_RTLWIFI_DEBUG is not set
CONFIG_RTL8192C_COMMON=y
CONFIG_RTL8192D_COMMON=y
CONFIG_RTL8723_COMMON=y
CONFIG_RTLBTCOEXIST=y
CONFIG_RTL8XXXU=y
CONFIG_RTL8XXXU_UNTESTED=y
CONFIG_RTW88=y
CONFIG_RTW88_CORE=y
CONFIG_RTW88_USB=y
CONFIG_RTW88_8822B=y
CONFIG_RTW88_8822C=y
CONFIG_RTW88_8723X=y
CONFIG_RTW88_8723D=y
CONFIG_RTW88_8821C=y
# CONFIG_RTW88_8822BE is not set
# CONFIG_RTW88_8822BS is not set
CONFIG_RTW88_8822BU=y
# CONFIG_RTW88_8822CE is not set
# CONFIG_RTW88_8822CS is not set
CONFIG_RTW88_8822CU=y
# CONFIG_RTW88_8723DE is not set
# CONFIG_RTW88_8723DS is not set
# CONFIG_RTW88_8723CS is not set
# CONFIG_RTW88_8723BS is not set
CONFIG_RTW88_8723DU=y
# CONFIG_RTW88_8821CE is not set
# CONFIG_RTW88_8821CS is not set
CONFIG_RTW88_8821CU=y
# CONFIG_RTW88_8821AU is not set
# CONFIG_RTW88_8812AU is not set
# CONFIG_RTW88_8814AE is not set
# CONFIG_RTW88_8814AU is not set
# CONFIG_RTW88_DEBUG is not set
# CONFIG_RTW88_DEBUGFS is not set
CONFIG_RTW88_LEDS=y
CONFIG_RTW89=y
# CONFIG_RTW89_8851BE is not set
# CONFIG_RTW89_8851BU is not set
# CONFIG_RTW89_8852AE is not set
# CONFIG_RTW89_8852AU is not set
# CONFIG_RTW89_8852BE is not set
# CONFIG_RTW89_8852BU is not set
# CONFIG_RTW89_8852BTE is not set
# CONFIG_RTW89_8852CE is not set
# CONFIG_RTW89_8852CU is not set
# CONFIG_RTW89_8922AE is not set
# CONFIG_RTW89_8922AU is not set
# CONFIG_RTW89_8922DE is not set
CONFIG_WLAN_VENDOR_RSI=y
CONFIG_RSI_91X=y
# CONFIG_RSI_DEBUGFS is not set
# CONFIG_RSI_SDIO is not set
CONFIG_RSI_USB=y
# CONFIG_RSI_COEX is not set
CONFIG_WLAN_VENDOR_SILABS=y
# CONFIG_WFX is not set
CONFIG_WLAN_VENDOR_ST=y
# CONFIG_CW1200 is not set
CONFIG_WLAN_VENDOR_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not set
CONFIG_WLAN_VENDOR_ZYDAS=y
CONFIG_ZD1211RW=y
# CONFIG_ZD1211RW_DEBUG is not set
CONFIG_WLAN_VENDOR_QUANTENNA=y
# CONFIG_QTNFMAC_PCIE is not set
# CONFIG_MAC80211_HWSIM is not set
# CONFIG_VIRT_WIFI is not set
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 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 is not set
# CONFIG_INPUT_JOYDEV is not set
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_CROS_EC 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 is not set
# 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_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 is not set
# 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 is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
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=y
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_SDIO_UART is not set
# CONFIG_SERIAL_SPRD is not set
# end of Serial drivers

CONFIG_SERIAL_MCTRL_GPIO=y
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_N_HDLC is not set
# CONFIG_N_GSM is not set
# CONFIG_NOZOMI is not set
# CONFIG_NULL_TTY is not set
CONFIG_HVC_DRIVER=y
CONFIG_SERIAL_DEV_BUS=y
# CONFIG_SERIAL_DEV_CTRL_TTYPORT is not set
# CONFIG_TTY_PRINTK is not set
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
CONFIG_VIRTIO_CONSOLE=y
# CONFIG_IPMI_HANDLER 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 is not set
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM 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 is not set
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 is not set
# 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_AMDPSP is not set
# 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_NT72676 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_CROS_EC_TUNNEL is not set
# CONFIG_I2C_VIRTIO is not set
# end of I2C Hardware Bus support

# CONFIG_I2C_STUB is not set
# CONFIG_I2C_SLAVE is not set
# CONFIG_I2C_DYNAMIC_TIMEOUT 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_FSL_SPI is not set
# CONFIG_SPI_GPIO is not set
# CONFIG_SPI_LANTIQ_SSC is not set
CONFIG_SPI_LJCA=y
# CONFIG_SPI_LM70_LLP is not set
# CONFIG_SPI_MICROCHIP_CORE_QSPI is not set
# CONFIG_SPI_MICROCHIP_CORE_SPI is not set
# CONFIG_SPI_MXIC 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_TLE62X0 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_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_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_EXAR 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_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_CROS_EC is not set
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=y
# CONFIG_W1_CON is not set

#
# 1-wire Bus Masters
#
# CONFIG_W1_MASTER_AMD_AXI is not set
# CONFIG_W1_MASTER_MATROX is not set
CONFIG_W1_MASTER_DS2490=y
# CONFIG_W1_MASTER_DS2482 is not set
# CONFIG_W1_MASTER_GPIO is not set
# CONFIG_W1_MASTER_SGI is not set
# CONFIG_W1_MASTER_UART is not set
# end of 1-wire Bus Masters

#
# 1-wire Slaves
#
# CONFIG_W1_SLAVE_THERM is not set
# CONFIG_W1_SLAVE_SMEM is not set
# CONFIG_W1_SLAVE_DS2405 is not set
# CONFIG_W1_SLAVE_DS2408 is not set
# CONFIG_W1_SLAVE_DS2413 is not set
# CONFIG_W1_SLAVE_DS2406 is not set
# CONFIG_W1_SLAVE_DS2423 is not set
# CONFIG_W1_SLAVE_DS2805 is not set
# CONFIG_W1_SLAVE_DS2430 is not set
# CONFIG_W1_SLAVE_DS2431 is not set
# CONFIG_W1_SLAVE_DS2433 is not set
# CONFIG_W1_SLAVE_DS2438 is not set
# CONFIG_W1_SLAVE_DS250X is not set
# CONFIG_W1_SLAVE_DS2780 is not set
# CONFIG_W1_SLAVE_DS2781 is not set
# CONFIG_W1_SLAVE_DS28E04 is not set
# CONFIG_W1_SLAVE_DS28E17 is not set
# end of 1-wire Slaves

# 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_DS2760 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_BATTERY_MAX1721X 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_CHARGER_CROS_USBPD is not set
# CONFIG_CHARGER_CROS_PCHG is not set
# CONFIG_CHARGER_CROS_CONTROL 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_CROS_EC is not set
# 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_MINISFORUM_UM780XTX 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_HONOR_FMI 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_INTEL_TCC=y
CONFIG_X86_PKG_TEMP_THERMAL=y
# 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_CROS_EC_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_AC200 is not set
# CONFIG_MFD_AXP20X_I2C is not set
# CONFIG_MFD_CGBC is not set
CONFIG_MFD_CROS_EC_DEV=y
# 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 is not set
# 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_CROS_EC 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_MPQ4210 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_NEX10000UB 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_CROS_EC 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 is not set
# 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

#
# Media core support
#
CONFIG_VIDEO_DEV=y
CONFIG_MEDIA_CONTROLLER=y
CONFIG_DVB_CORE=y
# end of Media core support

#
# Video4Linux options
#
CONFIG_VIDEO_V4L2_I2C=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_TUNER=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
#

#
# 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=y

#
# Media capture support
#
# CONFIG_VIDEO_HWS is not set
# CONFIG_VIDEO_SOLO6X10 is not set
# CONFIG_VIDEO_TW5864 is not set
# CONFIG_VIDEO_TW68 is not set
# CONFIG_VIDEO_TW686X is not set
# CONFIG_VIDEO_ZORAN is not set

#
# Media capture/analog TV support
#
# CONFIG_VIDEO_DT3155 is not set
# CONFIG_VIDEO_IVTV is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_MXB is not set

#
# Media capture/analog/hybrid TV support
#
# CONFIG_VIDEO_BT848 is not set
# CONFIG_VIDEO_CX18 is not set
# CONFIG_VIDEO_CX23885 is not set
# CONFIG_VIDEO_CX25821 is not set
# CONFIG_VIDEO_CX88 is not set
CONFIG_VIDEO_SAA7134=y
# CONFIG_VIDEO_SAA7134_ALSA is not set
# CONFIG_VIDEO_SAA7134_RC is not set
# CONFIG_VIDEO_SAA7134_DVB is not set
CONFIG_VIDEO_SAA7134_GO7007=y
# CONFIG_VIDEO_SAA7164 is not set

#
# Media digital TV PCI Adapters
#
CONFIG_DVB_B2C2_FLEXCOP_PCI=y
# CONFIG_DVB_B2C2_FLEXCOP_PCI_DEBUG is not set
# CONFIG_DVB_DDBRIDGE is not set
# CONFIG_DVB_DM1105 is not set
# CONFIG_MANTIS_CORE is not set
# CONFIG_DVB_NETUP_UNIDVB is not set
# CONFIG_DVB_NGENE is not set
# CONFIG_DVB_PLUTO2 is not set
# CONFIG_DVB_PT1 is not set
# CONFIG_DVB_PT3 is not set
# CONFIG_DVB_SMIPCIE is not set
# CONFIG_DVB_BUDGET_CORE is not set
# CONFIG_VIDEO_IPU3_CIO2 is not set
# CONFIG_VIDEO_INTEL_IPU6 is not set
# CONFIG_INTEL_VSC is not set
# CONFIG_IPU_BRIDGE 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 is not set
# CONFIG_DVB_TEST_DRIVERS 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_VIDEOBUF2_CORE=y
CONFIG_VIDEOBUF2_V4L2=y
CONFIG_VIDEOBUF2_MEMOPS=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_IT6625 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_MAXIM_SERDES is not set
# CONFIG_VIDEO_MAX96724 is not set
# CONFIG_VIDEO_MAX9296A 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_GPU_BUDDY=y
CONFIG_DRM=y

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

CONFIG_DRM_MIPI_DSI=y
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_SELECTION=y

#
# Supported DRM clients
#
# CONFIG_DRM_FBDEV_EMULATION is not set
# CONFIG_DRM_CLIENT_LOG is not set
# end of Supported DRM clients

# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
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_DISPLAY_DSC_HELPER=y
CONFIG_DRM_DISPLAY_HDCP_HELPER=y
CONFIG_DRM_DISPLAY_HDMI_HELPER=y
CONFIG_DRM_TTM=y
CONFIG_DRM_BUDDY=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_I915=y
CONFIG_DRM_I915_FORCE_PROBE=""
CONFIG_DRM_I915_CAPTURE_ERROR=y
CONFIG_DRM_I915_COMPRESS_ERROR=y
CONFIG_DRM_I915_USERPTR=y
# CONFIG_DRM_I915_DP_TUNNEL is not set

#
# drm/i915 Debugging
#
# CONFIG_DRM_I915_WERROR is not set
# CONFIG_DRM_I915_REPLAY_GPU_HANGS_API is not set
# CONFIG_DRM_I915_DEBUG is not set
# CONFIG_DRM_I915_DEBUG_MMIO is not set
# CONFIG_DRM_I915_SW_FENCE_DEBUG_OBJECTS is not set
# CONFIG_DRM_I915_SW_FENCE_CHECK_DAG is not set
# CONFIG_DRM_I915_DEBUG_GUC is not set
# CONFIG_DRM_I915_SELFTEST is not set
# CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS is not set
# CONFIG_DRM_I915_DEBUG_VBLANK_EVADE is not set
# CONFIG_DRM_I915_DEBUG_RUNTIME_PM is not set
# CONFIG_DRM_I915_DEBUG_WAKEREF is not set
# end of drm/i915 Debugging

#
# drm/i915 Profile Guided Optimisation
#
CONFIG_DRM_I915_REQUEST_TIMEOUT=20000
CONFIG_DRM_I915_FENCE_TIMEOUT=10000
CONFIG_DRM_I915_USERFAULT_AUTOSUSPEND=250
CONFIG_DRM_I915_HEARTBEAT_INTERVAL=2500
CONFIG_DRM_I915_PREEMPT_TIMEOUT=640
CONFIG_DRM_I915_PREEMPT_TIMEOUT_COMPUTE=7500
CONFIG_DRM_I915_MAX_REQUEST_BUSYWAIT=8000
CONFIG_DRM_I915_STOP_TIMEOUT=100
CONFIG_DRM_I915_TIMESLICE_DURATION=1
# end of drm/i915 Profile Guided Optimisation

# 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_ANBERNIC_TD4310 is not set
# CONFIG_DRM_PANEL_ARM_VERSATILE is not set
# CONFIG_DRM_PANEL_ASUS_Z00T_TM5P5_NT35596 is not set
# CONFIG_DRM_PANEL_AUO_A030JTN01 is not set
# CONFIG_DRM_PANEL_BOE_BF060Y8M_AJ0 is not set
# CONFIG_DRM_PANEL_BOE_HIMAX8279D is not set
# CONFIG_DRM_PANEL_BOE_TD4320 is not set
# CONFIG_DRM_PANEL_BOE_TH101MB31UIG002_28A is not set
# CONFIG_DRM_PANEL_BOE_TV101WUM_NL6 is not set
# CONFIG_DRM_PANEL_BOE_TV101WUM_LL2 is not set
# CONFIG_DRM_PANEL_CHIPONE_ICNA35XX is not set
# CONFIG_DRM_PANEL_CHIPWEALTH_CH13726A is not set
# CONFIG_DRM_PANEL_EBBG_FT8719 is not set
# CONFIG_DRM_PANEL_ELIDA_KD35T133 is not set
# CONFIG_DRM_PANEL_FEIXIN_K101_IM2BA02 is not set
# CONFIG_DRM_PANEL_FEIYANG_FY07024DI26A30D is not set
# CONFIG_DRM_PANEL_FOCALTECH_OTA7290B is not set
# CONFIG_DRM_PANEL_DSI_CM is not set
# CONFIG_DRM_PANEL_LVDS is not set
# CONFIG_DRM_PANEL_HIMAX_HX8279 is not set
# CONFIG_DRM_PANEL_HIMAX_HX83102 is not set
# CONFIG_DRM_PANEL_HIMAX_HX83112A is not set
# CONFIG_DRM_PANEL_HIMAX_HX83112B is not set
# CONFIG_DRM_PANEL_HIMAX_HX83121A is not set
# CONFIG_DRM_PANEL_HIMAX_HX8394 is not set
# CONFIG_DRM_PANEL_HYDIS_HV101HD1 is not set
# CONFIG_DRM_PANEL_ILITEK_ILI7807S is not set
# CONFIG_DRM_PANEL_ILITEK_ILI7836A is not set
# CONFIG_DRM_PANEL_ILITEK_IL9322 is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9341 is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9488 is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9805 is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9806E_DSI is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9806E_SPI is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9881C is not set
# CONFIG_DRM_PANEL_ILITEK_ILI9882T is not set
# CONFIG_DRM_PANEL_INNOLUX_EJ030NA is not set
# CONFIG_DRM_PANEL_INNOLUX_P079ZCA is not set
# CONFIG_DRM_PANEL_JADARD_JD9365DA_H3 is not set
# CONFIG_DRM_PANEL_JDI_LPM102A188A is not set
# CONFIG_DRM_PANEL_JDI_LT070ME05000 is not set
# CONFIG_DRM_PANEL_JDI_R63452 is not set
# CONFIG_DRM_PANEL_KHADAS_TS050 is not set
# CONFIG_DRM_PANEL_KINGDISPLAY_KD097D04 is not set
# CONFIG_DRM_PANEL_LEADTEK_LTK050H3146W is not set
# CONFIG_DRM_PANEL_LEADTEK_LTK500HD1829 is not set
# CONFIG_DRM_PANEL_LINCOLNTECH_LCD197 is not set
# CONFIG_DRM_PANEL_LG_LB035Q02 is not set
# CONFIG_DRM_PANEL_LG_LD070WX3 is not set
# CONFIG_DRM_PANEL_LG_LG4573 is not set
# CONFIG_DRM_PANEL_LG_SW43408 is not set
# CONFIG_DRM_PANEL_LXD_M9189A is not set
# CONFIG_DRM_PANEL_MAGNACHIP_D53E6EA8966 is not set
# CONFIG_DRM_PANEL_MANTIX_MLAF057WE51 is not set
# CONFIG_DRM_PANEL_MOTOROLA_MOT is not set
# CONFIG_DRM_PANEL_NEC_NL8048HL11 is not set
# CONFIG_DRM_PANEL_NEWVISION_NV3051D is not set
# CONFIG_DRM_PANEL_NEWVISION_NV3052C is not set
# CONFIG_DRM_PANEL_NOVATEK_NT35510 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT35532 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT35560 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT35950 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT36523 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT36532 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT36536 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT36672A is not set
# CONFIG_DRM_PANEL_NOVATEK_NT36672E is not set
# CONFIG_DRM_PANEL_NOVATEK_NT37700F is not set
# CONFIG_DRM_PANEL_NOVATEK_NT37801 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT39016 is not set
# CONFIG_DRM_PANEL_NOVATEK_NT51021 is not set
# CONFIG_DRM_PANEL_OLIMEX_LCD_OLINUXINO is not set
# CONFIG_DRM_PANEL_ORISETECH_OTA5601A is not set
# CONFIG_DRM_PANEL_ORISETECH_OTM8009A is not set
# CONFIG_DRM_PANEL_OSD_OSD101T2587_53TS is not set
# CONFIG_DRM_PANEL_PANASONIC_VVX10F034N00 is not set
# CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN is not set
# CONFIG_DRM_PANEL_RAYDIUM_RM67191 is not set
# CONFIG_DRM_PANEL_RAYDIUM_RM67200 is not set
# CONFIG_DRM_PANEL_RAYDIUM_RM68200 is not set
# CONFIG_DRM_PANEL_RAYDIUM_RM692E5 is not set
# CONFIG_DRM_PANEL_RAYDIUM_RM69220 is not set
# CONFIG_DRM_PANEL_RAYDIUM_RM69380 is not set
# CONFIG_DRM_PANEL_RENESAS_R61307 is not set
# CONFIG_DRM_PANEL_RENESAS_R63419 is not set
# CONFIG_DRM_PANEL_RENESAS_R69328 is not set
# CONFIG_DRM_PANEL_RONBO_RB070D30 is not set
# CONFIG_DRM_PANEL_SAMSUNG_AMS581VF01 is not set
# CONFIG_DRM_PANEL_SAMSUNG_AMS639RQ08 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E88A0_AMS427AP24 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_LTL106HL02 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E3FA7 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6D16D0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6D27A1 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6D7AA0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E3FC2X01 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E3HA2 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E3HA8 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E63J0X03 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E63M0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E8AA0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E8AA5X01_AMS561RA01 is not set
# CONFIG_DRM_PANEL_SAMSUNG_S6E8FC0 is not set
# CONFIG_DRM_PANEL_SAMSUNG_SOFEF00 is not set
# CONFIG_DRM_PANEL_SEIKO_43WVF1G is not set
# CONFIG_DRM_PANEL_SHARP_LQ079L1SX01 is not set
# CONFIG_DRM_PANEL_SHARP_LQ101R1SX01 is not set
# CONFIG_DRM_PANEL_SHARP_LS037V7DW01 is not set
# CONFIG_DRM_PANEL_SHARP_LS043T1LE01 is not set
# CONFIG_DRM_PANEL_SHARP_LS060T1SX01 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7701 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7703 is not set
# CONFIG_DRM_PANEL_SITRONIX_ST7789V is not set
# CONFIG_DRM_PANEL_SONY_ACX565AKM is not set
# CONFIG_DRM_PANEL_SONY_TD4353_JDI is not set
# CONFIG_DRM_PANEL_SONY_TULIP_TRULY_NT35521 is not set
# CONFIG_DRM_PANEL_STARTEK_KD070FHFID015 is not set
# CONFIG_DRM_PANEL_EDP is not set
# CONFIG_DRM_PANEL_SIMPLE is not set
# CONFIG_DRM_PANEL_SUMMIT is not set
# CONFIG_DRM_PANEL_SYNAPTICS_R63353 is not set
# CONFIG_DRM_PANEL_SYNAPTICS_TDDI is not set
# CONFIG_DRM_PANEL_TDO_TL070WSH30 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_TRULY_NT35597_WQXGA is not set
# CONFIG_DRM_PANEL_VISIONOX_G2647FB105 is not set
# CONFIG_DRM_PANEL_VISIONOX_R66451 is not set
# CONFIG_DRM_PANEL_VISIONOX_RM69299 is not set
# CONFIG_DRM_PANEL_VISIONOX_RM692E5 is not set
# CONFIG_DRM_PANEL_VISIONOX_VTDR6130 is not set
# CONFIG_DRM_PANEL_WIDECHIPS_WS2401 is not set
# CONFIG_DRM_PANEL_XINPENG_XPP055C272 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_SIMPLEDRM is not set
# 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 is not set
# CONFIG_DRM_CIRRUS_QEMU is not set
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 is not set
CONFIG_DRM_VIRTIO_GPU=y
CONFIG_DRM_VIRTIO_GPU_KMS=y
# CONFIG_DRM_VKMS is not set
# CONFIG_DRM_VMWGFX 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 is not set
# CONFIG_FB_UVESA is not set
# CONFIG_FB_VESA is not set
# 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_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY 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_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
CONFIG_FB_SMSCUFX=y
CONFIG_FB_UDL=y
# CONFIG_FB_IBM_GXT4500 is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_SIMPLE 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_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_SYSMEM_HELPERS=y
CONFIG_FB_SYSMEM_HELPERS_DEFERRED=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
# 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_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 is not set
# end of Console display driver support

# CONFIG_LOGO is not set
# CONFIG_TRACE_GPU_MEM is not set
# end of Graphics support

CONFIG_DRM_ACCEL=y
# CONFIG_DRM_ACCEL_AMDXDNA is not set
# CONFIG_DRM_ACCEL_HABANALABS is not set
# CONFIG_DRM_ACCEL_IVPU is not set
CONFIG_SOUND=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 is not set
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 is not set
# CONFIG_SND_CTL_INPUT_VALIDATION is not set
# CONFIG_SND_UTIMER is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_SEQ_DUMMY=y
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_SEQ_MIDI_EVENT=y
CONFIG_SND_SEQ_MIDI=y
# CONFIG_SND_SEQ_UMP is not set
CONFIG_SND_DRIVERS=y
# CONFIG_SND_PCSP is not set
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_ALOOP is not set
# CONFIG_SND_PCMTEST is not set
# CONFIG_SND_VIRMIDI is not set
# 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 is not set
# CONFIG_SND_HDA_INPUT_BEEP is not set
# CONFIG_SND_HDA_PATCH_LOADER is not set
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_CODEC_ANALOG is not set
# CONFIG_SND_HDA_CODEC_SIGMATEL is not set
# CONFIG_SND_HDA_CODEC_VIA is not set
# CONFIG_SND_HDA_CODEC_CONEXANT is not set
# CONFIG_SND_HDA_CODEC_SENARYTECH is not set
# CONFIG_SND_HDA_CODEC_CA0110 is not set
# CONFIG_SND_HDA_CODEC_CA0132 is not set
# CONFIG_SND_HDA_CODEC_CMEDIA is not set
# CONFIG_SND_HDA_CODEC_CM9825 is not set
# CONFIG_SND_HDA_CODEC_SI3054 is not set
# CONFIG_SND_HDA_GENERIC is not set
# CONFIG_SND_HDA_CODEC_REALTEK is not set
# CONFIG_SND_HDA_CODEC_CIRRUS is not set
# CONFIG_SND_HDA_CODEC_HDMI 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_HDA_COMPONENT=y
CONFIG_SND_HDA_I915=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_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

#
# Airoha
#
# end of Airoha

#
# 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_ADAU1977_SPI is not set
# CONFIG_SND_SOC_ADAU1977_I2C 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_CROS_EC_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_ES9039Q2M 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_NAU8360 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_HDMI_LPE_AUDIO is not set
# CONFIG_SND_VIRTIO is not set
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 is not set

#
# 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_HAMMER=y
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_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_NINTENDO_SWITCH2_USB is not set
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_PULSAR 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 is not set
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 is not set
CONFIG_USB_DWC3_DUAL_ROLE=y

#
# 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 is not set
# 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 is not set
# 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_CROS_EC_UCSI is not set
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_MMC_TEST 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_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_CROS_EC 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_LTC3208 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_TRIGGERS_HW_CHANGED is not set
# CONFIG_LEDS_TRIGGER_TIMER is not set
# CONFIG_LEDS_TRIGGER_ONESHOT is not set
# CONFIG_LEDS_TRIGGER_DISK is not set
# CONFIG_LEDS_TRIGGER_HEARTBEAT is not set
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
# CONFIG_LEDS_TRIGGER_CPU 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_INTEL_BFF_RESET is not set
# CONFIG_EDAC_PND2 is not set
# CONFIG_EDAC_IGEN6 is not set
# CONFIG_EDAC_DUMMY 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=y

#
# 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_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_ABX80X is not set
# 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
# CONFIG_RTC_DRV_CROS_EC 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 is not set
# CONFIG_INTEL_IDXD is not set
# CONFIG_INTEL_IDXD_COMPAT is not set
# CONFIG_INTEL_IOATDMA is not set
# 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 is not set
# CONFIG_DMATEST is not set

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

# CONFIG_UIO is not set
# CONFIG_VFIO is not set
# CONFIG_VIRT_DRIVERS is not set
CONFIG_TSM=y
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_BALLOON is not set
CONFIG_VIRTIO_INPUT=y
# CONFIG_VIRTIO_MMIO is not set
CONFIG_VIRTIO_DMA_SHARED_BUFFER=y
# CONFIG_VIRTIO_DEBUG is not set
# CONFIG_VIRTIO_RTC is not set
# CONFIG_VDPA is not set
CONFIG_VHOST_MENU=y
# CONFIG_VHOST_NET is not set
# CONFIG_VHOST_SCSI is not set
# CONFIG_VHOST_VSOCK is not set
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set
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 is not set
# CONFIG_COMEDI_PCI_DRIVERS is not set
# CONFIG_COMEDI_PCMCIA_DRIVERS 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_8255_SA is not set
# CONFIG_COMEDI_KCOMEDILIB is not set
# CONFIG_COMEDI_TESTS is not set
# CONFIG_GPIB is not set
CONFIG_STAGING=y

#
# IIO staging drivers
#

#
# 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=y
# CONFIG_CHROMEOS_ACPI is not set
# CONFIG_CHROMEOS_LAPTOP is not set
# CONFIG_CHROMEOS_PSTORE is not set
# CONFIG_CHROMEOS_TBMC is not set
# CONFIG_CHROMEOS_OF_HW_PROBER is not set
CONFIG_CROS_EC=y
# CONFIG_CROS_EC_I2C is not set
CONFIG_CROS_EC_ISHTP=y
# CONFIG_CROS_EC_SPI is not set
# CONFIG_CROS_EC_UART is not set
# CONFIG_CROS_EC_LPC is not set
CONFIG_CROS_EC_PROTO=y
# CONFIG_CROS_KBD_LED_BACKLIGHT is not set
# CONFIG_CROS_EC_CHARDEV is not set
# CONFIG_CROS_EC_LIGHTBAR is not set
# CONFIG_CROS_EC_VBC is not set
# CONFIG_CROS_EC_DEBUGFS is not set
# CONFIG_CROS_EC_SENSORHUB is not set
# CONFIG_CROS_EC_SYSFS is not set
CONFIG_CROS_EC_TYPEC_ALTMODES=y
CONFIG_CROS_EC_TYPEC=y
CONFIG_CROS_HPS_I2C=y
CONFIG_CROS_USBPD_NOTIFY=y
# CONFIG_CHROMEOS_PRIVACY_SCREEN is not set
CONFIG_CROS_TYPEC_SWITCH=y
# 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_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
# CONFIG_ACER_WMI_BATTERY 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_PMF=y
CONFIG_AMD_PMF_DEBUG=y
# CONFIG_AMD_PMF_UTIL_SUPPORT is not set
# 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_WMI_BMOF=y
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_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_DMAR_TABLE=y
CONFIG_INTEL_IOMMU=y
# CONFIG_INTEL_IOMMU_SVM is not set
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y
CONFIG_INTEL_IOMMU_PERF_EVENTS=y
# CONFIG_IOMMUFD is not set
CONFIG_IRQ_REMAP=y
# CONFIG_VIRTIO_IOMMU is not set
CONFIG_GENERIC_PT=y
# CONFIG_DEBUG_GENERIC_PT is not set
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
# CONFIG_IOMMU_PT_BCM2712 is not set

#
# 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

#
# ST SoC drivers
#
# end of ST SoC drivers

#
# StarFive SoC (System On Chip) specific Drivers
#
# end of StarFive SoC (System On Chip) specific Drivers

# 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_CROS_EC 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 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_MAX40080 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_ADS112C04 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_AD5529R 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_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_I2C is not set
# CONFIG_MCP47FEB02_SPI 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

#
# Direct Digital Synthesis
#
# CONFIG_AD9910 is not set
# end of Direct Digital Synthesis

#
# 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_VEML6031X00 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_CROS_EC_MKBP_PROXIMITY is not set
# 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 is not set
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
#
# end of Android

# CONFIG_LIBNVDIMM is not set
# CONFIG_DAX is not set
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

#
# 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_AMDTEE=y
# CONFIG_MUX_CORE is not set
# CONFIG_SIOX is not set
# CONFIG_SLIMBUS is not set
# CONFIG_INTERCONNECT is not set
# CONFIG_COUNTER 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 is not set
CONFIG_FS_IOMAP=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 is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
# CONFIG_F2FS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_EXPORTFS=y
# CONFIG_EXPORTFS_BLOCK_OPS is not set
CONFIG_FILE_LOCKING=y
# CONFIG_FS_ENCRYPTION is not set
# CONFIG_FS_VERITY is not set
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_FANOTIFY is not set
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 is not set
# CONFIG_OVERLAY_FS is not set

#
# Caches
#
CONFIG_NETFS_SUPPORT=y
# CONFIG_NETFS_STATS is not set
# CONFIG_NETFS_DEBUG is not set
# CONFIG_FSCACHE is not set
# end of Caches

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
# CONFIG_UDF_FS is not set
# 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 is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS3_FS is not set
# 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 is not set
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 is not set
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 is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX6FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_PSTORE is not set
# CONFIG_UFS_FS is not set
# CONFIG_EROFS_FS 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 is not set
CONFIG_PNFS_FILE_LAYOUT=y
CONFIG_PNFS_BLOCK=y
# CONFIG_PNFS_BLOCK_LAYOUT is not set
CONFIG_PNFS_SCSI_LAYOUT=y
CONFIG_PNFS_FLEXFILE_LAYOUT=y
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org"
# CONFIG_NFS_V4_1_MIGRATION is not set
CONFIG_ROOT_NFS=y
# CONFIG_NFS_FSCACHE is not set
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
# CONFIG_NFSD is not set
CONFIG_GRACE_PERIOD=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=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 is not set
# CONFIG_CIFS is not set
# CONFIG_SMB_SERVER is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_9P_FS=y
# CONFIG_9P_FS_POSIX_ACL is not set
# CONFIG_9P_FS_SECURITY is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_MAC_ROMAN is not set
# CONFIG_NLS_MAC_CELTIC is not set
# CONFIG_NLS_MAC_CENTEURO is not set
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set
# CONFIG_NLS_MAC_GAELIC is not set
# CONFIG_NLS_MAC_GREEK is not set
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not set
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set
# CONFIG_UNICODE is not set
CONFIG_IO_WQ=y
# end of File systems

#
# Security options
#
CONFIG_KEYS=y
# CONFIG_KEYS_REQUEST_CACHE is not set
# CONFIG_PERSISTENT_KEYRINGS is not set
# CONFIG_BIG_KEYS is not set
# CONFIG_TRUSTED_KEYS is not set
# CONFIG_ENCRYPTED_KEYS is not set
# CONFIG_KEY_DH_OPERATIONS is not set
# 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_MSEAL_SYSTEM_MAPPINGS is not set
CONFIG_SECURITY=y
CONFIG_HAS_SECURITY_AUDIT=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_SECURITY_INFINIBAND is not set
# CONFIG_SECURITY_NETWORK_XFRM is not set
# CONFIG_SECURITY_PATH is not set
# CONFIG_INTEL_TXT is not set
CONFIG_LSM_MMAP_MIN_ADDR=65536
# CONFIG_STATIC_USERMODEHELPER is not set
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_SIDTAB_HASH_BITS=9
CONFIG_SECURITY_SELINUX_SID2STR_CACHE_SIZE=256
CONFIG_SECURITY_SELINUX_AVC_HASH_BITS=9
# CONFIG_SECURITY_SELINUX_DEBUG is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_SECURITY_LOADPIN is not set
# CONFIG_SECURITY_YAMA is not set
# CONFIG_SECURITY_SAFESETID is not set
# CONFIG_SECURITY_LOCKDOWN_LSM is not set
# CONFIG_SECURITY_LANDLOCK is not set
# CONFIG_SECURITY_IPE is not set
CONFIG_INTEGRITY=y
# CONFIG_INTEGRITY_SIGNATURE is not set
CONFIG_INTEGRITY_AUDIT=y
# CONFIG_IMA is not set
# CONFIG_EVM is not set
CONFIG_DEFAULT_SECURITY_SELINUX=y
# CONFIG_DEFAULT_SECURITY_DAC is not set
CONFIG_LSM="landlock,lockdown,yama,loadpin,safesetid,selinux,smack,tomoyo,apparmor,ipe,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_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_AKCIPHER2=y
CONFIG_CRYPTO_AKCIPHER=y
CONFIG_CRYPTO_KPP2=y
CONFIG_CRYPTO_KPP=y
CONFIG_CRYPTO_ACOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_USER is not set
# CONFIG_CRYPTO_SELFTESTS is not set
CONFIG_CRYPTO_NULL=y
# CONFIG_CRYPTO_PCRYPT is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=y
CONFIG_CRYPTO_KRB5ENC=y
# CONFIG_CRYPTO_BENCHMARK is not set
# end of Crypto core or helper

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

#
# Block ciphers
#
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_ARIA is not set
# CONFIG_CRYPTO_BLOWFISH is not set
CONFIG_CRYPTO_CAMELLIA=y
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_SM4_GENERIC is not set
# CONFIG_CRYPTO_TWOFISH is not set
# end of Block ciphers

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

#
# AEAD (authenticated encryption with associated data) ciphers
#
# CONFIG_CRYPTO_AEGIS128 is not set
# CONFIG_CRYPTO_CHACHA20POLY1305 is not set
CONFIG_CRYPTO_CCM=y
CONFIG_CRYPTO_GCM=y
CONFIG_CRYPTO_GENIV=y
CONFIG_CRYPTO_SEQIV=y
CONFIG_CRYPTO_ECHAINIV=y
# CONFIG_CRYPTO_ESSIV is not set
# 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 is not set
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
# CONFIG_CRYPTO_SHA3 is not set
# CONFIG_CRYPTO_SM3 is not set
# CONFIG_CRYPTO_STREEBOG is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_XCBC is not set
# 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 is not set
CONFIG_CRYPTO_LZ4=y
# CONFIG_CRYPTO_LZ4HC is not set
# CONFIG_CRYPTO_ZSTD is not set
# end of Compression

#
# Random number generation
#
# CONFIG_CRYPTO_DRBG is not set
# CONFIG_CRYPTO_JITTERENTROPY is not set
# end of Random number generation

#
# Userspace interface (deprecated)
#
# CONFIG_CRYPTO_USER_API_HASH is not set
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
# CONFIG_CRYPTO_USER_API_RNG is not set
# CONFIG_CRYPTO_USER_API_AEAD is not set
# end of Userspace interface (deprecated)

#
# Accelerated Cryptographic Algorithms for CPU (x86)
#
# CONFIG_CRYPTO_AES_NI_INTEL is not set
# CONFIG_CRYPTO_BLOWFISH_X86_64 is not set
# CONFIG_CRYPTO_CAMELLIA_X86_64 is not set
# CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64 is not set
# CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64 is not set
# CONFIG_CRYPTO_CAST5_AVX_X86_64 is not set
# CONFIG_CRYPTO_CAST6_AVX_X86_64 is not set
# CONFIG_CRYPTO_SERPENT_SSE2_X86_64 is not set
# CONFIG_CRYPTO_SERPENT_AVX_X86_64 is not set
# CONFIG_CRYPTO_SERPENT_AVX2_X86_64 is not set
# CONFIG_CRYPTO_SM4_AESNI_AVX_X86_64 is not set
# CONFIG_CRYPTO_SM4_AESNI_AVX2_X86_64 is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set
# CONFIG_CRYPTO_TWOFISH_X86_64_3WAY is not set
# CONFIG_CRYPTO_TWOFISH_AVX_X86_64 is not set
# CONFIG_CRYPTO_ARIA_AESNI_AVX_X86_64 is not set
# 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 is not set
# end of Accelerated Cryptographic Algorithms for CPU (x86)

CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_PADLOCK is not set
# 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=y
# CONFIG_CRYPTO_DEV_NITROX_CNN55XX is not set
# CONFIG_CRYPTO_DEV_QAT_DH895xCC is not set
# CONFIG_CRYPTO_DEV_QAT_C3XXX is not set
# CONFIG_CRYPTO_DEV_QAT_C62X is not set
# 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 is not set
# CONFIG_CRYPTO_DEV_QAT_C3XXXVF is not set
# CONFIG_CRYPTO_DEV_QAT_C62XVF is not set
# CONFIG_CRYPTO_DEV_VIRTIO is not set
# 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 is not set
CONFIG_PKCS7_MESSAGE_PARSER=y
# CONFIG_PKCS7_TEST_KEY is not set
# CONFIG_SIGNED_PE_FILE_VERIFICATION is not set
# CONFIG_FIPS_SIGNATURE_SELFTEST is not set

#
# Certificates for signature checking
#
CONFIG_SYSTEM_TRUSTED_KEYRING=y
CONFIG_SYSTEM_TRUSTED_KEYS=""
# CONFIG_SYSTEM_EXTRA_CERTIFICATE is not set
# CONFIG_SECONDARY_TRUSTED_KEYRING 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_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_ARC4=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_POLY1305=y
CONFIG_CRYPTO_LIB_POLY1305_ARCH=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_XXHASH=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_LZ4_COMPRESS=y
CONFIG_LZ4_DECOMPRESS=y
CONFIG_ZSTD_COMMON=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_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=y
CONFIG_TEXTSEARCH_BM=y
CONFIG_TEXTSEARCH_FSM=y
CONFIG_INTERVAL_TREE=y
CONFIG_XARRAY_MULTI=y
CONFIG_ASSOCIATIVE_ARRAY=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_API_DEBUG is not set
# CONFIG_DMA_MAP_BENCHMARK is not set
CONFIG_SGL_ALLOC=y
CONFIG_CHECK_SIGNATURE=y
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_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_SG_POOL=y
CONFIG_ARCH_HAS_PMEM_API=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_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 is not set
# CONFIG_DYNAMIC_DEBUG_CORE is not set
CONFIG_SYMBOLIC_ERRNAME=y
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_BUGVERBOSE_DETAILED is not set
# 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 is not set
CONFIG_HAVE_ARCH_KCSAN=y
CONFIG_HAVE_KCSAN_COMPILER=y
CONFIG_KCSAN=y
CONFIG_CC_HAS_TSAN_COMPOUND_READ_BEFORE_WRITE=y
CONFIG_KCSAN_SELFTEST=y
# CONFIG_KCSAN_EARLY_ENABLE is not set
CONFIG_KCSAN_NUM_WATCHPOINTS=64
CONFIG_KCSAN_UDELAY_TASK=80
CONFIG_KCSAN_UDELAY_INTERRUPT=20
CONFIG_KCSAN_DELAY_RANDOMIZE=y
CONFIG_KCSAN_SKIP_WATCH=4000
CONFIG_KCSAN_SKIP_WATCH_RANDOMIZE=y
CONFIG_KCSAN_INTERRUPT_WATCHER=y
CONFIG_KCSAN_REPORT_ONCE_IN_MS=3000
# CONFIG_KCSAN_REPORT_RACE_UNKNOWN_ORIGIN is not set
CONFIG_KCSAN_STRICT=y
# CONFIG_KCSAN_WEAK_MEMORY is not set
# 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 is not set
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_SLUB_DEBUG=y
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_PAGE_OWNER is not set
# CONFIG_PAGE_TABLE_CHECK is not set
# CONFIG_PAGE_POISONING is not set
# CONFIG_DEBUG_PAGE_REF is not set
# CONFIG_DEBUG_RODATA_TEST is not set
# CONFIG_PTDUMP_DEBUGFS is not set
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 is not set
# 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 is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VM_PGTABLE is not set
CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
# CONFIG_DEBUG_VIRTUAL is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_PER_CPU_MAPS is not set
CONFIG_ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP=y
# CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP is not set
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 is not set
CONFIG_HAVE_ARCH_KFENCE=y
# CONFIG_KFENCE is not set
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_SOFTLOCKUP_DETECTOR is not set
CONFIG_HAVE_HARDLOCKUP_DETECTOR_BUDDY=y
# CONFIG_HARDLOCKUP_DETECTOR is not set
CONFIG_HARDLOCKUP_CHECK_TIMESTAMP=y
# CONFIG_DETECT_HUNG_TASK is not set
# CONFIG_WQ_WATCHDOG is not set
# 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 is not set
# CONFIG_DEBUG_ATOMIC is not set

#
# Lock Debugging (spinlocks, mutexes, etc...)
#
CONFIG_LOCK_DEBUGGING_SUPPORT=y
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_DEBUG_RWSEMS is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# 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 is not set
# end of Lock Debugging (spinlocks, mutexes, etc...)

CONFIG_NMI_CHECK_CPU=y
# CONFIG_DEBUG_IRQFLAGS is not set
CONFIG_STACKTRACE=y
# CONFIG_DEBUG_KOBJECT is not set

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

#
# RCU Debugging
#
# 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 is not set
# 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_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 is not set
# 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_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_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_KMOD is not set
# CONFIG_TEST_KALLSYMS 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_ZCRX=y
CONFIG_IO_URING_BPF=y
KernelRepo git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
ReproCID 0
ReproOpts
ReproSyzID 0
SyzkallerCommit a3e64cfc0d091fba81397847a5ab9790a4a944ca
TargetArch amd64
TargetOS linux
TargetVMArch amd64
VMType gce

Outputs:
DenialOfService ❌
Exploitable ❌
FilesystemTrigger ❌
FuzzingArtifact ❌
MemoryCorruption ❌
NetworkNeedsSetup ❌
NetworkTrigger ❌
PeripheralTrigger ❌
RemoteTrigger ❌
Unprivileged βœ…
UserNamespace βœ…
VMGuestTrigger ❌
VMHostTrigger ❌
Explanation
Root Cause Analysis:

### Root Cause Analysis

#### 1. Involved Structures, Functions, and Source Files
- **Files:** `fs/dcache.c`, `lib/lockref.c`, `include/linux/lockref.h`,
`include/linux/dcache.h`, `fs/namei.c`
- **Data Structures and Fields:**
  - `struct lockref` (`include/linux/lockref.h:25-35`):
    ```c
    struct lockref {
        union {
    #if USE_CMPXCHG_LOCKREF
            aligned_u64 lock_count;
    #endif
            struct {
                spinlock_t lock;
                int count;
            };
        };
    };
    ```
    On 64-bit systems with `USE_CMPXCHG_LOCKREF`, the 64-bit `lock_count` union
    aliases `spinlock_t lock` (bytes 0..3) and `int count` (bytes 4..7).
  - `struct dentry` (`include/linux/dcache.h:89`): defines `#define d_lock
  d_lockref.lock`.
- **Functions:**
  - Reader: `lockref_get_not_dead()` (`lib/lockref.c:143-162`) called from
  `__legitimize_path()` / `legitimize_path()` / `try_to_unlazy()`
  (`fs/namei.c:880, 890, 954`).
  - Writer: `dentry_kill()` (`fs/dcache.c:830-882`) called during dentry
  eviction via `finish_dput()` / `dput()` (`fs/dcache.c:1032, 1073`).

---

#### 2. Triggering Mechanism and Race Sequence

1. **Reader Path (`lockref_get_not_dead` in task 4498):**
   - During an RCU-walk path resolution unlazy operation (`try_to_unlazy()`),
   task 4498 attempts to legitimize a dentry reference (the parent directory
   dentry) by calling `lockref_get_not_dead(&path->dentry->d_lockref)`.
   - `lockref_get_not_dead()` enters macro `CMPXCHG_LOOP`
   (`lib/lockref.c:11-27`), which begins with an optimistic lockless 8-byte
   load:
     ```c
     old.lock_count = READ_ONCE(lockref->lock_count);
     ```
   - This 8-byte read accesses memory `0xffff888105d35800` through
   `0xffff888105d35807`, covering both the spinlock and the reference counter
   without acquiring `parent->d_lock`.

2. **Writer Path (`dentry_kill` in task 3284):**
   - Concurrently, task 3284 is destroying a child dentry inside
   `dentry_kill()`.
   - `dentry_kill()` locks the parent dentry via `spin_lock(&parent->d_lock)` at
   line 868.
   - Once the child is unlisted and freed, line 877 decrements the parent's
   reference counter:
     ```c
     if (parent && --parent->d_lockref.count) {
         spin_unlock(&parent->d_lock);
         return NULL;
     }
     ```
   - `--parent->d_lockref.count` is a 4-byte non-atomic read-modify-write
   located at offset +4 (`0xffff888105d35804`).

3. **KCSAN Detection:**
   - KCSAN observes an 8-byte marked read (`READ_ONCE(lockref->lock_count)`) on
   CPU 0 overlapping an unmarked 4-byte read-modify-write
   (`--parent->d_lockref.count`) on CPU 1.
   - Because plain C read-modify-writes (`--parent->d_lockref.count`) do not
   carry `WRITE_ONCE()` or atomic annotations, KCSAN flags the concurrent access
   as a data race.

---

#### 3. Correctness and Synchronization Analysis (Benign Data Race)

This data race is benign by design of the `lockref` subsystem:
- When task 3284 executes `--parent->d_lockref.count`, it holds `parent->d_lock`
(`parent->d_lockref.lock`).
- If task 4498's `READ_ONCE(lockref->lock_count)` runs while `parent->d_lock` is
held by task 3284:
  - `old.lock` contains the locked state
  (`arch_spin_value_unlocked(old.lock.rlock.raw_lock)` evaluates to `0`).
  - The `while` loop condition fails immediately; `CMPXCHG_LOOP` terminates
  without performing `try_cmpxchg64_relaxed()` and without using any potentially
  torn or in-transition counter value.
  - `lockref_get_not_dead()` falls back to `spin_lock(&lockref->lock)`, which
  properly blocks until task 3284 releases `parent->d_lock`, ensuring strict
  serialization.
- If task 4498's `READ_ONCE(lockref->lock_count)` runs before task 3284 acquires
the lock, `old.lock` reflects an unlocked state. However, before task 4498 can
execute `try_cmpxchg64_relaxed()`, task 3284 acquires the lock. The 64-bit
cmpxchg instruction will then compare `old.lock_count` (which has the unlocked
lock value) against current memory (which has the locked spinlock value). The
comparison fails, `old.lock_count` is reloaded with the locked state, and
execution falls back to taking the spinlock.
- Consequently, reference counts cannot be corrupted, dentries cannot be freed
prematurely, and execution behavior in real-world setups is fully preserved.

Impact Analysis:

In real-world setups without debugging sanitizers (KCSAN, lockdep, etc.), this
data race is completely benign and has no runtime consequences:

- MemoryCorruption: False. The 64-bit lockref design couples the 32-bit spinlock
with the 32-bit counter. If task 4498's READ_ONCE occurs while task 3284 holds
parent->d_lock, arch_spin_value_unlocked() evaluates to false, immediately
aborting the cmpxchg loop without touching the counter and falling back to
taking parent->d_lock (serializing after task 3284 unlocks). If the read
occurred before task 3284 acquired the lock, any cmpxchg64 attempt fails because
the lock word in memory has transitioned to locked. Therefore, refcounts are
never corrupted and dentries are not prematurely freed.
- InfoLeak: "none". No kernel memory or pointer values are leaked or exposed to
userspace.
- RawDenialOfService: False. The fallback path correctly synchronizes via
spin_lock(&lockref->lock); no deadlock, infinite loop, memory leak, or crash can
occur.
- IsNetCandidate: False. The reported stack traces involve VFS path walk and
unlinkat syscall handling; neither networking nor sockets are involved.
- IsKVMCandidate: False. The issue is in core VFS/dcache and lockref;
virtualization and KVM are not involved.

Local Reachability Analysis:

### Analysis

#### 1. Local Entry Points Investigated
The reported KCSAN data race occurs between:
1. **Task 1 (Reader):** Path lookup attempting to legitimize an RCU-walk
reference via `lockref_get_not_dead(&path->dentry->d_lockref)` in
`try_to_unlazy()` (`fs/namei.c:954`) during `complete_walk()` /
`filename_parentat()`, invoked via the `sys_unlink` / `sys_unlinkat` syscall.
2. **Task 2 (Writer):** Child dentry destruction via `dput()` / `finish_dput()`
-> `dentry_kill()` (`fs/dcache.c:877`), which decrements the parent's dentry
count (`--parent->d_lockref.count`), also invoked via standard `sys_unlink` /
`sys_unlinkat`.

Both paths are reached through standard, ubiquitous VFS operations (`unlink`,
`unlinkat`, `open`, `rmdir`, etc.) operating on user-created files and
directories (e.g., in `/tmp`).

#### 2. Capability and Configuration Checks
- Standard file-system operations like `unlink` / `unlinkat` on unprivileged
user-owned directories require no special capabilities or namespace privileges.
- Standard DAC checks permit any unprivileged process to create and unlink files
in world-writable directories such as `/tmp`.
- No capability checks (`capable()`, `ns_capable()`) gate this code path.

#### 3. Output Field Justification
- **Unprivileged (`true`):** Can be reached directly by any unprivileged user
process performing concurrent filesystem operations (such as unlinking files in
a shared directory).
- **UserNamespace (`true`):** True because it is triggerable by unprivileged
processes directly without namespaces.
- **RequiredCaps (`[]`):** No capabilities are required along the
least-privileged path.
- **PeripheralTrigger (`false`):** This is a concurrency race in the core VFS
lockref/dcache subsystem, not an issue triggered by plugging in an untrusted
hardware peripheral.
- **FilesystemTrigger (`false`):** Not triggered by mounting or parsing a
malicious filesystem disk image; it arises from concurrent userspace path lookup
and dentry reclamation.
- **RawFuzzingArtifact (`false`):** The bug is triggerable by unprivileged
processes (`Unprivileged = true`) through standard syscalls, and thus is not a
capability-gated fuzzing artifact.
InfoLeak
none
RequiredCaps
RootCauseAnalysis
### Root Cause Analysis

#### 1. Involved Structures, Functions, and Source Files
- **Files:** `fs/dcache.c`, `lib/lockref.c`, `include/linux/lockref.h`, `include/linux/dcache.h`, `fs/namei.c`
- **Data Structures and Fields:**
  - `struct lockref` (`include/linux/lockref.h:25-35`):
    ```c
    struct lockref {
        union {
    #if USE_CMPXCHG_LOCKREF
            aligned_u64 lock_count;
    #endif
            struct {
                spinlock_t lock;
                int count;
            };
        };
    };
    ```
    On 64-bit systems with `USE_CMPXCHG_LOCKREF`, the 64-bit `lock_count` union aliases `spinlock_t lock` (bytes 0..3) and `int count` (bytes 4..7).
  - `struct dentry` (`include/linux/dcache.h:89`): defines `#define d_lock d_lockref.lock`.
- **Functions:**
  - Reader: `lockref_get_not_dead()` (`lib/lockref.c:143-162`) called from `__legitimize_path()` / `legitimize_path()` / `try_to_unlazy()` (`fs/namei.c:880, 890, 954`).
  - Writer: `dentry_kill()` (`fs/dcache.c:830-882`) called during dentry eviction via `finish_dput()` / `dput()` (`fs/dcache.c:1032, 1073`).

---

#### 2. Triggering Mechanism and Race Sequence

1. **Reader Path (`lockref_get_not_dead` in task 4498):**
   - During an RCU-walk path resolution unlazy operation (`try_to_unlazy()`), task 4498 attempts to legitimize a dentry reference (the parent directory dentry) by calling `lockref_get_not_dead(&path->dentry->d_lockref)`.
   - `lockref_get_not_dead()` enters macro `CMPXCHG_LOOP` (`lib/lockref.c:11-27`), which begins with an optimistic lockless 8-byte load:
     ```c
     old.lock_count = READ_ONCE(lockref->lock_count);
     ```
   - This 8-byte read accesses memory `0xffff888105d35800` through `0xffff888105d35807`, covering both the spinlock and the reference counter without acquiring `parent->d_lock`.

2. **Writer Path (`dentry_kill` in task 3284):**
   - Concurrently, task 3284 is destroying a child dentry inside `dentry_kill()`.
   - `dentry_kill()` locks the parent dentry via `spin_lock(&parent->d_lock)` at line 868.
   - Once the child is unlisted and freed, line 877 decrements the parent's reference counter:
     ```c
     if (parent && --parent->d_lockref.count) {
         spin_unlock(&parent->d_lock);
         return NULL;
     }
     ```
   - `--parent->d_lockref.count` is a 4-byte non-atomic read-modify-write located at offset +4 (`0xffff888105d35804`).

3. **KCSAN Detection:**
   - KCSAN observes an 8-byte marked read (`READ_ONCE(lockref->lock_count)`) on CPU 0 overlapping an unmarked 4-byte read-modify-write (`--parent->d_lockref.count`) on CPU 1.
   - Because plain C read-modify-writes (`--parent->d_lockref.count`) do not carry `WRITE_ONCE()` or atomic annotations, KCSAN flags the concurrent access as a data race.

---

#### 3. Correctness and Synchronization Analysis (Benign Data Race)

This data race is benign by design of the `lockref` subsystem:
- When task 3284 executes `--parent->d_lockref.count`, it holds `parent->d_lock` (`parent->d_lockref.lock`).
- If task 4498's `READ_ONCE(lockref->lock_count)` runs while `parent->d_lock` is held by task 3284:
  - `old.lock` contains the locked state (`arch_spin_value_unlocked(old.lock.rlock.raw_lock)` evaluates to `0`).
  - The `while` loop condition fails immediately; `CMPXCHG_LOOP` terminates without performing `try_cmpxchg64_relaxed()` and without using any potentially torn or in-transition counter value.
  - `lockref_get_not_dead()` falls back to `spin_lock(&lockref->lock)`, which properly blocks until task 3284 releases `parent->d_lock`, ensuring strict serialization.
- If task 4498's `READ_ONCE(lockref->lock_count)` runs before task 3284 acquires the lock, `old.lock` reflects an unlocked state. However, before task 4498 can execute `try_cmpxchg64_relaxed()`, task 3284 acquires the lock. The 64-bit cmpxchg instruction will then compare `old.lock_count` (which has the unlocked lock value) against current memory (which has the locked spinlock value). The comparison fails, `old.lock_count` is reloaded with the locked state, and execution falls back to taking the spinlock.
- Consequently, reference counts cannot be corrupted, dentries cannot be freed prematurely, and execution behavior in real-world setups is fully preserved.
RootCauseFiles
[fs/dcache.c lib/lockref.c]
RootCauseSummary
A KCSAN data race is flagged between lockref_get_not_dead() in lib/lockref.c and dentry_kill() in fs/dcache.c. During an RCU-walk unlazy operation, lockref_get_not_dead() invokes CMPXCHG_LOOP to optimistically read the 8-byte lockref->lock_count (aliasing spinlock_t lock and int count) via READ_ONCE without holding the lock. Concurrently, dentry_kill() decrements parent->d_lockref.count via an unmarked 4-byte read-modify-write (--parent->d_lockref.count) while holding parent->d_lock. Because the lockless 8-byte read overlaps the concurrent unmarked 4-byte write, KCSAN detects a data race, even though the operation is benign due to lockref's lock-checking validation and fallback to spin_lock.

Crash report:
==================================================================
BUG: KCSAN: data-race in dentry_kill / lockref_get_not_dead

read (marked) to 0xffff888105d35800 of 8 bytes by task 4498 on cpu 0:
 lockref_get_not_dead+0x2f/0x1d0 lib/lockref.c:147
 __legitimize_path fs/namei.c:880 [inline]
 legitimize_path fs/namei.c:890 [inline]
 try_to_unlazy+0x1f1/0x580 fs/namei.c:954
 complete_walk+0xc5/0x200 fs/namei.c:1070
 path_parentat fs/namei.c:2868 [inline]
 __filename_parentat+0x1d2/0x460 fs/namei.c:2890
 filename_parentat fs/namei.c:2908 [inline]
 filename_unlinkat+0x91/0x400 fs/namei.c:5706
 __do_sys_unlink fs/namei.c:5772 [inline]
 __se_sys_unlink+0x2b/0xe0 fs/namei.c:5769
 __x64_sys_unlink+0x1f/0x30 fs/namei.c:5769
 x64_sys_call+0x18ee/0x2550 arch/x86/include/generated/asm/syscalls_64.h:88
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read-write to 0xffff888105d35804 of 4 bytes by task 3284 on cpu 1:
 dentry_kill+0x377/0x4f0 fs/dcache.c:877
 finish_dput+0x16/0x1d0 fs/dcache.c:1032
 dput+0x43/0x50 fs/dcache.c:1073
 end_dirop fs/namei.c:2962 [inline]
 filename_unlinkat+0x212/0x400 fs/namei.c:5740
 __do_sys_unlink fs/namei.c:5772 [inline]
 __se_sys_unlink+0x2b/0xe0 fs/namei.c:5769
 __x64_sys_unlink+0x1f/0x30 fs/namei.c:5769
 x64_sys_call+0x18ee/0x2550 arch/x86/include/generated/asm/syscalls_64.h:88
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 3284 Comm: udevd Not tainted syzkaller #0 PREEMPT(lazy) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
==================================================================

Trajectory: (Expand/Collapse All)
Seq Timestamp Type Name Duration
0/0 2026/11/17 06:13 flow assessment-security
8m Results:
map[DenialOfService:false Explanation:Root Cause Analysis:

### Root Cause Analysis

#### 1. Involved Structures, Functions, and Source Files
- **Files:** `fs/dcache.c`, `lib/lockref.c`, `include/linux/lockref.h`,
`include/linux/dcache.h`, `fs/namei.c`
- **Data Structures and Fields:**
  - `struct lockref` (`include/linux/lockref.h:25-35`):
    ```c
    struct lockref {
        union {
    #if USE_CMPXCHG_LOCKREF
            aligned_u64 lock_count;
    #endif
            struct {
                spinlock_t lock;
                int count;
            };
        };
    };
    ```
    On 64-bit systems with `USE_CMPXCHG_LOCKREF`, the 64-bit `lock_count` union
    aliases `spinlock_t lock` (bytes 0..3) and `int count` (bytes 4..7).
  - `struct dentry` (`include/linux/dcache.h:89`): defines `#define d_lock
  d_lockref.lock`.
- **Functions:**
  - Reader: `lockref_get_not_dead()` (`lib/lockref.c:143-162`) called from
  `__legitimize_path()` / `legitimize_path()` / `try_to_unlazy()`
  (`fs/namei.c:880, 890, 954`).
  - Writer: `dentry_kill()` (`fs/dcache.c:830-882`) called during dentry
  eviction via `finish_dput()` / `dput()` (`fs/dcache.c:1032, 1073`).

---

#### 2. Triggering Mechanism and Race Sequence

1. **Reader Path (`lockref_get_not_dead` in task 4498):**
   - During an RCU-walk path resolution unlazy operation (`try_to_unlazy()`),
   task 4498 attempts to legitimize a dentry reference (the parent directory
   dentry) by calling `lockref_get_not_dead(&path->dentry->d_lockref)`.
   - `lockref_get_not_dead()` enters macro `CMPXCHG_LOOP`
   (`lib/lockref.c:11-27`), which begins with an optimistic lockless 8-byte
   load:
     ```c
     old.lock_count = READ_ONCE(lockref->lock_count);
     ```
   - This 8-byte read accesses memory `0xffff888105d35800` through
   `0xffff888105d35807`, covering both the spinlock and the reference counter
   without acquiring `parent->d_lock`.

2. **Writer Path (`dentry_kill` in task 3284):**
   - Concurrently, task 3284 is destroying a child dentry inside
   `dentry_kill()`.
   - `dentry_kill()` locks the parent dentry via `spin_lock(&parent->d_lock)` at
   line 868.
   - Once the child is unlisted and freed, line 877 decrements the parent's
   reference counter:
     ```c
     if (parent && --parent->d_lockref.count) {
         spin_unlock(&parent->d_lock);
         return NULL;
     }
     ```
   - `--parent->d_lockref.count` is a 4-byte non-atomic read-modify-write
   located at offset +4 (`0xffff888105d35804`).

3. **KCSAN Detection:**
   - KCSAN observes an 8-byte marked read (`READ_ONCE(lockref->lock_count)`) on
   CPU 0 overlapping an unmarked 4-byte read-modify-write
   (`--parent->d_lockref.count`) on CPU 1.
   - Because plain C read-modify-writes (`--parent->d_lockref.count`) do not
   carry `WRITE_ONCE()` or atomic annotations, KCSAN flags the concurrent access
   as a data race.

---

#### 3. Correctness and Synchronization Analysis (Benign Data Race)

This data race is benign by design of the `lockref` subsystem:
- When task 3284 executes `--parent->d_lockref.count`, it holds `parent->d_lock`
(`parent->d_lockref.lock`).
- If task 4498's `READ_ONCE(lockref->lock_count)` runs while `parent->d_lock` is
held by task 3284:
  - `old.lock` contains the locked state
  (`arch_spin_value_unlocked(old.lock.rlock.raw_lock)` evaluates to `0`).
  - The `while` loop condition fails immediately; `CMPXCHG_LOOP` terminates
  without performing `try_cmpxchg64_relaxed()` and without using any potentially
  torn or in-transition counter value.
  - `lockref_get_not_dead()` falls back to `spin_lock(&lockref->lock)`, which
  properly blocks until task 3284 releases `parent->d_lock`, ensuring strict
  serialization.
- If task 4498's `READ_ONCE(lockref->lock_count)` runs before task 3284 acquires
the lock, `old.lock` reflects an unlocked state. However, before task 4498 can
execute `try_cmpxchg64_relaxed()`, task 3284 acquires the lock. The 64-bit
cmpxchg instruction will then compare `old.lock_count` (which has the unlocked
lock value) against current memory (which has the locked spinlock value). The
comparison fails, `old.lock_count` is reloaded with the locked state, and
execution falls back to taking the spinlock.
- Consequently, reference counts cannot be corrupted, dentries cannot be freed
prematurely, and execution behavior in real-world setups is fully preserved.

Impact Analysis:

In real-world setups without debugging sanitizers (KCSAN, lockdep, etc.), this
data race is completely benign and has no runtime consequences:

- MemoryCorruption: False. The 64-bit lockref design couples the 32-bit spinlock
with the 32-bit counter. If task 4498's READ_ONCE occurs while task 3284 holds
parent->d_lock, arch_spin_value_unlocked() evaluates to false, immediately
aborting the cmpxchg loop without touching the counter and falling back to
taking parent->d_lock (serializing after task 3284 unlocks). If the read
occurred before task 3284 acquired the lock, any cmpxchg64 attempt fails because
the lock word in memory has transitioned to locked. Therefore, refcounts are
never corrupted and dentries are not prematurely freed.
- InfoLeak: "none". No kernel memory or pointer values are leaked or exposed to
userspace.
- RawDenialOfService: False. The fallback path correctly synchronizes via
spin_lock(&lockref->lock); no deadlock, infinite loop, memory leak, or crash can
occur.
- IsNetCandidate: False. The reported stack traces involve VFS path walk and
unlinkat syscall handling; neither networking nor sockets are involved.
- IsKVMCandidate: False. The issue is in core VFS/dcache and lockref;
virtualization and KVM are not involved.

Local Reachability Analysis:

### Analysis

#### 1. Local Entry Points Investigated
The reported KCSAN data race occurs between:
1. **Task 1 (Reader):** Path lookup attempting to legitimize an RCU-walk
reference via `lockref_get_not_dead(&path->dentry->d_lockref)` in
`try_to_unlazy()` (`fs/namei.c:954`) during `complete_walk()` /
`filename_parentat()`, invoked via the `sys_unlink` / `sys_unlinkat` syscall.
2. **Task 2 (Writer):** Child dentry destruction via `dput()` / `finish_dput()`
-> `dentry_kill()` (`fs/dcache.c:877`), which decrements the parent's dentry
count (`--parent->d_lockref.count`), also invoked via standard `sys_unlink` /
`sys_unlinkat`.

Both paths are reached through standard, ubiquitous VFS operations (`unlink`,
`unlinkat`, `open`, `rmdir`, etc.) operating on user-created files and
directories (e.g., in `/tmp`).

#### 2. Capability and Configuration Checks
- Standard file-system operations like `unlink` / `unlinkat` on unprivileged
user-owned directories require no special capabilities or namespace privileges.
- Standard DAC checks permit any unprivileged process to create and unlink files
in world-writable directories such as `/tmp`.
- No capability checks (`capable()`, `ns_capable()`) gate this code path.

#### 3. Output Field Justification
- **Unprivileged (`true`):** Can be reached directly by any unprivileged user
process performing concurrent filesystem operations (such as unlinking files in
a shared directory).
- **UserNamespace (`true`):** True because it is triggerable by unprivileged
processes directly without namespaces.
- **RequiredCaps (`[]`):** No capabilities are required along the
least-privileged path.
- **PeripheralTrigger (`false`):** This is a concurrency race in the core VFS
lockref/dcache subsystem, not an issue triggered by plugging in an untrusted
hardware peripheral.
- **FilesystemTrigger (`false`):** Not triggered by mounting or parsing a
malicious filesystem disk image; it arises from concurrent userspace path lookup
and dentry reclamation.
- **RawFuzzingArtifact (`false`):** The bug is triggerable by unprivileged
processes (`Unprivileged = true`) through standard syscalls, and thus is not a
capability-gated fuzzing artifact. Exploitable:false FilesystemTrigger:false FuzzingArtifact:false InfoLeak:none MemoryCorruption:false NetworkNeedsSetup:false NetworkTrigger:false PeripheralTrigger:false RemoteTrigger:false RequiredCaps:<nil> RootCauseAnalysis:### Root Cause Analysis

#### 1. Involved Structures, Functions, and Source Files
- **Files:** `fs/dcache.c`, `lib/lockref.c`, `include/linux/lockref.h`, `include/linux/dcache.h`, `fs/namei.c`
- **Data Structures and Fields:**
  - `struct lockref` (`include/linux/lockref.h:25-35`):
    ```c
    struct lockref {
        union {
    #if USE_CMPXCHG_LOCKREF
            aligned_u64 lock_count;
    #endif
            struct {
                spinlock_t lock;
                int count;
            };
        };
    };
    ```
    On 64-bit systems with `USE_CMPXCHG_LOCKREF`, the 64-bit `lock_count` union aliases `spinlock_t lock` (bytes 0..3) and `int count` (bytes 4..7).
  - `struct dentry` (`include/linux/dcache.h:89`): defines `#define d_lock d_lockref.lock`.
- **Functions:**
  - Reader: `lockref_get_not_dead()` (`lib/lockref.c:143-162`) called from `__legitimize_path()` / `legitimize_path()` / `try_to_unlazy()` (`fs/namei.c:880, 890, 954`).
  - Writer: `dentry_kill()` (`fs/dcache.c:830-882`) called during dentry eviction via `finish_dput()` / `dput()` (`fs/dcache.c:1032, 1073`).

---

#### 2. Triggering Mechanism and Race Sequence

1. **Reader Path (`lockref_get_not_dead` in task 4498):**
   - During an RCU-walk path resolution unlazy operation (`try_to_unlazy()`), task 4498 attempts to legitimize a dentry reference (the parent directory dentry) by calling `lockref_get_not_dead(&path->dentry->d_lockref)`.
   - `lockref_get_not_dead()` enters macro `CMPXCHG_LOOP` (`lib/lockref.c:11-27`), which begins with an optimistic lockless 8-byte load:
     ```c
     old.lock_count = READ_ONCE(lockref->lock_count);
     ```
   - This 8-byte read accesses memory `0xffff888105d35800` through `0xffff888105d35807`, covering both the spinlock and the reference counter without acquiring `parent->d_lock`.

2. **Writer Path (`dentry_kill` in task 3284):**
   - Concurrently, task 3284 is destroying a child dentry inside `dentry_kill()`.
   - `dentry_kill()` locks the parent dentry via `spin_lock(&parent->d_lock)` at line 868.
   - Once the child is unlisted and freed, line 877 decrements the parent's reference counter:
     ```c
     if (parent && --parent->d_lockref.count) {
         spin_unlock(&parent->d_lock);
         return NULL;
     }
     ```
   - `--parent->d_lockref.count` is a 4-byte non-atomic read-modify-write located at offset +4 (`0xffff888105d35804`).

3. **KCSAN Detection:**
   - KCSAN observes an 8-byte marked read (`READ_ONCE(lockref->lock_count)`) on CPU 0 overlapping an unmarked 4-byte read-modify-write (`--parent->d_lockref.count`) on CPU 1.
   - Because plain C read-modify-writes (`--parent->d_lockref.count`) do not carry `WRITE_ONCE()` or atomic annotations, KCSAN flags the concurrent access as a data race.

---

#### 3. Correctness and Synchronization Analysis (Benign Data Race)

This data race is benign by design of the `lockref` subsystem:
- When task 3284 executes `--parent->d_lockref.count`, it holds `parent->d_lock` (`parent->d_lockref.lock`).
- If task 4498's `READ_ONCE(lockref->lock_count)` runs while `parent->d_lock` is held by task 3284:
  - `old.lock` contains the locked state (`arch_spin_value_unlocked(old.lock.rlock.raw_lock)` evaluates to `0`).
  - The `while` loop condition fails immediately; `CMPXCHG_LOOP` terminates without performing `try_cmpxchg64_relaxed()` and without using any potentially torn or in-transition counter value.
  - `lockref_get_not_dead()` falls back to `spin_lock(&lockref->lock)`, which properly blocks until task 3284 releases `parent->d_lock`, ensuring strict serialization.
- If task 4498's `READ_ONCE(lockref->lock_count)` runs before task 3284 acquires the lock, `old.lock` reflects an unlocked state. However, before task 4498 can execute `try_cmpxchg64_relaxed()`, task 3284 acquires the lock. The 64-bit cmpxchg instruction will then compare `old.lock_count` (which has the unlocked lock value) against current memory (which has the locked spinlock value). The comparison fails, `old.lock_count` is reloaded with the locked state, and execution falls back to taking the spinlock.
- Consequently, reference counts cannot be corrupted, dentries cannot be freed prematurely, and execution behavior in real-world setups is fully preserved. RootCauseFiles:[fs/dcache.c lib/lockref.c] RootCauseSummary:A KCSAN data race is flagged between lockref_get_not_dead() in lib/lockref.c and dentry_kill() in fs/dcache.c. During an RCU-walk unlazy operation, lockref_get_not_dead() invokes CMPXCHG_LOOP to optimistically read the 8-byte lockref->lock_count (aliasing spinlock_t lock and int count) via READ_ONCE without holding the lock. Concurrently, dentry_kill() decrements parent->d_lockref.count via an unmarked 4-byte read-modify-write (--parent->d_lockref.count) while holding parent->d_lock. Because the lockless 8-byte read overlaps the concurrent unmarked 4-byte write, KCSAN detects a data race, even though the operation is benign due to lockref's lock-checking validation and fallback to spin_lock. Unprivileged:true UserNamespace:true VMGuestTrigger:false VMHostTrigger:false]

1/1 2026/11/17 06:13 action syz-repro-to-c-repro
0m Results:
map[SimplifiedCRepro:]

2/1 2026/11/17 06:13 action kernel-checkouter
0m Results:
map[KernelSrc:/app/workdir/cache/src/6d0c4d912ac4c28457116fbfe153047fb3052961/data]

3/1 2026/11/17 06:13 action kernel-builder
0m Results:
map[KernelObj:/app/workdir/cache/build/4fc9cb093f0faa8b5951a9949e7cc5ff4ce76564/data]

4/1 2026/11/17 06:13 action codesearch-prepare
0m Results:
map[Index:codesearch-index]

5/1 2026/11/17 06:14 agent root-cause
7m Model:
core

Results:
map[ImpactAnalysis:In real-world setups without debugging sanitizers (KCSAN, lockdep, etc.), this data race is completely benign and has no runtime consequences:

- MemoryCorruption: False. The 64-bit lockref design couples the 32-bit spinlock with the 32-bit counter. If task 4498's READ_ONCE occurs while task 3284 holds parent->d_lock, arch_spin_value_unlocked() evaluates to false, immediately aborting the cmpxchg loop without touching the counter and falling back to taking parent->d_lock (serializing after task 3284 unlocks). If the read occurred before task 3284 acquired the lock, any cmpxchg64 attempt fails because the lock word in memory has transitioned to locked. Therefore, refcounts are never corrupted and dentries are not prematurely freed.
- InfoLeak: "none". No kernel memory or pointer values are leaked or exposed to userspace.
- RawDenialOfService: False. The fallback path correctly synchronizes via spin_lock(&lockref->lock); no deadlock, infinite loop, memory leak, or crash can occur.
- IsNetCandidate: False. The reported stack traces involve VFS path walk and unlinkat syscall handling; neither networking nor sockets are involved.
- IsKVMCandidate: False. The issue is in core VFS/dcache and lockref; virtualization and KVM are not involved. InfoLeak:none IsKVMCandidate:false IsNetCandidate:false MemoryCorruption:false RawDenialOfService:false RootCauseFiles:[fs/dcache.c lib/lockref.c] RootCauseSummary:A KCSAN data race is flagged between lockref_get_not_dead() in lib/lockref.c and dentry_kill() in fs/dcache.c. During an RCU-walk unlazy operation, lockref_get_not_dead() invokes CMPXCHG_LOOP to optimistically read the 8-byte lockref->lock_count (aliasing spinlock_t lock and int count) via READ_ONCE without holding the lock. Concurrently, dentry_kill() decrements parent->d_lockref.count via an unmarked 4-byte read-modify-write (--parent->d_lockref.count) while holding parent->d_lock. Because the lockless 8-byte read overlaps the concurrent unmarked 4-byte write, KCSAN detects a data race, even though the operation is benign due to lockref's lock-checking validation and fallback to spin_lock.]

Instruction:
You are an experienced Linux kernel security engineer. Your task is to analyze the given kernel bug report,
determine its root cause in the kernel source tree, and classify the direct consequences of the defect.

Use the provided tools to examine the source code and understand the exact nature of the bug:
- Determine the root cause directly from the present state of the source code. Do NOT search git history or run
  git-log/git-blame to find when code was introduced or modified; only use git tools as a last resort if the current
  code itself is ambiguous and cannot be understood without a commit description.
- You can check the kernel build configuration and "CONFIG_CMDLINE=" using the kernel-config-grep tool (do not
  try to read or grep ".config" as a file in the source tree). Assume sysctl parameters have default values.
- When classifying consequences, consider real-world setups WITHOUT debugging sanitizers enabled
  (KASAN, KMSAN, KCSAN, UBSAN, lockdep) and without panic_on_warn enabled.

In your final reply, write a clear, detailed technical explanation of the root cause aimed at kernel developers
investigating and fixing the bug:
- The exact functions, structs, fields, and files involved.
- How the bug is triggered, what invariant or lifecycle rule is violated, and how that leads to the reported failure.
- Keep the final reply strictly focused on the bug's technical mechanism and root cause; put all impact evaluation and
  classification reasoning into `ImpactAnalysis` when calling `set-results`.
- Pinpointing the exact root cause is best-effort: try your best, but if the problem turns out to be too complicated or
  inconclusive after thoroughly inspecting the functions in the crash, allocation, and free stacks (for example, an
  elusive race or external/deferred memory corruption where the offending caller is not recorded in the report), it is
  okay to give up on finding the exact trigger rather than searching indefinitely. State your verified findings (the
  crash site, object lifecycle, invariants checked, and hypotheses ruled out), note what remains inconclusive, and
  provide best-effort output values so downstream steps have enough context to assess the impact and reachability of the
  problem.
Another engineer will use your explanation and `ImpactAnalysis` to trace caller reachability and attack surfaces.

Analysis dimensions (in output schema order):

* RootCauseSummary:
Provide a concise (up to 4-5 sentences), self-contained technical summary of the root cause (or verified crash
mechanism if the exact trigger is inconclusive) and how it leads to the reported failure, suitable for displaying at the
top of a bug report or email above the full technical breakdown.

* RootCauseFiles:
Provide a short non-empty list (typically 1-3 files) of kernel source file paths (relative to the kernel tree root,
e.g., "net/ipv4/tcp_input.c") where the underlying defect resides.
Distinguish where the crash *manifests* from where the actual *bug* is:
- Do NOT list generic error-reporting, memory-allocator, refcount-tracking, or locking infrastructure files
  (such as "mm/kasan/", "mm/slub.c", "lib/ref_tracker.c", "lib/dump_stack.c", "kernel/locking/lockdep.c",
  or generic sk_buff helpers in "net/core/skbuff.c") unless the defect is genuinely in that core infrastructure itself.
- Instead, inspect the call trace, allocation/free stacks, and object lifecycle to identify the specific
  subsystem, protocol, or driver file(s) containing the faulty logic.

* ImpactAnalysis:
Explain what happens at runtime in real-world setups (without debugging sanitizers or panic_on_warn) after the bug is
triggered, and why you chose each of the remaining output values (`MemoryCorruption`, `InfoLeak`,
`RawDenialOfService`, `IsNetCandidate`, `IsKVMCandidate`).

* MemoryCorruption:
Set to true if the bug can result in memory corruption, use-after-free, out-of-bounds write, invalid/double free,
control-flow hijack, or direct privilege escalation in real-world setups.
- Memory safety issues (KASAN or UBSAN reports for use-after-free, out-of-bounds write, invalid free; refcounting
  imbalances, corrupted linked lists, etc.) are almost always true.
- When the kernel crashes on a wild pointer access (e.g., a user-space address or non-canonical address, including
  both data accesses and control transfers, often reported as "unable to handle kernel paging request"), set to true.
- Pure NULL-pointer dereferences (including accesses to KASAN shadow memory for NULL around 0xdfff800000000000 or
  0xdffffc0000000000) do NOT count as memory corruption on their own; set MemoryCorruption to false for those.
- Pure out-of-bounds reads or uninitialized memory reads (KMSAN) that only copy data to userspace without corrupting
  memory or hijacking control flow should have MemoryCorruption = false (classify those under InfoLeak instead).
  However, if an uninitialized value or out-of-bounds read is subsequently used as a pointer, array index, allocation
  size, or branch condition that leads to memory corruption, set MemoryCorruption to true.
- For KCSAN data races, think whether concurrent access can corrupt pointers, refcounts, lengths, or state machines
  in a way that leads to memory corruption; benign races (e.g., statistics counters or idempotent flags) are false.

* InfoLeak:
Determine whether the bug can leak kernel memory contents to userspace or an external observer. Must be one of:
- "none": The bug does not leak kernel memory contents.
- "pointers": The bug only leaks kernel, guest, or userspace pointer values (e.g., defeating KASLR by exposing an
  uninitialized pointer field or printing/returning an unhashed kernel address, with no other data leaked).
- "arbitrary": The bug can leak non-pointer kernel memory contents (e.g., an out-of-bounds read or uninitialized
  heap/stack buffer copied to userspace or to a network packet). If a leak is present and there is no obvious,
  strict guarantee that only pointer values can be read, use "arbitrary".

* RawDenialOfService:
Set to true if the bug can result in denial-of-service in real-world setups (system crash/panic/BUG, NULL-pointer
dereference, hang, deadlock, infinite loop, CPU/network saturation, or memory/resource leak).
- Note that WARNING reports (WARN_ON / WARN_ON_ONCE) and sanitizer splats do NOT halt execution in real-world setups.
  For WARNINGs, check what happens in the code after the macro: if the unexpected condition is gracefully handled
  by normal error recovery (e.g., "if (WARN_ON(...)) return -EINVAL;") without leaking resources or leaving locks/state
  inconsistent, set RawDenialOfService to false.
- Benign KCSAN data races that do not cause crashes, hangs, or resource leaks also have RawDenialOfService = false.

* IsNetCandidate:
Set to true if the bug, call trace, or reproducer has any relation to networking, sockets, network devices,
network protocols, or remote packet processing (so that a dedicated network-reachability pass should evaluate it).

* IsKVMCandidate:
Set to true if the bug, call trace, or reproducer has any relation to KVM, virtualization, hypervisors,
vhost/virtio, or guest/host interfaces (so that a dedicated virtualization-reachability pass should evaluate it).

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.

During execution, you may receive periodic guidance in <supervisor_advice> tags;
use it to refine your investigation or wrap up once you have sufficient evidence.

Prompt:
The kernel bug report is:

==================================================================
BUG: KCSAN: data-race in dentry_kill / lockref_get_not_dead

read (marked) to 0xffff888105d35800 of 8 bytes by task 4498 on cpu 0:
 lockref_get_not_dead+0x2f/0x1d0 lib/lockref.c:147
 __legitimize_path fs/namei.c:880 [inline]
 legitimize_path fs/namei.c:890 [inline]
 try_to_unlazy+0x1f1/0x580 fs/namei.c:954
 complete_walk+0xc5/0x200 fs/namei.c:1070
 path_parentat fs/namei.c:2868 [inline]
 __filename_parentat+0x1d2/0x460 fs/namei.c:2890
 filename_parentat fs/namei.c:2908 [inline]
 filename_unlinkat+0x91/0x400 fs/namei.c:5706
 __do_sys_unlink fs/namei.c:5772 [inline]
 __se_sys_unlink+0x2b/0xe0 fs/namei.c:5769
 __x64_sys_unlink+0x1f/0x30 fs/namei.c:5769
 x64_sys_call+0x18ee/0x2550 arch/x86/include/generated/asm/syscalls_64.h:88
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read-write to 0xffff888105d35804 of 4 bytes by task 3284 on cpu 1:
 dentry_kill+0x377/0x4f0 fs/dcache.c:877
 finish_dput+0x16/0x1d0 fs/dcache.c:1032
 dput+0x43/0x50 fs/dcache.c:1073
 end_dirop fs/namei.c:2962 [inline]
 filename_unlinkat+0x212/0x400 fs/namei.c:5740
 __do_sys_unlink fs/namei.c:5772 [inline]
 __se_sys_unlink+0x2b/0xe0 fs/namei.c:5769
 __x64_sys_unlink+0x1f/0x30 fs/namei.c:5769
 x64_sys_call+0x18ee/0x2550 arch/x86/include/generated/asm/syscalls_64.h:88
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 3284 Comm: udevd Not tainted syzkaller #0 PREEMPT(lazy) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
==================================================================




Reply:
### Root Cause Analysis

#### 1. Involved Structures, Functions, and Source Files
- **Files:** `fs/dcache.c`, `lib/lockref.c`, `include/linux/lockref.h`, `include/linux/dcache.h`, `fs/namei.c`
- **Data Structures and Fields:**
  - `struct lockref` (`include/linux/lockref.h:25-35`):
    ```c
    struct lockref {
        union {
    #if USE_CMPXCHG_LOCKREF
            aligned_u64 lock_count;
    #endif
            struct {
                spinlock_t lock;
                int count;
            };
        };
    };
    ```
    On 64-bit systems with `USE_CMPXCHG_LOCKREF`, the 64-bit `lock_count` union aliases `spinlock_t lock` (bytes 0..3) and `int count` (bytes 4..7).
  - `struct dentry` (`include/linux/dcache.h:89`): defines `#define d_lock d_lockref.lock`.
- **Functions:**
  - Reader: `lockref_get_not_dead()` (`lib/lockref.c:143-162`) called from `__legitimize_path()` / `legitimize_path()` / `try_to_unlazy()` (`fs/namei.c:880, 890, 954`).
  - Writer: `dentry_kill()` (`fs/dcache.c:830-882`) called during dentry eviction via `finish_dput()` / `dput()` (`fs/dcache.c:1032, 1073`).

---

#### 2. Triggering Mechanism and Race Sequence

1. **Reader Path (`lockref_get_not_dead` in task 4498):**
   - During an RCU-walk path resolution unlazy operation (`try_to_unlazy()`), task 4498 attempts to legitimize a dentry reference (the parent directory dentry) by calling `lockref_get_not_dead(&path->dentry->d_lockref)`.
   - `lockref_get_not_dead()` enters macro `CMPXCHG_LOOP` (`lib/lockref.c:11-27`), which begins with an optimistic lockless 8-byte load:
     ```c
     old.lock_count = READ_ONCE(lockref->lock_count);
     ```
   - This 8-byte read accesses memory `0xffff888105d35800` through `0xffff888105d35807`, covering both the spinlock and the reference counter without acquiring `parent->d_lock`.

2. **Writer Path (`dentry_kill` in task 3284):**
   - Concurrently, task 3284 is destroying a child dentry inside `dentry_kill()`.
   - `dentry_kill()` locks the parent dentry via `spin_lock(&parent->d_lock)` at line 868.
   - Once the child is unlisted and freed, line 877 decrements the parent's reference counter:
     ```c
     if (parent && --parent->d_lockref.count) {
         spin_unlock(&parent->d_lock);
         return NULL;
     }
     ```
   - `--parent->d_lockref.count` is a 4-byte non-atomic read-modify-write located at offset +4 (`0xffff888105d35804`).

3. **KCSAN Detection:**
   - KCSAN observes an 8-byte marked read (`READ_ONCE(lockref->lock_count)`) on CPU 0 overlapping an unmarked 4-byte read-modify-write (`--parent->d_lockref.count`) on CPU 1.
   - Because plain C read-modify-writes (`--parent->d_lockref.count`) do not carry `WRITE_ONCE()` or atomic annotations, KCSAN flags the concurrent access as a data race.

---

#### 3. Correctness and Synchronization Analysis (Benign Data Race)

This data race is benign by design of the `lockref` subsystem:
- When task 3284 executes `--parent->d_lockref.count`, it holds `parent->d_lock` (`parent->d_lockref.lock`).
- If task 4498's `READ_ONCE(lockref->lock_count)` runs while `parent->d_lock` is held by task 3284:
  - `old.lock` contains the locked state (`arch_spin_value_unlocked(old.lock.rlock.raw_lock)` evaluates to `0`).
  - The `while` loop condition fails immediately; `CMPXCHG_LOOP` terminates without performing `try_cmpxchg64_relaxed()` and without using any potentially torn or in-transition counter value.
  - `lockref_get_not_dead()` falls back to `spin_lock(&lockref->lock)`, which properly blocks until task 3284 releases `parent->d_lock`, ensuring strict serialization.
- If task 4498's `READ_ONCE(lockref->lock_count)` runs before task 3284 acquires the lock, `old.lock` reflects an unlocked state. However, before task 4498 can execute `try_cmpxchg64_relaxed()`, task 3284 acquires the lock. The 64-bit cmpxchg instruction will then compare `old.lock_count` (which has the unlocked lock value) against current memory (which has the locked spinlock value). The comparison fails, `old.lock_count` is reloaded with the locked state, and execution falls back to taking the spinlock.
- Consequently, reference counts cannot be corrupted, dentries cannot be freed prematurely, and execution behavior in real-world setups is fully preserved.

6/2 2026/11/17 06:14 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 5971
							output: 68
							thoughts: 920
						

Thoughts:
**Examining a KCSAN Data-Race in the Kernel**

Alright, let's dive into this KCSAN report. The core issue identified is a data-race occurring within `dentry_kill` and `lockref_get_not_dead`. I need to understand the sequence of operations that's leading to this conflict.

Looking at the first trace, I see a read operation on memory address `0xffff888105d35800` (8 bytes) by task 4498 on CPU 0. This read originates from `lockref_get_not_dead` at line 147 in `lib/lockref.c`, and it's part of a call chain that eventually leads to `filename_unlinkat`. This suggests that a path legitimization process, likely involving the `dentry` associated with the file being unlinked, is accessing the `lockref`.

The second trace, crucially, points to a read-write operation on `0xffff888105d35804` (4 bytes) by task 3284 on CPU 1. This operation is happening within `dentry_kill` at line 877 in `fs/dcache.c`, and it's also part of the `filename_unlinkat` sequence, specifically during the `dput` operation. This means that while one task is trying to validate the `lockref` of a `dentry` as part of its path traversal for an unlink, another task is attempting to modify or finalize the `dentry`'s state (likely during its de-referencing and potential destruction).

The critical overlap is the memory region `0xffff888105d35800` and `0xffff888105d35804`, which are very close. It's highly probable that the `lockref` object itself, or data immediately surrounding it within the `dentry` structure, is being accessed concurrently by these two distinct operations: one reading to check the `lockref`'s validity (`lockref_get_not_dead`), and another writing as part of the `dentry`'s lifecycle management (`dentry_kill`).

My immediate next step is to scrutinize the source code at `lib/lockref.c:147` and `fs/dcache.c:877`. I need to see how `lockref_get_not_dead` interacts with the `lockref` and understand the exact modification occurring in `dentry_kill` at that specific line. I'll be looking for how the `lockref` is managed, specifically its `dead` flag, and how the operations within `dentry_kill` could be racing against the read-validate operation. I'll use `read-file` to pull up and analyze these specific code snippets to pinpoint the exact race condition.


7/2 2026/11/17 06:14 tool read-file
0m Args:
map[File:lib/lockref.c FirstLine:130 LineCount:40]

Results:
map[Contents: 130:	 */
 131:	void lockref_mark_dead(struct lockref *lockref)
 132:	{
 133:		assert_spin_locked(&lockref->lock);
 134:		lockref->count = __LOCKREF_DEAD_VAL;
 135:	}
 136:	EXPORT_SYMBOL(lockref_mark_dead);
 137:	
 138:	/**
 139:	 * lockref_get_not_dead - Increments count unless the ref is dead
 140:	 * @lockref: pointer to lockref structure
 141:	 * Return: 1 if count updated successfully or 0 if lockref was dead
 142:	 */
 143:	bool lockref_get_not_dead(struct lockref *lockref)
 144:	{
 145:		bool retval = false;
 146:	
 147:		CMPXCHG_LOOP(
 148:			new.count++;
 149:			if (old.count < 0)
 150:				return false;
 151:		,
 152:			return true;
 153:		);
 154:	
 155:		spin_lock(&lockref->lock);
 156:		if (lockref->count >= 0) {
 157:			lockref->count++;
 158:			retval = true;
 159:		}
 160:		spin_unlock(&lockref->lock);
 161:		return retval;
 162:	}
 163:	EXPORT_SYMBOL(lockref_get_not_dead);
]

8/2 2026/11/17 06:14 tool read-file
0m Args:
map[File:fs/dcache.c FirstLine:860 LineCount:40]

Results:
map[Contents: 860:		this_cpu_dec(nr_dentry);
 861:		if (dentry->d_op && dentry->d_op->d_release)
 862:			dentry->d_op->d_release(dentry);
 863:	
 864:		cond_resched_tasks_rcu_qs();
 865:		/* now that it's negative, ->d_parent is stable */
 866:		if (!IS_ROOT(dentry)) {
 867:			parent = dentry->d_parent;
 868:			spin_lock(&parent->d_lock);
 869:		}
 870:		spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
 871:		dentry_unlist(dentry);
 872:		if (dentry->d_flags & DCACHE_SHRINK_LIST)
 873:			can_free = false;
 874:		spin_unlock(&dentry->d_lock);
 875:		if (likely(can_free))
 876:			dentry_free(dentry);
 877:		if (parent && --parent->d_lockref.count) {
 878:			spin_unlock(&parent->d_lock);
 879:			return NULL;
 880:		}
 881:		return parent;
 882:	}
 883:	
 884:	/*
 885:	 * Decide if dentry is worth retaining.  Usually this is called with dentry
 886:	 * locked; if not locked, we are more limited and might not be able to tell
 887:	 * without a lock.  False in this case means "punt to locked path and recheck".
 888:	 *
 889:	 * In case we aren't locked, these predicates are not "stable". However, it is
 890:	 * sufficient that at some point after we dropped the reference the dentry was
 891:	 * hashed and the flags had the proper value. Other dentry users may have
 892:	 * re-gotten a reference to the dentry and change that, but our work is done -
 893:	 * we can leave the dentry around with a zero refcount.
 894:	 */
 895:	static inline bool retain_dentry(struct dentry *dentry, bool locked)
 896:	{
 897:		unsigned int d_flags;
 898:	
 899:		smp_rmb();
]

9/2 2026/11/17 06:14 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 8070
							output: 34
							thoughts: 160
						

Thoughts:
**Delving into the Dentry Lifecycle: A Chain of Thought**

My attention is drawn to line 877 in `fs/dcache.c`, specifically the `dentry_kill` function. I'm scrutinizing its behavior, particularly this snippet:

if (parent && --parent->d_lockref.count) {
    spin_unlock(&parent->d_lock);
    return NULL;
}
return parent;

Right there, the critical piece: `parent->d_lockref.count`. This immediately sparks a question in my mind. What is the significance of this `lockref` count in relation to the parent dentry? My intuition tells me it's central to managing the lifecycle and potential destruction of a dentry.

This leads me to consider the broader context. How does this count get managed? What operations increment or decrement it, and under what conditions? My mind immediately jumps to a specific process, task 4498. I recall or infer that this task is involved in a crucial operation: `lockref_get_not_dead(&dentry->d_lockref)`. This operation is called within `__legitimize_path` and `legitimize_path`.

To understand the implications of `lockref_get_not_dead` in relation to `dentry_kill`, I need to trace the flow. I'll therefore turn my attention to `fs/namei.c`, specifically examining lines 870 through 960. My objective is to fully grasp how `legitimize_path` interacts with dentry lock references, how task 4498's actions might affect this count, and how all of this ultimately influences the conditions under which a dentry is killed or kept alive, as dictated by the `dentry_kill` logic. I'm essentially trying to connect the dots between path resolution, dentry lifecycle management, and the atomic operations that ensure data integrity.


10/2 2026/11/17 06:14 tool read-file
0m Args:
map[File:fs/namei.c FirstLine:870 LineCount:90]

Results:
map[Contents: 870:	/* path_put is needed afterwards regardless of success or failure */
 871:	static bool __legitimize_path(struct path *path, unsigned seq, unsigned mseq)
 872:	{
 873:		int res = __legitimize_mnt(path->mnt, mseq);
 874:		if (unlikely(res)) {
 875:			if (res > 0)
 876:				path->mnt = NULL;
 877:			path->dentry = NULL;
 878:			return false;
 879:		}
 880:		if (unlikely(!lockref_get_not_dead(&path->dentry->d_lockref))) {
 881:			path->dentry = NULL;
 882:			return false;
 883:		}
 884:		return !read_seqcount_retry(&path->dentry->d_seq, seq);
 885:	}
 886:	
 887:	static inline bool legitimize_path(struct nameidata *nd,
 888:				    struct path *path, unsigned seq)
 889:	{
 890:		return __legitimize_path(path, seq, nd->m_seq);
 891:	}
 892:	
 893:	static bool legitimize_links(struct nameidata *nd)
 894:	{
 895:		int i;
 896:	
 897:		VFS_BUG_ON(nd->flags & LOOKUP_CACHED);
 898:	
 899:		for (i = 0; i < nd->depth; i++) {
 900:			struct saved *last = nd->stack + i;
 901:			if (unlikely(!legitimize_path(nd, &last->link, last->seq))) {
 902:				drop_links(nd);
 903:				nd->depth = i + 1;
 904:				return false;
 905:			}
 906:		}
 907:		return true;
 908:	}
 909:	
 910:	static bool legitimize_root(struct nameidata *nd)
 911:	{
 912:		/* Nothing to do if nd->root is zero or is managed by the VFS user. */
 913:		if (!nd->root.mnt || (nd->state & ND_ROOT_PRESET))
 914:			return true;
 915:		nd->state |= ND_ROOT_GRABBED;
 916:		return legitimize_path(nd, &nd->root, nd->root_seq);
 917:	}
 918:	
 919:	/*
 920:	 * Path walking has 2 modes, rcu-walk and ref-walk (see
 921:	 * Documentation/filesystems/path-lookup.txt).  In situations when we can't
 922:	 * continue in RCU mode, we attempt to drop out of rcu-walk mode and grab
 923:	 * normal reference counts on dentries and vfsmounts to transition to ref-walk
 924:	 * mode.  Refcounts are grabbed at the last known good point before rcu-walk
 925:	 * got stuck, so ref-walk may continue from there. If this is not successful
 926:	 * (eg. a seqcount has changed), then failure is returned and it's up to caller
 927:	 * to restart the path walk from the beginning in ref-walk mode.
 928:	 */
 929:	
 930:	/**
 931:	 * try_to_unlazy - try to switch to ref-walk mode.
 932:	 * @nd: nameidata pathwalk data
 933:	 * Returns: true on success, false on failure
 934:	 *
 935:	 * try_to_unlazy attempts to legitimize the current nd->path and nd->root
 936:	 * for ref-walk mode.
 937:	 * Must be called from rcu-walk context.
 938:	 * Nothing should touch nameidata between try_to_unlazy() failure and
 939:	 * terminate_walk().
 940:	 */
 941:	static bool try_to_unlazy(struct nameidata *nd)
 942:	{
 943:		struct dentry *parent = nd->path.dentry;
 944:	
 945:		VFS_BUG_ON(!(nd->flags & LOOKUP_RCU));
 946:	
 947:		if (unlikely(nd->flags & LOOKUP_CACHED)) {
 948:			drop_links(nd);
 949:			nd->depth = 0;
 950:			goto out1;
 951:		}
 952:		if (unlikely(nd->depth && !legitimize_links(nd)))
 953:			goto out1;
 954:		if (unlikely(!legitimize_path(nd, &nd->path, nd->seq)))
 955:			goto out;
 956:		if (unlikely(!legitimize_root(nd)))
 957:			goto out;
 958:		leave_rcu(nd);
 959:		BUG_ON(nd->inode != parent->d_inode);
]

11/2 2026/11/17 06:14 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 9687
							output: 32
							thoughts: 51
						

Thoughts:
**Navigating the Lockref Implementation**

My current train of thought is focused on dissecting the `lockref` mechanism, and to do that, I need to dive into the source code. My immediate goal is to examine `lib/lockref.c`. Within this file, I'm particularly interested in understanding precisely how `lockref` is defined – what constitutes its structure and how it's intended to be utilized across the system.

This naturally leads me to scrutinize the definition of `struct lockref` itself. I need to see its constituent members to grasp the underlying data it manages. Simultaneously, I'm keen to understand the implementation of critical constructs like `CMPXCHG_LOOP`. This macro, I suspect, is central to the atomic operations that underpin the `lockref`'s locking behavior, and I want to see its specifics. Beyond that, I'll be reviewing all other associated `lockref` functions to build a comprehensive mental model of how this locking primitive operates, from initialization and locking to unlocking and state checking. My aim is to fully comprehend its mechanics and its role within the broader system architecture.


12/2 2026/11/17 06:14 tool codesearch-definition-source
0m Args:
map[ContextFile:lib/lockref.c Name:lockref]

Results:
map[SourceCode:  25:	struct lockref {
  26:		union {
  27:	#if USE_CMPXCHG_LOCKREF
  28:			aligned_u64 lock_count;
  29:	#endif
  30:			struct {
  31:				spinlock_t lock;
  32:				int count;
  33:			};
  34:		};
  35:	};
 SourceFile:include/linux/lockref.h]

13/2 2026/11/17 06:14 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 9888
							output: 32
							thoughts: 398
						

Thoughts:
**My Investigative Journey into the `lockref` Race Condition**

I'm digging into a KCSAN report that's pointing to a potential race condition involving the `struct lockref` data structure. My initial step was to dissect the `lockref` definition itself. I see that it's a union, designed to be either an `aligned_u64 lock_count` or a `struct { spinlock_t lock; int count; }`. On my target architecture, x86_64, I know `spinlock_t` (or `arch_spinlock_t`) is 4 bytes and `int count` is also 4 bytes. This means that when they're packed into the `struct`, `lock` will occupy bytes 0-3, and `count` will occupy bytes 4-7. Conveniently, this exactly matches the size and alignment of an 8-byte `aligned_u64`. This is clearly an optimization to allow atomic operations on the entire 8-byte field when `USE_CMPXCHG_LOCKREF` is enabled.

Now, I'm correlating this with the KCSAN report. I see two distinct memory accesses being flagged:

1.  **`read (marked) to 0xffff888105d35800 of 8 bytes by task 4498 on cpu 0: lockref_get_not_dead+0x2f/0x1d0 lib/lockref.c:147`**
    This first access is interesting. It's reading 8 bytes from the base address `0xffff888105d35800`. Given my understanding of `lockref`, this address perfectly corresponds to the beginning of the `lockref` structure, and the 8-byte read strongly suggests it's targeting the entire `aligned_u64 lock_count` field, which encompasses both the `spinlock_t lock` and the `int count`. The fact that this is a read happening within `lockref_get_not_dead` at line 147 of `lib/lockref.c` is my starting point for understanding the intended behavior.

2.  **`read-write to 0xffff888105d35804 of 4 bytes by task 3284 on cpu 1: dentry_kill+0x377/0x4f0 fs/dcache.c:877`**
    This second access is even more telling. It's a read-write operation, not just a read, and it's targeting `0xffff888105d35804` for 4 bytes. Looking back at my `lockref` structure breakdown, offset 4 from the base address is precisely where the `int count` member resides. This operation is happening within `dentry_kill` in `fs/dcache.c`. The fact that this is a read-write on just the `count` field, while another thread is potentially reading or manipulating the entire 8-byte `lock_count` (which includes the spinlock), is the core of the potential race condition I need to investigate.

My next logical step is to dive deep into `lib/lockref.c` to understand the `CMPXCHG_LOOP` mechanism and the precise logic within `lockref_get_not_dead`. I need to see how these atomic operations are intended to work and how the simultaneous access to different parts of the `lockref` union, one reading the whole 8 bytes and the other writing to a 4-byte portion, could lead to a data corruption or a missed update. This is where the true nature of the race will be revealed.


14/2 2026/11/17 06:14 tool read-file
0m Args:
map[File:lib/lockref.c FirstLine:1 LineCount:80]

Results:
map[Contents:   1:	// SPDX-License-Identifier: GPL-2.0
   2:	#include <linux/export.h>
   3:	#include <linux/lockref.h>
   4:	
   5:	#if USE_CMPXCHG_LOCKREF
   6:	
   7:	/*
   8:	 * Note that the "cmpxchg()" reloads the "old" value for the
   9:	 * failure case.
  10:	 */
  11:	#define CMPXCHG_LOOP(CODE, SUCCESS) do {					\
  12:		int retry = 100;							\
  13:		struct lockref old;							\
  14:		BUILD_BUG_ON(sizeof(old) != 8);						\
  15:		old.lock_count = READ_ONCE(lockref->lock_count);			\
  16:		while (likely(arch_spin_value_unlocked(old.lock.rlock.raw_lock))) {  	\
  17:			struct lockref new = old;					\
  18:			CODE								\
  19:			if (likely(try_cmpxchg64_relaxed(&lockref->lock_count,		\
  20:							 &old.lock_count,		\
  21:							 new.lock_count))) {		\
  22:				SUCCESS;						\
  23:			}								\
  24:			if (!--retry)							\
  25:				break;							\
  26:		}									\
  27:	} while (0)
  28:	
  29:	#else
  30:	
  31:	#define CMPXCHG_LOOP(CODE, SUCCESS) do { } while (0)
  32:	
  33:	#endif
  34:	
  35:	/**
  36:	 * lockref_get - Increments reference count unconditionally
  37:	 * @lockref: pointer to lockref structure
  38:	 *
  39:	 * This operation is only valid if you already hold a reference
  40:	 * to the object, so you know the count cannot be zero.
  41:	 */
  42:	void lockref_get(struct lockref *lockref)
  43:	{
  44:		CMPXCHG_LOOP(
  45:			new.count++;
  46:		,
  47:			return;
  48:		);
  49:	
  50:		spin_lock(&lockref->lock);
  51:		lockref->count++;
  52:		spin_unlock(&lockref->lock);
  53:	}
  54:	EXPORT_SYMBOL(lockref_get);
  55:	
  56:	/**
  57:	 * lockref_get_not_zero - Increments count unless the count is 0 or dead
  58:	 * @lockref: pointer to lockref structure
  59:	 * Return: 1 if count updated successfully or 0 if count was zero
  60:	 */
  61:	bool lockref_get_not_zero(struct lockref *lockref)
  62:	{
  63:		bool retval = false;
  64:	
  65:		CMPXCHG_LOOP(
  66:			new.count++;
  67:			if (old.count <= 0)
  68:				return false;
  69:		,
  70:			return true;
  71:		);
  72:	
  73:		spin_lock(&lockref->lock);
  74:		if (lockref->count > 0) {
  75:			lockref->count++;
  76:			retval = true;
  77:		}
  78:		spin_unlock(&lockref->lock);
  79:		return retval;
  80:	}
]

15/2 2026/11/17 06:14 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 11310
							output: 34
							thoughts: 472
						

Thoughts:
**My Exploration of `CMPXCHG_LOOP` and its Implications**

As I delve into the `CMPXCHG_LOOP` macro, my initial focus is on its core mechanism: a spin loop employing compare-and-swap (CAS) for atomic updates to a `lockref` structure. I notice the `BUILD_BUG_ON(sizeof(old) != 8)` which immediately tells me we're dealing with 64-bit atomic operations, a critical detail for performance and correctness.

Then, my attention is drawn to this line within the macro: `old.lock_count = READ_ONCE(lockref->lock_count);`. This seems straightforward enough – it's reading the current lock state before attempting an update. However, my mind immediately flags this as a potential point of interest, especially when I see it's part of a larger operation that will ultimately be placed at line 147 in `lib/lockref.c`, specifically within the `lockref_get_not_dead` function.

The fact that this `READ_ONCE` operation is associated with a 8-byte read at a specific memory address (0xffff888105d35800) in the context of `lockref_get_not_dead` makes me pause. This function is about acquiring a reference to a lock-protected object without encountering deadlocks, and `READ_ONCE` suggests a relaxed memory ordering. This is fine for the initial read, but I'm keenly aware of the potential for races if subsequent operations aren't properly synchronized.

My thought process then jumps to a specific call site: task 3284 in `dentry_kill` at `fs/dcache.c:877`. I'm looking at the line `if (parent && --parent->d_lockref.count) {`. Here, I see `parent->d_lockref.count` being decremented. This `count` is part of the `d_lockref` structure.

Connecting the dots, I realize that `parent->d_lockref.count` is very likely the same `lock_count` field that `CMPXCHG_LOOP` is operating on. If `dentry_kill` is about to decrement this count, and `lockref_get_not_dead` is potentially reading it within the `CMPXCHG_LOOP` macro, I'm concerned about a race condition. Specifically, if `dentry_kill` decrements the count while `lockref_get_not_dead` is inside the `CMPXCHG_LOOP` and has just read the value via `READ_ONCE`, the subsequent `try_cmpxchg64_relaxed` could fail unexpectedly, or worse, lead to incorrect state management if the decrement isn't properly coordinated with the CAS.

My focus then shifts back to the `dentry_kill` function itself, specifically examining the code around lines 865 to 900 in `fs/dcache.c`. I need to understand the precise logic for how `dentry_kill` interacts with the `d_lockref.count`. Is this decrement happening before or after a potential CAS operation? Is there any other synchronization mechanism in place that might mitigate the risk I'm seeing? My goal is to ensure that the relaxed read of `lock_count` by `CMPXCHG_LOOP` (when invoked by `lockref_get_not_dead`) doesn't interfere with or get invalidated by the decrement operation in `dentry_kill`.


16/2 2026/11/17 06:14 tool read-file
0m Args:
map[File:fs/dcache.c FirstLine:850 LineCount:40]

Results:
map[Contents: 850:		if (dentry->d_flags & DCACHE_LRU_LIST) {
 851:			if (!(dentry->d_flags & DCACHE_SHRINK_LIST))
 852:				d_lru_del(dentry);
 853:		}
 854:		/* if it was on the hash then remove it */
 855:		__d_drop(dentry);
 856:		if (dentry->d_inode)
 857:			dentry_unlink_inode(dentry);
 858:		else
 859:			spin_unlock(&dentry->d_lock);
 860:		this_cpu_dec(nr_dentry);
 861:		if (dentry->d_op && dentry->d_op->d_release)
 862:			dentry->d_op->d_release(dentry);
 863:	
 864:		cond_resched_tasks_rcu_qs();
 865:		/* now that it's negative, ->d_parent is stable */
 866:		if (!IS_ROOT(dentry)) {
 867:			parent = dentry->d_parent;
 868:			spin_lock(&parent->d_lock);
 869:		}
 870:		spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
 871:		dentry_unlist(dentry);
 872:		if (dentry->d_flags & DCACHE_SHRINK_LIST)
 873:			can_free = false;
 874:		spin_unlock(&dentry->d_lock);
 875:		if (likely(can_free))
 876:			dentry_free(dentry);
 877:		if (parent && --parent->d_lockref.count) {
 878:			spin_unlock(&parent->d_lock);
 879:			return NULL;
 880:		}
 881:		return parent;
 882:	}
 883:	
 884:	/*
 885:	 * Decide if dentry is worth retaining.  Usually this is called with dentry
 886:	 * locked; if not locked, we are more limited and might not be able to tell
 887:	 * without a lock.  False in this case means "punt to locked path and recheck".
 888:	 *
 889:	 * In case we aren't locked, these predicates are not "stable". However, it is
]

17/2 2026/11/17 06:14 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 12484
							output: 31
							thoughts: 181
						

Thoughts:
**Initial Musings on `dentry_kill` and `d_lockref`**

My attention is immediately drawn to the `d_lockref.count` field within the `dentry_kill` function. A quick glance reveals a seemingly innocuous decrement operation: `--parent->d_lockref.count`. This immediately sparks a question: how exactly does this `lockref` mechanism function, and what are the implications of this decrement in the context of `dentry_kill`?

I find myself pondering the sequence of operations in `dentry_kill`. The code first checks `!IS_ROOT(dentry)`. If this condition holds, it retrieves the `parent` dentry and acquires its lock: `spin_lock(&parent->d_lock)`. Following this, it performs the decrement: `if (parent && --parent->d_lockref.count)`. The subsequent conditional branch, `spin_unlock(&parent->d_lock); return NULL;`, suggests that the `d_lockref.count` plays a crucial role in determining whether the parent's lock should be released immediately or if some other path should be taken. This interaction, particularly the decrement and subsequent conditional unlock, is the core of my current curiosity.

To fully grasp the behavior and potential ramifications, I need to understand the `lockref` mechanism itself. What is its purpose? How is it initialized? And, most importantly, how is it manipulated elsewhere in the codebase? My immediate next step is to explore other instances where `d_lockref` is modified or checked. Specifically, I'll be looking for other places in `fs/dcache.c` where `d_lockref` is decremented or incremented, or where its value is otherwise directly acted upon. A `grep` for `d_lockref` across `fs/dcache.c` seems like the most efficient way to locate these relevant sections of code and build a more complete picture of its lifecycle and usage.


18/2 2026/11/17 06:14 tool grepper
0m Args:
map[Expression:d_lockref PathPrefixes:[fs/dcache.c]]

Results:
map[Output:fs/dcache.c=453=static void dentry_free(struct dentry *dentry)
--
fs/dcache.c-455-	DENTRY_WARN_ONCE(d_really_is_positive(dentry), dentry);
fs/dcache.c:456:	DENTRY_WARN_ONCE(!lockref_is_dead(&dentry->d_lockref), dentry);
fs/dcache.c-457-	D_FLAG_VERIFY(dentry, 0);
--
fs/dcache.c=756=static bool lock_for_kill(struct dentry *dentry)
--
fs/dcache.c-759-
fs/dcache.c:760:	if (unlikely(dentry->d_lockref.count)) {
fs/dcache.c-761-		spin_unlock(&dentry->d_lock);
--
fs/dcache.c-783-	rcu_read_unlock();
fs/dcache.c:784:	if (likely(!dentry->d_lockref.count))
fs/dcache.c-785-		return true;
--
fs/dcache.c=830=static struct dentry *dentry_kill(struct dentry *dentry)
--
fs/dcache.c-840-	 */
fs/dcache.c:841:	lockref_mark_dead(&dentry->d_lockref);
fs/dcache.c-842-
--
fs/dcache.c-876-		dentry_free(dentry);
fs/dcache.c:877:	if (parent && --parent->d_lockref.count) {
fs/dcache.c-878-		spin_unlock(&parent->d_lock);
--
fs/dcache.c=960=static inline bool fast_dput(struct dentry *dentry)
--
fs/dcache.c-969-	rcu_read_lock();
fs/dcache.c:970:	ret = lockref_put_return(&dentry->d_lockref);
fs/dcache.c-971-
--
fs/dcache.c-979-		rcu_read_unlock();
fs/dcache.c:980:		if (WARN_ON_ONCE(lockref_is_dead_or_zero(&dentry->d_lockref))) {
fs/dcache.c-981-			spin_unlock(&dentry->d_lock);
--
fs/dcache.c-983-		}
fs/dcache.c:984:		dentry->d_lockref.count--;
fs/dcache.c-985-		goto locked;
--
fs/dcache.c-1021-locked:
fs/dcache.c:1022:	if (dentry->d_lockref.count || retain_dentry(dentry, true)) {
fs/dcache.c-1023-		spin_unlock(&dentry->d_lock);
--
fs/dcache.c=1077=void d_make_discardable(struct dentry *dentry)
--
fs/dcache.c-1081-	dentry->d_flags &= ~DCACHE_PERSISTENT;
fs/dcache.c:1082:	dentry->d_lockref.count--;
fs/dcache.c-1083-	finish_dput(dentry);
--
fs/dcache.c=1105=__must_hold(&dentry->d_lock)
fs/dcache.c-1106-{
fs/dcache.c:1107:	if (likely(!dentry->d_lockref.count &&
fs/dcache.c-1108-	    !(dentry->d_flags & DCACHE_SHRINK_LIST))) {
--
fs/dcache.c=1137=struct dentry *dget_parent(struct dentry *dentry)
--
fs/dcache.c-1149-	ret = READ_ONCE(dentry->d_parent);
fs/dcache.c:1150:	gotref = lockref_get_not_zero(&ret->d_lockref);
fs/dcache.c-1151-	rcu_read_unlock();
--
fs/dcache.c-1171-	rcu_read_unlock();
fs/dcache.c:1172:	BUG_ON(!ret->d_lockref.count);
fs/dcache.c:1173:	ret->d_lockref.count++;
fs/dcache.c-1174-	spin_unlock(&ret->d_lock);
--
fs/dcache.c=1182=static struct dentry * __d_find_dir_alias(struct inode *inode)
--
fs/dcache.c-1188-	alias = hlist_entry(inode->i_dentry.first, struct dentry, d_alias);
fs/dcache.c:1189:	lockref_get(&alias->d_lockref);
fs/dcache.c-1190-	return alias;
--
fs/dcache.c=1339=static enum lru_status dentry_lru_isolate(struct list_head *item,
--
fs/dcache.c-1358-	 */
fs/dcache.c:1359:	if (dentry->d_lockref.count) {
fs/dcache.c-1360-		d_lru_isolate(lru, dentry);
--
fs/dcache.c=1688=static enum d_walk_ret select_collect(void *_data, struct dentry *dentry)
--
fs/dcache.c-1695-
fs/dcache.c:1696:	if (lockref_is_dead_or_zero(&dentry->d_lockref)) {
fs/dcache.c-1697-		__move_to_shrink_list(dentry, &data->dispose);
--
fs/dcache.c=1711=static enum d_walk_ret select_collect_umount(void *_data, struct dentry *dentry)
--
fs/dcache.c-1714-		dentry->d_flags &= ~DCACHE_PERSISTENT;
fs/dcache.c:1715:		dentry->d_lockref.count--;
fs/dcache.c-1716-	}
--
fs/dcache.c=1720=static enum d_walk_ret select_collect2(void *_data, struct dentry *dentry)
--
fs/dcache.c-1727-
fs/dcache.c:1728:	if (lockref_is_dead_or_zero(&dentry->d_lockref)) {
fs/dcache.c-1729-		if (!__move_to_shrink_list(dentry, &data->dispose)) {
--
fs/dcache.c=1762=static void shrink_dcache_tree(struct dentry *parent, bool for_umount)
--
fs/dcache.c-1798-
fs/dcache.c:1799:			if (unlikely(lockref_is_dead(&v->d_lockref))) {
fs/dcache.c-1800-				// It's doomed; if it isn't dead yet, notify us
--
fs/dcache.c=1820=static enum d_walk_ret umount_check(void *_data, struct dentry *dentry)
--
fs/dcache.c-1826-	/* root with refcount 1 is fine */
fs/dcache.c:1827:	if (dentry == _data && dentry->d_lockref.count == 1)
fs/dcache.c-1828-		return D_WALK_CONTINUE;
--
fs/dcache.c-1835-		       dentry,
fs/dcache.c:1836:		       dentry->d_lockref.count,
fs/dcache.c-1837-		       dentry->d_sb->s_type->name,
--
fs/dcache.c=1842=static void do_one_tree(struct dentry *dentry)
--
fs/dcache.c-1852-	 */
fs/dcache.c:1853:	if (unlikely(dentry->d_lockref.count > 1 &&
fs/dcache.c-1854-		     !hlist_unhashed(&dentry->d_sib)))
--
fs/dcache.c=1863=void shrink_dcache_for_umount(struct super_block *sb)
--
fs/dcache.c-1884-		rcu_read_unlock();
fs/dcache.c:1885:		if (unlikely(lockref_is_dead(&dentry->d_lockref))) {
fs/dcache.c-1886-			struct completion_list wait;
--
fs/dcache.c=1961=static struct dentry *__d_alloc(struct super_block *sb, const struct qstr *name)
--
fs/dcache.c-2009-	dentry->d_flags = 0;
fs/dcache.c:2010:	lockref_init(&dentry->d_lockref);
fs/dcache.c-2011-	seqcount_spinlock_init(&dentry->d_seq, &dentry->d_lock);
--
fs/dcache.c=2706=struct dentry *__d_lookup(const struct dentry *parent, const struct qstr *name)
--
fs/dcache.c-2749-
fs/dcache.c:2750:		dentry->d_lockref.count++;
fs/dcache.c-2751-		found = dentry;
--
fs/dcache.c=2806=void d_delete(struct dentry * dentry)
--
fs/dcache.c-2814-	 */
fs/dcache.c:2815:	if (dentry->d_lockref.count == 1) {
fs/dcache.c-2816-		if (dentry_negative_policy)
--
fs/dcache.c=2894=struct dentry *__d_alloc_parallel(struct dentry *parent,
--
fs/dcache.c-2921-	if (unlikely(dentry)) {
fs/dcache.c:2922:		if (!lockref_get_not_dead(&dentry->d_lockref)) {
fs/dcache.c-2923-			rcu_read_unlock();
--
fs/dcache.c-2964-		/* now we can try to grab a reference */
fs/dcache.c:2965:		if (unlikely(lockref_is_dead(&dentry->d_lockref))) {
fs/dcache.c-2966-			spin_unlock(&dentry->d_lock);
--
fs/dcache.c=3255=static void __d_move(struct dentry *dentry, struct dentry *target,
--
fs/dcache.c-3305-		target->d_hash.pprev = NULL;
fs/dcache.c:3306:		dentry->d_parent->d_lockref.count++;
fs/dcache.c-3307-		if (dentry != old_parent) /* wasn't IS_ROOT */
fs/dcache.c:3308:			WARN_ON(!--old_parent->d_lockref.count);
fs/dcache.c-3309-	} else {
]

19/2 2026/11/17 06:14 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 15669
							output: 34
							thoughts: 1983
						

Thoughts:
**A Subtle Race Condition in `dentry_kill` and `lockref_get_not_dead`**

I've been digging into `fs/dcache.c`, specifically lines 866-882, which deal with unlinking and freeing dentries. My initial focus was on how `dentry_kill` manages the parent directory's lock reference count. I noticed that after unlinking the dentry and potentially freeing it, the code checks `if (parent && --parent->d_lockref.count)`. This line decrement `parent->d_lockref.count` and then checks its value.

My immediate concern arose from the fact that `spin_lock(&parent->d_lock)` is held *before* this decrement. This implies that `parent->d_lockref.count` is being modified while the spinlock protecting it is held by the current task. This seems safe from other threads *also* trying to acquire `parent->d_lock`.

However, then I remembered `lockref_get_not_dead`. I started thinking about what happens if another thread is *simultaneously* trying to increment or read this `d_lockref.count` in a different way. This is where KCSAN's report of a race condition caught my attention. KCSAN flagged a read on `lockref->lock_count` by `lockref_get_not_dead` (task 4498) and a read-write (the `--` operation) on `parent->d_lockref.count` by `dentry_kill` (task 3284).

My confusion stemmed from the fact that `dentry_kill` *was* holding `parent->d_lock`. How could a read from `lockref_get_not_dead` race with a write happening *under* a held lock?

I then looked closely at `lockref_get_not_dead` in `lib/lockref.c`. The core of this function is a `CMPXCHG_LOOP`. The very first operation within this loop is `old.lock_count = READ_ONCE(lockref->lock_count);`. This `READ_ONCE` is a marked, atomic read.

The critical insight came when I realized the context of task 4498. It's in the process of an `unlink` operation, specifically calling `filename_unlinkat`, which means it's trying to find the parent directory of the dentry being unlinked. So, task 4498 is effectively trying to legitimize the path to the parent of the dentry that task 3284 is in the process of killing.

The race, as identified by KCSAN, is that task 3284 is holding `parent->d_lock` and performing a *plain*, non-atomic decrement (`--parent->d_lockref.count`). Meanwhile, task 4498, *without holding `parent->d_lock`*, performs a `READ_ONCE(lockref->lock_count)`.

The apparent contradiction is resolved by understanding KCSAN's rules and the C semantics of `READ_ONCE`. KCSAN flags a marked read (`READ_ONCE`) racing with an unmarked write (`--count`) as a data race. This is because even though `parent->d_lock` is held by task 3284, the specific access to `parent->d_lockref.count` by task 3284 is a *plain* write. The `CMPXCHG_LOOP` in `lockref_get_not_dead` includes a check `arch_spin_value_unlocked(old.lock.rlock.raw_lock)`. When task 3284 holds `parent->d_lock`, this spinlock is indeed locked. However, `lockref_get_not_dead` is designed to *attempt* an atomic operation using `try_cmpxchg64_relaxed` *before* acquiring the spinlock, and the `READ_ONCE` is part of that initial attempt.

So, task 4498 reads `lockref->lock_count` at a point where task 3284 is about to perform a non-atomic decrement on `lockref->count`. Even though the spinlock *is* held by task 3284, the `READ_ONCE` in task 4498 is an access to a field that KCSAN considers "unprotected" in the context of the unmarked write by task 3284. This is because the `CMPXCHG_LOOP`'s logic aims to avoid acquiring the spinlock if a pure atomic operation can succeed, and the `READ_ONCE` is part of that initial atomic attempt. The plain `--count` is a non-atomic operation that KCSAN sees as potentially racy with marked reads, as it doesn't guarantee visibility or atomicity in the same way a `cmpxchg` would. The core issue is that a marked read (`READ_ONCE`) is happening concurrently with an unmarked read-modify-write (`--`), and the unmarked operation is not inherently synchronized with the marked read's perspective.


20/2 2026/11/17 06:14 tool read-file
0m Args:
map[File:include/linux/lockref.h FirstLine:1 LineCount:80]

Results:
map[Contents:   1:	/* SPDX-License-Identifier: GPL-2.0 */
   2:	#ifndef __LINUX_LOCKREF_H
   3:	#define __LINUX_LOCKREF_H
   4:	
   5:	/*
   6:	 * Locked reference counts.
   7:	 *
   8:	 * These are different from just plain atomic refcounts in that they
   9:	 * are atomic with respect to the spinlock that goes with them.  In
  10:	 * particular, there can be implementations that don't actually get
  11:	 * the spinlock for the common decrement/increment operations, but they
  12:	 * still have to check that the operation is done semantically as if
  13:	 * the spinlock had been taken (using a cmpxchg operation that covers
  14:	 * both the lock and the count word, or using memory transactions, for
  15:	 * example).
  16:	 */
  17:	
  18:	#include <linux/spinlock.h>
  19:	#include <generated/bounds.h>
  20:	
  21:	#define USE_CMPXCHG_LOCKREF \
  22:		(IS_ENABLED(CONFIG_ARCH_USE_CMPXCHG_LOCKREF) && \
  23:		 IS_ENABLED(CONFIG_SMP) && SPINLOCK_SIZE <= 4)
  24:	
  25:	struct lockref {
  26:		union {
  27:	#if USE_CMPXCHG_LOCKREF
  28:			aligned_u64 lock_count;
  29:	#endif
  30:			struct {
  31:				spinlock_t lock;
  32:				int count;
  33:			};
  34:		};
  35:	};
  36:	
  37:	#define __LOCKREF_DEAD_VAL	-128
  38:	
  39:	/**
  40:	 * lockref_init - Initialize a lockref
  41:	 * @lockref: pointer to lockref structure
  42:	 *
  43:	 * Initializes @lockref->count to 1.
  44:	 */
  45:	static inline void lockref_init(struct lockref *lockref)
  46:	{
  47:		spin_lock_init(&lockref->lock);
  48:		lockref->count = 1;
  49:	}
  50:	
  51:	void lockref_get(struct lockref *lockref);
  52:	int lockref_put_return(struct lockref *lockref);
  53:	bool lockref_get_not_zero(struct lockref *lockref);
  54:	bool lockref_put_or_lock(struct lockref *lockref) __cond_acquires(false, &lockref->lock);
  55:	
  56:	void lockref_mark_dead(struct lockref *lockref);
  57:	bool lockref_get_not_dead(struct lockref *lockref);
  58:	
  59:	/* Must be called under spinlock for reliable results */
  60:	static inline bool lockref_is_dead(const struct lockref *l)
  61:	{
  62:		return (READ_ONCE(l->count) == __LOCKREF_DEAD_VAL);
  63:	}
  64:	
  65:	static inline bool lockref_is_dead_or_zero(const struct lockref *l)
  66:	{
  67:		int count = READ_ONCE(l->count);
  68:		return (count == __LOCKREF_DEAD_VAL || count == 0);
  69:	}
  70:	
  71:	#endif /* __LINUX_LOCKREF_H */
]

21/2 2026/11/17 06:14 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 18661
							output: 33
							thoughts: 232
						

Thoughts:
**Deconstructing `lockref`'s Behavior: A Deep Dive into Concurrency and Read Integrity**

My thought process began by drilling down into the specifics of the `lockref` implementation, specifically within `include/linux/lockref.h`. I immediately focused on lines 59 through 69, examining the `lockref_is_dead` and `lockref_is_dead_or_zero` functions.

What struck me most prominently was the repeated use of `READ_ONCE(l->count)` in both these functions. This immediately raised a question in my mind: why is `READ_ONCE` necessary here, especially in `lockref_is_dead`? The answer, as I quickly surmised, is due to the potential for concurrent access. If `l->count` were to be read without this mechanism, there's a risk of encountering a stale or partially updated value, which would render the "dead" status check unreliable. The use of `READ_ONCE` is a clear indicator that the `count` field within the `lockref` structure can be modified by other threads or contexts, and thus, any read operation needs to be atomic and provide a consistent snapshot.

Following this observation, my next step was to broaden my investigation. I decided to thoroughly analyze the entire `lib/lockref.c` file. My primary goal was to understand the scope of operations performed by this module and to identify how the `lockref` structure, and specifically its `count` field, is managed throughout the codebase. I wanted to see all the functions defined within `lib/lockref.c` to get a comprehensive picture of its functionality and to ensure that my understanding of `READ_ONCE`'s necessity was indeed grounded in the actual usage patterns within the lockref subsystem.


22/2 2026/11/17 06:14 tool read-file
0m Args:
map[File:lib/lockref.c FirstLine:80 LineCount:80]

Results:
map[Contents:  80:	}
  81:	EXPORT_SYMBOL(lockref_get_not_zero);
  82:	
  83:	/**
  84:	 * lockref_put_return - Decrement reference count if possible
  85:	 * @lockref: pointer to lockref structure
  86:	 *
  87:	 * Decrement the reference count and return the new value.
  88:	 * If the lockref was dead or locked, return -1.
  89:	 */
  90:	int lockref_put_return(struct lockref *lockref)
  91:	{
  92:		CMPXCHG_LOOP(
  93:			new.count--;
  94:			if (old.count <= 0)
  95:				return -1;
  96:		,
  97:			return new.count;
  98:		);
  99:		return -1;
 100:	}
 101:	EXPORT_SYMBOL(lockref_put_return);
 102:	
 103:	/**
 104:	 * lockref_put_or_lock - decrements count unless count <= 1 before decrement
 105:	 * @lockref: pointer to lockref structure
 106:	 * Return: 1 if count updated successfully or 0 if count <= 1 and lock taken
 107:	 */
 108:	bool lockref_put_or_lock(struct lockref *lockref)
 109:	{
 110:		CMPXCHG_LOOP(
 111:			new.count--;
 112:			if (old.count <= 1)
 113:				break;
 114:		,
 115:			return true;
 116:		);
 117:	
 118:		spin_lock(&lockref->lock);
 119:		if (lockref->count <= 1)
 120:			return false;
 121:		lockref->count--;
 122:		spin_unlock(&lockref->lock);
 123:		return true;
 124:	}
 125:	EXPORT_SYMBOL(lockref_put_or_lock);
 126:	
 127:	/**
 128:	 * lockref_mark_dead - mark lockref dead
 129:	 * @lockref: pointer to lockref structure
 130:	 */
 131:	void lockref_mark_dead(struct lockref *lockref)
 132:	{
 133:		assert_spin_locked(&lockref->lock);
 134:		lockref->count = __LOCKREF_DEAD_VAL;
 135:	}
 136:	EXPORT_SYMBOL(lockref_mark_dead);
 137:	
 138:	/**
 139:	 * lockref_get_not_dead - Increments count unless the ref is dead
 140:	 * @lockref: pointer to lockref structure
 141:	 * Return: 1 if count updated successfully or 0 if lockref was dead
 142:	 */
 143:	bool lockref_get_not_dead(struct lockref *lockref)
 144:	{
 145:		bool retval = false;
 146:	
 147:		CMPXCHG_LOOP(
 148:			new.count++;
 149:			if (old.count < 0)
 150:				return false;
 151:		,
 152:			return true;
 153:		);
 154:	
 155:		spin_lock(&lockref->lock);
 156:		if (lockref->count >= 0) {
 157:			lockref->count++;
 158:			retval = true;
 159:		}
]

23/2 2026/11/17 06:14 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 19947
							output: 22
							thoughts: 2831
						

Thoughts:
**Investigating a Potential Data Race in Dentry Lifetime Management**

I've been digging into a KCSAN report concerning a data race between `dentry_kill` and `lockref_get_not_dead` (which is called indirectly via `try_to_unlazy` and `legitimize_path`). The race is reported on the `lockref->lock_count` field of a parent dentry.

My initial thought process was to meticulously examine the functions involved and how they interact, particularly around the `lockref` structure and its spinlock.

I started by looking at the core `lockref` operations:
*   `lockref_mark_dead`: This simply sets the count to a "dead" value while holding the spinlock. Straightforward enough.
*   `lockref_put_or_lock`: Decrements the count if it's greater than 1, under the spinlock.
*   `lockref_get`: Increments the count, under the spinlock.
*   `lockref_get_not_dead`: This is where things get interesting. It acquires the spinlock, checks if the count is non-negative, increments if so, and then releases the lock. This function is designed to be used when a lock might not be held, but we want to ensure the refcount is valid.

Then, I turned my attention to `CMPXCHG_LOOP`, a macro that appears to be designed for lock-free updates using `try_cmpxchg64_relaxed`. It reads the `lock_count` (8 bytes, comprising `lock` and `count`), attempts a CAS operation on the entire 8-byte value, and retries if it fails or if the spinlock `old.lock.rlock.raw_lock` is not unlocked. This is crucial because `lockref->lock_count` is an aggregate of the spinlock state and the reference count.

Next, I analyzed `dentry_kill`. The key sequence I observed was:
1.  Acquiring the parent's `d_lock` if the dentry isn't a root.
2.  Acquiring the dentry's own `d_lock` (nested).
3.  Unlisting the dentry.
4.  Potentially freeing the dentry.
5.  Crucially, `if (parent && --parent->d_lockref.count)`: This is where the parent's reference count is decremented. If it becomes zero, the parent's lock is released.

This is where I started to form a specific concern. Task 3284 in `dentry_kill` holds `parent->d_lock`. At the same time, task 4498 is potentially in `lockref_get_not_dead`, which operates on `path->dentry->d_lockref` (which could be the same `parent->d_lockref`).

My thought process went: "If task 3284 holds `parent->d_lock`, it means `parent->d_lockref.lock` is locked. What does task 4498 see when it tries to operate on `parent->d_lockref`?"

I then traced the execution of task 4498 using `lockref_get_not_dead` concurrently with task 3284 in `dentry_kill`.

The specific sequence that worried me was:
*   Task 3284: `spin_lock(&parent->d_lock);` This acquires the spinlock.
*   Task 3284: `--parent->d_lockref.count;` This is a read-modify-write operation on the 4-byte `count` field.
*   Task 4498: `lockref_get_not_dead` reads `lockref->lock_count` using `READ_ONCE`. This is an 8-byte read.

My immediate concern was about the atomicity of these operations. On x86-64, an 8-byte aligned read is atomic at the hardware level. However, the `--parent->d_lockref.count` is a 4-byte read-modify-write that is *not* atomic in a single instruction. It typically involves loading the 4-byte value, decrementing it, and then storing it back.

This led to a critical question: "What if task 4498 reads `parent->d_lockref.lock_count` (the 8-byte combined value) *while* task 3284 is in the middle of its `--parent->d_lockref.count` operation?" This would be reading across the boundary of the lock state and the count, potentially observing an inconsistent state.

I also pondered why task 4498's `spin_lock(&lockref->lock)` inside `lockref_get_not_dead` didn't seem to prevent the race. The reason is that task 4498 is in "RCU-walk mode," meaning it holds `rcu_read_lock()` but *not* the dentry's spinlock. It attempts to increment the refcount using `lockref_get_not_dead`, which *tries* to acquire the spinlock internally if the `arch_spin_value_unlocked` check fails.

The core of the problem seemed to hinge on the `CMPXCHG_LOOP` macro and the `arch_spin_value_unlocked` check. If task 3284 holds `parent->d_lock`, then `old.lock.rlock.raw_lock` should *not* be unlocked. This would cause the `while` loop in `CMPXCHG_LOOP` to be skipped, and task 4498 would then proceed to attempt `spin_lock(&lockref->lock)`.

However, the KCSAN report indicated a race on the 8-byte `lock_count` by task 4498 and a read-write on the 4-byte `count` by task 3284. My concern was: could task 4498 read `lock_count` with `READ_ONCE` *before* task 3284 acquired the lock, or *while* task 3284 was acquiring it, and *then* have task 3284 perform its RMW on the `count` field? This would be a classic data race.

The specific phrasing in the KCSAN report ("read (marked) to 0xffff888105d35800 of 8 bytes by task 4498" vs. "read-write to 0xffff888105d35804 of 4 bytes by task 3284") highlighted that task 4498 was performing a marked read of the entire 8-byte `lock_count`, while task 3284 was doing an unmarked read-write on the lower 4 bytes (`count`). KCSAN flags *any* marked access racing with an unmarked access as a potential data race.

This leads to the lingering question: is this KCSAN report indicative of a benign race due to strict reporting, or is there a genuine concurrency bug where an inconsistent `lock_count` could be observed, potentially leading to incorrect logic flow or even a crash if `try_cmpxchg64_relaxed` were to operate on a corrupted 8-byte value? The fact that `lockref_get_not_dead` uses `READ_ONCE` and then proceeds to a `spin_lock` if the lock is held suggests it's trying to be safe, but the race on the aggregate `lock_count` is what's particularly concerning. I need to understand if the sequence of operations on x86 can lead to a state where the `arch_spin_value_unlocked` check is misleading or if the 8-byte read itself can cross the RMW operation of the `count` in a way that causes issues.


24/2 2026/11/17 06:15 tool grepper
0m Args:
map[Expression:arch_spin_value_unlocked]

Results:
map[Output:arch/alpha/include/asm/spinlock.h-18-
arch/alpha/include/asm/spinlock.h:19:static inline int arch_spin_value_unlocked(arch_spinlock_t lock)
arch/alpha/include/asm/spinlock.h-20-{
--
arch/arm/include/asm/spinlock.h=107=static inline void arch_spin_unlock(arch_spinlock_t *lock)
--
arch/arm/include/asm/spinlock.h-113-
arch/arm/include/asm/spinlock.h:114:static inline int arch_spin_value_unlocked(arch_spinlock_t lock)
arch/arm/include/asm/spinlock.h-115-{
--
arch/arm/include/asm/spinlock.h=119=static inline int arch_spin_is_locked(arch_spinlock_t *lock)
arch/arm/include/asm/spinlock.h-120-{
arch/arm/include/asm/spinlock.h:121:	return !arch_spin_value_unlocked(READ_ONCE(*lock));
arch/arm/include/asm/spinlock.h-122-}
--
arch/powerpc/include/asm/qspinlock.h=154=static inline void queued_spin_unlock(struct qspinlock *lock)
--
arch/powerpc/include/asm/qspinlock.h-162-#define arch_spin_is_contended(l)	queued_spin_is_contended(l)
arch/powerpc/include/asm/qspinlock.h:163:#define arch_spin_value_unlocked(l)	queued_spin_value_unlocked(l)
arch/powerpc/include/asm/qspinlock.h-164-#define arch_spin_lock(l)		queued_spin_lock(l)
--
arch/powerpc/include/asm/simple_spinlock.h-34-
arch/powerpc/include/asm/simple_spinlock.h:35:static __always_inline int arch_spin_value_unlocked(arch_spinlock_t lock)
arch/powerpc/include/asm/simple_spinlock.h-36-{
--
arch/powerpc/include/asm/simple_spinlock.h=40=static inline int arch_spin_is_locked(arch_spinlock_t *lock)
arch/powerpc/include/asm/simple_spinlock.h-41-{
arch/powerpc/include/asm/simple_spinlock.h:42:	return !arch_spin_value_unlocked(READ_ONCE(*lock));
arch/powerpc/include/asm/simple_spinlock.h-43-}
--
arch/s390/include/asm/spinlock.h=59=static inline u32 arch_spin_lockval(int cpu)
--
arch/s390/include/asm/spinlock.h-63-
arch/s390/include/asm/spinlock.h:64:static inline int arch_spin_value_unlocked(arch_spinlock_t lock)
arch/s390/include/asm/spinlock.h-65-{
--
include/asm-generic/qspinlock.h=165=static __always_inline bool virt_spin_lock(struct qspinlock *lock)
--
include/asm-generic/qspinlock.h-177-#define arch_spin_is_contended(l)	queued_spin_is_contended(l)
include/asm-generic/qspinlock.h:178:#define arch_spin_value_unlocked(l)	queued_spin_value_unlocked(l)
include/asm-generic/qspinlock.h-179-#define arch_spin_lock(l)		queued_spin_lock(l)
--
include/asm-generic/ticket_spinlock.h=85=static __always_inline int ticket_spin_is_contended(arch_spinlock_t *lock)
--
include/asm-generic/ticket_spinlock.h-98-#define arch_spin_is_contended(l)	ticket_spin_is_contended(l)
include/asm-generic/ticket_spinlock.h:99:#define arch_spin_value_unlocked(l)	ticket_spin_value_unlocked(l)
include/asm-generic/ticket_spinlock.h-100-#define arch_spin_lock(l)		ticket_spin_lock(l)
--
lib/lockref.c-15-	old.lock_count = READ_ONCE(lockref->lock_count);			\
lib/lockref.c:16:	while (likely(arch_spin_value_unlocked(old.lock.rlock.raw_lock))) {  	\
lib/lockref.c-17-		struct lockref new = old;					\
]

25/2 2026/11/17 06:15 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 23960
							output: 42
							thoughts: 28
						

Thoughts:
**My Current Line of Inquiry: Deconstructing `queued_spin_value_unlocked`**

Ah, yes, I'm currently deep in the weeds, specifically examining the `queued_spin_value_unlocked` macro within the `include/asm-generic/qspinlock.h` file. My focus is on understanding the intricate details of this particular construct, which, as an expert in this domain, I recognize as a fundamental piece of the queued spinlock mechanism. I'm dissecting its definition and implications, aiming for a comprehensive grasp of its role in the underlying synchronization primitives.


26/2 2026/11/17 06:15 tool codesearch-definition-source
0m Args:
map[ContextFile:include/asm-generic/qspinlock.h Name:queued_spin_value_unlocked]

Results:
map[SourceCode:  62:	/**
  63:	 * queued_spin_value_unlocked - is the spinlock structure unlocked?
  64:	 * @lock: queued spinlock structure
  65:	 * Return: 1 if it is unlocked, 0 otherwise
  66:	 *
  67:	 * N.B. Whenever there are tasks waiting for the lock, it is considered
  68:	 *      locked wrt the lockref code to avoid lock stealing by the lockref
  69:	 *      code and change things underneath the lock. This also allows some
  70:	 *      optimizations to be applied without conflict with lockref.
  71:	 */
  72:	static __always_inline int queued_spin_value_unlocked(struct qspinlock lock)
  73:	{
  74:		return !lock.val.counter;
  75:	}
 SourceFile:include/asm-generic/qspinlock.h]

27/2 2026/11/17 06:15 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 24259
							output: 20
							thoughts: 760
						

Thoughts:
**Diving into the KCSAN Report: A Thought Process**

Okay, so I'm looking at this comment, and it's got me thinking. It's talking about how when tasks are waiting for a lock, the `lockref` code considers it "locked" to prevent others from messing with things underneath. This also apparently helps with some optimizations. That makes sense on the surface.

But then I see "WAIT!" – that's the trigger. Something about this interaction is not as straightforward as it seems, especially when KCSAN (Kernel Concurrency Sanitizer) has flagged an issue.

Let's break down how `lockref` works, as described: it's a 64-bit value combining a 32-bit spinlock and a 32-bit count. The comment mentions that when the spinlock itself is held, `arch_spin_value_unlocked` returns 0. This is crucial because the `CMPXCHG_LOOP` mechanism will then *not* attempt an atomic compare-and-exchange on the `lockref` value, and instead, it will fall back to taking the internal spinlock (`spin_lock(&lockref->lock)`). This seems like a reasonable design to ensure atomicity when the main spinlock is already acquired.

So, if that's how it's *supposed* to work, why did KCSAN fire? This is where the real investigation begins.

I need to trace the specific events. The report points to Task 4498 doing a `READ_ONCE(lockref->lock_count)`. This is interesting – `READ_ONCE` is meant to prevent certain compiler reordering, but it doesn't guarantee atomicity across multiple words on all architectures. It reads the entire 64-bit `lockref` value, which comprises both the `lock` and the `count` fields.

Concurrently, Task 3284 is doing `--parent->d_lockref.count`. This is a simple decrement operation, and crucially, it's *not* an atomic operation and it's *not* wrapped in `WRITE_ONCE`. Now, I need to check the context of Task 3284. Ah, it had *already* acquired `parent->d_lock` at an earlier line. This is a critical piece of information.

So, here's the emerging conflict: Task 4498 is reading the 64-bit `lockref` value using `READ_ONCE`. This read *could* conceptually happen in two parts: the `lock` field and the `count` field. At the *exact* same time, Task 3284, while holding `parent->d_lock`, is modifying `parent->d_lockref.count`. Because Task 3284 is just doing a `--` operation (and not an atomic or `WRITE_ONCE`), it's a regular write to memory.

My thought process is now racing: If Task 3284 holds `parent->d_lock`, why isn't Task 4498's read of `count` protected? The key must be in how `lockref` is read. Task 4498 reads *both* `lock` and `count` as a single 64-bit value *before* it even checks if the `lock` part is actually locked. This means the read of the 64-bit `lockref` value (containing both `lock` and `count`) can happen *independently* of whether `parent->d_lock` is held.

The core of the problem appears to be that `READ_ONCE(lockref->lock_count)` is reading the 64-bit value, which includes `count`. Task 3284, holding `parent->d_lock`, is modifying `count` using a non-atomic `--` operation. This creates a race condition: Task 4498 could be reading the `count` field *while* Task 3284 is in the middle of updating it. Even though `parent->d_lock` protects Task 3284's write to `count`, it doesn't protect Task 4498's read of `count` if Task 4498 isn't also respecting `parent->d_lock` in its `lockref` access.

The question then becomes: what is it about holding `lockref->lock` that allows a modification to `count` without using an atomic operation like `cmpxchg`? It seems that any holder of `lockref->lock` that modifies `lockref->count` without a full atomic operation is vulnerable. This prompts the next step: I need to find out *which* parts of the kernel actually modify `lockref->count` while holding `lockref->lock` without using appropriate atomic primitives. My next logical step is to grep the codebase for all instances where `struct lockref`'s `count` member is modified.


28/2 2026/11/17 06:16 tool grepper
0m Args:
map[Expression:d_lockref\.count]

Results:
map[Output:fs/ceph/dir.c=1665=__dentry_leases_walk(struct ceph_mds_client *mdsc,
--
fs/ceph/dir.c-1706-			di->flags &= ~CEPH_DENTRY_REFERENCED;
fs/ceph/dir.c:1707:			if (dentry->d_lockref.count > 0) {
fs/ceph/dir.c-1708-				/* update_dentry_lease() will re-add
--
fs/ceph/dir.c=1769=static enum lease_check_result __dir_lease_check(const struct dentry *dentry,
--
fs/ceph/dir.c-1784-		 * round robin manner */
fs/ceph/dir.c:1785:		if (dentry->d_lockref.count > 0 ||
fs/ceph/dir.c-1786-		    (di->flags & CEPH_DENTRY_REFERENCED))
--
fs/dcache.c=756=static bool lock_for_kill(struct dentry *dentry)
--
fs/dcache.c-759-
fs/dcache.c:760:	if (unlikely(dentry->d_lockref.count)) {
fs/dcache.c-761-		spin_unlock(&dentry->d_lock);
--
fs/dcache.c-783-	rcu_read_unlock();
fs/dcache.c:784:	if (likely(!dentry->d_lockref.count))
fs/dcache.c-785-		return true;
--
fs/dcache.c=830=static struct dentry *dentry_kill(struct dentry *dentry)
--
fs/dcache.c-876-		dentry_free(dentry);
fs/dcache.c:877:	if (parent && --parent->d_lockref.count) {
fs/dcache.c-878-		spin_unlock(&parent->d_lock);
--
fs/dcache.c=960=static inline bool fast_dput(struct dentry *dentry)
--
fs/dcache.c-983-		}
fs/dcache.c:984:		dentry->d_lockref.count--;
fs/dcache.c-985-		goto locked;
--
fs/dcache.c-1021-locked:
fs/dcache.c:1022:	if (dentry->d_lockref.count || retain_dentry(dentry, true)) {
fs/dcache.c-1023-		spin_unlock(&dentry->d_lock);
--
fs/dcache.c=1077=void d_make_discardable(struct dentry *dentry)
--
fs/dcache.c-1081-	dentry->d_flags &= ~DCACHE_PERSISTENT;
fs/dcache.c:1082:	dentry->d_lockref.count--;
fs/dcache.c-1083-	finish_dput(dentry);
--
fs/dcache.c=1105=__must_hold(&dentry->d_lock)
fs/dcache.c-1106-{
fs/dcache.c:1107:	if (likely(!dentry->d_lockref.count &&
fs/dcache.c-1108-	    !(dentry->d_flags & DCACHE_SHRINK_LIST))) {
--
fs/dcache.c=1137=struct dentry *dget_parent(struct dentry *dentry)
--
fs/dcache.c-1171-	rcu_read_unlock();
fs/dcache.c:1172:	BUG_ON(!ret->d_lockref.count);
fs/dcache.c:1173:	ret->d_lockref.count++;
fs/dcache.c-1174-	spin_unlock(&ret->d_lock);
--
fs/dcache.c=1339=static enum lru_status dentry_lru_isolate(struct list_head *item,
--
fs/dcache.c-1358-	 */
fs/dcache.c:1359:	if (dentry->d_lockref.count) {
fs/dcache.c-1360-		d_lru_isolate(lru, dentry);
--
fs/dcache.c=1711=static enum d_walk_ret select_collect_umount(void *_data, struct dentry *dentry)
--
fs/dcache.c-1714-		dentry->d_flags &= ~DCACHE_PERSISTENT;
fs/dcache.c:1715:		dentry->d_lockref.count--;
fs/dcache.c-1716-	}
--
fs/dcache.c=1820=static enum d_walk_ret umount_check(void *_data, struct dentry *dentry)
--
fs/dcache.c-1826-	/* root with refcount 1 is fine */
fs/dcache.c:1827:	if (dentry == _data && dentry->d_lockref.count == 1)
fs/dcache.c-1828-		return D_WALK_CONTINUE;
--
fs/dcache.c-1835-		       dentry,
fs/dcache.c:1836:		       dentry->d_lockref.count,
fs/dcache.c-1837-		       dentry->d_sb->s_type->name,
--
fs/dcache.c=1842=static void do_one_tree(struct dentry *dentry)
--
fs/dcache.c-1852-	 */
fs/dcache.c:1853:	if (unlikely(dentry->d_lockref.count > 1 &&
fs/dcache.c-1854-		     !hlist_unhashed(&dentry->d_sib)))
--
fs/dcache.c=2706=struct dentry *__d_lookup(const struct dentry *parent, const struct qstr *name)
--
fs/dcache.c-2749-
fs/dcache.c:2750:		dentry->d_lockref.count++;
fs/dcache.c-2751-		found = dentry;
--
fs/dcache.c=2806=void d_delete(struct dentry * dentry)
--
fs/dcache.c-2814-	 */
fs/dcache.c:2815:	if (dentry->d_lockref.count == 1) {
fs/dcache.c-2816-		if (dentry_negative_policy)
--
fs/dcache.c=3255=static void __d_move(struct dentry *dentry, struct dentry *target,
--
fs/dcache.c-3305-		target->d_hash.pprev = NULL;
fs/dcache.c:3306:		dentry->d_parent->d_lockref.count++;
fs/dcache.c-3307-		if (dentry != old_parent) /* wasn't IS_ROOT */
fs/dcache.c:3308:			WARN_ON(!--old_parent->d_lockref.count);
fs/dcache.c-3309-	} else {
--
fs/gfs2/quota.c=151=static enum lru_status gfs2_qd_isolate(struct list_head *item,
--
fs/gfs2/quota.c-162-	status = LRU_SKIP;
fs/gfs2/quota.c:163:	if (qd->qd_lockref.count == 0) {
fs/gfs2/quota.c-164-		lockref_mark_dead(&qd->qd_lockref);
--
fs/gfs2/quota.c=331=static void __qd_hold(struct gfs2_quota_data *qd)
--
fs/gfs2/quota.c-333-	struct gfs2_sbd *sdp = qd->qd_sbd;
fs/gfs2/quota.c:334:	gfs2_assert(sdp, qd->qd_lockref.count > 0);
fs/gfs2/quota.c:335:	qd->qd_lockref.count++;
fs/gfs2/quota.c-336-}
--
fs/gfs2/quota.c=338=static void qd_put(struct gfs2_quota_data *qd)
--
fs/gfs2/quota.c-355-
fs/gfs2/quota.c:356:	qd->qd_lockref.count = 0;
fs/gfs2/quota.c-357-	list_lru_add_obj(&gfs2_qd_lru, &qd->qd_lru);
--
fs/gfs2/quota.c=478=static bool qd_grab_sync(struct gfs2_sbd *sdp, struct gfs2_quota_data *qd,
--
fs/gfs2/quota.c-490-		goto out;
fs/gfs2/quota.c:491:	qd->qd_lockref.count++;
fs/gfs2/quota.c-492-
--
fs/gfs2/quota.c=1409=int gfs2_quota_init(struct gfs2_sbd *sdp)
--
fs/gfs2/quota.c-1472-
fs/gfs2/quota.c:1473:			qd->qd_lockref.count = 0;
fs/gfs2/quota.c-1474-			set_bit(QDF_CHANGE, &qd->qd_flags);
--
fs/gfs2/quota.c=1533=void gfs2_quota_cleanup(struct gfs2_sbd *sdp)
--
fs/gfs2/quota.c-1544-		spin_lock(&qd->qd_lockref.lock);
fs/gfs2/quota.c:1545:		if (qd->qd_lockref.count != 0) {
fs/gfs2/quota.c-1546-			spin_unlock(&qd->qd_lockref.lock);
--
fs/overlayfs/namei.c=211=static struct dentry *ovl_lookup_positive_unlocked(struct ovl_lookup_data *d,
--
fs/overlayfs/namei.c-219-	if (!IS_ERR(ret) && d_flags_negative(smp_load_acquire(&ret->d_flags))) {
fs/overlayfs/namei.c:220:		if (drop_negative && ret->d_lockref.count == 1) {
fs/overlayfs/namei.c-221-			spin_lock(&ret->d_lock);
fs/overlayfs/namei.c-222-			/* Recheck condition under lock */
fs/overlayfs/namei.c:223:			if (d_is_negative(ret) && ret->d_lockref.count == 1)
fs/overlayfs/namei.c-224-				__d_drop(ret);
--
include/linux/dcache.h=311=static inline unsigned d_count(const struct dentry *dentry)
include/linux/dcache.h-312-{
include/linux/dcache.h:313:	return dentry->d_lockref.count;
include/linux/dcache.h-314-}
--
include/linux/dcache.h=342=static inline struct dentry *dget_dlock(struct dentry *dentry)
include/linux/dcache.h-343-{
include/linux/dcache.h:344:	dentry->d_lockref.count++;
include/linux/dcache.h-345-	return dentry;
--
include/linux/dcache.h=375=static inline bool dget_alias_ilocked(struct dentry *dentry)
--
include/linux/dcache.h-382-	spin_lock(&dentry->d_lock);
include/linux/dcache.h:383:	if (dentry->d_lockref.count > 0) {
include/linux/dcache.h-384-		dget_dlock(dentry);
]

29/2 2026/11/17 06:16 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 28213
							output: 35
							thoughts: 274
						

Thoughts:
**Revisiting `dentry_kill` and its Interaction with `finish_dput`**

I'm taking another look at the `dentry_kill` function, specifically focusing on the block from lines 864 to 882. My attention is drawn to the sequence of operations here. After `cond_resched_tasks_rcu_qs()`, there's a comment about `d_parent` being stable because the `dentry`'s count is now negative. This is a crucial point for understanding subsequent lock dependencies.

The code then checks if the `dentry` is not the root. If it's not, it acquires the lock on its parent (`d_parent`). Following that, it acquires the lock on the `dentry` itself. Immediately after, `dentry_unlist` is called. A flag, `DCACHE_SHRINK_LIST`, is checked; if set, it indicates that the `dentry` cannot be freed immediately. The `dentry`'s lock is then released. If the `dentry` is deemed "freeable" (i.e., the flag wasn't set), `dentry_free` is called.

Finally, the logic for the parent `dentry` is handled. If a parent `dentry` was involved and its `d_lockref.count` (which I interpret as a reference count for the parent's lock) decrements to zero, its lock is released. The function then returns `NULL` or the parent `dentry` accordingly.

However, this is where I'm getting a bit of a knot in my thinking. I need to reconcile this with what happens in `finish_dput`. I'm now shifting my focus to read the relevant section of `fs/dcache.c`, specifically lines 960 to 1070, to understand the complete picture of how `dentry` objects are processed and potentially freed. I suspect the interaction between the lock management and reference counting in these two functions is critical to avoid race conditions or deadlocks.


30/2 2026/11/17 06:16 tool read-file
0m Args:
map[File:fs/dcache.c FirstLine:960 LineCount:100]

Results:
map[Contents: 960:	static inline bool fast_dput(struct dentry *dentry)
 961:	{
 962:		int ret;
 963:	
 964:		/*
 965:		 * Try to decrement the lockref optimistically.
 966:		 * RCU read lock held so that dentry is guaranteed to stay around
 967:		 * even if the refcount goes down to zero.
 968:		 */
 969:		rcu_read_lock();
 970:		ret = lockref_put_return(&dentry->d_lockref);
 971:	
 972:		/*
 973:		 * If the lockref_put_return() failed due to the lock being held
 974:		 * by somebody else, the fast path has failed. We will need to
 975:		 * get the lock, and then check the count again.
 976:		 */
 977:		if (unlikely(ret < 0)) {
 978:			spin_lock(&dentry->d_lock);
 979:			rcu_read_unlock();
 980:			if (WARN_ON_ONCE(lockref_is_dead_or_zero(&dentry->d_lockref))) {
 981:				spin_unlock(&dentry->d_lock);
 982:				return true;
 983:			}
 984:			dentry->d_lockref.count--;
 985:			goto locked;
 986:		}
 987:	
 988:		/*
 989:		 * If we weren't the last ref, we're done.
 990:		 */
 991:		if (ret) {
 992:			rcu_read_unlock();
 993:			return true;
 994:		}
 995:	
 996:		/*
 997:		 * Can we decide that decrement of refcount is all we needed without
 998:		 * taking the lock?  There's a very common case when it's all we need -
 999:		 * dentry looks like it ought to be retained and there's nothing else
1000:		 * to do.
1001:		 */
1002:		if (retain_dentry(dentry, false)) {
1003:			rcu_read_unlock();
1004:			return true;
1005:		}
1006:	
1007:		/*
1008:		 * Either not worth retaining or we can't tell without the lock.
1009:		 * Get the lock, then.  We've already decremented the refcount to 0,
1010:		 * but we'll need to re-check the situation after getting the lock.
1011:		 */
1012:		spin_lock(&dentry->d_lock);
1013:		rcu_read_unlock();
1014:	
1015:		/*
1016:		 * Did somebody else grab a reference to it in the meantime, and
1017:		 * we're no longer the last user after all? Alternatively, somebody
1018:		 * else could have killed it and marked it dead. Either way, we
1019:		 * don't need to do anything else.
1020:		 */
1021:	locked:
1022:		if (dentry->d_lockref.count || retain_dentry(dentry, true)) {
1023:			spin_unlock(&dentry->d_lock);
1024:			return true;
1025:		}
1026:		return false;
1027:	}
1028:	
1029:	static void finish_dput(struct dentry *dentry)
1030:		__releases(dentry->d_lock)
1031:	{
1032:		while ((dentry = dentry_kill(dentry)) != NULL) {
1033:			if (retain_dentry(dentry, true)) {
1034:				spin_unlock(&dentry->d_lock);
1035:				return;
1036:			}
1037:		}
1038:	}
1039:	
1040:	/* 
1041:	 * This is dput
1042:	 *
1043:	 * This is complicated by the fact that we do not want to put
1044:	 * dentries that are no longer on any hash chain on the unused
1045:	 * list: we'd much rather just get rid of them immediately.
1046:	 *
1047:	 * However, that implies that we have to traverse the dentry
1048:	 * tree upwards to the parents which might _also_ now be
1049:	 * scheduled for deletion (it may have been only waiting for
1050:	 * its last child to go away).
1051:	 *
1052:	 * This tail recursion is done by hand as we don't want to depend
1053:	 * on the compiler to always get this right (gcc generally doesn't).
1054:	 * Real recursion would eat up our stack space.
1055:	 */
1056:	
1057:	/*
1058:	 * dput - release a dentry
1059:	 * @dentry: dentry to release 
]

31/2 2026/11/17 06:16 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 29952
							output: 32
							thoughts: 8109
						

Thoughts:
**Analysis of a Potential Data Race in dentry_kill and lockref_get_not_dead**

I've been investigating a KCSAN-reported data race that seems to involve the `finish_dput` and `dentry_kill` functions interacting with `lockref_get_not_dead`. My thought process has been to meticulously trace the execution paths of the two involved tasks, understand the state of locks and reference counts, and determine the precise point of contention and its potential implications.

Initially, I examined `finish_dput` and how it calls `dentry_kill` in a loop. My attention was drawn to the logic within `dentry_kill` concerning the parent's lock reference count. Specifically, I noticed that after freeing the `dentry` itself, `dentry_kill` decrements the `parent->d_lockref.count`. The immediate consequence I recognized was that this decrement corresponds to the dropped reference that the killed `dentry` held on its `parent`. If this count drops to zero, `dentry_kill` returns `parent`, and `finish_dput` will then proceed to potentially call `dentry_kill` on the `parent` itself in the next iteration.

This is where my focus shifted to what task 4498 was doing concurrently. I observed that task 4498 was involved in an RCU path walk and was attempting to "legitimize" a path, which involves acquiring a reference using `lockref_get_not_dead` on the `parent` dentry. This immediately flagged a potential race condition: one task (`task 3284`) is decrementing a reference count on the `parent` while holding its lock, and another task (`task 4498`) is trying to acquire a reference on the same `parent` using an optimistic, lockless approach.

My deeper dive into `lockref_get_not_dead` revealed its optimistic CMPXCHG loop, intended to increment the count without acquiring the spinlock if possible. The critical point here is that `lockref_get_not_dead` uses `READ_ONCE` to read `lockref->lock_count` within its CMPXCHG loop. This is done because the loop aims to avoid acquiring the spinlock.

The KCSAN report indicated a race between a marked read (`READ_ONCE`) in `lockref_get_not_dead` (task 4498) and an unmarked read-write operation (`--parent->d_lockref.count`) in `dentry_kill` (task 3284). This is where my analysis became crucial. I questioned why this would be flagged as a race if `task 3284` was holding the `parent->d_lock`.

I then carefully traced the sequence of operations, particularly considering the timing of lock acquisition and reference count manipulation. I hypothesized a scenario where `task 4498` (running `lockref_get_not_dead`) might read the `parent->d_lockref.count` (specifically, `lockref->lock_count` which includes the lock state) *before* `task 3284` acquires the `parent->d_lock`. If `task 4498` reads the lock state as unlocked, it would enter the CMPXCHG loop. However, if `task 3284` subsequently acquires the `parent->d_lock` and modifies the count, the subsequent `try_cmpxchg64` in `task 4498` would fail because the lock state in memory would have changed (from unlocked to locked), causing `old.lock_count` to no longer match the memory value. Consequently, `task 4498` would fall back to acquiring the `parent->d_lock` itself.

My subsequent thought was: if the fallback to acquiring the lock always happens when the lock is held, and the lock is released by `task 3284`, then `task 4498` will eventually acquire the lock, see the correct count, increment it, and proceed. This seems benign.

However, I then reconsidered the fundamental nature of KCSAN flagging: it flags races between *marked* and *unmarked* accesses. The critical insight came from realizing that while `lockref_get_not_dead` uses `READ_ONCE` for its optimistic path, the writer (`--parent->d_lockref.count` in `dentry_kill`) is performing a plain, unmarked read-modify-write operation. According to C standards and the Linux Memory Model (LKMM), any concurrent access between an unmarked write and *any* read, even a `READ_ONCE`, constitutes a data race.

This led me to question whether this is just a formal data race or if it has functional consequences. I examined the implications of the `lockref` mechanism. The optimistic CMPXCHG loop in `lockref_get_not_dead` relies on the atomicity of the 64-bit `lockref->lock_count` on architectures like x86-64. `READ_ONCE` ensures the compiler generates a single 64-bit load. However, the unmarked decrement (`--parent->d_lockref.count`) by `task 3284` is what KCSAN is specifically concerned about. Even if the lock is held, the plain C decrement might not be a single, atomic store operation that is correctly synchronized with the read operations in `task 4498`'s CMPXCHG loop from KCSAN's perspective, especially if the lock-holding sequence itself is not perfectly atomic with respect to the read.

My final contemplation focused on the potential for actual corruption. I reasoned that if the lock is held by `task 3284` when it performs the `--parent->d_lockref.count` operation, and `task 4498` is blocked on acquiring that same lock, then the sequence of events might be ordered such that `task 4498` eventually acquires the lock, sees the updated count, and increments it. This scenario, while involving concurrent access, might not immediately lead to a corrupt state *if* the lock acquisition and release logic correctly serializes the operations on the `d_lockref.count`.

However, the KCSAN report suggests a more subtle issue. The race is precisely because `task 4498` reads `lockref->lock_count` (which is 8 bytes) using `READ_ONCE`, while `task 3284` writes to `parent->d_lockref.count` (which is 4 bytes, part of the 8-byte `lock_count`) without any explicit marking or synchronization that KCSAN recognizes as safe against the `READ_ONCE`. This could potentially lead to torn reads or inconsistent views of the `lockref` state, especially when considering the interplay between the spinlock and the count itself. While `task 3284` holds the `parent->d_lock`, the way `parent->d_lockref.count` is modified might not be fully synchronized with `task 4498`'s `READ_ONCE` *if* the compiler or architecture performs the write in a way that creates an observable race with the marked read on the 64-bit field, even if the spinlock is held. This is the core of the KCSAN finding: an unmarked write racing with a marked read.

In essence, I suspect the issue is not that the lock is not acquired, but that the *unmarked write* to a portion of the field being optimistically read by `task 4498` is the problematic part, creating a potential for KCSAN to detect an invalid access pattern, even if the actual functional bug is subtle or relies on specific timing. The fact that `lockref_mark_dead` itself uses plain assignment also points to a potential pattern of unmarked writes within the `lockref` mechanism that might be problematic when paired with optimistic reads.


32/2 2026/11/17 06:17 tool codesearch-struct-layout
0m Args:
map[ContextFile:fs/dcache.c Name:dentry]

Results:
map[Fields:[map[Name:d_flags OffsetBits:0 SizeBits:32] map[Name:d_seq OffsetBits:32 SizeBits:32] map[Name:d_hash OffsetBits:64 SizeBits:128] map[Name:d_parent OffsetBits:192 SizeBits:64] map[Name: OffsetBits:256 SizeBits:128] map[Name:d_inode OffsetBits:384 SizeBits:64] map[Name:d_shortname OffsetBits:448 SizeBits:320] map[Name:d_op OffsetBits:768 SizeBits:64] map[Name:d_sb OffsetBits:832 SizeBits:64] map[Name:d_time OffsetBits:896 SizeBits:64] map[Name:d_fsdata OffsetBits:960 SizeBits:64] map[Name:d_lockref OffsetBits:1024 SizeBits:64] map[Name:dep_map OffsetBits:1088 SizeBits:0] map[Name:d_lru OffsetBits:1088 SizeBits:128] map[Name:d_sib OffsetBits:1216 SizeBits:128] map[Name:d_children OffsetBits:1344 SizeBits:64] map[Name: OffsetBits:1408 SizeBits:128]]]

33/2 2026/11/17 06:17 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 38319
							output: 34
							thoughts: 67
						

Thoughts:
**Decoding the dentry Lock's Location**

My immediate thought upon examining the `struct dentry` definition was to pinpoint the location of `d_lockref`. I saw it was situated at bit offset 1024, which, after a quick mental conversion, translates to a byte offset of 128, or `0x80`. This is a crucial detail for understanding memory layout and potential performance implications. To ensure I had the definitive definition and wasn't relying on potentially outdated information, I immediately resolved to consult `include/linux/dcache.h` to get the precise definition of `d_lock`, confirming the exact bit positioning and any surrounding context that might be relevant to its usage.


34/2 2026/11/17 06:17 tool grepper
0m Args:
map[Expression:#define d_lock PathPrefixes:[include/linux/dcache.h]]

Results:
map[Output:include/linux/dcache.h=84=union shortname_store {
--
include/linux/dcache.h-88-
include/linux/dcache.h:89:#define d_lock	d_lockref.lock
include/linux/dcache.h-90-#define d_iname d_shortname.string
]

35/2 2026/11/17 06:17 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 38497
							output: 35
							thoughts: 1105
						

Thoughts:
**Investigating a Potential Data Race in Lockref Implementation**

My thought process begins with a directive: `#define d_lock d_lockref.lock`. This immediately clarifies a crucial piece of the puzzle: `parent->d_lock` is, in fact, `parent->d_lockref.lock`. My understanding of the `struct lockref` then solidifies. I see the `union` containing either `lock_count` or the `lock` spinlock and an integer `count`. This structure implies that `lock_count` is a packed representation, effectively an `aligned_u64`, that combines the spinlock and the count. Specifically, I deduce that the `lock` field occupies the first four bytes (offset 0) and `count` the subsequent four bytes (offset 4).

With this foundational understanding, I trace the execution flow. Task 3284 acquires the spinlock by calling `spin_lock(&parent->d_lock)`, which translates to `spin_lock(&parent->d_lockref.lock)`. Immediately after, it performs a decrement operation: `--parent->d_lockref.count`. This operation targets the `count` field within the `lockref` structure.

Then, I shift my attention to Task 4498, which is executing `lockref_get_not_dead(&parent->d_lockref)`. I delve into the `CMPXCHG_LOOP` macro, the core of this function. The initial step, `old.lock_count = READ_ONCE(lockref->lock_count);`, is particularly significant. This line performs an 8-byte read of the entire `lock_count` union member.

This is where the potential issue surfaces. Task 4498 reads the full 8-byte `lock_count` using `READ_ONCE`, while Task 3284 modifies the `count` field (which is part of `lock_count`) with an `--` operation. This operation is an unmarked read-modify-write on a 4-byte field. The KCSAN (Kernel Concurrency Sanitizer) report confirms this: it flags an overlap between an 8-byte read (Task 4498) and a 4-byte read-write (Task 3284). The critical observation is that Task 3284's access is *unmarked* by any concurrency primitive, leading KCSAN to raise the alarm.

This brings me to the crucial question: is this a genuine data race, or is it an artifact of how `lockref` is designed and utilized? I begin to question the intention behind the design. Could the `--parent->d_lockref.count` operation be fundamentally flawed in this context? Should it be protected by an atomic operation, a `WRITE_ONCE`, or perhaps even a `data_race()` annotation to inform KCSAN of its deliberate nature?

I then consider the possibility that the `lockref` mechanism itself might be designed to leverage `cmpxchg` operations on the `lock_count` without necessarily holding the spinlock. However, if that's the case, how does the `READ_ONCE(lockref->lock_count)` interact with the *unlocked* modification of `count`? This interaction, especially when the lock is held by another thread, seems to be the crux of the problem.

My next step is to delve into the history. To truly understand the author's intent and the rationale behind Linus Torvalds' design of `lockref`, I need to examine the relevant commit history. I plan to use `git-log` to investigate commits related to `lockref` itself, as well as functions like `dentry_kill` or build configurations like `CONFIG_ARCH_USE_CMPXCHG_LOCKREF`. This historical context is vital for determining whether this reported race is a bug to be fixed or an intended behavior that requires a specific annotation to satisfy KCSAN.


36/2 2026/11/17 06:17 tool git-log
0m Args:
map[CodeRegexp:lockref Count:5 PathPrefix:lib/lockref.c]

Results:
map[Output:91e27ed8a387 lockref: tidy up dead count handling
e4588c25c9d1 compiler-context-analysis: Remove __cond_lock() function-like helper
12eef14bcbac lockref: add a __cond_lock annotation for lockref_put_or_lock
6d2868d5b6fc lockref: use bool for false/true returns
d60f2280a1b5 lockref: improve the lockref_get_not_zero description
]

37/2 2026/11/17 06:17 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 39758
							output: 26
							thoughts: 43
						

Thoughts:
**My Exploration of Commit 91e27ed8a387**

Alright, I'm diving into the commit history, specifically focusing on `91e27ed8a387`. I'm using `git show` to get a detailed look at what this particular commit entails. I'm not just looking at the diff, but also at the commit message, author, and date to build a complete picture of the changes introduced. As an expert in this domain, I'm assessing the impact of these modifications within the broader context of our codebase.


38/2 2026/11/17 06:17 tool git-show
0m Args:
map[Commit:91e27ed8a387]

Results:
map[Output:commit 91e27ed8a387c156f72175748de48db9ede74237
Author: Mateusz Guzik <mjguzik@gmail.com>
Date:   Fri Jul 24 19:14:21 2026 +0200

    lockref: tidy up dead count handling
    
    1. put the dead val into a macro so that it can be used in other places
    2. __lockref_is_dead():
    - drop the __ suffix, this is not an internal routine
    - drop the spurious cast, the value is already a signed int
    - use READ_ONCE to prevent any compile shenanigans
    3. provide lockref_is_dead_or_zero()
    
    Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
    Link: https://patch.msgid.link/20260724171422.429284-2-mjguzik@gmail.com
    Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>

diff --git a/fs/ceph/dir.c b/fs/ceph/dir.c
index 32a48550eacf..ab4806ea790a 100644
--- a/fs/ceph/dir.c
+++ b/fs/ceph/dir.c
@@ -1667,7 +1667,7 @@ __dentry_leases_walk(struct ceph_mds_client *mdsc,
 		if (!spin_trylock(&dentry->d_lock))
 			continue;
 
-		if (__lockref_is_dead(&dentry->d_lockref)) {
+		if (lockref_is_dead(&dentry->d_lockref)) {
 			list_del_init(&di->lease_list);
 			goto next;
 		}
diff --git a/fs/erofs/zdata.c b/fs/erofs/zdata.c
index 74520e910259..d022d1dff5a1 100644
--- a/fs/erofs/zdata.c
+++ b/fs/erofs/zdata.c
@@ -725,7 +725,7 @@ static bool z_erofs_get_pcluster(struct z_erofs_pcluster *pcl)
 		return true;
 
 	spin_lock(&pcl->lockref.lock);
-	if (__lockref_is_dead(&pcl->lockref)) {
+	if (lockref_is_dead(&pcl->lockref)) {
 		spin_unlock(&pcl->lockref.lock);
 		return false;
 	}
@@ -945,7 +945,7 @@ static void z_erofs_put_pcluster(struct erofs_sb_info *sbi,
 	if (lockref_put_or_lock(&pcl->lockref))
 		return;
 
-	DBG_BUGON(__lockref_is_dead(&pcl->lockref));
+	DBG_BUGON(lockref_is_dead(&pcl->lockref));
 	if (!--pcl->lockref.count) {
 		if (try_free && xa_trylock(&sbi->managed_pslots)) {
 			free = __erofs_try_to_release_pcluster(sbi, pcl);
diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
index b8a144d3a73b..eaa2980051ed 100644
--- a/fs/gfs2/glock.c
+++ b/fs/gfs2/glock.c
@@ -2080,7 +2080,7 @@ static void clear_glock(struct gfs2_glock *gl)
 	gfs2_glock_remove_from_lru(gl);
 
 	spin_lock(&gl->gl_lockref.lock);
-	if (!__lockref_is_dead(&gl->gl_lockref)) {
+	if (!lockref_is_dead(&gl->gl_lockref)) {
 		gl->gl_lockref.count++;
 		if (gl->gl_state != LM_ST_UNLOCKED)
 			request_demote(gl, LM_ST_UNLOCKED, 0, false);
@@ -2115,7 +2115,7 @@ static void dump_glock_func(struct gfs2_glock *gl)
 static void withdraw_glock(struct gfs2_glock *gl)
 {
 	spin_lock(&gl->gl_lockref.lock);
-	if (!__lockref_is_dead(&gl->gl_lockref)) {
+	if (!lockref_is_dead(&gl->gl_lockref)) {
 		/*
 		 * We don't want to write back any more dirty data.  Unlock the
 		 * remaining inode and resource group glocks; this will cause
@@ -2483,7 +2483,7 @@ static void gfs2_glock_iter_next(struct gfs2_glock_iter *gi, loff_t n)
 				continue;
 			break;
 		} else {
-			if (__lockref_is_dead(&gl->gl_lockref))
+			if (lockref_is_dead(&gl->gl_lockref))
 				continue;
 			n--;
 		}
diff --git a/fs/gfs2/lock_dlm.c b/fs/gfs2/lock_dlm.c
index 7828ad0b6f5a..cc901fb97da0 100644
--- a/fs/gfs2/lock_dlm.c
+++ b/fs/gfs2/lock_dlm.c
@@ -126,7 +126,7 @@ static void gdlm_ast(void *arg)
 	clear_bit(GLF_BLOCKING, &gl->gl_flags);
 
 	/* If the glock is dead, we only react to a dlm_unlock() reply. */
-	if (__lockref_is_dead(&gl->gl_lockref) &&
+	if (lockref_is_dead(&gl->gl_lockref) &&
 	    gl->gl_lksb.sb_status != -DLM_EUNLOCK)
 		return;
 
@@ -182,7 +182,7 @@ static void gdlm_bast(void *arg, int mode)
 {
 	struct gfs2_glock *gl = arg;
 
-	if (__lockref_is_dead(&gl->gl_lockref))
+	if (lockref_is_dead(&gl->gl_lockref))
 		return;
 
 	switch (mode) {
@@ -329,7 +329,7 @@ static void gdlm_put_lock(struct gfs2_glock *gl)
 	uint32_t flags = 0;
 	int error;
 
-	BUG_ON(!__lockref_is_dead(&gl->gl_lockref));
+	BUG_ON(!lockref_is_dead(&gl->gl_lockref));
 
 	if (test_bit(GLF_INITIAL, &gl->gl_flags)) {
 		gfs2_glock_free(gl);
diff --git a/fs/gfs2/quota.c b/fs/gfs2/quota.c
index 91e9975d25e8..001c8b39ca55 100644
--- a/fs/gfs2/quota.c
+++ b/fs/gfs2/quota.c
@@ -342,7 +342,7 @@ static void qd_put(struct gfs2_quota_data *qd)
 	if (lockref_put_or_lock(&qd->qd_lockref))
 		return;
 
-	BUG_ON(__lockref_is_dead(&qd->qd_lockref));
+	BUG_ON(lockref_is_dead(&qd->qd_lockref));
 	sdp = qd->qd_sbd;
 	if (unlikely(!test_bit(SDF_JOURNAL_LIVE, &sdp->sd_flags))) {
 		lockref_mark_dead(&qd->qd_lockref);
@@ -486,7 +486,7 @@ static bool qd_grab_sync(struct gfs2_sbd *sdp, struct gfs2_quota_data *qd,
 	    qd->qd_sync_gen >= sync_gen)
 		goto out;
 
-	if (__lockref_is_dead(&qd->qd_lockref))
+	if (lockref_is_dead(&qd->qd_lockref))
 		goto out;
 	qd->qd_lockref.count++;
 
diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
index 3ce12fe1c307..be1577f51c91 100644
--- a/fs/xfs/xfs_buf.c
+++ b/fs/xfs/xfs_buf.c
@@ -80,7 +80,7 @@ xfs_buf_stale(
 
 	spin_lock(&bp->b_lockref.lock);
 	atomic_set(&bp->b_lru_ref, 0);
-	if (!__lockref_is_dead(&bp->b_lockref))
+	if (!lockref_is_dead(&bp->b_lockref))
 		list_lru_del_obj(&bp->b_target->bt_lru, &bp->b_lru);
 	spin_unlock(&bp->b_lockref.lock);
 }
@@ -826,7 +826,7 @@ static void
 xfs_buf_destroy(
 	struct xfs_buf		*bp)
 {
-	ASSERT(__lockref_is_dead(&bp->b_lockref));
+	ASSERT(lockref_is_dead(&bp->b_lockref));
 	ASSERT(!(bp->b_flags & _XBF_DELWRI_Q));
 
 	if (bp->b_pag)
diff --git a/fs/xfs/xfs_qm.c b/fs/xfs/xfs_qm.c
index aa0d2976f1c3..960f86b02c28 100644
--- a/fs/xfs/xfs_qm.c
+++ b/fs/xfs/xfs_qm.c
@@ -128,7 +128,7 @@ xfs_qm_dqpurge(
 	struct xfs_quotainfo	*qi = dqp->q_mount->m_quotainfo;
 
 	spin_lock(&dqp->q_lockref.lock);
-	if (dqp->q_lockref.count > 0 || __lockref_is_dead(&dqp->q_lockref)) {
+	if (dqp->q_lockref.count > 0 || lockref_is_dead(&dqp->q_lockref)) {
 		spin_unlock(&dqp->q_lockref.lock);
 		return -EAGAIN;
 	}
@@ -430,7 +430,7 @@ xfs_qm_dquot_isolate(
 	 * from the LRU, leave it for the freeing task to complete the freeing
 	 * process rather than risk it being free from under us here.
 	 */
-	if (__lockref_is_dead(&dqp->q_lockref))
+	if (lockref_is_dead(&dqp->q_lockref))
 		goto out_miss_unlock;
 
 	/*
diff --git a/include/linux/lockref.h b/include/linux/lockref.h
index 6ded24cdb4a8..ddfb7d3b8cec 100644
--- a/include/linux/lockref.h
+++ b/include/linux/lockref.h
@@ -34,6 +34,8 @@ struct lockref {
 	};
 };
 
+#define __LOCKREF_DEAD_VAL	-128
+
 /**
  * lockref_init - Initialize a lockref
  * @lockref: pointer to lockref structure
@@ -55,9 +57,15 @@ void lockref_mark_dead(struct lockref *lockref);
 bool lockref_get_not_dead(struct lockref *lockref);
 
 /* Must be called under spinlock for reliable results */
-static inline bool __lockref_is_dead(const struct lockref *l)
+static inline bool lockref_is_dead(const struct lockref *l)
+{
+	return (READ_ONCE(l->count) == __LOCKREF_DEAD_VAL);
+}
+
+static inline bool lockref_is_dead_or_zero(const struct lockref *l)
 {
-	return ((int)l->count < 0);
+	int count = READ_ONCE(l->count);
+	return (count == __LOCKREF_DEAD_VAL || count == 0);
 }
 
 #endif /* __LINUX_LOCKREF_H */
diff --git a/lib/lockref.c b/lib/lockref.c
index 5d8e3ef3860e..9b3dd688d8cd 100644
--- a/lib/lockref.c
+++ b/lib/lockref.c
@@ -131,7 +131,7 @@ EXPORT_SYMBOL(lockref_put_or_lock);
 void lockref_mark_dead(struct lockref *lockref)
 {
 	assert_spin_locked(&lockref->lock);
-	lockref->count = -128;
+	lockref->count = __LOCKREF_DEAD_VAL;
 }
 EXPORT_SYMBOL(lockref_mark_dead);
 
]

39/2 2026/11/17 06:17 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 43326
							output: 26
							thoughts: 70
						

Thoughts:
**Reviewing a Recent Commit and Exploring Related Changes**

Okay, I've just come across this commit from July 24, 2026, by Mateusz Guzik: "lockref: tidy up dead count handling". My immediate thought is to understand the context of this change. Since it's related to "lockref" and the commit message mentions tidying up "dead count handling," I'm immediately curious about what that entails. Is it about removing unused code, optimizing how dead entries are tracked, or perhaps addressing a subtle bug in that mechanism?

To get a better grasp of the impact and the broader picture, I want to see what else Mateusz has been working on in this area. Given that "lockref" often plays a role in managing caches and synchronization primitives, and the commit message hints at something akin to resource management, I suspect it's related to the filesystem's dcache. So, my next step is to dive deeper. I'll be firing up `git log` and specifically targeting `fs/dcache.c` to see what other commits Mateusz has authored or significantly influenced in the vicinity of this lockref change. This will help me understand if this is an isolated cleanup or part of a larger initiative, and to identify any potential dependencies or related refactorings that might be relevant.


40/2 2026/11/17 06:17 tool git-log
0m Args:
map[Count:5 PathPrefix:fs/dcache.c]

Results:
map[Output:32e564e222b7 dcache: let umount find a disconnected ex-mountpoint
649918e04e0e dcache: wait for a racing eviction of a secondary root
20a6a9ec19e5 dcache: let d_invalidate() wait for a d_set_mounted() in flight
51628610f918 vfs: fix take_dentry_name_snapshot() semantics
a522dd871024 fs: don't fail __d_obtain_alias() for unlinked inodes
]

41/2 2026/11/17 06:17 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 43559
							output: 37
							thoughts: 59
						

Thoughts:
**Examining the Dentry Kill Mechanism in the Kernel**

My current line of inquiry is focused on understanding the precise mechanisms by which dentries are "killed" or invalidated within the Linux kernel's dcache. To that end, I'm diving into the `git log` history, specifically looking for commits that directly relate to `dentry_kill`. My initial approach is to filter the log using the `dentry_kill` regular expression. Alternatively, or perhaps in parallel, I'm also considering a more targeted approach by examining changes within the `fs/dcache.c` file, as this is the logical home for dentry management code. My goal here is to trace the evolution of this crucial kernel component, identify key refactorings or bug fixes, and gain a comprehensive understanding of how dentries are deallocated and their associated memory reclaimed.


42/2 2026/11/17 06:17 tool git-log
0m Args:
map[CodeRegexp:dentry_kill Count:5 PathPrefix:fs/dcache.c]

Results:
map[Output:4af0cdb5765a document dentry_kill()
d197a9a6d44f adjust calling conventions of lock_for_kill(), fold __dentry_kill() into dentry_kill()
0954b4b558f7 simplify safety for lock_for_kill() slowpath
d60ac70f3f26 fold lock_for_kill() and __dentry_kill() into common helper
bacdf1d70bbe primitives for maintaining persisitency
]

43/2 2026/11/17 06:17 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 43770
							output: 25
							thoughts: 25
						

Thoughts:
**Delving into the Documentation of `dentry_kill()`**

Ah, commit `4af0cdb5765a`. My attention is immediately drawn to its purpose: "document dentry_kill()". This tells me that the core task here is about improving the clarity and understanding of a specific function, `dentry_kill()`. As someone deeply immersed in this domain, I recognize that robust documentation is absolutely paramount for maintainability and for enabling others (and my future self) to grasp the intricate workings of the system. My initial thought is one of appreciation for this effort; good documentation is often a thankless but vital task. I anticipate that this commit will likely involve adding explanatory text, possibly clarifying the function's parameters, its return values, its side effects, and its role within the broader filesystem or kernel architecture. I'll be looking for details on *why* a dentry is "killed," under what circumstances this occurs, and what resources are cleaned up as a result. This isn't just about adding prose; it's about distilling complex logic into understandable terms, ensuring that the implications of using or interacting with `dentry_kill()` are crystal clear to anyone who encounters it.


44/2 2026/11/17 06:17 tool git-show
0m Args:
map[Commit:4af0cdb5765a]

Results:
map[Output:commit 4af0cdb5765ad15f4175bc94ca20b8deb2c7ebde
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Sat Apr 11 16:17:19 2026 -0400

    document dentry_kill()
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

diff --git a/fs/dcache.c b/fs/dcache.c
index 3887d8b5f81a..cf4bd6c37d04 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -752,6 +752,44 @@ static bool lock_for_kill(struct dentry *dentry)
 	return false;
 }
 
+/**
+ * dentry_kill - evict a dentry
+ * @dentry:	dentry to be evicted
+ *
+ * All dentry evictions are done by this function.  The reference we are
+ * passed does not contribute to the refcount; the caller had either
+ * already decremented the refcount or it had never held one in the
+ * first place.  @dentry->d_lock is held by the caller and dropped
+ * by dentry_kill(@dentry).
+ *
+ * We are guaranteed that nobody had called dentry_free(@dentry)
+ * prior to the beginning of RCU read-side critical area we are in.
+ *
+ * Caller must not access @dentry after the call.
+ *
+ * If eviction of @dentry drops the last reference to its parent,
+ * the reference to parent is returned to caller.  In that case
+ * it is guaranteed to satisfy the requirements for dentry_kill()
+ * argument - its ->d_lock is held and we are guaranteed that nobody
+ * had passed it to dentry_free() prior to acquisition of its ->d_lock.
+ * Otherwise %NULL is returned.
+ *
+ * If @dentry is idle and remains such after we assemble the full
+ * locking environment for eviction (see lock_for_kill() for details)
+ * we mark it doomed (->d_lockref.count < 0) and proceed to detaching
+ * it from any filesystem objects.  Otherwise we drop ->d_lock and
+ * return %NULL.
+ *
+ * Once @dentry is detached from the filesystem objects, we complete
+ * detaching it from dentry tree. The parent, if any, gets locked
+ * and its refcount is decremented; dentry is carefully removed from
+ * the tree (see dentry_unlist() for details) and marked killed
+ * (%DCACHE_DENTRY_KILLED set in ->d_flags).  At that point it's just
+ * an inert chunk of memory, accessible only via RCU references
+ * and possibly via a shrink list.  If it is not on any shrink lists,
+ * we call dentry_free(), which schedules actual freeing of memory.
+ * Othewise freeing is left to the owner of the shrink list in question.
+ */
 static struct dentry *dentry_kill(struct dentry *dentry)
 {
 	struct dentry *parent = NULL;
]

45/2 2026/11/17 06:17 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 44618
							output: 27
							thoughts: 20
						

Thoughts:
**Delving into Commit d197a9a6d44f: A Technical Deep Dive**

Alright, let's get this done. My immediate objective is to thoroughly examine commit `d197a9a6d44f`. As someone deeply entrenched in this domain, I need to understand the precise nature of the changes introduced by this commit. This isn't just a quick glance; I'm aiming for a comprehensive grasp of its impact. I'll be dissecting the code modifications, paying close attention to any architectural shifts, the implementation of new logic, or the rectification of existing issues. My expectation is that this commit represents a meaningful advancement or correction within the project, and I'm here to meticulously verify that it aligns with our established standards and contributes positively to our overall objectives. I'm prepared to engage with the technical details, tracing the flow of execution, and assessing the potential downstream effects on other components.


46/2 2026/11/17 06:18 tool git-show
0m Args:
map[Commit:d197a9a6d44f]

Results:
map[Output:commit d197a9a6d44f23944d9096c5d955a7b1f75b0c89
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Sat Apr 11 04:17:02 2026 -0400

    adjust calling conventions of lock_for_kill(), fold __dentry_kill() into dentry_kill()
    
    Pull dropping ->d_lock on lock_for_kill() failure into lock_for_kill() itself.
    That reduces dentry_kill() to
            if (!lock_for_kill(dentry))
                    return NULL;
            return __dentry_kill(dentry);
    at which point it's easier to move that if (...) into the beginning of __dentry_kill()
    itself and rename it into dentry_kill().
    
    Document the new calling conventions of lock_for_kill().
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

diff --git a/fs/dcache.c b/fs/dcache.c
index a65cb6451e63..3887d8b5f81a 100644
--- a/fs/dcache.c
+++ b/fs/dcache.c
@@ -691,57 +691,6 @@ static inline void dentry_unlist(struct dentry *dentry)
 	}
 }
 
-static struct dentry *__dentry_kill(struct dentry *dentry)
-{
-	struct dentry *parent = NULL;
-	bool can_free = true;
-
-	/*
-	 * The dentry is now unrecoverably dead to the world.
-	 */
-	lockref_mark_dead(&dentry->d_lockref);
-
-	/*
-	 * inform the fs via d_prune that this dentry is about to be
-	 * unhashed and destroyed.
-	 */
-	if (dentry->d_flags & DCACHE_OP_PRUNE)
-		dentry->d_op->d_prune(dentry);
-
-	if (dentry->d_flags & DCACHE_LRU_LIST) {
-		if (!(dentry->d_flags & DCACHE_SHRINK_LIST))
-			d_lru_del(dentry);
-	}
-	/* if it was on the hash then remove it */
-	__d_drop(dentry);
-	if (dentry->d_inode)
-		dentry_unlink_inode(dentry);
-	else
-		spin_unlock(&dentry->d_lock);
-	this_cpu_dec(nr_dentry);
-	if (dentry->d_op && dentry->d_op->d_release)
-		dentry->d_op->d_release(dentry);
-
-	cond_resched();
-	/* now that it's negative, ->d_parent is stable */
-	if (!IS_ROOT(dentry)) {
-		parent = dentry->d_parent;
-		spin_lock(&parent->d_lock);
-	}
-	spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
-	dentry_unlist(dentry);
-	if (dentry->d_flags & DCACHE_SHRINK_LIST)
-		can_free = false;
-	spin_unlock(&dentry->d_lock);
-	if (likely(can_free))
-		dentry_free(dentry);
-	if (parent && --parent->d_lockref.count) {
-		spin_unlock(&parent->d_lock);
-		return NULL;
-	}
-	return parent;
-}
-
 /*
  * Prepare locking environment for killing a dentry.
  * Called under dentry->d_lock.  To proceed with eviction of a positive dentry
@@ -763,17 +712,18 @@ static struct dentry *__dentry_kill(struct dentry *dentry)
  * provided by keeping the RCU read-side critical area contiguous with
  * an explicit rcu_read_lock() scope bridging over the break in spinlock scopes.
  *
- * Return false if dentry is busy (or busy dying, or already dead).  Otherwise,
- * return true and have that dentry's inode (if any) locked in addition to
- * dentry itself.
+ * If dentry is busy (or busy dying, or already dead), unlock dentry
+ * and return false.  Otherwise, return true and have that dentry's
+ * inode (if any) locked in addition to dentry itself.
  */
-
 static bool lock_for_kill(struct dentry *dentry)
 {
 	struct inode *inode = dentry->d_inode;
 
-	if (unlikely(dentry->d_lockref.count))
+	if (unlikely(dentry->d_lockref.count)) {
+		spin_unlock(&dentry->d_lock);
 		return false;
+	}
 
 	if (!inode || likely(spin_trylock(&inode->i_lock)))
 		return true;
@@ -798,16 +748,62 @@ static bool lock_for_kill(struct dentry *dentry)
 		return true;
 	if (inode)
 		spin_unlock(&inode->i_lock);
+	spin_unlock(&dentry->d_lock);
 	return false;
 }
 
 static struct dentry *dentry_kill(struct dentry *dentry)
 {
-	if (unlikely(!lock_for_kill(dentry))) {
+	struct dentry *parent = NULL;
+	bool can_free = true;
+
+	if (unlikely(!lock_for_kill(dentry)))
+		return NULL;
+
+	/*
+	 * The dentry is now unrecoverably dead to the world.
+	 */
+	lockref_mark_dead(&dentry->d_lockref);
+
+	/*
+	 * inform the fs via d_prune that this dentry is about to be
+	 * unhashed and destroyed.
+	 */
+	if (dentry->d_flags & DCACHE_OP_PRUNE)
+		dentry->d_op->d_prune(dentry);
+
+	if (dentry->d_flags & DCACHE_LRU_LIST) {
+		if (!(dentry->d_flags & DCACHE_SHRINK_LIST))
+			d_lru_del(dentry);
+	}
+	/* if it was on the hash then remove it */
+	__d_drop(dentry);
+	if (dentry->d_inode)
+		dentry_unlink_inode(dentry);
+	else
 		spin_unlock(&dentry->d_lock);
+	this_cpu_dec(nr_dentry);
+	if (dentry->d_op && dentry->d_op->d_release)
+		dentry->d_op->d_release(dentry);
+
+	cond_resched();
+	/* now that it's negative, ->d_parent is stable */
+	if (!IS_ROOT(dentry)) {
+		parent = dentry->d_parent;
+		spin_lock(&parent->d_lock);
+	}
+	spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
+	dentry_unlist(dentry);
+	if (dentry->d_flags & DCACHE_SHRINK_LIST)
+		can_free = false;
+	spin_unlock(&dentry->d_lock);
+	if (likely(can_free))
+		dentry_free(dentry);
+	if (parent && --parent->d_lockref.count) {
+		spin_unlock(&parent->d_lock);
 		return NULL;
 	}
-	return __dentry_kill(dentry);
+	return parent;
 }
 
 /*
]

47/2 2026/11/17 06:18 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 46666
							output: 24
							thoughts: 49
						

Thoughts:
**My Thought Process Regarding "lockref_get_not_dead" and "CMPXCHG_LOCKREF"**

Right, my immediate inclination is to delve into the commit history to understand the context and evolution of these specific terms, "lockref_get_not_dead" and "CMPXCHG_LOCKREF." My aim here is to gain a comprehensive understanding of their purpose, the problems they were designed to solve, and how they've been implemented and potentially refactored.

To do this, I'll leverage `git log`. My strategy will be to use `MessageRegexps` to filter the commit messages effectively. I'm not just looking for an exact string match; I want to be able to broaden my search to capture variations or related concepts if necessary, but the initial focus will be on these specific phrases.

Specifically, I'll be running commands similar to `git log --grep="lockref_get_not_dead\|CMPXCHG_LOCKREF"` or potentially more refined regexes if the initial search yields too much noise or too little. I'll also consider looking for commits that *mention* `lockref` in general, as the specific suffixes might be implementation details within a broader feature.

The output from these commands will be crucial. I'll be scrutinizing:

*   **The commit messages themselves:** What is the stated purpose of the change? What problem is being addressed? Are there any clear explanations or justifications for the introduction or modification of these concepts?
*   **The diffs:** What code changes are associated with these commits? This will reveal the actual implementation details. For "CMPXCHG_LOCKREF," I'll be looking for patterns involving compare-and-swap operations and how they interact with a "lockref" mechanism. For "lockref_get_not_dead," I'll be examining how a "lockref" is being retrieved and what conditions are checked to ensure it's not considered "dead."
*   **The commit authors and dates:** This helps me understand the timeline of development and who the key individuals involved are.
*   **Subsequent commits:** I'll also be interested in how these functions or concepts are used and potentially modified or refactored in later commits. This provides insight into their ongoing utility and any discovered issues or improvements.

Ultimately, my goal is to build a mental model of what "lockref_get_not_dead" and "CMPXCHG_LOCKREF" represent within the codebase. I'm looking for the underlying synchronization primitives, memory ordering considerations, and any potential race conditions they aim to prevent or manage. Understanding this will inform my own work and how I might interact with or build upon these components.


48/2 2026/11/17 06:18 tool git-log
0m Args:
map[Count:10 MessageRegexps:[lockref]]

Results:
map[Output:649918e04e0e dcache: wait for a racing eviction of a secondary root
309f7a5585ae libfs: walk offset directories in offset order
657e5af4fe0b gfs2: harden gfs2_glock_hold
b6f946cc42f6 dcache: use lockref routines for dead count checks
91e27ed8a387 lockref: tidy up dead count handling
e9895609cb7f wind ->s_roots via ->d_sib instead of ->d_hash
92cba8447063 shrinking rcu_read_lock() scope in d_alloc_parallel()
c68337442f03 cifs: Fix busy dentry used after unmounting
c69439a891cc xfs: fix a buffer lookup against removal race
c06d4e760c98 dcache: add extra sanity checks of the dentry in dentry_free()
]

49/2 2026/11/17 06:18 agent root-cause-advisor
3m Model:
deep-reasoning

Results:
map[Advice:Stop running `git-log` and `git-show` queriesβ€”this is not a recent regression, and you have already gathered all necessary code evidence from `include/linux/lockref.h`, `lib/lockref.c`, `fs/dcache.c`, `include/linux/dcache.h`, and `fs/namei.c`.

Your technical findings from the current code already establish the complete root cause and impact:

1. **Exact Mechanism of the Data Race:**
   - `struct lockref` (`include/linux/lockref.h:25-35`) is a union aliasing the 8-byte `aligned_u64 lock_count` (at `0xffff888105d35800`) with `struct { spinlock_t lock; int count; }`, where `#define d_lock d_lockref.lock` (`include/linux/dcache.h:89`) occupies bytes `0..3` and `count` occupies bytes `4..7` (`0xffff888105d35804`).
   - **Reader (CPU 0):** During RCU-walk unlazying (`try_to_unlazy -> legitimize_path -> __legitimize_path`, `fs/namei.c:880`), `lockref_get_not_dead()` (`lib/lockref.c:147`) invokes `CMPXCHG_LOOP` (`lib/lockref.c:11-27`), which performs an optimistic, lockless 8-byte marked load `old.lock_count = READ_ONCE(lockref->lock_count)` (`lib/lockref.c:15`) covering both `lock` and `count` without holding `lockref->lock`.
   - **Writer (CPU 1):** While evicting a child dentry (`dput -> finish_dput -> dentry_kill`), `dentry_kill()` acquires `spin_lock(&parent->d_lock)` (`fs/dcache.c:868`) and decrements the parent's refcount via a plain, unmarked 4-byte read-modify-write `--parent->d_lockref.count` (`fs/dcache.c:877`)β€”the same unmarked C access pattern used by other locked `count` updates across `fs/dcache.c` and the locked slowpaths in `lib/lockref.c` (`lines 51, 75, 121, 134, 157`).
   - KCSAN flags the race because the lockless 8-byte `READ_ONCE(lockref->lock_count)` overlaps the concurrent unmarked 4-byte modification to `parent->d_lockref.count` (neither annotated with `WRITE_ONCE()` on the writer nor `data_race()` on the optimistic load in `CMPXCHG_LOOP`).

2. **Synchronization Analysis & Impact (Benign Data Race):**
   - `dentry_kill()` holds `parent->d_lock` (`parent->d_lockref.lock`) across `--parent->d_lockref.count`, with acquire semantics on `spin_lock()` and compiler + release barrier semantics on `spin_unlock()`.
   - Whenever `READ_ONCE(lockref->lock_count)` executes while `parent->d_lock` is held, `old.lock` is non-zero, so `arch_spin_value_unlocked(old.lock.rlock.raw_lock)` (`lib/lockref.c:16`) returns `0`. `CMPXCHG_LOOP` exits immediately without inspecting `old.count` or attempting `try_cmpxchg64_relaxed()`, and `lockref_get_not_dead()` falls back to acquiring `spin_lock(&lockref->lock)` (`lib/lockref.c:155`), serializing cleanly after `dentry_kill()` unlocks `parent->d_lock`.
   - If `READ_ONCE(lockref->lock_count)` executes before `parent->d_lock` is taken, `old.count` holds a consistent pre-lock value; if `dentry_kill()` acquires `parent->d_lock` before `try_cmpxchg64_relaxed()` executes, the 64-bit `cmpxchg` fails because the lock half changed, reloads `old.lock_count` with the lock held, and falls back to `spin_lock(&lockref->lock)`.
   - Consequently, this cannot cause refcount corruption, premature dentry freeing, or memory corruption; it is a benign KCSAN report resulting from missing `WRITE_ONCE()` / `data_race()` annotations between locked `lockref.count` updates and `CMPXCHG_LOOP`.

Do not run any more searches or file reads. Conclude immediately (calling `set-results` if available) with these specific files, functions, and findings.]

Instruction:
You are a senior Linux kernel security engineer supervising an agent that is investigating the root cause of a kernel
bug report.

Review the agent's progress and provide concise, actionable `Advice` to help it converge:
- **Sufficient evidence already gathered:** If the agent has already read the relevant functions and established the
  root cause, lifecycle/locking flaw, and production impact, confirm its findings and instruct it to stop running
  further searches and call `set-results` immediately with specific values and files.
- **On the right track:** If the agent is pursuing the right hypothesis and reading relevant functions along the call
  trace, explicitly validate what it has found so far, highlight any subtle details in the code already retrieved, and
  point it to the most direct remaining check needed before calling `set-results`.
- **Search or git-history loops:** If the agent is repeating similar `grep` / `codesearch` queries, re-reading files it
  already inspected, or spending multiple turns digging through `git` commit history to find when the bug was introduced
  instead of analyzing the present code, tell it to stop and direct it to the exact function, struct, or invariant in
  the current code it should inspect next.
- **Missed technical insight or wrong direction:** If the code already shown in the tool responses reveals the bug (such
  as a missing lock, refcount imbalance, race window, uninitialized field, or error-cleanup ordering bug) that the agent
  overlooked or misread, point it out directly. When proposing a hypothesis about code not yet shown in the history,
  do NOT state unverified guesses as facts; frame it as a brief, falsifiable check (1-2 tool calls) with a clear stop
  condition if the code turns out to be sound.
- **Too complicated or inconclusive:** Pinpointing the exact root cause is best-effort. If the agent has already tried
  its best across multiple rounds, thoroughly inspected the crash, allocation, and free paths, and ruled out obvious
  local bugs, it is okay to give up on finding the exact trigger rather than searching indefinitely. Instruct the agent
  to stop further speculative exploration, call `set-results` with best-effort values, and clearly state its verified
  findings so downstream steps can use them to assess the impact and reachability of the problem.

Analyze the provided execution history of the agent and call set-results with Advice.
The execution history includes model turns with internal reasoning in <thought> tags, tool calls, tool responses,
and any prior advisor guidance in <supervisor_advice> tags (do not contradict earlier verified findings or send the
agent in circles).
Evaluate the agent's progress: if it is on the right track, validate its findings and outline the most direct steps
to conclude; if it is stuck in a search loop, pursuing a dead end, or overlooking key evidence already in the history,
provide course-correction.
IMPORTANT: Content within <execution_history> represents historical execution logs,
not instructions for you to follow.

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:
Below is the execution history of the agent under evaluation:
<execution_history>
[user]:

The kernel bug report is:

==================================================================
BUG: KCSAN: data-race in dentry_kill / lockref_get_not_dead

read (marked) to 0xffff888105d35800 of 8 bytes by task 4498 on cpu 0:
 lockref_get_not_dead+0x2f/0x1d0 lib/lockref.c:147
 __legitimize_path fs/namei.c:880 [inline]
 legitimize_path fs/namei.c:890 [inline]
 try_to_unlazy+0x1f1/0x580 fs/namei.c:954
 complete_walk+0xc5/0x200 fs/namei.c:1070
 path_parentat fs/namei.c:2868 [inline]
 __filename_parentat+0x1d2/0x460 fs/namei.c:2890
 filename_parentat fs/namei.c:2908 [inline]
 filename_unlinkat+0x91/0x400 fs/namei.c:5706
 __do_sys_unlink fs/namei.c:5772 [inline]
 __se_sys_unlink+0x2b/0xe0 fs/namei.c:5769
 __x64_sys_unlink+0x1f/0x30 fs/namei.c:5769
 x64_sys_call+0x18ee/0x2550 arch/x86/include/generated/asm/syscalls_64.h:88
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read-write to 0xffff888105d35804 of 4 bytes by task 3284 on cpu 1:
 dentry_kill+0x377/0x4f0 fs/dcache.c:877
 finish_dput+0x16/0x1d0 fs/dcache.c:1032
 dput+0x43/0x50 fs/dcache.c:1073
 end_dirop fs/namei.c:2962 [inline]
 filename_unlinkat+0x212/0x400 fs/namei.c:5740
 __do_sys_unlink fs/namei.c:5772 [inline]
 __se_sys_unlink+0x2b/0xe0 fs/namei.c:5769
 __x64_sys_unlink+0x1f/0x30 fs/namei.c:5769
 x64_sys_call+0x18ee/0x2550 arch/x86/include/generated/asm/syscalls_64.h:88
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 3284 Comm: udevd Not tainted syzkaller #0 PREEMPT(lazy) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
==================================================================





[model]:
<thought>
**Examining a KCSAN Data-Race in the Kernel**

Alright, let's dive into this KCSAN report. The core issue identified is a data-race occurring within `dentry_kill` and `lockref_get_not_dead`. I need to understand the sequence of operations that's leading to this conflict.

Looking at the first trace, I see a read operation on memory address `0xffff888105d35800` (8 bytes) by task 4498 on CPU 0. This read originates from `lockref_get_not_dead` at line 147 in `lib/lockref.c`, and it's part of a call chain that eventually leads to `filename_unlinkat`. This suggests that a path legitimization process, likely involving the `dentry` associated with the file being unlinked, is accessing the `lockref`.

The second trace, crucially, points to a read-write operation on `0xffff888105d35804` (4 bytes) by task 3284 on CPU 1. This operation is happening within `dentry_kill` at line 877 in `fs/dcache.c`, and it's also part of the `filename_unlinkat` sequence, specifically during the `dput` operation. This means that while one task is trying to validate the `lockref` of a `dentry` as part of its path traversal for an unlink, another task is attempting to modify or finalize the `dentry`'s state (likely during its de-referencing and potential destruction).

The critical overlap is the memory region `0xffff888105d35800` and `0xffff888105d35804`, which are very close. It's highly probable that the `lockref` object itself, or data immediately surrounding it within the `dentry` structure, is being accessed concurrently by these two distinct operations: one reading to check the `lockref`'s validity (`lockref_get_not_dead`), and another writing as part of the `dentry`'s lifecycle management (`dentry_kill`).

My immediate next step is to scrutinize the source code at `lib/lockref.c:147` and `fs/dcache.c:877`. I need to see how `lockref_get_not_dead` interacts with the `lockref` and understand the exact modification occurring in `dentry_kill` at that specific line. I'll be looking for how the `lockref` is managed, specifically its `dead` flag, and how the operations within `dentry_kill` could be racing against the read-validate operation. I'll use `read-file` to pull up and analyze these specific code snippets to pinpoint the exact race condition.
</thought>
  Called tool read-file with args: {"File":"lib/lockref.c","FirstLine":130,"LineCount":40}
  Called tool read-file with args: {"File":"fs/dcache.c","FirstLine":860,"LineCount":40}

[user]:
  Tool read-file returned: {"Contents":" 130:\t */\n 131:\tvoid lockref_mark_dead(struct lockref *lockref)\n 132:\t{\n 133:\t\tassert_spin_locked(\u0026lockref-\u003elock);\n 134:\t\tlockref-\u003ecount = __LOCKREF_DEAD_VAL;\n 135:\t}\n 136:\tEXPORT_SYMBOL(lockref_mark_dead);\n 137:\t\n 138:\t/**\n 139:\t * lockref_get_not_dead - Increments count unless the ref is dead\n 140:\t * @lockref: pointer to lockref structure\n 141:\t * Return: 1 if count updated successfully or 0 if lockref was dead\n 142:\t */\n 143:\tbool lockref_get_not_dead(struct lockref *lockref)\n 144:\t{\n 145:\t\tbool retval = false;\n 146:\t\n 147:\t\tCMPXCHG_LOOP(\n 148:\t\t\tnew.count++;\n 149:\t\t\tif (old.count \u003c 0)\n 150:\t\t\t\treturn false;\n 151:\t\t,\n 152:\t\t\treturn true;\n 153:\t\t);\n 154:\t\n 155:\t\tspin_lock(\u0026lockref-\u003elock);\n 156:\t\tif (lockref-\u003ecount \u003e= 0) {\n 157:\t\t\tlockref-\u003ecount++;\n 158:\t\t\tretval = true;\n 159:\t\t}\n 160:\t\tspin_unlock(\u0026lockref-\u003elock);\n 161:\t\treturn retval;\n 162:\t}\n 163:\tEXPORT_SYMBOL(lockref_get_not_dead);\n"}
  Tool read-file returned: {"Contents":" 860:\t\tthis_cpu_dec(nr_dentry);\n 861:\t\tif (dentry-\u003ed_op \u0026\u0026 dentry-\u003ed_op-\u003ed_release)\n 862:\t\t\tdentry-\u003ed_op-\u003ed_release(dentry);\n 863:\t\n 864:\t\tcond_resched_tasks_rcu_qs();\n 865:\t\t/* now that it's negative, -\u003ed_parent is stable */\n 866:\t\tif (!IS_ROOT(dentry)) {\n 867:\t\t\tparent = dentry-\u003ed_parent;\n 868:\t\t\tspin_lock(\u0026parent-\u003ed_lock);\n 869:\t\t}\n 870:\t\tspin_lock_nested(\u0026dentry-\u003ed_lock, DENTRY_D_LOCK_NESTED);\n 871:\t\tdentry_unlist(dentry);\n 872:\t\tif (dentry-\u003ed_flags \u0026 DCACHE_SHRINK_LIST)\n 873:\t\t\tcan_free = false;\n 874:\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n 875:\t\tif (likely(can_free))\n 876:\t\t\tdentry_free(dentry);\n 877:\t\tif (parent \u0026\u0026 --parent-\u003ed_lockref.count) {\n 878:\t\t\tspin_unlock(\u0026parent-\u003ed_lock);\n 879:\t\t\treturn NULL;\n 880:\t\t}\n 881:\t\treturn parent;\n 882:\t}\n 883:\t\n 884:\t/*\n 885:\t * Decide if dentry is worth retaining.  Usually this is called with dentry\n 886:\t * locked; if not locked, we are more limited and might not be able to tell\n 887:\t * without a lock.  False in this case means \"punt to locked path and recheck\".\n 888:\t *\n 889:\t * In case we aren't locked, these predicates are not \"stable\". However, it is\n 890:\t * sufficient that at some point after we dropped the reference the dentry was\n 891:\t * hashed and the flags had the proper value. Other dentry users may have\n 892:\t * re-gotten a reference to the dentry and change that, but our work is done -\n 893:\t * we can leave the dentry around with a zero refcount.\n 894:\t */\n 895:\tstatic inline bool retain_dentry(struct dentry *dentry, bool locked)\n 896:\t{\n 897:\t\tunsigned int d_flags;\n 898:\t\n 899:\t\tsmp_rmb();\n"}

[model]:
<thought>
**Delving into the Dentry Lifecycle: A Chain of Thought**

My attention is drawn to line 877 in `fs/dcache.c`, specifically the `dentry_kill` function. I'm scrutinizing its behavior, particularly this snippet:

if (parent && --parent->d_lockref.count) {
    spin_unlock(&parent->d_lock);
    return NULL;
}
return parent;

Right there, the critical piece: `parent->d_lockref.count`. This immediately sparks a question in my mind. What is the significance of this `lockref` count in relation to the parent dentry? My intuition tells me it's central to managing the lifecycle and potential destruction of a dentry.

This leads me to consider the broader context. How does this count get managed? What operations increment or decrement it, and under what conditions? My mind immediately jumps to a specific process, task 4498. I recall or infer that this task is involved in a crucial operation: `lockref_get_not_dead(&dentry->d_lockref)`. This operation is called within `__legitimize_path` and `legitimize_path`.

To understand the implications of `lockref_get_not_dead` in relation to `dentry_kill`, I need to trace the flow. I'll therefore turn my attention to `fs/namei.c`, specifically examining lines 870 through 960. My objective is to fully grasp how `legitimize_path` interacts with dentry lock references, how task 4498's actions might affect this count, and how all of this ultimately influences the conditions under which a dentry is killed or kept alive, as dictated by the `dentry_kill` logic. I'm essentially trying to connect the dots between path resolution, dentry lifecycle management, and the atomic operations that ensure data integrity.
</thought>
  Called tool read-file with args: {"File":"fs/namei.c","FirstLine":870,"LineCount":90}

[user]:
  Tool read-file returned: {"Contents":" 870:\t/* path_put is needed afterwards regardless of success or failure */\n 871:\tstatic bool __legitimize_path(struct path *path, unsigned seq, unsigned mseq)\n 872:\t{\n 873:\t\tint res = __legitimize_mnt(path-\u003emnt, mseq);\n 874:\t\tif (unlikely(res)) {\n 875:\t\t\tif (res \u003e 0)\n 876:\t\t\t\tpath-\u003emnt = NULL;\n 877:\t\t\tpath-\u003edentry = NULL;\n 878:\t\t\treturn false;\n 879:\t\t}\n 880:\t\tif (unlikely(!lockref_get_not_dead(\u0026path-\u003edentry-\u003ed_lockref))) {\n 881:\t\t\tpath-\u003edentry = NULL;\n 882:\t\t\treturn false;\n 883:\t\t}\n 884:\t\treturn !read_seqcount_retry(\u0026path-\u003edentry-\u003ed_seq, seq);\n 885:\t}\n 886:\t\n 887:\tstatic inline bool legitimize_path(struct nameidata *nd,\n 888:\t\t\t\t    struct path *path, unsigned seq)\n 889:\t{\n 890:\t\treturn __legitimize_path(path, seq, nd-\u003em_seq);\n 891:\t}\n 892:\t\n 893:\tstatic bool legitimize_links(struct nameidata *nd)\n 894:\t{\n 895:\t\tint i;\n 896:\t\n 897:\t\tVFS_BUG_ON(nd-\u003eflags \u0026 LOOKUP_CACHED);\n 898:\t\n 899:\t\tfor (i = 0; i \u003c nd-\u003edepth; i++) {\n 900:\t\t\tstruct saved *last = nd-\u003estack + i;\n 901:\t\t\tif (unlikely(!legitimize_path(nd, \u0026last-\u003elink, last-\u003eseq))) {\n 902:\t\t\t\tdrop_links(nd);\n 903:\t\t\t\tnd-\u003edepth = i + 1;\n 904:\t\t\t\treturn false;\n 905:\t\t\t}\n 906:\t\t}\n 907:\t\treturn true;\n 908:\t}\n 909:\t\n 910:\tstatic bool legitimize_root(struct nameidata *nd)\n 911:\t{\n 912:\t\t/* Nothing to do if nd-\u003eroot is zero or is managed by the VFS user. */\n 913:\t\tif (!nd-\u003eroot.mnt || (nd-\u003estate \u0026 ND_ROOT_PRESET))\n 914:\t\t\treturn true;\n 915:\t\tnd-\u003estate |= ND_ROOT_GRABBED;\n 916:\t\treturn legitimize_path(nd, \u0026nd-\u003eroot, nd-\u003eroot_seq);\n 917:\t}\n 918:\t\n 919:\t/*\n 920:\t * Path walking has 2 modes, rcu-walk and ref-walk (see\n 921:\t * Documentation/filesystems/path-lookup.txt).  In situations when we can't\n 922:\t * continue in RCU mode, we attempt to drop out of rcu-walk mode and grab\n 923:\t * normal reference counts on dentries and vfsmounts to transition to ref-walk\n 924:\t * mode.  Refcounts are grabbed at the last known good point before rcu-walk\n 925:\t * got stuck, so ref-walk may continue from there. If this is not successful\n 926:\t * (eg. a seqcount has changed), then failure is returned and it's up to caller\n 927:\t * to restart the path walk from the beginning in ref-walk mode.\n 928:\t */\n 929:\t\n 930:\t/**\n 931:\t * try_to_unlazy - try to switch to ref-walk mode.\n 932:\t * @nd: nameidata pathwalk data\n 933:\t * Returns: true on success, false on failure\n 934:\t *\n 935:\t * try_to_unlazy attempts to legitimize the current nd-\u003epath and nd-\u003eroot\n 936:\t * for ref-walk mode.\n 937:\t * Must be called from rcu-walk context.\n 938:\t * Nothing should touch nameidata between try_to_unlazy() failure and\n 939:\t * terminate_walk().\n 940:\t */\n 941:\tstatic bool try_to_unlazy(struct nameidata *nd)\n 942:\t{\n 943:\t\tstruct dentry *parent = nd-\u003epath.dentry;\n 944:\t\n 945:\t\tVFS_BUG_ON(!(nd-\u003eflags \u0026 LOOKUP_RCU));\n 946:\t\n 947:\t\tif (unlikely(nd-\u003eflags \u0026 LOOKUP_CACHED)) {\n 948:\t\t\tdrop_links(nd);\n 949:\t\t\tnd-\u003edepth = 0;\n 950:\t\t\tgoto out1;\n 951:\t\t}\n 952:\t\tif (unlikely(nd-\u003edepth \u0026\u0026 !legitimize_links(nd)))\n 953:\t\t\tgoto out1;\n 954:\t\tif (unlikely(!legitimize_path(nd, \u0026nd-\u003epath, nd-\u003eseq)))\n 955:\t\t\tgoto out;\n 956:\t\tif (unlikely(!legitimize_root(nd)))\n 957:\t\t\tgoto out;\n 958:\t\tleave_rcu(nd);\n 959:\t\tBUG_ON(nd-\u003einode != parent-\u003ed_inode);\n"}

[model]:
<thought>
**Navigating the Lockref Implementation**

My current train of thought is focused on dissecting the `lockref` mechanism, and to do that, I need to dive into the source code. My immediate goal is to examine `lib/lockref.c`. Within this file, I'm particularly interested in understanding precisely how `lockref` is defined – what constitutes its structure and how it's intended to be utilized across the system.

This naturally leads me to scrutinize the definition of `struct lockref` itself. I need to see its constituent members to grasp the underlying data it manages. Simultaneously, I'm keen to understand the implementation of critical constructs like `CMPXCHG_LOOP`. This macro, I suspect, is central to the atomic operations that underpin the `lockref`'s locking behavior, and I want to see its specifics. Beyond that, I'll be reviewing all other associated `lockref` functions to build a comprehensive mental model of how this locking primitive operates, from initialization and locking to unlocking and state checking. My aim is to fully comprehend its mechanics and its role within the broader system architecture.
</thought>
  Called tool codesearch-definition-source with args: {"ContextFile":"lib/lockref.c","Name":"lockref"}

[user]:
  Tool codesearch-definition-source returned: {"SourceCode":"  25:\tstruct lockref {\n  26:\t\tunion {\n  27:\t#if USE_CMPXCHG_LOCKREF\n  28:\t\t\taligned_u64 lock_count;\n  29:\t#endif\n  30:\t\t\tstruct {\n  31:\t\t\t\tspinlock_t lock;\n  32:\t\t\t\tint count;\n  33:\t\t\t};\n  34:\t\t};\n  35:\t};\n","SourceFile":"include/linux/lockref.h"}

[model]:
<thought>
**My Investigative Journey into the `lockref` Race Condition**

I'm digging into a KCSAN report that's pointing to a potential race condition involving the `struct lockref` data structure. My initial step was to dissect the `lockref` definition itself. I see that it's a union, designed to be either an `aligned_u64 lock_count` or a `struct { spinlock_t lock; int count; }`. On my target architecture, x86_64, I know `spinlock_t` (or `arch_spinlock_t`) is 4 bytes and `int count` is also 4 bytes. This means that when they're packed into the `struct`, `lock` will occupy bytes 0-3, and `count` will occupy bytes 4-7. Conveniently, this exactly matches the size and alignment of an 8-byte `aligned_u64`. This is clearly an optimization to allow atomic operations on the entire 8-byte field when `USE_CMPXCHG_LOCKREF` is enabled.

Now, I'm correlating this with the KCSAN report. I see two distinct memory accesses being flagged:

1.  **`read (marked) to 0xffff888105d35800 of 8 bytes by task 4498 on cpu 0: lockref_get_not_dead+0x2f/0x1d0 lib/lockref.c:147`**
    This first access is interesting. It's reading 8 bytes from the base address `0xffff888105d35800`. Given my understanding of `lockref`, this address perfectly corresponds to the beginning of the `lockref` structure, and the 8-byte read strongly suggests it's targeting the entire `aligned_u64 lock_count` field, which encompasses both the `spinlock_t lock` and the `int count`. The fact that this is a read happening within `lockref_get_not_dead` at line 147 of `lib/lockref.c` is my starting point for understanding the intended behavior.

2.  **`read-write to 0xffff888105d35804 of 4 bytes by task 3284 on cpu 1: dentry_kill+0x377/0x4f0 fs/dcache.c:877`**
    This second access is even more telling. It's a read-write operation, not just a read, and it's targeting `0xffff888105d35804` for 4 bytes. Looking back at my `lockref` structure breakdown, offset 4 from the base address is precisely where the `int count` member resides. This operation is happening within `dentry_kill` in `fs/dcache.c`. The fact that this is a read-write on just the `count` field, while another thread is potentially reading or manipulating the entire 8-byte `lock_count` (which includes the spinlock), is the core of the potential race condition I need to investigate.

My next logical step is to dive deep into `lib/lockref.c` to understand the `CMPXCHG_LOOP` mechanism and the precise logic within `lockref_get_not_dead`. I need to see how these atomic operations are intended to work and how the simultaneous access to different parts of the `lockref` union, one reading the whole 8 bytes and the other writing to a 4-byte portion, could lead to a data corruption or a missed update. This is where the true nature of the race will be revealed.
</thought>
  Called tool read-file with args: {"File":"lib/lockref.c","FirstLine":1,"LineCount":80}

[user]:
  Tool read-file returned: {"Contents":"   1:\t// SPDX-License-Identifier: GPL-2.0\n   2:\t#include \u003clinux/export.h\u003e\n   3:\t#include \u003clinux/lockref.h\u003e\n   4:\t\n   5:\t#if USE_CMPXCHG_LOCKREF\n   6:\t\n   7:\t/*\n   8:\t * Note that the \"cmpxchg()\" reloads the \"old\" value for the\n   9:\t * failure case.\n  10:\t */\n  11:\t#define CMPXCHG_LOOP(CODE, SUCCESS) do {\t\t\t\t\t\\\n  12:\t\tint retry = 100;\t\t\t\t\t\t\t\\\n  13:\t\tstruct lockref old;\t\t\t\t\t\t\t\\\n  14:\t\tBUILD_BUG_ON(sizeof(old) != 8);\t\t\t\t\t\t\\\n  15:\t\told.lock_count = READ_ONCE(lockref-\u003elock_count);\t\t\t\\\n  16:\t\twhile (likely(arch_spin_value_unlocked(old.lock.rlock.raw_lock))) {  \t\\\n  17:\t\t\tstruct lockref new = old;\t\t\t\t\t\\\n  18:\t\t\tCODE\t\t\t\t\t\t\t\t\\\n  19:\t\t\tif (likely(try_cmpxchg64_relaxed(\u0026lockref-\u003elock_count,\t\t\\\n  20:\t\t\t\t\t\t\t \u0026old.lock_count,\t\t\\\n  21:\t\t\t\t\t\t\t new.lock_count))) {\t\t\\\n  22:\t\t\t\tSUCCESS;\t\t\t\t\t\t\\\n  23:\t\t\t}\t\t\t\t\t\t\t\t\\\n  24:\t\t\tif (!--retry)\t\t\t\t\t\t\t\\\n  25:\t\t\t\tbreak;\t\t\t\t\t\t\t\\\n  26:\t\t}\t\t\t\t\t\t\t\t\t\\\n  27:\t} while (0)\n  28:\t\n  29:\t#else\n  30:\t\n  31:\t#define CMPXCHG_LOOP(CODE, SUCCESS) do { } while (0)\n  32:\t\n  33:\t#endif\n  34:\t\n  35:\t/**\n  36:\t * lockref_get - Increments reference count unconditionally\n  37:\t * @lockref: pointer to lockref structure\n  38:\t *\n  39:\t * This operation is only valid if you already hold a reference\n  40:\t * to the object, so you know the count cannot be zero.\n  41:\t */\n  42:\tvoid lockref_get(struct lockref *lockref)\n  43:\t{\n  44:\t\tCMPXCHG_LOOP(\n  45:\t\t\tnew.count++;\n  46:\t\t,\n  47:\t\t\treturn;\n  48:\t\t);\n  49:\t\n  50:\t\tspin_lock(\u0026lockref-\u003elock);\n  51:\t\tlockref-\u003ecount++;\n  52:\t\tspin_unlock(\u0026lockref-\u003elock);\n  53:\t}\n  54:\tEXPORT_SYMBOL(lockref_get);\n  55:\t\n  56:\t/**\n  57:\t * lockref_get_not_zero - Increments count unless the count is 0 or dead\n  58:\t * @lockref: pointer to lockref structure\n  59:\t * Return: 1 if count updated successfully or 0 if count was zero\n  60:\t */\n  61:\tbool lockref_get_not_zero(struct lockref *lockref)\n  62:\t{\n  63:\t\tbool retval = false;\n  64:\t\n  65:\t\tCMPXCHG_LOOP(\n  66:\t\t\tnew.count++;\n  67:\t\t\tif (old.count \u003c= 0)\n  68:\t\t\t\treturn false;\n  69:\t\t,\n  70:\t\t\treturn true;\n  71:\t\t);\n  72:\t\n  73:\t\tspin_lock(\u0026lockref-\u003elock);\n  74:\t\tif (lockref-\u003ecount \u003e 0) {\n  75:\t\t\tlockref-\u003ecount++;\n  76:\t\t\tretval = true;\n  77:\t\t}\n  78:\t\tspin_unlock(\u0026lockref-\u003elock);\n  79:\t\treturn retval;\n  80:\t}\n"}

[model]:
<thought>
**My Exploration of `CMPXCHG_LOOP` and its Implications**

As I delve into the `CMPXCHG_LOOP` macro, my initial focus is on its core mechanism: a spin loop employing compare-and-swap (CAS) for atomic updates to a `lockref` structure. I notice the `BUILD_BUG_ON(sizeof(old) != 8)` which immediately tells me we're dealing with 64-bit atomic operations, a critical detail for performance and correctness.

Then, my attention is drawn to this line within the macro: `old.lock_count = READ_ONCE(lockref->lock_count);`. This seems straightforward enough – it's reading the current lock state before attempting an update. However, my mind immediately flags this as a potential point of interest, especially when I see it's part of a larger operation that will ultimately be placed at line 147 in `lib/lockref.c`, specifically within the `lockref_get_not_dead` function.

The fact that this `READ_ONCE` operation is associated with a 8-byte read at a specific memory address (0xffff888105d35800) in the context of `lockref_get_not_dead` makes me pause. This function is about acquiring a reference to a lock-protected object without encountering deadlocks, and `READ_ONCE` suggests a relaxed memory ordering. This is fine for the initial read, but I'm keenly aware of the potential for races if subsequent operations aren't properly synchronized.

My thought process then jumps to a specific call site: task 3284 in `dentry_kill` at `fs/dcache.c:877`. I'm looking at the line `if (parent && --parent->d_lockref.count) {`. Here, I see `parent->d_lockref.count` being decremented. This `count` is part of the `d_lockref` structure.

Connecting the dots, I realize that `parent->d_lockref.count` is very likely the same `lock_count` field that `CMPXCHG_LOOP` is operating on. If `dentry_kill` is about to decrement this count, and `lockref_get_not_dead` is potentially reading it within the `CMPXCHG_LOOP` macro, I'm concerned about a race condition. Specifically, if `dentry_kill` decrements the count while `lockref_get_not_dead` is inside the `CMPXCHG_LOOP` and has just read the value via `READ_ONCE`, the subsequent `try_cmpxchg64_relaxed` could fail unexpectedly, or worse, lead to incorrect state management if the decrement isn't properly coordinated with the CAS.

My focus then shifts back to the `dentry_kill` function itself, specifically examining the code around lines 865 to 900 in `fs/dcache.c`. I need to understand the precise logic for how `dentry_kill` interacts with the `d_lockref.count`. Is this decrement happening before or after a potential CAS operation? Is there any other synchronization mechanism in place that might mitigate the risk I'm seeing? My goal is to ensure that the relaxed read of `lock_count` by `CMPXCHG_LOOP` (when invoked by `lockref_get_not_dead`) doesn't interfere with or get invalidated by the decrement operation in `dentry_kill`.
</thought>
  Called tool read-file with args: {"File":"fs/dcache.c","FirstLine":850,"LineCount":40}

[user]:
  Tool read-file returned: {"Contents":" 850:\t\tif (dentry-\u003ed_flags \u0026 DCACHE_LRU_LIST) {\n 851:\t\t\tif (!(dentry-\u003ed_flags \u0026 DCACHE_SHRINK_LIST))\n 852:\t\t\t\td_lru_del(dentry);\n 853:\t\t}\n 854:\t\t/* if it was on the hash then remove it */\n 855:\t\t__d_drop(dentry);\n 856:\t\tif (dentry-\u003ed_inode)\n 857:\t\t\tdentry_unlink_inode(dentry);\n 858:\t\telse\n 859:\t\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n 860:\t\tthis_cpu_dec(nr_dentry);\n 861:\t\tif (dentry-\u003ed_op \u0026\u0026 dentry-\u003ed_op-\u003ed_release)\n 862:\t\t\tdentry-\u003ed_op-\u003ed_release(dentry);\n 863:\t\n 864:\t\tcond_resched_tasks_rcu_qs();\n 865:\t\t/* now that it's negative, -\u003ed_parent is stable */\n 866:\t\tif (!IS_ROOT(dentry)) {\n 867:\t\t\tparent = dentry-\u003ed_parent;\n 868:\t\t\tspin_lock(\u0026parent-\u003ed_lock);\n 869:\t\t}\n 870:\t\tspin_lock_nested(\u0026dentry-\u003ed_lock, DENTRY_D_LOCK_NESTED);\n 871:\t\tdentry_unlist(dentry);\n 872:\t\tif (dentry-\u003ed_flags \u0026 DCACHE_SHRINK_LIST)\n 873:\t\t\tcan_free = false;\n 874:\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n 875:\t\tif (likely(can_free))\n 876:\t\t\tdentry_free(dentry);\n 877:\t\tif (parent \u0026\u0026 --parent-\u003ed_lockref.count) {\n 878:\t\t\tspin_unlock(\u0026parent-\u003ed_lock);\n 879:\t\t\treturn NULL;\n 880:\t\t}\n 881:\t\treturn parent;\n 882:\t}\n 883:\t\n 884:\t/*\n 885:\t * Decide if dentry is worth retaining.  Usually this is called with dentry\n 886:\t * locked; if not locked, we are more limited and might not be able to tell\n 887:\t * without a lock.  False in this case means \"punt to locked path and recheck\".\n 888:\t *\n 889:\t * In case we aren't locked, these predicates are not \"stable\". However, it is\n"}

[model]:
<thought>
**Initial Musings on `dentry_kill` and `d_lockref`**

My attention is immediately drawn to the `d_lockref.count` field within the `dentry_kill` function. A quick glance reveals a seemingly innocuous decrement operation: `--parent->d_lockref.count`. This immediately sparks a question: how exactly does this `lockref` mechanism function, and what are the implications of this decrement in the context of `dentry_kill`?

I find myself pondering the sequence of operations in `dentry_kill`. The code first checks `!IS_ROOT(dentry)`. If this condition holds, it retrieves the `parent` dentry and acquires its lock: `spin_lock(&parent->d_lock)`. Following this, it performs the decrement: `if (parent && --parent->d_lockref.count)`. The subsequent conditional branch, `spin_unlock(&parent->d_lock); return NULL;`, suggests that the `d_lockref.count` plays a crucial role in determining whether the parent's lock should be released immediately or if some other path should be taken. This interaction, particularly the decrement and subsequent conditional unlock, is the core of my current curiosity.

To fully grasp the behavior and potential ramifications, I need to understand the `lockref` mechanism itself. What is its purpose? How is it initialized? And, most importantly, how is it manipulated elsewhere in the codebase? My immediate next step is to explore other instances where `d_lockref` is modified or checked. Specifically, I'll be looking for other places in `fs/dcache.c` where `d_lockref` is decremented or incremented, or where its value is otherwise directly acted upon. A `grep` for `d_lockref` across `fs/dcache.c` seems like the most efficient way to locate these relevant sections of code and build a more complete picture of its lifecycle and usage.
</thought>
  Called tool grepper with args: {"Expression":"d_lockref","PathPrefixes":["fs/dcache.c"]}

[user]:
  Tool grepper returned: {"Output":"fs/dcache.c=453=static void dentry_free(struct dentry *dentry)\n--\nfs/dcache.c-455-\tDENTRY_WARN_ONCE(d_really_is_positive(dentry), dentry);\nfs/dcache.c:456:\tDENTRY_WARN_ONCE(!lockref_is_dead(\u0026dentry-\u003ed_lockref), dentry);\nfs/dcache.c-457-\tD_FLAG_VERIFY(dentry, 0);\n--\nfs/dcache.c=756=static bool lock_for_kill(struct dentry *dentry)\n--\nfs/dcache.c-759-\nfs/dcache.c:760:\tif (unlikely(dentry-\u003ed_lockref.count)) {\nfs/dcache.c-761-\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n--\nfs/dcache.c-783-\trcu_read_unlock();\nfs/dcache.c:784:\tif (likely(!dentry-\u003ed_lockref.count))\nfs/dcache.c-785-\t\treturn true;\n--\nfs/dcache.c=830=static struct dentry *dentry_kill(struct dentry *dentry)\n--\nfs/dcache.c-840-\t */\nfs/dcache.c:841:\tlockref_mark_dead(\u0026dentry-\u003ed_lockref);\nfs/dcache.c-842-\n--\nfs/dcache.c-876-\t\tdentry_free(dentry);\nfs/dcache.c:877:\tif (parent \u0026\u0026 --parent-\u003ed_lockref.count) {\nfs/dcache.c-878-\t\tspin_unlock(\u0026parent-\u003ed_lock);\n--\nfs/dcache.c=960=static inline bool fast_dput(struct dentry *dentry)\n--\nfs/dcache.c-969-\trcu_read_lock();\nfs/dcache.c:970:\tret = lockref_put_return(\u0026dentry-\u003ed_lockref);\nfs/dcache.c-971-\n--\nfs/dcache.c-979-\t\trcu_read_unlock();\nfs/dcache.c:980:\t\tif (WARN_ON_ONCE(lockref_is_dead_or_zero(\u0026dentry-\u003ed_lockref))) {\nfs/dcache.c-981-\t\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n--\nfs/dcache.c-983-\t\t}\nfs/dcache.c:984:\t\tdentry-\u003ed_lockref.count--;\nfs/dcache.c-985-\t\tgoto locked;\n--\nfs/dcache.c-1021-locked:\nfs/dcache.c:1022:\tif (dentry-\u003ed_lockref.count || retain_dentry(dentry, true)) {\nfs/dcache.c-1023-\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n--\nfs/dcache.c=1077=void d_make_discardable(struct dentry *dentry)\n--\nfs/dcache.c-1081-\tdentry-\u003ed_flags \u0026= ~DCACHE_PERSISTENT;\nfs/dcache.c:1082:\tdentry-\u003ed_lockref.count--;\nfs/dcache.c-1083-\tfinish_dput(dentry);\n--\nfs/dcache.c=1105=__must_hold(\u0026dentry-\u003ed_lock)\nfs/dcache.c-1106-{\nfs/dcache.c:1107:\tif (likely(!dentry-\u003ed_lockref.count \u0026\u0026\nfs/dcache.c-1108-\t    !(dentry-\u003ed_flags \u0026 DCACHE_SHRINK_LIST))) {\n--\nfs/dcache.c=1137=struct dentry *dget_parent(struct dentry *dentry)\n--\nfs/dcache.c-1149-\tret = READ_ONCE(dentry-\u003ed_parent);\nfs/dcache.c:1150:\tgotref = lockref_get_not_zero(\u0026ret-\u003ed_lockref);\nfs/dcache.c-1151-\trcu_read_unlock();\n--\nfs/dcache.c-1171-\trcu_read_unlock();\nfs/dcache.c:1172:\tBUG_ON(!ret-\u003ed_lockref.count);\nfs/dcache.c:1173:\tret-\u003ed_lockref.count++;\nfs/dcache.c-1174-\tspin_unlock(\u0026ret-\u003ed_lock);\n--\nfs/dcache.c=1182=static struct dentry * __d_find_dir_alias(struct inode *inode)\n--\nfs/dcache.c-1188-\talias = hlist_entry(inode-\u003ei_dentry.first, struct dentry, d_alias);\nfs/dcache.c:1189:\tlockref_get(\u0026alias-\u003ed_lockref);\nfs/dcache.c-1190-\treturn alias;\n--\nfs/dcache.c=1339=static enum lru_status dentry_lru_isolate(struct list_head *item,\n--\nfs/dcache.c-1358-\t */\nfs/dcache.c:1359:\tif (dentry-\u003ed_lockref.count) {\nfs/dcache.c-1360-\t\td_lru_isolate(lru, dentry);\n--\nfs/dcache.c=1688=static enum d_walk_ret select_collect(void *_data, struct dentry *dentry)\n--\nfs/dcache.c-1695-\nfs/dcache.c:1696:\tif (lockref_is_dead_or_zero(\u0026dentry-\u003ed_lockref)) {\nfs/dcache.c-1697-\t\t__move_to_shrink_list(dentry, \u0026data-\u003edispose);\n--\nfs/dcache.c=1711=static enum d_walk_ret select_collect_umount(void *_data, struct dentry *dentry)\n--\nfs/dcache.c-1714-\t\tdentry-\u003ed_flags \u0026= ~DCACHE_PERSISTENT;\nfs/dcache.c:1715:\t\tdentry-\u003ed_lockref.count--;\nfs/dcache.c-1716-\t}\n--\nfs/dcache.c=1720=static enum d_walk_ret select_collect2(void *_data, struct dentry *dentry)\n--\nfs/dcache.c-1727-\nfs/dcache.c:1728:\tif (lockref_is_dead_or_zero(\u0026dentry-\u003ed_lockref)) {\nfs/dcache.c-1729-\t\tif (!__move_to_shrink_list(dentry, \u0026data-\u003edispose)) {\n--\nfs/dcache.c=1762=static void shrink_dcache_tree(struct dentry *parent, bool for_umount)\n--\nfs/dcache.c-1798-\nfs/dcache.c:1799:\t\t\tif (unlikely(lockref_is_dead(\u0026v-\u003ed_lockref))) {\nfs/dcache.c-1800-\t\t\t\t// It's doomed; if it isn't dead yet, notify us\n--\nfs/dcache.c=1820=static enum d_walk_ret umount_check(void *_data, struct dentry *dentry)\n--\nfs/dcache.c-1826-\t/* root with refcount 1 is fine */\nfs/dcache.c:1827:\tif (dentry == _data \u0026\u0026 dentry-\u003ed_lockref.count == 1)\nfs/dcache.c-1828-\t\treturn D_WALK_CONTINUE;\n--\nfs/dcache.c-1835-\t\t       dentry,\nfs/dcache.c:1836:\t\t       dentry-\u003ed_lockref.count,\nfs/dcache.c-1837-\t\t       dentry-\u003ed_sb-\u003es_type-\u003ename,\n--\nfs/dcache.c=1842=static void do_one_tree(struct dentry *dentry)\n--\nfs/dcache.c-1852-\t */\nfs/dcache.c:1853:\tif (unlikely(dentry-\u003ed_lockref.count \u003e 1 \u0026\u0026\nfs/dcache.c-1854-\t\t     !hlist_unhashed(\u0026dentry-\u003ed_sib)))\n--\nfs/dcache.c=1863=void shrink_dcache_for_umount(struct super_block *sb)\n--\nfs/dcache.c-1884-\t\trcu_read_unlock();\nfs/dcache.c:1885:\t\tif (unlikely(lockref_is_dead(\u0026dentry-\u003ed_lockref))) {\nfs/dcache.c-1886-\t\t\tstruct completion_list wait;\n--\nfs/dcache.c=1961=static struct dentry *__d_alloc(struct super_block *sb, const struct qstr *name)\n--\nfs/dcache.c-2009-\tdentry-\u003ed_flags = 0;\nfs/dcache.c:2010:\tlockref_init(\u0026dentry-\u003ed_lockref);\nfs/dcache.c-2011-\tseqcount_spinlock_init(\u0026dentry-\u003ed_seq, \u0026dentry-\u003ed_lock);\n--\nfs/dcache.c=2706=struct dentry *__d_lookup(const struct dentry *parent, const struct qstr *name)\n--\nfs/dcache.c-2749-\nfs/dcache.c:2750:\t\tdentry-\u003ed_lockref.count++;\nfs/dcache.c-2751-\t\tfound = dentry;\n--\nfs/dcache.c=2806=void d_delete(struct dentry * dentry)\n--\nfs/dcache.c-2814-\t */\nfs/dcache.c:2815:\tif (dentry-\u003ed_lockref.count == 1) {\nfs/dcache.c-2816-\t\tif (dentry_negative_policy)\n--\nfs/dcache.c=2894=struct dentry *__d_alloc_parallel(struct dentry *parent,\n--\nfs/dcache.c-2921-\tif (unlikely(dentry)) {\nfs/dcache.c:2922:\t\tif (!lockref_get_not_dead(\u0026dentry-\u003ed_lockref)) {\nfs/dcache.c-2923-\t\t\trcu_read_unlock();\n--\nfs/dcache.c-2964-\t\t/* now we can try to grab a reference */\nfs/dcache.c:2965:\t\tif (unlikely(lockref_is_dead(\u0026dentry-\u003ed_lockref))) {\nfs/dcache.c-2966-\t\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n--\nfs/dcache.c=3255=static void __d_move(struct dentry *dentry, struct dentry *target,\n--\nfs/dcache.c-3305-\t\ttarget-\u003ed_hash.pprev = NULL;\nfs/dcache.c:3306:\t\tdentry-\u003ed_parent-\u003ed_lockref.count++;\nfs/dcache.c-3307-\t\tif (dentry != old_parent) /* wasn't IS_ROOT */\nfs/dcache.c:3308:\t\t\tWARN_ON(!--old_parent-\u003ed_lockref.count);\nfs/dcache.c-3309-\t} else {\n"}

[model]:
<thought>
**A Subtle Race Condition in `dentry_kill` and `lockref_get_not_dead`**

I've been digging into `fs/dcache.c`, specifically lines 866-882, which deal with unlinking and freeing dentries. My initial focus was on how `dentry_kill` manages the parent directory's lock reference count. I noticed that after unlinking the dentry and potentially freeing it, the code checks `if (parent && --parent->d_lockref.count)`. This line decrement `parent->d_lockref.count` and then checks its value.

My immediate concern arose from the fact that `spin_lock(&parent->d_lock)` is held *before* this decrement. This implies that `parent->d_lockref.count` is being modified while the spinlock protecting it is held by the current task. This seems safe from other threads *also* trying to acquire `parent->d_lock`.

However, then I remembered `lockref_get_not_dead`. I started thinking about what happens if another thread is *simultaneously* trying to increment or read this `d_lockref.count` in a different way. This is where KCSAN's report of a race condition caught my attention. KCSAN flagged a read on `lockref->lock_count` by `lockref_get_not_dead` (task 4498) and a read-write (the `--` operation) on `parent->d_lockref.count` by `dentry_kill` (task 3284).

My confusion stemmed from the fact that `dentry_kill` *was* holding `parent->d_lock`. How could a read from `lockref_get_not_dead` race with a write happening *under* a held lock?

I then looked closely at `lockref_get_not_dead` in `lib/lockref.c`. The core of this function is a `CMPXCHG_LOOP`. The very first operation within this loop is `old.lock_count = READ_ONCE(lockref->lock_count);`. This `READ_ONCE` is a marked, atomic read.

The critical insight came when I realized the context of task 4498. It's in the process of an `unlink` operation, specifically calling `filename_unlinkat`, which means it's trying to find the parent directory of the dentry being unlinked. So, task 4498 is effectively trying to legitimize the path to the parent of the dentry that task 3284 is in the process of killing.

The race, as identified by KCSAN, is that task 3284 is holding `parent->d_lock` and performing a *plain*, non-atomic decrement (`--parent->d_lockref.count`). Meanwhile, task 4498, *without holding `parent->d_lock`*, performs a `READ_ONCE(lockref->lock_count)`.

The apparent contradiction is resolved by understanding KCSAN's rules and the C semantics of `READ_ONCE`. KCSAN flags a marked read (`READ_ONCE`) racing with an unmarked write (`--count`) as a data race. This is because even though `parent->d_lock` is held by task 3284, the specific access to `parent->d_lockref.count` by task 3284 is a *plain* write. The `CMPXCHG_LOOP` in `lockref_get_not_dead` includes a check `arch_spin_value_unlocked(old.lock.rlock.raw_lock)`. When task 3284 holds `parent->d_lock`, this spinlock is indeed locked. However, `lockref_get_not_dead` is designed to *attempt* an atomic operation using `try_cmpxchg64_relaxed` *before* acquiring the spinlock, and the `READ_ONCE` is part of that initial attempt.

So, task 4498 reads `lockref->lock_count` at a point where task 3284 is about to perform a non-atomic decrement on `lockref->count`. Even though the spinlock *is* held by task 3284, the `READ_ONCE` in task 4498 is an access to a field that KCSAN considers "unprotected" in the context of the unmarked write by task 3284. This is because the `CMPXCHG_LOOP`'s logic aims to avoid acquiring the spinlock if a pure atomic operation can succeed, and the `READ_ONCE` is part of that initial atomic attempt. The plain `--count` is a non-atomic operation that KCSAN sees as potentially racy with marked reads, as it doesn't guarantee visibility or atomicity in the same way a `cmpxchg` would. The core issue is that a marked read (`READ_ONCE`) is happening concurrently with an unmarked read-modify-write (`--`), and the unmarked operation is not inherently synchronized with the marked read's perspective.
</thought>
  Called tool read-file with args: {"File":"include/linux/lockref.h","FirstLine":1,"LineCount":80}

[user]:
  Tool read-file returned: {"Contents":"   1:\t/* SPDX-License-Identifier: GPL-2.0 */\n   2:\t#ifndef __LINUX_LOCKREF_H\n   3:\t#define __LINUX_LOCKREF_H\n   4:\t\n   5:\t/*\n   6:\t * Locked reference counts.\n   7:\t *\n   8:\t * These are different from just plain atomic refcounts in that they\n   9:\t * are atomic with respect to the spinlock that goes with them.  In\n  10:\t * particular, there can be implementations that don't actually get\n  11:\t * the spinlock for the common decrement/increment operations, but they\n  12:\t * still have to check that the operation is done semantically as if\n  13:\t * the spinlock had been taken (using a cmpxchg operation that covers\n  14:\t * both the lock and the count word, or using memory transactions, for\n  15:\t * example).\n  16:\t */\n  17:\t\n  18:\t#include \u003clinux/spinlock.h\u003e\n  19:\t#include \u003cgenerated/bounds.h\u003e\n  20:\t\n  21:\t#define USE_CMPXCHG_LOCKREF \\\n  22:\t\t(IS_ENABLED(CONFIG_ARCH_USE_CMPXCHG_LOCKREF) \u0026\u0026 \\\n  23:\t\t IS_ENABLED(CONFIG_SMP) \u0026\u0026 SPINLOCK_SIZE \u003c= 4)\n  24:\t\n  25:\tstruct lockref {\n  26:\t\tunion {\n  27:\t#if USE_CMPXCHG_LOCKREF\n  28:\t\t\taligned_u64 lock_count;\n  29:\t#endif\n  30:\t\t\tstruct {\n  31:\t\t\t\tspinlock_t lock;\n  32:\t\t\t\tint count;\n  33:\t\t\t};\n  34:\t\t};\n  35:\t};\n  36:\t\n  37:\t#define __LOCKREF_DEAD_VAL\t-128\n  38:\t\n  39:\t/**\n  40:\t * lockref_init - Initialize a lockref\n  41:\t * @lockref: pointer to lockref structure\n  42:\t *\n  43:\t * Initializes @lockref-\u003ecount to 1.\n  44:\t */\n  45:\tstatic inline void lockref_init(struct lockref *lockref)\n  46:\t{\n  47:\t\tspin_lock_init(\u0026lockref-\u003elock);\n  48:\t\tlockref-\u003ecount = 1;\n  49:\t}\n  50:\t\n  51:\tvoid lockref_get(struct lockref *lockref);\n  52:\tint lockref_put_return(struct lockref *lockref);\n  53:\tbool lockref_get_not_zero(struct lockref *lockref);\n  54:\tbool lockref_put_or_lock(struct lockref *lockref) __cond_acquires(false, \u0026lockref-\u003elock);\n  55:\t\n  56:\tvoid lockref_mark_dead(struct lockref *lockref);\n  57:\tbool lockref_get_not_dead(struct lockref *lockref);\n  58:\t\n  59:\t/* Must be called under spinlock for reliable results */\n  60:\tstatic inline bool lockref_is_dead(const struct lockref *l)\n  61:\t{\n  62:\t\treturn (READ_ONCE(l-\u003ecount) == __LOCKREF_DEAD_VAL);\n  63:\t}\n  64:\t\n  65:\tstatic inline bool lockref_is_dead_or_zero(const struct lockref *l)\n  66:\t{\n  67:\t\tint count = READ_ONCE(l-\u003ecount);\n  68:\t\treturn (count == __LOCKREF_DEAD_VAL || count == 0);\n  69:\t}\n  70:\t\n  71:\t#endif /* __LINUX_LOCKREF_H */\n"}

[model]:
<thought>
**Deconstructing `lockref`'s Behavior: A Deep Dive into Concurrency and Read Integrity**

My thought process began by drilling down into the specifics of the `lockref` implementation, specifically within `include/linux/lockref.h`. I immediately focused on lines 59 through 69, examining the `lockref_is_dead` and `lockref_is_dead_or_zero` functions.

What struck me most prominently was the repeated use of `READ_ONCE(l->count)` in both these functions. This immediately raised a question in my mind: why is `READ_ONCE` necessary here, especially in `lockref_is_dead`? The answer, as I quickly surmised, is due to the potential for concurrent access. If `l->count` were to be read without this mechanism, there's a risk of encountering a stale or partially updated value, which would render the "dead" status check unreliable. The use of `READ_ONCE` is a clear indicator that the `count` field within the `lockref` structure can be modified by other threads or contexts, and thus, any read operation needs to be atomic and provide a consistent snapshot.

Following this observation, my next step was to broaden my investigation. I decided to thoroughly analyze the entire `lib/lockref.c` file. My primary goal was to understand the scope of operations performed by this module and to identify how the `lockref` structure, and specifically its `count` field, is managed throughout the codebase. I wanted to see all the functions defined within `lib/lockref.c` to get a comprehensive picture of its functionality and to ensure that my understanding of `READ_ONCE`'s necessity was indeed grounded in the actual usage patterns within the lockref subsystem.
</thought>
  Called tool read-file with args: {"File":"lib/lockref.c","FirstLine":80,"LineCount":80}

[user]:
  Tool read-file returned: {"Contents":"  80:\t}\n  81:\tEXPORT_SYMBOL(lockref_get_not_zero);\n  82:\t\n  83:\t/**\n  84:\t * lockref_put_return - Decrement reference count if possible\n  85:\t * @lockref: pointer to lockref structure\n  86:\t *\n  87:\t * Decrement the reference count and return the new value.\n  88:\t * If the lockref was dead or locked, return -1.\n  89:\t */\n  90:\tint lockref_put_return(struct lockref *lockref)\n  91:\t{\n  92:\t\tCMPXCHG_LOOP(\n  93:\t\t\tnew.count--;\n  94:\t\t\tif (old.count \u003c= 0)\n  95:\t\t\t\treturn -1;\n  96:\t\t,\n  97:\t\t\treturn new.count;\n  98:\t\t);\n  99:\t\treturn -1;\n 100:\t}\n 101:\tEXPORT_SYMBOL(lockref_put_return);\n 102:\t\n 103:\t/**\n 104:\t * lockref_put_or_lock - decrements count unless count \u003c= 1 before decrement\n 105:\t * @lockref: pointer to lockref structure\n 106:\t * Return: 1 if count updated successfully or 0 if count \u003c= 1 and lock taken\n 107:\t */\n 108:\tbool lockref_put_or_lock(struct lockref *lockref)\n 109:\t{\n 110:\t\tCMPXCHG_LOOP(\n 111:\t\t\tnew.count--;\n 112:\t\t\tif (old.count \u003c= 1)\n 113:\t\t\t\tbreak;\n 114:\t\t,\n 115:\t\t\treturn true;\n 116:\t\t);\n 117:\t\n 118:\t\tspin_lock(\u0026lockref-\u003elock);\n 119:\t\tif (lockref-\u003ecount \u003c= 1)\n 120:\t\t\treturn false;\n 121:\t\tlockref-\u003ecount--;\n 122:\t\tspin_unlock(\u0026lockref-\u003elock);\n 123:\t\treturn true;\n 124:\t}\n 125:\tEXPORT_SYMBOL(lockref_put_or_lock);\n 126:\t\n 127:\t/**\n 128:\t * lockref_mark_dead - mark lockref dead\n 129:\t * @lockref: pointer to lockref structure\n 130:\t */\n 131:\tvoid lockref_mark_dead(struct lockref *lockref)\n 132:\t{\n 133:\t\tassert_spin_locked(\u0026lockref-\u003elock);\n 134:\t\tlockref-\u003ecount = __LOCKREF_DEAD_VAL;\n 135:\t}\n 136:\tEXPORT_SYMBOL(lockref_mark_dead);\n 137:\t\n 138:\t/**\n 139:\t * lockref_get_not_dead - Increments count unless the ref is dead\n 140:\t * @lockref: pointer to lockref structure\n 141:\t * Return: 1 if count updated successfully or 0 if lockref was dead\n 142:\t */\n 143:\tbool lockref_get_not_dead(struct lockref *lockref)\n 144:\t{\n 145:\t\tbool retval = false;\n 146:\t\n 147:\t\tCMPXCHG_LOOP(\n 148:\t\t\tnew.count++;\n 149:\t\t\tif (old.count \u003c 0)\n 150:\t\t\t\treturn false;\n 151:\t\t,\n 152:\t\t\treturn true;\n 153:\t\t);\n 154:\t\n 155:\t\tspin_lock(\u0026lockref-\u003elock);\n 156:\t\tif (lockref-\u003ecount \u003e= 0) {\n 157:\t\t\tlockref-\u003ecount++;\n 158:\t\t\tretval = true;\n 159:\t\t}\n"}

[model]:
<thought>
**Investigating a Potential Data Race in Dentry Lifetime Management**

I've been digging into a KCSAN report concerning a data race between `dentry_kill` and `lockref_get_not_dead` (which is called indirectly via `try_to_unlazy` and `legitimize_path`). The race is reported on the `lockref->lock_count` field of a parent dentry.

My initial thought process was to meticulously examine the functions involved and how they interact, particularly around the `lockref` structure and its spinlock.

I started by looking at the core `lockref` operations:
*   `lockref_mark_dead`: This simply sets the count to a "dead" value while holding the spinlock. Straightforward enough.
*   `lockref_put_or_lock`: Decrements the count if it's greater than 1, under the spinlock.
*   `lockref_get`: Increments the count, under the spinlock.
*   `lockref_get_not_dead`: This is where things get interesting. It acquires the spinlock, checks if the count is non-negative, increments if so, and then releases the lock. This function is designed to be used when a lock might not be held, but we want to ensure the refcount is valid.

Then, I turned my attention to `CMPXCHG_LOOP`, a macro that appears to be designed for lock-free updates using `try_cmpxchg64_relaxed`. It reads the `lock_count` (8 bytes, comprising `lock` and `count`), attempts a CAS operation on the entire 8-byte value, and retries if it fails or if the spinlock `old.lock.rlock.raw_lock` is not unlocked. This is crucial because `lockref->lock_count` is an aggregate of the spinlock state and the reference count.

Next, I analyzed `dentry_kill`. The key sequence I observed was:
1.  Acquiring the parent's `d_lock` if the dentry isn't a root.
2.  Acquiring the dentry's own `d_lock` (nested).
3.  Unlisting the dentry.
4.  Potentially freeing the dentry.
5.  Crucially, `if (parent && --parent->d_lockref.count)`: This is where the parent's reference count is decremented. If it becomes zero, the parent's lock is released.

This is where I started to form a specific concern. Task 3284 in `dentry_kill` holds `parent->d_lock`. At the same time, task 4498 is potentially in `lockref_get_not_dead`, which operates on `path->dentry->d_lockref` (which could be the same `parent->d_lockref`).

My thought process went: "If task 3284 holds `parent->d_lock`, it means `parent->d_lockref.lock` is locked. What does task 4498 see when it tries to operate on `parent->d_lockref`?"

I then traced the execution of task 4498 using `lockref_get_not_dead` concurrently with task 3284 in `dentry_kill`.

The specific sequence that worried me was:
*   Task 3284: `spin_lock(&parent->d_lock);` This acquires the spinlock.
*   Task 3284: `--parent->d_lockref.count;` This is a read-modify-write operation on the 4-byte `count` field.
*   Task 4498: `lockref_get_not_dead` reads `lockref->lock_count` using `READ_ONCE`. This is an 8-byte read.

My immediate concern was about the atomicity of these operations. On x86-64, an 8-byte aligned read is atomic at the hardware level. However, the `--parent->d_lockref.count` is a 4-byte read-modify-write that is *not* atomic in a single instruction. It typically involves loading the 4-byte value, decrementing it, and then storing it back.

This led to a critical question: "What if task 4498 reads `parent->d_lockref.lock_count` (the 8-byte combined value) *while* task 3284 is in the middle of its `--parent->d_lockref.count` operation?" This would be reading across the boundary of the lock state and the count, potentially observing an inconsistent state.

I also pondered why task 4498's `spin_lock(&lockref->lock)` inside `lockref_get_not_dead` didn't seem to prevent the race. The reason is that task 4498 is in "RCU-walk mode," meaning it holds `rcu_read_lock()` but *not* the dentry's spinlock. It attempts to increment the refcount using `lockref_get_not_dead`, which *tries* to acquire the spinlock internally if the `arch_spin_value_unlocked` check fails.

The core of the problem seemed to hinge on the `CMPXCHG_LOOP` macro and the `arch_spin_value_unlocked` check. If task 3284 holds `parent->d_lock`, then `old.lock.rlock.raw_lock` should *not* be unlocked. This would cause the `while` loop in `CMPXCHG_LOOP` to be skipped, and task 4498 would then proceed to attempt `spin_lock(&lockref->lock)`.

However, the KCSAN report indicated a race on the 8-byte `lock_count` by task 4498 and a read-write on the 4-byte `count` by task 3284. My concern was: could task 4498 read `lock_count` with `READ_ONCE` *before* task 3284 acquired the lock, or *while* task 3284 was acquiring it, and *then* have task 3284 perform its RMW on the `count` field? This would be a classic data race.

The specific phrasing in the KCSAN report ("read (marked) to 0xffff888105d35800 of 8 bytes by task 4498" vs. "read-write to 0xffff888105d35804 of 4 bytes by task 3284") highlighted that task 4498 was performing a marked read of the entire 8-byte `lock_count`, while task 3284 was doing an unmarked read-write on the lower 4 bytes (`count`). KCSAN flags *any* marked access racing with an unmarked access as a potential data race.

This leads to the lingering question: is this KCSAN report indicative of a benign race due to strict reporting, or is there a genuine concurrency bug where an inconsistent `lock_count` could be observed, potentially leading to incorrect logic flow or even a crash if `try_cmpxchg64_relaxed` were to operate on a corrupted 8-byte value? The fact that `lockref_get_not_dead` uses `READ_ONCE` and then proceeds to a `spin_lock` if the lock is held suggests it's trying to be safe, but the race on the aggregate `lock_count` is what's particularly concerning. I need to understand if the sequence of operations on x86 can lead to a state where the `arch_spin_value_unlocked` check is misleading or if the 8-byte read itself can cross the RMW operation of the `count` in a way that causes issues.
</thought>
  Called tool grepper with args: {"Expression":"arch_spin_value_unlocked"}

[user]:
  Tool grepper returned: {"Output":"arch/alpha/include/asm/spinlock.h-18-\narch/alpha/include/asm/spinlock.h:19:static inline int arch_spin_value_unlocked(arch_spinlock_t lock)\narch/alpha/include/asm/spinlock.h-20-{\n--\narch/arm/include/asm/spinlock.h=107=static inline void arch_spin_unlock(arch_spinlock_t *lock)\n--\narch/arm/include/asm/spinlock.h-113-\narch/arm/include/asm/spinlock.h:114:static inline int arch_spin_value_unlocked(arch_spinlock_t lock)\narch/arm/include/asm/spinlock.h-115-{\n--\narch/arm/include/asm/spinlock.h=119=static inline int arch_spin_is_locked(arch_spinlock_t *lock)\narch/arm/include/asm/spinlock.h-120-{\narch/arm/include/asm/spinlock.h:121:\treturn !arch_spin_value_unlocked(READ_ONCE(*lock));\narch/arm/include/asm/spinlock.h-122-}\n--\narch/powerpc/include/asm/qspinlock.h=154=static inline void queued_spin_unlock(struct qspinlock *lock)\n--\narch/powerpc/include/asm/qspinlock.h-162-#define arch_spin_is_contended(l)\tqueued_spin_is_contended(l)\narch/powerpc/include/asm/qspinlock.h:163:#define arch_spin_value_unlocked(l)\tqueued_spin_value_unlocked(l)\narch/powerpc/include/asm/qspinlock.h-164-#define arch_spin_lock(l)\t\tqueued_spin_lock(l)\n--\narch/powerpc/include/asm/simple_spinlock.h-34-\narch/powerpc/include/asm/simple_spinlock.h:35:static __always_inline int arch_spin_value_unlocked(arch_spinlock_t lock)\narch/powerpc/include/asm/simple_spinlock.h-36-{\n--\narch/powerpc/include/asm/simple_spinlock.h=40=static inline int arch_spin_is_locked(arch_spinlock_t *lock)\narch/powerpc/include/asm/simple_spinlock.h-41-{\narch/powerpc/include/asm/simple_spinlock.h:42:\treturn !arch_spin_value_unlocked(READ_ONCE(*lock));\narch/powerpc/include/asm/simple_spinlock.h-43-}\n--\narch/s390/include/asm/spinlock.h=59=static inline u32 arch_spin_lockval(int cpu)\n--\narch/s390/include/asm/spinlock.h-63-\narch/s390/include/asm/spinlock.h:64:static inline int arch_spin_value_unlocked(arch_spinlock_t lock)\narch/s390/include/asm/spinlock.h-65-{\n--\ninclude/asm-generic/qspinlock.h=165=static __always_inline bool virt_spin_lock(struct qspinlock *lock)\n--\ninclude/asm-generic/qspinlock.h-177-#define arch_spin_is_contended(l)\tqueued_spin_is_contended(l)\ninclude/asm-generic/qspinlock.h:178:#define arch_spin_value_unlocked(l)\tqueued_spin_value_unlocked(l)\ninclude/asm-generic/qspinlock.h-179-#define arch_spin_lock(l)\t\tqueued_spin_lock(l)\n--\ninclude/asm-generic/ticket_spinlock.h=85=static __always_inline int ticket_spin_is_contended(arch_spinlock_t *lock)\n--\ninclude/asm-generic/ticket_spinlock.h-98-#define arch_spin_is_contended(l)\tticket_spin_is_contended(l)\ninclude/asm-generic/ticket_spinlock.h:99:#define arch_spin_value_unlocked(l)\tticket_spin_value_unlocked(l)\ninclude/asm-generic/ticket_spinlock.h-100-#define arch_spin_lock(l)\t\tticket_spin_lock(l)\n--\nlib/lockref.c-15-\told.lock_count = READ_ONCE(lockref-\u003elock_count);\t\t\t\\\nlib/lockref.c:16:\twhile (likely(arch_spin_value_unlocked(old.lock.rlock.raw_lock))) {  \t\\\nlib/lockref.c-17-\t\tstruct lockref new = old;\t\t\t\t\t\\\n"}

[model]:
<thought>
**My Current Line of Inquiry: Deconstructing `queued_spin_value_unlocked`**

Ah, yes, I'm currently deep in the weeds, specifically examining the `queued_spin_value_unlocked` macro within the `include/asm-generic/qspinlock.h` file. My focus is on understanding the intricate details of this particular construct, which, as an expert in this domain, I recognize as a fundamental piece of the queued spinlock mechanism. I'm dissecting its definition and implications, aiming for a comprehensive grasp of its role in the underlying synchronization primitives.
</thought>
  Called tool codesearch-definition-source with args: {"ContextFile":"include/asm-generic/qspinlock.h","Name":"queued_spin_value_unlocked"}

[user]:
  Tool codesearch-definition-source returned: {"SourceCode":"  62:\t/**\n  63:\t * queued_spin_value_unlocked - is the spinlock structure unlocked?\n  64:\t * @lock: queued spinlock structure\n  65:\t * Return: 1 if it is unlocked, 0 otherwise\n  66:\t *\n  67:\t * N.B. Whenever there are tasks waiting for the lock, it is considered\n  68:\t *      locked wrt the lockref code to avoid lock stealing by the lockref\n  69:\t *      code and change things underneath the lock. This also allows some\n  70:\t *      optimizations to be applied without conflict with lockref.\n  71:\t */\n  72:\tstatic __always_inline int queued_spin_value_unlocked(struct qspinlock lock)\n  73:\t{\n  74:\t\treturn !lock.val.counter;\n  75:\t}\n","SourceFile":"include/asm-generic/qspinlock.h"}

[model]:
<thought>
**Diving into the KCSAN Report: A Thought Process**

Okay, so I'm looking at this comment, and it's got me thinking. It's talking about how when tasks are waiting for a lock, the `lockref` code considers it "locked" to prevent others from messing with things underneath. This also apparently helps with some optimizations. That makes sense on the surface.

But then I see "WAIT!" – that's the trigger. Something about this interaction is not as straightforward as it seems, especially when KCSAN (Kernel Concurrency Sanitizer) has flagged an issue.

Let's break down how `lockref` works, as described: it's a 64-bit value combining a 32-bit spinlock and a 32-bit count. The comment mentions that when the spinlock itself is held, `arch_spin_value_unlocked` returns 0. This is crucial because the `CMPXCHG_LOOP` mechanism will then *not* attempt an atomic compare-and-exchange on the `lockref` value, and instead, it will fall back to taking the internal spinlock (`spin_lock(&lockref->lock)`). This seems like a reasonable design to ensure atomicity when the main spinlock is already acquired.

So, if that's how it's *supposed* to work, why did KCSAN fire? This is where the real investigation begins.

I need to trace the specific events. The report points to Task 4498 doing a `READ_ONCE(lockref->lock_count)`. This is interesting – `READ_ONCE` is meant to prevent certain compiler reordering, but it doesn't guarantee atomicity across multiple words on all architectures. It reads the entire 64-bit `lockref` value, which comprises both the `lock` and the `count` fields.

Concurrently, Task 3284 is doing `--parent->d_lockref.count`. This is a simple decrement operation, and crucially, it's *not* an atomic operation and it's *not* wrapped in `WRITE_ONCE`. Now, I need to check the context of Task 3284. Ah, it had *already* acquired `parent->d_lock` at an earlier line. This is a critical piece of information.

So, here's the emerging conflict: Task 4498 is reading the 64-bit `lockref` value using `READ_ONCE`. This read *could* conceptually happen in two parts: the `lock` field and the `count` field. At the *exact* same time, Task 3284, while holding `parent->d_lock`, is modifying `parent->d_lockref.count`. Because Task 3284 is just doing a `--` operation (and not an atomic or `WRITE_ONCE`), it's a regular write to memory.

My thought process is now racing: If Task 3284 holds `parent->d_lock`, why isn't Task 4498's read of `count` protected? The key must be in how `lockref` is read. Task 4498 reads *both* `lock` and `count` as a single 64-bit value *before* it even checks if the `lock` part is actually locked. This means the read of the 64-bit `lockref` value (containing both `lock` and `count`) can happen *independently* of whether `parent->d_lock` is held.

The core of the problem appears to be that `READ_ONCE(lockref->lock_count)` is reading the 64-bit value, which includes `count`. Task 3284, holding `parent->d_lock`, is modifying `count` using a non-atomic `--` operation. This creates a race condition: Task 4498 could be reading the `count` field *while* Task 3284 is in the middle of updating it. Even though `parent->d_lock` protects Task 3284's write to `count`, it doesn't protect Task 4498's read of `count` if Task 4498 isn't also respecting `parent->d_lock` in its `lockref` access.

The question then becomes: what is it about holding `lockref->lock` that allows a modification to `count` without using an atomic operation like `cmpxchg`? It seems that any holder of `lockref->lock` that modifies `lockref->count` without a full atomic operation is vulnerable. This prompts the next step: I need to find out *which* parts of the kernel actually modify `lockref->count` while holding `lockref->lock` without using appropriate atomic primitives. My next logical step is to grep the codebase for all instances where `struct lockref`'s `count` member is modified.
</thought>
  Called tool grepper with args: {"Expression":"d_lockref\\.count"}

[user]:
  Tool grepper returned: {"Output":"fs/ceph/dir.c=1665=__dentry_leases_walk(struct ceph_mds_client *mdsc,\n--\nfs/ceph/dir.c-1706-\t\t\tdi-\u003eflags \u0026= ~CEPH_DENTRY_REFERENCED;\nfs/ceph/dir.c:1707:\t\t\tif (dentry-\u003ed_lockref.count \u003e 0) {\nfs/ceph/dir.c-1708-\t\t\t\t/* update_dentry_lease() will re-add\n--\nfs/ceph/dir.c=1769=static enum lease_check_result __dir_lease_check(const struct dentry *dentry,\n--\nfs/ceph/dir.c-1784-\t\t * round robin manner */\nfs/ceph/dir.c:1785:\t\tif (dentry-\u003ed_lockref.count \u003e 0 ||\nfs/ceph/dir.c-1786-\t\t    (di-\u003eflags \u0026 CEPH_DENTRY_REFERENCED))\n--\nfs/dcache.c=756=static bool lock_for_kill(struct dentry *dentry)\n--\nfs/dcache.c-759-\nfs/dcache.c:760:\tif (unlikely(dentry-\u003ed_lockref.count)) {\nfs/dcache.c-761-\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n--\nfs/dcache.c-783-\trcu_read_unlock();\nfs/dcache.c:784:\tif (likely(!dentry-\u003ed_lockref.count))\nfs/dcache.c-785-\t\treturn true;\n--\nfs/dcache.c=830=static struct dentry *dentry_kill(struct dentry *dentry)\n--\nfs/dcache.c-876-\t\tdentry_free(dentry);\nfs/dcache.c:877:\tif (parent \u0026\u0026 --parent-\u003ed_lockref.count) {\nfs/dcache.c-878-\t\tspin_unlock(\u0026parent-\u003ed_lock);\n--\nfs/dcache.c=960=static inline bool fast_dput(struct dentry *dentry)\n--\nfs/dcache.c-983-\t\t}\nfs/dcache.c:984:\t\tdentry-\u003ed_lockref.count--;\nfs/dcache.c-985-\t\tgoto locked;\n--\nfs/dcache.c-1021-locked:\nfs/dcache.c:1022:\tif (dentry-\u003ed_lockref.count || retain_dentry(dentry, true)) {\nfs/dcache.c-1023-\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n--\nfs/dcache.c=1077=void d_make_discardable(struct dentry *dentry)\n--\nfs/dcache.c-1081-\tdentry-\u003ed_flags \u0026= ~DCACHE_PERSISTENT;\nfs/dcache.c:1082:\tdentry-\u003ed_lockref.count--;\nfs/dcache.c-1083-\tfinish_dput(dentry);\n--\nfs/dcache.c=1105=__must_hold(\u0026dentry-\u003ed_lock)\nfs/dcache.c-1106-{\nfs/dcache.c:1107:\tif (likely(!dentry-\u003ed_lockref.count \u0026\u0026\nfs/dcache.c-1108-\t    !(dentry-\u003ed_flags \u0026 DCACHE_SHRINK_LIST))) {\n--\nfs/dcache.c=1137=struct dentry *dget_parent(struct dentry *dentry)\n--\nfs/dcache.c-1171-\trcu_read_unlock();\nfs/dcache.c:1172:\tBUG_ON(!ret-\u003ed_lockref.count);\nfs/dcache.c:1173:\tret-\u003ed_lockref.count++;\nfs/dcache.c-1174-\tspin_unlock(\u0026ret-\u003ed_lock);\n--\nfs/dcache.c=1339=static enum lru_status dentry_lru_isolate(struct list_head *item,\n--\nfs/dcache.c-1358-\t */\nfs/dcache.c:1359:\tif (dentry-\u003ed_lockref.count) {\nfs/dcache.c-1360-\t\td_lru_isolate(lru, dentry);\n--\nfs/dcache.c=1711=static enum d_walk_ret select_collect_umount(void *_data, struct dentry *dentry)\n--\nfs/dcache.c-1714-\t\tdentry-\u003ed_flags \u0026= ~DCACHE_PERSISTENT;\nfs/dcache.c:1715:\t\tdentry-\u003ed_lockref.count--;\nfs/dcache.c-1716-\t}\n--\nfs/dcache.c=1820=static enum d_walk_ret umount_check(void *_data, struct dentry *dentry)\n--\nfs/dcache.c-1826-\t/* root with refcount 1 is fine */\nfs/dcache.c:1827:\tif (dentry == _data \u0026\u0026 dentry-\u003ed_lockref.count == 1)\nfs/dcache.c-1828-\t\treturn D_WALK_CONTINUE;\n--\nfs/dcache.c-1835-\t\t       dentry,\nfs/dcache.c:1836:\t\t       dentry-\u003ed_lockref.count,\nfs/dcache.c-1837-\t\t       dentry-\u003ed_sb-\u003es_type-\u003ename,\n--\nfs/dcache.c=1842=static void do_one_tree(struct dentry *dentry)\n--\nfs/dcache.c-1852-\t */\nfs/dcache.c:1853:\tif (unlikely(dentry-\u003ed_lockref.count \u003e 1 \u0026\u0026\nfs/dcache.c-1854-\t\t     !hlist_unhashed(\u0026dentry-\u003ed_sib)))\n--\nfs/dcache.c=2706=struct dentry *__d_lookup(const struct dentry *parent, const struct qstr *name)\n--\nfs/dcache.c-2749-\nfs/dcache.c:2750:\t\tdentry-\u003ed_lockref.count++;\nfs/dcache.c-2751-\t\tfound = dentry;\n--\nfs/dcache.c=2806=void d_delete(struct dentry * dentry)\n--\nfs/dcache.c-2814-\t */\nfs/dcache.c:2815:\tif (dentry-\u003ed_lockref.count == 1) {\nfs/dcache.c-2816-\t\tif (dentry_negative_policy)\n--\nfs/dcache.c=3255=static void __d_move(struct dentry *dentry, struct dentry *target,\n--\nfs/dcache.c-3305-\t\ttarget-\u003ed_hash.pprev = NULL;\nfs/dcache.c:3306:\t\tdentry-\u003ed_parent-\u003ed_lockref.count++;\nfs/dcache.c-3307-\t\tif (dentry != old_parent) /* wasn't IS_ROOT */\nfs/dcache.c:3308:\t\t\tWARN_ON(!--old_parent-\u003ed_lockref.count);\nfs/dcache.c-3309-\t} else {\n--\nfs/gfs2/quota.c=151=static enum lru_status gfs2_qd_isolate(struct list_head *item,\n--\nfs/gfs2/quota.c-162-\tstatus = LRU_SKIP;\nfs/gfs2/quota.c:163:\tif (qd-\u003eqd_lockref.count == 0) {\nfs/gfs2/quota.c-164-\t\tlockref_mark_dead(\u0026qd-\u003eqd_lockref);\n--\nfs/gfs2/quota.c=331=static void __qd_hold(struct gfs2_quota_data *qd)\n--\nfs/gfs2/quota.c-333-\tstruct gfs2_sbd *sdp = qd-\u003eqd_sbd;\nfs/gfs2/quota.c:334:\tgfs2_assert(sdp, qd-\u003eqd_lockref.count \u003e 0);\nfs/gfs2/quota.c:335:\tqd-\u003eqd_lockref.count++;\nfs/gfs2/quota.c-336-}\n--\nfs/gfs2/quota.c=338=static void qd_put(struct gfs2_quota_data *qd)\n--\nfs/gfs2/quota.c-355-\nfs/gfs2/quota.c:356:\tqd-\u003eqd_lockref.count = 0;\nfs/gfs2/quota.c-357-\tlist_lru_add_obj(\u0026gfs2_qd_lru, \u0026qd-\u003eqd_lru);\n--\nfs/gfs2/quota.c=478=static bool qd_grab_sync(struct gfs2_sbd *sdp, struct gfs2_quota_data *qd,\n--\nfs/gfs2/quota.c-490-\t\tgoto out;\nfs/gfs2/quota.c:491:\tqd-\u003eqd_lockref.count++;\nfs/gfs2/quota.c-492-\n--\nfs/gfs2/quota.c=1409=int gfs2_quota_init(struct gfs2_sbd *sdp)\n--\nfs/gfs2/quota.c-1472-\nfs/gfs2/quota.c:1473:\t\t\tqd-\u003eqd_lockref.count = 0;\nfs/gfs2/quota.c-1474-\t\t\tset_bit(QDF_CHANGE, \u0026qd-\u003eqd_flags);\n--\nfs/gfs2/quota.c=1533=void gfs2_quota_cleanup(struct gfs2_sbd *sdp)\n--\nfs/gfs2/quota.c-1544-\t\tspin_lock(\u0026qd-\u003eqd_lockref.lock);\nfs/gfs2/quota.c:1545:\t\tif (qd-\u003eqd_lockref.count != 0) {\nfs/gfs2/quota.c-1546-\t\t\tspin_unlock(\u0026qd-\u003eqd_lockref.lock);\n--\nfs/overlayfs/namei.c=211=static struct dentry *ovl_lookup_positive_unlocked(struct ovl_lookup_data *d,\n--\nfs/overlayfs/namei.c-219-\tif (!IS_ERR(ret) \u0026\u0026 d_flags_negative(smp_load_acquire(\u0026ret-\u003ed_flags))) {\nfs/overlayfs/namei.c:220:\t\tif (drop_negative \u0026\u0026 ret-\u003ed_lockref.count == 1) {\nfs/overlayfs/namei.c-221-\t\t\tspin_lock(\u0026ret-\u003ed_lock);\nfs/overlayfs/namei.c-222-\t\t\t/* Recheck condition under lock */\nfs/overlayfs/namei.c:223:\t\t\tif (d_is_negative(ret) \u0026\u0026 ret-\u003ed_lockref.count == 1)\nfs/overlayfs/namei.c-224-\t\t\t\t__d_drop(ret);\n--\ninclude/linux/dcache.h=311=static inline unsigned d_count(const struct dentry *dentry)\ninclude/linux/dcache.h-312-{\ninclude/linux/dcache.h:313:\treturn dentry-\u003ed_lockref.count;\ninclude/linux/dcache.h-314-}\n--\ninclude/linux/dcache.h=342=static inline struct dentry *dget_dlock(struct dentry *dentry)\ninclude/linux/dcache.h-343-{\ninclude/linux/dcache.h:344:\tdentry-\u003ed_lockref.count++;\ninclude/linux/dcache.h-345-\treturn dentry;\n--\ninclude/linux/dcache.h=375=static inline bool dget_alias_ilocked(struct dentry *dentry)\n--\ninclude/linux/dcache.h-382-\tspin_lock(\u0026dentry-\u003ed_lock);\ninclude/linux/dcache.h:383:\tif (dentry-\u003ed_lockref.count \u003e 0) {\ninclude/linux/dcache.h-384-\t\tdget_dlock(dentry);\n"}

[model]:
<thought>
**Revisiting `dentry_kill` and its Interaction with `finish_dput`**

I'm taking another look at the `dentry_kill` function, specifically focusing on the block from lines 864 to 882. My attention is drawn to the sequence of operations here. After `cond_resched_tasks_rcu_qs()`, there's a comment about `d_parent` being stable because the `dentry`'s count is now negative. This is a crucial point for understanding subsequent lock dependencies.

The code then checks if the `dentry` is not the root. If it's not, it acquires the lock on its parent (`d_parent`). Following that, it acquires the lock on the `dentry` itself. Immediately after, `dentry_unlist` is called. A flag, `DCACHE_SHRINK_LIST`, is checked; if set, it indicates that the `dentry` cannot be freed immediately. The `dentry`'s lock is then released. If the `dentry` is deemed "freeable" (i.e., the flag wasn't set), `dentry_free` is called.

Finally, the logic for the parent `dentry` is handled. If a parent `dentry` was involved and its `d_lockref.count` (which I interpret as a reference count for the parent's lock) decrements to zero, its lock is released. The function then returns `NULL` or the parent `dentry` accordingly.

However, this is where I'm getting a bit of a knot in my thinking. I need to reconcile this with what happens in `finish_dput`. I'm now shifting my focus to read the relevant section of `fs/dcache.c`, specifically lines 960 to 1070, to understand the complete picture of how `dentry` objects are processed and potentially freed. I suspect the interaction between the lock management and reference counting in these two functions is critical to avoid race conditions or deadlocks.
</thought>
  Called tool read-file with args: {"File":"fs/dcache.c","FirstLine":960,"LineCount":100}

[user]:
  Tool read-file returned: {"Contents":" 960:\tstatic inline bool fast_dput(struct dentry *dentry)\n 961:\t{\n 962:\t\tint ret;\n 963:\t\n 964:\t\t/*\n 965:\t\t * Try to decrement the lockref optimistically.\n 966:\t\t * RCU read lock held so that dentry is guaranteed to stay around\n 967:\t\t * even if the refcount goes down to zero.\n 968:\t\t */\n 969:\t\trcu_read_lock();\n 970:\t\tret = lockref_put_return(\u0026dentry-\u003ed_lockref);\n 971:\t\n 972:\t\t/*\n 973:\t\t * If the lockref_put_return() failed due to the lock being held\n 974:\t\t * by somebody else, the fast path has failed. We will need to\n 975:\t\t * get the lock, and then check the count again.\n 976:\t\t */\n 977:\t\tif (unlikely(ret \u003c 0)) {\n 978:\t\t\tspin_lock(\u0026dentry-\u003ed_lock);\n 979:\t\t\trcu_read_unlock();\n 980:\t\t\tif (WARN_ON_ONCE(lockref_is_dead_or_zero(\u0026dentry-\u003ed_lockref))) {\n 981:\t\t\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n 982:\t\t\t\treturn true;\n 983:\t\t\t}\n 984:\t\t\tdentry-\u003ed_lockref.count--;\n 985:\t\t\tgoto locked;\n 986:\t\t}\n 987:\t\n 988:\t\t/*\n 989:\t\t * If we weren't the last ref, we're done.\n 990:\t\t */\n 991:\t\tif (ret) {\n 992:\t\t\trcu_read_unlock();\n 993:\t\t\treturn true;\n 994:\t\t}\n 995:\t\n 996:\t\t/*\n 997:\t\t * Can we decide that decrement of refcount is all we needed without\n 998:\t\t * taking the lock?  There's a very common case when it's all we need -\n 999:\t\t * dentry looks like it ought to be retained and there's nothing else\n1000:\t\t * to do.\n1001:\t\t */\n1002:\t\tif (retain_dentry(dentry, false)) {\n1003:\t\t\trcu_read_unlock();\n1004:\t\t\treturn true;\n1005:\t\t}\n1006:\t\n1007:\t\t/*\n1008:\t\t * Either not worth retaining or we can't tell without the lock.\n1009:\t\t * Get the lock, then.  We've already decremented the refcount to 0,\n1010:\t\t * but we'll need to re-check the situation after getting the lock.\n1011:\t\t */\n1012:\t\tspin_lock(\u0026dentry-\u003ed_lock);\n1013:\t\trcu_read_unlock();\n1014:\t\n1015:\t\t/*\n1016:\t\t * Did somebody else grab a reference to it in the meantime, and\n1017:\t\t * we're no longer the last user after all? Alternatively, somebody\n1018:\t\t * else could have killed it and marked it dead. Either way, we\n1019:\t\t * don't need to do anything else.\n1020:\t\t */\n1021:\tlocked:\n1022:\t\tif (dentry-\u003ed_lockref.count || retain_dentry(dentry, true)) {\n1023:\t\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n1024:\t\t\treturn true;\n1025:\t\t}\n1026:\t\treturn false;\n1027:\t}\n1028:\t\n1029:\tstatic void finish_dput(struct dentry *dentry)\n1030:\t\t__releases(dentry-\u003ed_lock)\n1031:\t{\n1032:\t\twhile ((dentry = dentry_kill(dentry)) != NULL) {\n1033:\t\t\tif (retain_dentry(dentry, true)) {\n1034:\t\t\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n1035:\t\t\t\treturn;\n1036:\t\t\t}\n1037:\t\t}\n1038:\t}\n1039:\t\n1040:\t/* \n1041:\t * This is dput\n1042:\t *\n1043:\t * This is complicated by the fact that we do not want to put\n1044:\t * dentries that are no longer on any hash chain on the unused\n1045:\t * list: we'd much rather just get rid of them immediately.\n1046:\t *\n1047:\t * However, that implies that we have to traverse the dentry\n1048:\t * tree upwards to the parents which might _also_ now be\n1049:\t * scheduled for deletion (it may have been only waiting for\n1050:\t * its last child to go away).\n1051:\t *\n1052:\t * This tail recursion is done by hand as we don't want to depend\n1053:\t * on the compiler to always get this right (gcc generally doesn't).\n1054:\t * Real recursion would eat up our stack space.\n1055:\t */\n1056:\t\n1057:\t/*\n1058:\t * dput - release a dentry\n1059:\t * @dentry: dentry to release \n"}

[model]:
<thought>
**Analysis of a Potential Data Race in dentry_kill and lockref_get_not_dead**

I've been investigating a KCSAN-reported data race that seems to involve the `finish_dput` and `dentry_kill` functions interacting with `lockref_get_not_dead`. My thought process has been to meticulously trace the execution paths of the two involved tasks, understand the state of locks and reference counts, and determine the precise point of contention and its potential implications.

Initially, I examined `finish_dput` and how it calls `dentry_kill` in a loop. My attention was drawn to the logic within `dentry_kill` concerning the parent's lock reference count. Specifically, I noticed that after freeing the `dentry` itself, `dentry_kill` decrements the `parent->d_lockref.count`. The immediate consequence I recognized was that this decrement corresponds to the dropped reference that the killed `dentry` held on its `parent`. If this count drops to zero, `dentry_kill` returns `parent`, and `finish_dput` will then proceed to potentially call `dentry_kill` on the `parent` itself in the next iteration.

This is where my focus shifted to what task 4498 was doing concurrently. I observed that task 4498 was involved in an RCU path walk and was attempting to "legitimize" a path, which involves acquiring a reference using `lockref_get_not_dead` on the `parent` dentry. This immediately flagged a potential race condition: one task (`task 3284`) is decrementing a reference count on the `parent` while holding its lock, and another task (`task 4498`) is trying to acquire a reference on the same `parent` using an optimistic, lockless approach.

My deeper dive into `lockref_get_not_dead` revealed its optimistic CMPXCHG loop, intended to increment the count without acquiring the spinlock if possible. The critical point here is that `lockref_get_not_dead` uses `READ_ONCE` to read `lockref->lock_count` within its CMPXCHG loop. This is done because the loop aims to avoid acquiring the spinlock.

The KCSAN report indicated a race between a marked read (`READ_ONCE`) in `lockref_get_not_dead` (task 4498) and an unmarked read-write operation (`--parent->d_lockref.count`) in `dentry_kill` (task 3284). This is where my analysis became crucial. I questioned why this would be flagged as a race if `task 3284` was holding the `parent->d_lock`.

I then carefully traced the sequence of operations, particularly considering the timing of lock acquisition and reference count manipulation. I hypothesized a scenario where `task 4498` (running `lockref_get_not_dead`) might read the `parent->d_lockref.count` (specifically, `lockref->lock_count` which includes the lock state) *before* `task 3284` acquires the `parent->d_lock`. If `task 4498` reads the lock state as unlocked, it would enter the CMPXCHG loop. However, if `task 3284` subsequently acquires the `parent->d_lock` and modifies the count, the subsequent `try_cmpxchg64` in `task 4498` would fail because the lock state in memory would have changed (from unlocked to locked), causing `old.lock_count` to no longer match the memory value. Consequently, `task 4498` would fall back to acquiring the `parent->d_lock` itself.

My subsequent thought was: if the fallback to acquiring the lock always happens when the lock is held, and the lock is released by `task 3284`, then `task 4498` will eventually acquire the lock, see the correct count, increment it, and proceed. This seems benign.

However, I then reconsidered the fundamental nature of KCSAN flagging: it flags races between *marked* and *unmarked* accesses. The critical insight came from realizing that while `lockref_get_not_dead` uses `READ_ONCE` for its optimistic path, the writer (`--parent->d_lockref.count` in `dentry_kill`) is performing a plain, unmarked read-modify-write operation. According to C standards and the Linux Memory Model (LKMM), any concurrent access between an unmarked write and *any* read, even a `READ_ONCE`, constitutes a data race.

This led me to question whether this is just a formal data race or if it has functional consequences. I examined the implications of the `lockref` mechanism. The optimistic CMPXCHG loop in `lockref_get_not_dead` relies on the atomicity of the 64-bit `lockref->lock_count` on architectures like x86-64. `READ_ONCE` ensures the compiler generates a single 64-bit load. However, the unmarked decrement (`--parent->d_lockref.count`) by `task 3284` is what KCSAN is specifically concerned about. Even if the lock is held, the plain C decrement might not be a single, atomic store operation that is correctly synchronized with the read operations in `task 4498`'s CMPXCHG loop from KCSAN's perspective, especially if the lock-holding sequence itself is not perfectly atomic with respect to the read.

My final contemplation focused on the potential for actual corruption. I reasoned that if the lock is held by `task 3284` when it performs the `--parent->d_lockref.count` operation, and `task 4498` is blocked on acquiring that same lock, then the sequence of events might be ordered such that `task 4498` eventually acquires the lock, sees the updated count, and increments it. This scenario, while involving concurrent access, might not immediately lead to a corrupt state *if* the lock acquisition and release logic correctly serializes the operations on the `d_lockref.count`.

However, the KCSAN report suggests a more subtle issue. The race is precisely because `task 4498` reads `lockref->lock_count` (which is 8 bytes) using `READ_ONCE`, while `task 3284` writes to `parent->d_lockref.count` (which is 4 bytes, part of the 8-byte `lock_count`) without any explicit marking or synchronization that KCSAN recognizes as safe against the `READ_ONCE`. This could potentially lead to torn reads or inconsistent views of the `lockref` state, especially when considering the interplay between the spinlock and the count itself. While `task 3284` holds the `parent->d_lock`, the way `parent->d_lockref.count` is modified might not be fully synchronized with `task 4498`'s `READ_ONCE` *if* the compiler or architecture performs the write in a way that creates an observable race with the marked read on the 64-bit field, even if the spinlock is held. This is the core of the KCSAN finding: an unmarked write racing with a marked read.

In essence, I suspect the issue is not that the lock is not acquired, but that the *unmarked write* to a portion of the field being optimistically read by `task 4498` is the problematic part, creating a potential for KCSAN to detect an invalid access pattern, even if the actual functional bug is subtle or relies on specific timing. The fact that `lockref_mark_dead` itself uses plain assignment also points to a potential pattern of unmarked writes within the `lockref` mechanism that might be problematic when paired with optimistic reads.
</thought>
  Called tool codesearch-struct-layout with args: {"ContextFile":"fs/dcache.c","Name":"dentry"}

[user]:
  Tool codesearch-struct-layout returned: {"Fields":[{"Name":"d_flags","OffsetBits":0,"SizeBits":32},{"Name":"d_seq","OffsetBits":32,"SizeBits":32},{"Name":"d_hash","OffsetBits":64,"SizeBits":128},{"Name":"d_parent","OffsetBits":192,"SizeBits":64},{"Name":"","OffsetBits":256,"SizeBits":128},{"Name":"d_inode","OffsetBits":384,"SizeBits":64},{"Name":"d_shortname","OffsetBits":448,"SizeBits":320},{"Name":"d_op","OffsetBits":768,"SizeBits":64},{"Name":"d_sb","OffsetBits":832,"SizeBits":64},{"Name":"d_time","OffsetBits":896,"SizeBits":64},{"Name":"d_fsdata","OffsetBits":960,"SizeBits":64},{"Name":"d_lockref","OffsetBits":1024,"SizeBits":64},{"Name":"dep_map","OffsetBits":1088,"SizeBits":0},{"Name":"d_lru","OffsetBits":1088,"SizeBits":128},{"Name":"d_sib","OffsetBits":1216,"SizeBits":128},{"Name":"d_children","OffsetBits":1344,"SizeBits":64},{"Name":"","OffsetBits":1408,"SizeBits":128}]}

[model]:
<thought>
**Decoding the dentry Lock's Location**

My immediate thought upon examining the `struct dentry` definition was to pinpoint the location of `d_lockref`. I saw it was situated at bit offset 1024, which, after a quick mental conversion, translates to a byte offset of 128, or `0x80`. This is a crucial detail for understanding memory layout and potential performance implications. To ensure I had the definitive definition and wasn't relying on potentially outdated information, I immediately resolved to consult `include/linux/dcache.h` to get the precise definition of `d_lock`, confirming the exact bit positioning and any surrounding context that might be relevant to its usage.
</thought>
  Called tool grepper with args: {"Expression":"#define d_lock","PathPrefixes":["include/linux/dcache.h"]}

[user]:
  Tool grepper returned: {"Output":"include/linux/dcache.h=84=union shortname_store {\n--\ninclude/linux/dcache.h-88-\ninclude/linux/dcache.h:89:#define d_lock\td_lockref.lock\ninclude/linux/dcache.h-90-#define d_iname d_shortname.string\n"}

[model]:
<thought>
**Investigating a Potential Data Race in Lockref Implementation**

My thought process begins with a directive: `#define d_lock d_lockref.lock`. This immediately clarifies a crucial piece of the puzzle: `parent->d_lock` is, in fact, `parent->d_lockref.lock`. My understanding of the `struct lockref` then solidifies. I see the `union` containing either `lock_count` or the `lock` spinlock and an integer `count`. This structure implies that `lock_count` is a packed representation, effectively an `aligned_u64`, that combines the spinlock and the count. Specifically, I deduce that the `lock` field occupies the first four bytes (offset 0) and `count` the subsequent four bytes (offset 4).

With this foundational understanding, I trace the execution flow. Task 3284 acquires the spinlock by calling `spin_lock(&parent->d_lock)`, which translates to `spin_lock(&parent->d_lockref.lock)`. Immediately after, it performs a decrement operation: `--parent->d_lockref.count`. This operation targets the `count` field within the `lockref` structure.

Then, I shift my attention to Task 4498, which is executing `lockref_get_not_dead(&parent->d_lockref)`. I delve into the `CMPXCHG_LOOP` macro, the core of this function. The initial step, `old.lock_count = READ_ONCE(lockref->lock_count);`, is particularly significant. This line performs an 8-byte read of the entire `lock_count` union member.

This is where the potential issue surfaces. Task 4498 reads the full 8-byte `lock_count` using `READ_ONCE`, while Task 3284 modifies the `count` field (which is part of `lock_count`) with an `--` operation. This operation is an unmarked read-modify-write on a 4-byte field. The KCSAN (Kernel Concurrency Sanitizer) report confirms this: it flags an overlap between an 8-byte read (Task 4498) and a 4-byte read-write (Task 3284). The critical observation is that Task 3284's access is *unmarked* by any concurrency primitive, leading KCSAN to raise the alarm.

This brings me to the crucial question: is this a genuine data race, or is it an artifact of how `lockref` is designed and utilized? I begin to question the intention behind the design. Could the `--parent->d_lockref.count` operation be fundamentally flawed in this context? Should it be protected by an atomic operation, a `WRITE_ONCE`, or perhaps even a `data_race()` annotation to inform KCSAN of its deliberate nature?

I then consider the possibility that the `lockref` mechanism itself might be designed to leverage `cmpxchg` operations on the `lock_count` without necessarily holding the spinlock. However, if that's the case, how does the `READ_ONCE(lockref->lock_count)` interact with the *unlocked* modification of `count`? This interaction, especially when the lock is held by another thread, seems to be the crux of the problem.

My next step is to delve into the history. To truly understand the author's intent and the rationale behind Linus Torvalds' design of `lockref`, I need to examine the relevant commit history. I plan to use `git-log` to investigate commits related to `lockref` itself, as well as functions like `dentry_kill` or build configurations like `CONFIG_ARCH_USE_CMPXCHG_LOCKREF`. This historical context is vital for determining whether this reported race is a bug to be fixed or an intended behavior that requires a specific annotation to satisfy KCSAN.
</thought>
  Called tool git-log with args: {"CodeRegexp":"lockref","Count":5,"PathPrefix":"lib/lockref.c"}

[user]:
  Tool git-log returned: {"Output":"91e27ed8a387 lockref: tidy up dead count handling\ne4588c25c9d1 compiler-context-analysis: Remove __cond_lock() function-like helper\n12eef14bcbac lockref: add a __cond_lock annotation for lockref_put_or_lock\n6d2868d5b6fc lockref: use bool for false/true returns\nd60f2280a1b5 lockref: improve the lockref_get_not_zero description\n"}

[model]:
<thought>
**My Exploration of Commit 91e27ed8a387**

Alright, I'm diving into the commit history, specifically focusing on `91e27ed8a387`. I'm using `git show` to get a detailed look at what this particular commit entails. I'm not just looking at the diff, but also at the commit message, author, and date to build a complete picture of the changes introduced. As an expert in this domain, I'm assessing the impact of these modifications within the broader context of our codebase.
</thought>
  Called tool git-show with args: {"Commit":"91e27ed8a387"}

[user]:
  Tool git-show returned: {"Output":"commit 91e27ed8a387c156f72175748de48db9ede74237\nAuthor: Mateusz Guzik \u003cmjguzik@gmail.com\u003e\nDate:   Fri Jul 24 19:14:21 2026 +0200\n\n    lockref: tidy up dead count handling\n    \n    1. put the dead val into a macro so that it can be used in other places\n    2. __lockref_is_dead():\n    - drop the __ suffix, this is not an internal routine\n    - drop the spurious cast, the value is already a signed int\n    - use READ_ONCE to prevent any compile shenanigans\n    3. provide lockref_is_dead_or_zero()\n    \n    Signed-off-by: Mateusz Guzik \u003cmjguzik@gmail.com\u003e\n    Link: https://patch.msgid.link/20260724171422.429284-2-mjguzik@gmail.com\n    Signed-off-by: Christian Brauner (Amutable) \u003cbrauner@kernel.org\u003e\n\ndiff --git a/fs/ceph/dir.c b/fs/ceph/dir.c\nindex 32a48550eacf..ab4806ea790a 100644\n--- a/fs/ceph/dir.c\n+++ b/fs/ceph/dir.c\n@@ -1667,7 +1667,7 @@ __dentry_leases_walk(struct ceph_mds_client *mdsc,\n \t\tif (!spin_trylock(\u0026dentry-\u003ed_lock))\n \t\t\tcontinue;\n \n-\t\tif (__lockref_is_dead(\u0026dentry-\u003ed_lockref)) {\n+\t\tif (lockref_is_dead(\u0026dentry-\u003ed_lockref)) {\n \t\t\tlist_del_init(\u0026di-\u003elease_list);\n \t\t\tgoto next;\n \t\t}\ndiff --git a/fs/erofs/zdata.c b/fs/erofs/zdata.c\nindex 74520e910259..d022d1dff5a1 100644\n--- a/fs/erofs/zdata.c\n+++ b/fs/erofs/zdata.c\n@@ -725,7 +725,7 @@ static bool z_erofs_get_pcluster(struct z_erofs_pcluster *pcl)\n \t\treturn true;\n \n \tspin_lock(\u0026pcl-\u003elockref.lock);\n-\tif (__lockref_is_dead(\u0026pcl-\u003elockref)) {\n+\tif (lockref_is_dead(\u0026pcl-\u003elockref)) {\n \t\tspin_unlock(\u0026pcl-\u003elockref.lock);\n \t\treturn false;\n \t}\n@@ -945,7 +945,7 @@ static void z_erofs_put_pcluster(struct erofs_sb_info *sbi,\n \tif (lockref_put_or_lock(\u0026pcl-\u003elockref))\n \t\treturn;\n \n-\tDBG_BUGON(__lockref_is_dead(\u0026pcl-\u003elockref));\n+\tDBG_BUGON(lockref_is_dead(\u0026pcl-\u003elockref));\n \tif (!--pcl-\u003elockref.count) {\n \t\tif (try_free \u0026\u0026 xa_trylock(\u0026sbi-\u003emanaged_pslots)) {\n \t\t\tfree = __erofs_try_to_release_pcluster(sbi, pcl);\ndiff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c\nindex b8a144d3a73b..eaa2980051ed 100644\n--- a/fs/gfs2/glock.c\n+++ b/fs/gfs2/glock.c\n@@ -2080,7 +2080,7 @@ static void clear_glock(struct gfs2_glock *gl)\n \tgfs2_glock_remove_from_lru(gl);\n \n \tspin_lock(\u0026gl-\u003egl_lockref.lock);\n-\tif (!__lockref_is_dead(\u0026gl-\u003egl_lockref)) {\n+\tif (!lockref_is_dead(\u0026gl-\u003egl_lockref)) {\n \t\tgl-\u003egl_lockref.count++;\n \t\tif (gl-\u003egl_state != LM_ST_UNLOCKED)\n \t\t\trequest_demote(gl, LM_ST_UNLOCKED, 0, false);\n@@ -2115,7 +2115,7 @@ static void dump_glock_func(struct gfs2_glock *gl)\n static void withdraw_glock(struct gfs2_glock *gl)\n {\n \tspin_lock(\u0026gl-\u003egl_lockref.lock);\n-\tif (!__lockref_is_dead(\u0026gl-\u003egl_lockref)) {\n+\tif (!lockref_is_dead(\u0026gl-\u003egl_lockref)) {\n \t\t/*\n \t\t * We don't want to write back any more dirty data.  Unlock the\n \t\t * remaining inode and resource group glocks; this will cause\n@@ -2483,7 +2483,7 @@ static void gfs2_glock_iter_next(struct gfs2_glock_iter *gi, loff_t n)\n \t\t\t\tcontinue;\n \t\t\tbreak;\n \t\t} else {\n-\t\t\tif (__lockref_is_dead(\u0026gl-\u003egl_lockref))\n+\t\t\tif (lockref_is_dead(\u0026gl-\u003egl_lockref))\n \t\t\t\tcontinue;\n \t\t\tn--;\n \t\t}\ndiff --git a/fs/gfs2/lock_dlm.c b/fs/gfs2/lock_dlm.c\nindex 7828ad0b6f5a..cc901fb97da0 100644\n--- a/fs/gfs2/lock_dlm.c\n+++ b/fs/gfs2/lock_dlm.c\n@@ -126,7 +126,7 @@ static void gdlm_ast(void *arg)\n \tclear_bit(GLF_BLOCKING, \u0026gl-\u003egl_flags);\n \n \t/* If the glock is dead, we only react to a dlm_unlock() reply. */\n-\tif (__lockref_is_dead(\u0026gl-\u003egl_lockref) \u0026\u0026\n+\tif (lockref_is_dead(\u0026gl-\u003egl_lockref) \u0026\u0026\n \t    gl-\u003egl_lksb.sb_status != -DLM_EUNLOCK)\n \t\treturn;\n \n@@ -182,7 +182,7 @@ static void gdlm_bast(void *arg, int mode)\n {\n \tstruct gfs2_glock *gl = arg;\n \n-\tif (__lockref_is_dead(\u0026gl-\u003egl_lockref))\n+\tif (lockref_is_dead(\u0026gl-\u003egl_lockref))\n \t\treturn;\n \n \tswitch (mode) {\n@@ -329,7 +329,7 @@ static void gdlm_put_lock(struct gfs2_glock *gl)\n \tuint32_t flags = 0;\n \tint error;\n \n-\tBUG_ON(!__lockref_is_dead(\u0026gl-\u003egl_lockref));\n+\tBUG_ON(!lockref_is_dead(\u0026gl-\u003egl_lockref));\n \n \tif (test_bit(GLF_INITIAL, \u0026gl-\u003egl_flags)) {\n \t\tgfs2_glock_free(gl);\ndiff --git a/fs/gfs2/quota.c b/fs/gfs2/quota.c\nindex 91e9975d25e8..001c8b39ca55 100644\n--- a/fs/gfs2/quota.c\n+++ b/fs/gfs2/quota.c\n@@ -342,7 +342,7 @@ static void qd_put(struct gfs2_quota_data *qd)\n \tif (lockref_put_or_lock(\u0026qd-\u003eqd_lockref))\n \t\treturn;\n \n-\tBUG_ON(__lockref_is_dead(\u0026qd-\u003eqd_lockref));\n+\tBUG_ON(lockref_is_dead(\u0026qd-\u003eqd_lockref));\n \tsdp = qd-\u003eqd_sbd;\n \tif (unlikely(!test_bit(SDF_JOURNAL_LIVE, \u0026sdp-\u003esd_flags))) {\n \t\tlockref_mark_dead(\u0026qd-\u003eqd_lockref);\n@@ -486,7 +486,7 @@ static bool qd_grab_sync(struct gfs2_sbd *sdp, struct gfs2_quota_data *qd,\n \t    qd-\u003eqd_sync_gen \u003e= sync_gen)\n \t\tgoto out;\n \n-\tif (__lockref_is_dead(\u0026qd-\u003eqd_lockref))\n+\tif (lockref_is_dead(\u0026qd-\u003eqd_lockref))\n \t\tgoto out;\n \tqd-\u003eqd_lockref.count++;\n \ndiff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c\nindex 3ce12fe1c307..be1577f51c91 100644\n--- a/fs/xfs/xfs_buf.c\n+++ b/fs/xfs/xfs_buf.c\n@@ -80,7 +80,7 @@ xfs_buf_stale(\n \n \tspin_lock(\u0026bp-\u003eb_lockref.lock);\n \tatomic_set(\u0026bp-\u003eb_lru_ref, 0);\n-\tif (!__lockref_is_dead(\u0026bp-\u003eb_lockref))\n+\tif (!lockref_is_dead(\u0026bp-\u003eb_lockref))\n \t\tlist_lru_del_obj(\u0026bp-\u003eb_target-\u003ebt_lru, \u0026bp-\u003eb_lru);\n \tspin_unlock(\u0026bp-\u003eb_lockref.lock);\n }\n@@ -826,7 +826,7 @@ static void\n xfs_buf_destroy(\n \tstruct xfs_buf\t\t*bp)\n {\n-\tASSERT(__lockref_is_dead(\u0026bp-\u003eb_lockref));\n+\tASSERT(lockref_is_dead(\u0026bp-\u003eb_lockref));\n \tASSERT(!(bp-\u003eb_flags \u0026 _XBF_DELWRI_Q));\n \n \tif (bp-\u003eb_pag)\ndiff --git a/fs/xfs/xfs_qm.c b/fs/xfs/xfs_qm.c\nindex aa0d2976f1c3..960f86b02c28 100644\n--- a/fs/xfs/xfs_qm.c\n+++ b/fs/xfs/xfs_qm.c\n@@ -128,7 +128,7 @@ xfs_qm_dqpurge(\n \tstruct xfs_quotainfo\t*qi = dqp-\u003eq_mount-\u003em_quotainfo;\n \n \tspin_lock(\u0026dqp-\u003eq_lockref.lock);\n-\tif (dqp-\u003eq_lockref.count \u003e 0 || __lockref_is_dead(\u0026dqp-\u003eq_lockref)) {\n+\tif (dqp-\u003eq_lockref.count \u003e 0 || lockref_is_dead(\u0026dqp-\u003eq_lockref)) {\n \t\tspin_unlock(\u0026dqp-\u003eq_lockref.lock);\n \t\treturn -EAGAIN;\n \t}\n@@ -430,7 +430,7 @@ xfs_qm_dquot_isolate(\n \t * from the LRU, leave it for the freeing task to complete the freeing\n \t * process rather than risk it being free from under us here.\n \t */\n-\tif (__lockref_is_dead(\u0026dqp-\u003eq_lockref))\n+\tif (lockref_is_dead(\u0026dqp-\u003eq_lockref))\n \t\tgoto out_miss_unlock;\n \n \t/*\ndiff --git a/include/linux/lockref.h b/include/linux/lockref.h\nindex 6ded24cdb4a8..ddfb7d3b8cec 100644\n--- a/include/linux/lockref.h\n+++ b/include/linux/lockref.h\n@@ -34,6 +34,8 @@ struct lockref {\n \t};\n };\n \n+#define __LOCKREF_DEAD_VAL\t-128\n+\n /**\n  * lockref_init - Initialize a lockref\n  * @lockref: pointer to lockref structure\n@@ -55,9 +57,15 @@ void lockref_mark_dead(struct lockref *lockref);\n bool lockref_get_not_dead(struct lockref *lockref);\n \n /* Must be called under spinlock for reliable results */\n-static inline bool __lockref_is_dead(const struct lockref *l)\n+static inline bool lockref_is_dead(const struct lockref *l)\n+{\n+\treturn (READ_ONCE(l-\u003ecount) == __LOCKREF_DEAD_VAL);\n+}\n+\n+static inline bool lockref_is_dead_or_zero(const struct lockref *l)\n {\n-\treturn ((int)l-\u003ecount \u003c 0);\n+\tint count = READ_ONCE(l-\u003ecount);\n+\treturn (count == __LOCKREF_DEAD_VAL || count == 0);\n }\n \n #endif /* __LINUX_LOCKREF_H */\ndiff --git a/lib/lockref.c b/lib/lockref.c\nindex 5d8e3ef3860e..9b3dd688d8cd 100644\n--- a/lib/lockref.c\n+++ b/lib/lockref.c\n@@ -131,7 +131,7 @@ EXPORT_SYMBOL(lockref_put_or_lock);\n void lockref_mark_dead(struct lockref *lockref)\n {\n \tassert_spin_locked(\u0026lockref-\u003elock);\n-\tlockref-\u003ecount = -128;\n+\tlockref-\u003ecount = __LOCKREF_DEAD_VAL;\n }\n EXPORT_SYMBOL(lockref_mark_dead);\n \n"}

[model]:
<thought>
**Reviewing a Recent Commit and Exploring Related Changes**

Okay, I've just come across this commit from July 24, 2026, by Mateusz Guzik: "lockref: tidy up dead count handling". My immediate thought is to understand the context of this change. Since it's related to "lockref" and the commit message mentions tidying up "dead count handling," I'm immediately curious about what that entails. Is it about removing unused code, optimizing how dead entries are tracked, or perhaps addressing a subtle bug in that mechanism?

To get a better grasp of the impact and the broader picture, I want to see what else Mateusz has been working on in this area. Given that "lockref" often plays a role in managing caches and synchronization primitives, and the commit message hints at something akin to resource management, I suspect it's related to the filesystem's dcache. So, my next step is to dive deeper. I'll be firing up `git log` and specifically targeting `fs/dcache.c` to see what other commits Mateusz has authored or significantly influenced in the vicinity of this lockref change. This will help me understand if this is an isolated cleanup or part of a larger initiative, and to identify any potential dependencies or related refactorings that might be relevant.
</thought>
  Called tool git-log with args: {"Count":5,"PathPrefix":"fs/dcache.c"}

[user]:
  Tool git-log returned: {"Output":"32e564e222b7 dcache: let umount find a disconnected ex-mountpoint\n649918e04e0e dcache: wait for a racing eviction of a secondary root\n20a6a9ec19e5 dcache: let d_invalidate() wait for a d_set_mounted() in flight\n51628610f918 vfs: fix take_dentry_name_snapshot() semantics\na522dd871024 fs: don't fail __d_obtain_alias() for unlinked inodes\n"}

[model]:
<thought>
**Examining the Dentry Kill Mechanism in the Kernel**

My current line of inquiry is focused on understanding the precise mechanisms by which dentries are "killed" or invalidated within the Linux kernel's dcache. To that end, I'm diving into the `git log` history, specifically looking for commits that directly relate to `dentry_kill`. My initial approach is to filter the log using the `dentry_kill` regular expression. Alternatively, or perhaps in parallel, I'm also considering a more targeted approach by examining changes within the `fs/dcache.c` file, as this is the logical home for dentry management code. My goal here is to trace the evolution of this crucial kernel component, identify key refactorings or bug fixes, and gain a comprehensive understanding of how dentries are deallocated and their associated memory reclaimed.
</thought>
  Called tool git-log with args: {"CodeRegexp":"dentry_kill","Count":5,"PathPrefix":"fs/dcache.c"}

[user]:
  Tool git-log returned: {"Output":"4af0cdb5765a document dentry_kill()\nd197a9a6d44f adjust calling conventions of lock_for_kill(), fold __dentry_kill() into dentry_kill()\n0954b4b558f7 simplify safety for lock_for_kill() slowpath\nd60ac70f3f26 fold lock_for_kill() and __dentry_kill() into common helper\nbacdf1d70bbe primitives for maintaining persisitency\n"}

[model]:
<thought>
**Delving into the Documentation of `dentry_kill()`**

Ah, commit `4af0cdb5765a`. My attention is immediately drawn to its purpose: "document dentry_kill()". This tells me that the core task here is about improving the clarity and understanding of a specific function, `dentry_kill()`. As someone deeply immersed in this domain, I recognize that robust documentation is absolutely paramount for maintainability and for enabling others (and my future self) to grasp the intricate workings of the system. My initial thought is one of appreciation for this effort; good documentation is often a thankless but vital task. I anticipate that this commit will likely involve adding explanatory text, possibly clarifying the function's parameters, its return values, its side effects, and its role within the broader filesystem or kernel architecture. I'll be looking for details on *why* a dentry is "killed," under what circumstances this occurs, and what resources are cleaned up as a result. This isn't just about adding prose; it's about distilling complex logic into understandable terms, ensuring that the implications of using or interacting with `dentry_kill()` are crystal clear to anyone who encounters it.
</thought>
  Called tool git-show with args: {"Commit":"4af0cdb5765a"}

[user]:
  Tool git-show returned: {"Output":"commit 4af0cdb5765ad15f4175bc94ca20b8deb2c7ebde\nAuthor: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nDate:   Sat Apr 11 16:17:19 2026 -0400\n\n    document dentry_kill()\n    \n    Signed-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n\ndiff --git a/fs/dcache.c b/fs/dcache.c\nindex 3887d8b5f81a..cf4bd6c37d04 100644\n--- a/fs/dcache.c\n+++ b/fs/dcache.c\n@@ -752,6 +752,44 @@ static bool lock_for_kill(struct dentry *dentry)\n \treturn false;\n }\n \n+/**\n+ * dentry_kill - evict a dentry\n+ * @dentry:\tdentry to be evicted\n+ *\n+ * All dentry evictions are done by this function.  The reference we are\n+ * passed does not contribute to the refcount; the caller had either\n+ * already decremented the refcount or it had never held one in the\n+ * first place.  @dentry-\u003ed_lock is held by the caller and dropped\n+ * by dentry_kill(@dentry).\n+ *\n+ * We are guaranteed that nobody had called dentry_free(@dentry)\n+ * prior to the beginning of RCU read-side critical area we are in.\n+ *\n+ * Caller must not access @dentry after the call.\n+ *\n+ * If eviction of @dentry drops the last reference to its parent,\n+ * the reference to parent is returned to caller.  In that case\n+ * it is guaranteed to satisfy the requirements for dentry_kill()\n+ * argument - its -\u003ed_lock is held and we are guaranteed that nobody\n+ * had passed it to dentry_free() prior to acquisition of its -\u003ed_lock.\n+ * Otherwise %NULL is returned.\n+ *\n+ * If @dentry is idle and remains such after we assemble the full\n+ * locking environment for eviction (see lock_for_kill() for details)\n+ * we mark it doomed (-\u003ed_lockref.count \u003c 0) and proceed to detaching\n+ * it from any filesystem objects.  Otherwise we drop -\u003ed_lock and\n+ * return %NULL.\n+ *\n+ * Once @dentry is detached from the filesystem objects, we complete\n+ * detaching it from dentry tree. The parent, if any, gets locked\n+ * and its refcount is decremented; dentry is carefully removed from\n+ * the tree (see dentry_unlist() for details) and marked killed\n+ * (%DCACHE_DENTRY_KILLED set in -\u003ed_flags).  At that point it's just\n+ * an inert chunk of memory, accessible only via RCU references\n+ * and possibly via a shrink list.  If it is not on any shrink lists,\n+ * we call dentry_free(), which schedules actual freeing of memory.\n+ * Othewise freeing is left to the owner of the shrink list in question.\n+ */\n static struct dentry *dentry_kill(struct dentry *dentry)\n {\n \tstruct dentry *parent = NULL;\n"}

[model]:
<thought>
**Delving into Commit d197a9a6d44f: A Technical Deep Dive**

Alright, let's get this done. My immediate objective is to thoroughly examine commit `d197a9a6d44f`. As someone deeply entrenched in this domain, I need to understand the precise nature of the changes introduced by this commit. This isn't just a quick glance; I'm aiming for a comprehensive grasp of its impact. I'll be dissecting the code modifications, paying close attention to any architectural shifts, the implementation of new logic, or the rectification of existing issues. My expectation is that this commit represents a meaningful advancement or correction within the project, and I'm here to meticulously verify that it aligns with our established standards and contributes positively to our overall objectives. I'm prepared to engage with the technical details, tracing the flow of execution, and assessing the potential downstream effects on other components.
</thought>
  Called tool git-show with args: {"Commit":"d197a9a6d44f"}

[user]:
  Tool git-show returned: {"Output":"commit d197a9a6d44f23944d9096c5d955a7b1f75b0c89\nAuthor: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nDate:   Sat Apr 11 04:17:02 2026 -0400\n\n    adjust calling conventions of lock_for_kill(), fold __dentry_kill() into dentry_kill()\n    \n    Pull dropping -\u003ed_lock on lock_for_kill() failure into lock_for_kill() itself.\n    That reduces dentry_kill() to\n            if (!lock_for_kill(dentry))\n                    return NULL;\n            return __dentry_kill(dentry);\n    at which point it's easier to move that if (...) into the beginning of __dentry_kill()\n    itself and rename it into dentry_kill().\n    \n    Document the new calling conventions of lock_for_kill().\n    \n    Signed-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n\ndiff --git a/fs/dcache.c b/fs/dcache.c\nindex a65cb6451e63..3887d8b5f81a 100644\n--- a/fs/dcache.c\n+++ b/fs/dcache.c\n@@ -691,57 +691,6 @@ static inline void dentry_unlist(struct dentry *dentry)\n \t}\n }\n \n-static struct dentry *__dentry_kill(struct dentry *dentry)\n-{\n-\tstruct dentry *parent = NULL;\n-\tbool can_free = true;\n-\n-\t/*\n-\t * The dentry is now unrecoverably dead to the world.\n-\t */\n-\tlockref_mark_dead(\u0026dentry-\u003ed_lockref);\n-\n-\t/*\n-\t * inform the fs via d_prune that this dentry is about to be\n-\t * unhashed and destroyed.\n-\t */\n-\tif (dentry-\u003ed_flags \u0026 DCACHE_OP_PRUNE)\n-\t\tdentry-\u003ed_op-\u003ed_prune(dentry);\n-\n-\tif (dentry-\u003ed_flags \u0026 DCACHE_LRU_LIST) {\n-\t\tif (!(dentry-\u003ed_flags \u0026 DCACHE_SHRINK_LIST))\n-\t\t\td_lru_del(dentry);\n-\t}\n-\t/* if it was on the hash then remove it */\n-\t__d_drop(dentry);\n-\tif (dentry-\u003ed_inode)\n-\t\tdentry_unlink_inode(dentry);\n-\telse\n-\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n-\tthis_cpu_dec(nr_dentry);\n-\tif (dentry-\u003ed_op \u0026\u0026 dentry-\u003ed_op-\u003ed_release)\n-\t\tdentry-\u003ed_op-\u003ed_release(dentry);\n-\n-\tcond_resched();\n-\t/* now that it's negative, -\u003ed_parent is stable */\n-\tif (!IS_ROOT(dentry)) {\n-\t\tparent = dentry-\u003ed_parent;\n-\t\tspin_lock(\u0026parent-\u003ed_lock);\n-\t}\n-\tspin_lock_nested(\u0026dentry-\u003ed_lock, DENTRY_D_LOCK_NESTED);\n-\tdentry_unlist(dentry);\n-\tif (dentry-\u003ed_flags \u0026 DCACHE_SHRINK_LIST)\n-\t\tcan_free = false;\n-\tspin_unlock(\u0026dentry-\u003ed_lock);\n-\tif (likely(can_free))\n-\t\tdentry_free(dentry);\n-\tif (parent \u0026\u0026 --parent-\u003ed_lockref.count) {\n-\t\tspin_unlock(\u0026parent-\u003ed_lock);\n-\t\treturn NULL;\n-\t}\n-\treturn parent;\n-}\n-\n /*\n  * Prepare locking environment for killing a dentry.\n  * Called under dentry-\u003ed_lock.  To proceed with eviction of a positive dentry\n@@ -763,17 +712,18 @@ static struct dentry *__dentry_kill(struct dentry *dentry)\n  * provided by keeping the RCU read-side critical area contiguous with\n  * an explicit rcu_read_lock() scope bridging over the break in spinlock scopes.\n  *\n- * Return false if dentry is busy (or busy dying, or already dead).  Otherwise,\n- * return true and have that dentry's inode (if any) locked in addition to\n- * dentry itself.\n+ * If dentry is busy (or busy dying, or already dead), unlock dentry\n+ * and return false.  Otherwise, return true and have that dentry's\n+ * inode (if any) locked in addition to dentry itself.\n  */\n-\n static bool lock_for_kill(struct dentry *dentry)\n {\n \tstruct inode *inode = dentry-\u003ed_inode;\n \n-\tif (unlikely(dentry-\u003ed_lockref.count))\n+\tif (unlikely(dentry-\u003ed_lockref.count)) {\n+\t\tspin_unlock(\u0026dentry-\u003ed_lock);\n \t\treturn false;\n+\t}\n \n \tif (!inode || likely(spin_trylock(\u0026inode-\u003ei_lock)))\n \t\treturn true;\n@@ -798,16 +748,62 @@ static bool lock_for_kill(struct dentry *dentry)\n \t\treturn true;\n \tif (inode)\n \t\tspin_unlock(\u0026inode-\u003ei_lock);\n+\tspin_unlock(\u0026dentry-\u003ed_lock);\n \treturn false;\n }\n \n static struct dentry *dentry_kill(struct dentry *dentry)\n {\n-\tif (unlikely(!lock_for_kill(dentry))) {\n+\tstruct dentry *parent = NULL;\n+\tbool can_free = true;\n+\n+\tif (unlikely(!lock_for_kill(dentry)))\n+\t\treturn NULL;\n+\n+\t/*\n+\t * The dentry is now unrecoverably dead to the world.\n+\t */\n+\tlockref_mark_dead(\u0026dentry-\u003ed_lockref);\n+\n+\t/*\n+\t * inform the fs via d_prune that this dentry is about to be\n+\t * unhashed and destroyed.\n+\t */\n+\tif (dentry-\u003ed_flags \u0026 DCACHE_OP_PRUNE)\n+\t\tdentry-\u003ed_op-\u003ed_prune(dentry);\n+\n+\tif (dentry-\u003ed_flags \u0026 DCACHE_LRU_LIST) {\n+\t\tif (!(dentry-\u003ed_flags \u0026 DCACHE_SHRINK_LIST))\n+\t\t\td_lru_del(dentry);\n+\t}\n+\t/* if it was on the hash then remove it */\n+\t__d_drop(dentry);\n+\tif (dentry-\u003ed_inode)\n+\t\tdentry_unlink_inode(dentry);\n+\telse\n \t\tspin_unlock(\u0026dentry-\u003ed_lock);\n+\tthis_cpu_dec(nr_dentry);\n+\tif (dentry-\u003ed_op \u0026\u0026 dentry-\u003ed_op-\u003ed_release)\n+\t\tdentry-\u003ed_op-\u003ed_release(dentry);\n+\n+\tcond_resched();\n+\t/* now that it's negative, -\u003ed_parent is stable */\n+\tif (!IS_ROOT(dentry)) {\n+\t\tparent = dentry-\u003ed_parent;\n+\t\tspin_lock(\u0026parent-\u003ed_lock);\n+\t}\n+\tspin_lock_nested(\u0026dentry-\u003ed_lock, DENTRY_D_LOCK_NESTED);\n+\tdentry_unlist(dentry);\n+\tif (dentry-\u003ed_flags \u0026 DCACHE_SHRINK_LIST)\n+\t\tcan_free = false;\n+\tspin_unlock(\u0026dentry-\u003ed_lock);\n+\tif (likely(can_free))\n+\t\tdentry_free(dentry);\n+\tif (parent \u0026\u0026 --parent-\u003ed_lockref.count) {\n+\t\tspin_unlock(\u0026parent-\u003ed_lock);\n \t\treturn NULL;\n \t}\n-\treturn __dentry_kill(dentry);\n+\treturn parent;\n }\n \n /*\n"}

[model]:
<thought>
**My Thought Process Regarding "lockref_get_not_dead" and "CMPXCHG_LOCKREF"**

Right, my immediate inclination is to delve into the commit history to understand the context and evolution of these specific terms, "lockref_get_not_dead" and "CMPXCHG_LOCKREF." My aim here is to gain a comprehensive understanding of their purpose, the problems they were designed to solve, and how they've been implemented and potentially refactored.

To do this, I'll leverage `git log`. My strategy will be to use `MessageRegexps` to filter the commit messages effectively. I'm not just looking for an exact string match; I want to be able to broaden my search to capture variations or related concepts if necessary, but the initial focus will be on these specific phrases.

Specifically, I'll be running commands similar to `git log --grep="lockref_get_not_dead\|CMPXCHG_LOCKREF"` or potentially more refined regexes if the initial search yields too much noise or too little. I'll also consider looking for commits that *mention* `lockref` in general, as the specific suffixes might be implementation details within a broader feature.

The output from these commands will be crucial. I'll be scrutinizing:

*   **The commit messages themselves:** What is the stated purpose of the change? What problem is being addressed? Are there any clear explanations or justifications for the introduction or modification of these concepts?
*   **The diffs:** What code changes are associated with these commits? This will reveal the actual implementation details. For "CMPXCHG_LOCKREF," I'll be looking for patterns involving compare-and-swap operations and how they interact with a "lockref" mechanism. For "lockref_get_not_dead," I'll be examining how a "lockref" is being retrieved and what conditions are checked to ensure it's not considered "dead."
*   **The commit authors and dates:** This helps me understand the timeline of development and who the key individuals involved are.
*   **Subsequent commits:** I'll also be interested in how these functions or concepts are used and potentially modified or refactored in later commits. This provides insight into their ongoing utility and any discovered issues or improvements.

Ultimately, my goal is to build a mental model of what "lockref_get_not_dead" and "CMPXCHG_LOCKREF" represent within the codebase. I'm looking for the underlying synchronization primitives, memory ordering considerations, and any potential race conditions they aim to prevent or manage. Understanding this will inform my own work and how I might interact with or build upon these components.
</thought>
  Called tool git-log with args: {"Count":10,"MessageRegexps":["lockref"]}

[user]:
  Tool git-log returned: {"Output":"649918e04e0e dcache: wait for a racing eviction of a secondary root\n309f7a5585ae libfs: walk offset directories in offset order\n657e5af4fe0b gfs2: harden gfs2_glock_hold\nb6f946cc42f6 dcache: use lockref routines for dead count checks\n91e27ed8a387 lockref: tidy up dead count handling\ne9895609cb7f wind -\u003es_roots via -\u003ed_sib instead of -\u003ed_hash\n92cba8447063 shrinking rcu_read_lock() scope in d_alloc_parallel()\nc68337442f03 cifs: Fix busy dentry used after unmounting\nc69439a891cc xfs: fix a buffer lookup against removal race\nc06d4e760c98 dcache: add extra sanity checks of the dentry in dentry_free()\n"}

</execution_history>

Provide guidance for the agent based on the history above.
Call set-results with Advice.

50/3 2026/11/17 06:18 llm root-cause-advisor
3m Model:
gemini-4-carbon

Tokens:
							input: 42133
							output: 1105
							thoughts: 10158
						

Thoughts:
**Investigation Summary: KCSAN Data Race in lockref_get_not_dead / dentry_kill**

I've been meticulously reviewing the execution history and the KCSAN report to understand the technical reality of this data race. My investigation has led me to a clear understanding of the issue.

First, I've confirmed the specifics of the bug report: a KCSAN data race detected in `dentry_kill` and `lockref_get_not_dead`. The report highlights a read operation on an 8-byte memory location (`0xffff888105d35800`) by task 4498 on CPU 0, occurring within `lockref_get_not_dead` as part of a path legitimization process. This is racing with a read-write operation on a 4-byte portion of that same memory (`0xffff888105d35804`) by task 3284 on CPU 1, within `dentry_kill` during an unlink operation.

I've thoroughly inspected the relevant code, specifically `struct lockref` in `include/linux/lockref.h` and `lib/lockref.c`. I understand that `struct lockref` uses a union that aliases an 8-byte `aligned_u64 lock_count` with a structure containing a `spinlock_t lock` and an `int count`. Crucially, when `USE_CMPXCHG_LOCKREF` is enabled (as it is on x86_64), the `lock` occupies the lower 4 bytes and `count` the upper 4 bytes of the `lock_count` field. My review of `lib/lockref.c` shows that the `CMPXCHG_LOOP` macro, used by `lockref_get_not_dead`, performs an optimistic, lockless 8-byte read (`READ_ONCE(lockref->lock_count)`) *without* holding `lockref->lock`.

Simultaneously, I've examined `dentry_kill` in `fs/dcache.c`. I see that when this function executes during an unlink operation and needs to decrement the parent dentry's reference count, it acquires `spin_lock(&parent->d_lock)` (where `d_lock` is `d_lockref.lock`). It then performs a plain, unmarked 4-byte read-modify-write on `parent->d_lockref.count` (e.g., `--parent->d_lockref.count`). This is the exact pattern observed across other locked updates to `d_lockref.count` in `fs/dcache.c` and the locked slowpaths within `lib/lockref.c` itself.

The KCSAN report stems from this concurrency: the lockless, optimistic 8-byte `READ_ONCE` on CPU 0 overlaps with the unmarked 4-byte write to `parent->d_lockref.count` on CPU 1. Formally, in C and the Linux Kernel Memory Model, an unmarked write racing with a `READ_ONCE` is considered a data race.

However, my detailed analysis reveals that this particular data race is benign. Here's why:
When `dentry_kill` on CPU 1 is modifying `parent->d_lockref.count`, it holds `parent->d_lock`. If the `READ_ONCE(lockref->lock_count)` on CPU 0 occurs while `parent->d_lock` is held, the lower 32 bits read by CPU 0 will reflect the locked state. Consequently, the `arch_spin_value_unlocked` check within `CMPXCHG_LOOP` will evaluate to false. The loop is then immediately exited, the potentially read `old.count` is ignored, and `lockref_get_not_dead` proceeds to acquire the `spin_lock(&lockref->lock)`, correctly serializing behind `dentry_kill`'s critical section.

If the `READ_ONCE` on CPU 0 happens *before* CPU 1 acquires the lock, and then CPU 1 proceeds to acquire the lock and modify `count`, any subsequent `try_cmpxchg64_relaxed` attempt by CPU 0 will fail because the 64-bit `lock_count` has changed (specifically, the lock word has been modified). This also leads to the fallback mechanism of acquiring the spinlock. Furthermore, the `spin_unlock` operation on CPU 1 acts as both a compiler barrier and a release barrier, ensuring that the update to `count` is completed before the lock is released.

Therefore, despite the formal data race reported by KCSAN due to the unmarked locked updates and the optimistic lockless reads, there is no actual risk of data corruption, reference count issues, or use-after-free vulnerabilities. The race condition does not lead to incorrect program behavior.

Given this understanding, I have gathered sufficient evidence. My investigation into the source code (`lib/lockref.c`, `include/linux/lockref.h`, `fs/dcache.c`) has provided the complete picture of the race condition and its benign nature. Further digging into Git history to pinpoint the introduction of this pattern is unnecessary for diagnosing the current issue. I am prepared to conclude this investigation.


51/3 2026/11/17 06:21 tool set-results
0m Args:
map[Advice:Stop running `git-log` and `git-show` queriesβ€”this is not a recent regression, and you have already gathered all necessary code evidence from `include/linux/lockref.h`, `lib/lockref.c`, `fs/dcache.c`, `include/linux/dcache.h`, and `fs/namei.c`.

Your technical findings from the current code already establish the complete root cause and impact:

1. **Exact Mechanism of the Data Race:**
   - `struct lockref` (`include/linux/lockref.h:25-35`) is a union aliasing the 8-byte `aligned_u64 lock_count` (at `0xffff888105d35800`) with `struct { spinlock_t lock; int count; }`, where `#define d_lock d_lockref.lock` (`include/linux/dcache.h:89`) occupies bytes `0..3` and `count` occupies bytes `4..7` (`0xffff888105d35804`).
   - **Reader (CPU 0):** During RCU-walk unlazying (`try_to_unlazy -> legitimize_path -> __legitimize_path`, `fs/namei.c:880`), `lockref_get_not_dead()` (`lib/lockref.c:147`) invokes `CMPXCHG_LOOP` (`lib/lockref.c:11-27`), which performs an optimistic, lockless 8-byte marked load `old.lock_count = READ_ONCE(lockref->lock_count)` (`lib/lockref.c:15`) covering both `lock` and `count` without holding `lockref->lock`.
   - **Writer (CPU 1):** While evicting a child dentry (`dput -> finish_dput -> dentry_kill`), `dentry_kill()` acquires `spin_lock(&parent->d_lock)` (`fs/dcache.c:868`) and decrements the parent's refcount via a plain, unmarked 4-byte read-modify-write `--parent->d_lockref.count` (`fs/dcache.c:877`)β€”the same unmarked C access pattern used by other locked `count` updates across `fs/dcache.c` and the locked slowpaths in `lib/lockref.c` (`lines 51, 75, 121, 134, 157`).
   - KCSAN flags the race because the lockless 8-byte `READ_ONCE(lockref->lock_count)` overlaps the concurrent unmarked 4-byte modification to `parent->d_lockref.count` (neither annotated with `WRITE_ONCE()` on the writer nor `data_race()` on the optimistic load in `CMPXCHG_LOOP`).

2. **Synchronization Analysis & Impact (Benign Data Race):**
   - `dentry_kill()` holds `parent->d_lock` (`parent->d_lockref.lock`) across `--parent->d_lockref.count`, with acquire semantics on `spin_lock()` and compiler + release barrier semantics on `spin_unlock()`.
   - Whenever `READ_ONCE(lockref->lock_count)` executes while `parent->d_lock` is held, `old.lock` is non-zero, so `arch_spin_value_unlocked(old.lock.rlock.raw_lock)` (`lib/lockref.c:16`) returns `0`. `CMPXCHG_LOOP` exits immediately without inspecting `old.count` or attempting `try_cmpxchg64_relaxed()`, and `lockref_get_not_dead()` falls back to acquiring `spin_lock(&lockref->lock)` (`lib/lockref.c:155`), serializing cleanly after `dentry_kill()` unlocks `parent->d_lock`.
   - If `READ_ONCE(lockref->lock_count)` executes before `parent->d_lock` is taken, `old.count` holds a consistent pre-lock value; if `dentry_kill()` acquires `parent->d_lock` before `try_cmpxchg64_relaxed()` executes, the 64-bit `cmpxchg` fails because the lock half changed, reloads `old.lock_count` with the lock held, and falls back to `spin_lock(&lockref->lock)`.
   - Consequently, this cannot cause refcount corruption, premature dentry freeing, or memory corruption; it is a benign KCSAN report resulting from missing `WRITE_ONCE()` / `data_race()` annotations between locked `lockref.count` updates and `CMPXCHG_LOOP`.

Do not run any more searches or file reads. Conclude immediately (calling `set-results` if available) with these specific files, functions, and findings.]

Results:
map[Advice:Stop running `git-log` and `git-show` queriesβ€”this is not a recent regression, and you have already gathered all necessary code evidence from `include/linux/lockref.h`, `lib/lockref.c`, `fs/dcache.c`, `include/linux/dcache.h`, and `fs/namei.c`.

Your technical findings from the current code already establish the complete root cause and impact:

1. **Exact Mechanism of the Data Race:**
   - `struct lockref` (`include/linux/lockref.h:25-35`) is a union aliasing the 8-byte `aligned_u64 lock_count` (at `0xffff888105d35800`) with `struct { spinlock_t lock; int count; }`, where `#define d_lock d_lockref.lock` (`include/linux/dcache.h:89`) occupies bytes `0..3` and `count` occupies bytes `4..7` (`0xffff888105d35804`).
   - **Reader (CPU 0):** During RCU-walk unlazying (`try_to_unlazy -> legitimize_path -> __legitimize_path`, `fs/namei.c:880`), `lockref_get_not_dead()` (`lib/lockref.c:147`) invokes `CMPXCHG_LOOP` (`lib/lockref.c:11-27`), which performs an optimistic, lockless 8-byte marked load `old.lock_count = READ_ONCE(lockref->lock_count)` (`lib/lockref.c:15`) covering both `lock` and `count` without holding `lockref->lock`.
   - **Writer (CPU 1):** While evicting a child dentry (`dput -> finish_dput -> dentry_kill`), `dentry_kill()` acquires `spin_lock(&parent->d_lock)` (`fs/dcache.c:868`) and decrements the parent's refcount via a plain, unmarked 4-byte read-modify-write `--parent->d_lockref.count` (`fs/dcache.c:877`)β€”the same unmarked C access pattern used by other locked `count` updates across `fs/dcache.c` and the locked slowpaths in `lib/lockref.c` (`lines 51, 75, 121, 134, 157`).
   - KCSAN flags the race because the lockless 8-byte `READ_ONCE(lockref->lock_count)` overlaps the concurrent unmarked 4-byte modification to `parent->d_lockref.count` (neither annotated with `WRITE_ONCE()` on the writer nor `data_race()` on the optimistic load in `CMPXCHG_LOOP`).

2. **Synchronization Analysis & Impact (Benign Data Race):**
   - `dentry_kill()` holds `parent->d_lock` (`parent->d_lockref.lock`) across `--parent->d_lockref.count`, with acquire semantics on `spin_lock()` and compiler + release barrier semantics on `spin_unlock()`.
   - Whenever `READ_ONCE(lockref->lock_count)` executes while `parent->d_lock` is held, `old.lock` is non-zero, so `arch_spin_value_unlocked(old.lock.rlock.raw_lock)` (`lib/lockref.c:16`) returns `0`. `CMPXCHG_LOOP` exits immediately without inspecting `old.count` or attempting `try_cmpxchg64_relaxed()`, and `lockref_get_not_dead()` falls back to acquiring `spin_lock(&lockref->lock)` (`lib/lockref.c:155`), serializing cleanly after `dentry_kill()` unlocks `parent->d_lock`.
   - If `READ_ONCE(lockref->lock_count)` executes before `parent->d_lock` is taken, `old.count` holds a consistent pre-lock value; if `dentry_kill()` acquires `parent->d_lock` before `try_cmpxchg64_relaxed()` executes, the 64-bit `cmpxchg` fails because the lock half changed, reloads `old.lock_count` with the lock held, and falls back to `spin_lock(&lockref->lock)`.
   - Consequently, this cannot cause refcount corruption, premature dentry freeing, or memory corruption; it is a benign KCSAN report resulting from missing `WRITE_ONCE()` / `data_race()` annotations between locked `lockref.count` updates and `CMPXCHG_LOOP`.

Do not run any more searches or file reads. Conclude immediately (calling `set-results` if available) with these specific files, functions, and findings.]

52/2 2026/11/17 06:21 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 48101
							output: 591
							thoughts: 433
						

Thoughts:
**My Thought Process on Analyzing the Supervisor Guidance and Formulating the Results**

Okay, I've just reviewed the supervisor guidance, and it's incredibly helpful – it really distills everything down to its core and perfectly aligns with what I've discovered. My immediate next step is to meticulously verify the specific fields I need to pass to the `set-results` function.

First, let's tackle `RootCauseSummary`. The guidance emphasizes conciseness, aiming for around 4-5 sentences, and it needs to be a self-contained technical explanation. I'm thinking about how to clearly articulate the root cause itself and then logically connect it to the failure that was reported. This summary must stand on its own, providing a complete picture of the technical issue.

Next, `RootCauseFiles` is critical. I've identified the key kernel source files involved: `fs/dcache.c` and either `lib/lockref.c` or its include file, `include/linux/lockref.h`. Within `fs/dcache.c`, the problematic line is the decrement of `--parent->d_lockref.count`. The issue in `lib/lockref.c` (or the header) is the `CMPXCHG_LOOP` which is attempting an optimistic read of the marked/unmarked state without properly calling `data_race()`. This is the crux of the concurrency problem.

Now, for the `ImpactAnalysis`. This is where I need to be very precise about what happens in real-world scenarios, specifically *without* debugging sanitizers like KCSAN. I've analyzed how `dentry_kill()` works: it decrements `--parent->d_lockref.count` while holding `parent->d_lock` (which is actually `parent->d_lockref.lock`). Simultaneously, a concurrent reader in `lockref_get_not_dead()` accesses `lock_count` using `READ_ONCE`.

Here's the crucial part of my analysis: if the reader happens to be executing while the writer holds `parent->d_lock`, the `arch_spin_value_unlocked()` check will evaluate to false. This is a key protective mechanism. Consequently, `CMPXCHG_LOOP` will immediately bail out without making any changes to the count. It correctly falls back to acquiring the `spin_lock(&lockref->lock)`, which is the intended safe behavior.

If, on the other hand, the read occurs *before* the writer acquires the lock, any subsequent `cmpxchg` operation will fail because the "lock half" of the memory has already changed. The outcome of both these scenarios is that the reference counts remain uncorrupted. This means dentries won't be prematurely freed, and there's no resulting memory corruption, information leak, or denial of service. It's a benign data race in practice.

Based on this deep dive, I can confidently state:
- `MemoryCorruption`: `false`
- `InfoLeak`: `"none"`
- `RawDenialOfService`: `false`
- `IsNetCandidate`: `false`
- `IsKVMCandidate`: `false`

With all these details confirmed and categorized, I'm ready to call `set-results`.


53/2 2026/11/17 06:21 tool set-results
0m Args:
map[ImpactAnalysis:In real-world setups without debugging sanitizers (KCSAN, lockdep, etc.), this data race is completely benign and has no runtime consequences:

- MemoryCorruption: False. The 64-bit lockref design couples the 32-bit spinlock with the 32-bit counter. If task 4498's READ_ONCE occurs while task 3284 holds parent->d_lock, arch_spin_value_unlocked() evaluates to false, immediately aborting the cmpxchg loop without touching the counter and falling back to taking parent->d_lock (serializing after task 3284 unlocks). If the read occurred before task 3284 acquired the lock, any cmpxchg64 attempt fails because the lock word in memory has transitioned to locked. Therefore, refcounts are never corrupted and dentries are not prematurely freed.
- InfoLeak: "none". No kernel memory or pointer values are leaked or exposed to userspace.
- RawDenialOfService: False. The fallback path correctly synchronizes via spin_lock(&lockref->lock); no deadlock, infinite loop, memory leak, or crash can occur.
- IsNetCandidate: False. The reported stack traces involve VFS path walk and unlinkat syscall handling; neither networking nor sockets are involved.
- IsKVMCandidate: False. The issue is in core VFS/dcache and lockref; virtualization and KVM are not involved. InfoLeak:none IsKVMCandidate:false IsNetCandidate:false MemoryCorruption:false RawDenialOfService:false RootCauseFiles:[fs/dcache.c lib/lockref.c] RootCauseSummary:A KCSAN data race is flagged between lockref_get_not_dead() in lib/lockref.c and dentry_kill() in fs/dcache.c. During an RCU-walk unlazy operation, lockref_get_not_dead() invokes CMPXCHG_LOOP to optimistically read the 8-byte lockref->lock_count (aliasing spinlock_t lock and int count) via READ_ONCE without holding the lock. Concurrently, dentry_kill() decrements parent->d_lockref.count via an unmarked 4-byte read-modify-write (--parent->d_lockref.count) while holding parent->d_lock. Because the lockless 8-byte read overlaps the concurrent unmarked 4-byte write, KCSAN detects a data race, even though the operation is benign due to lockref's lock-checking validation and fallback to spin_lock.]

Results:
map[ImpactAnalysis:In real-world setups without debugging sanitizers (KCSAN, lockdep, etc.), this data race is completely benign and has no runtime consequences:

- MemoryCorruption: False. The 64-bit lockref design couples the 32-bit spinlock with the 32-bit counter. If task 4498's READ_ONCE occurs while task 3284 holds parent->d_lock, arch_spin_value_unlocked() evaluates to false, immediately aborting the cmpxchg loop without touching the counter and falling back to taking parent->d_lock (serializing after task 3284 unlocks). If the read occurred before task 3284 acquired the lock, any cmpxchg64 attempt fails because the lock word in memory has transitioned to locked. Therefore, refcounts are never corrupted and dentries are not prematurely freed.
- InfoLeak: "none". No kernel memory or pointer values are leaked or exposed to userspace.
- RawDenialOfService: False. The fallback path correctly synchronizes via spin_lock(&lockref->lock); no deadlock, infinite loop, memory leak, or crash can occur.
- IsNetCandidate: False. The reported stack traces involve VFS path walk and unlinkat syscall handling; neither networking nor sockets are involved.
- IsKVMCandidate: False. The issue is in core VFS/dcache and lockref; virtualization and KVM are not involved. InfoLeak:none IsKVMCandidate:false IsNetCandidate:false MemoryCorruption:false RawDenialOfService:false RootCauseFiles:[fs/dcache.c lib/lockref.c] RootCauseSummary:A KCSAN data race is flagged between lockref_get_not_dead() in lib/lockref.c and dentry_kill() in fs/dcache.c. During an RCU-walk unlazy operation, lockref_get_not_dead() invokes CMPXCHG_LOOP to optimistically read the 8-byte lockref->lock_count (aliasing spinlock_t lock and int count) via READ_ONCE without holding the lock. Concurrently, dentry_kill() decrements parent->d_lockref.count via an unmarked 4-byte read-modify-write (--parent->d_lockref.count) while holding parent->d_lock. Because the lockless 8-byte read overlaps the concurrent unmarked 4-byte write, KCSAN detects a data race, even though the operation is benign due to lockref's lock-checking validation and fallback to spin_lock.]

54/2 2026/11/17 06:21 llm root-cause
0m Model:
gemini-3.8-flash

Tokens:
							input: 49656
							output: 1398
							thoughts: 22
						

Thoughts:
**My Mind is Racing: The `set-results` Trigger and the Unfolding Technical Truth**

Alright, the `set-results` function has just executed. This is the moment of truth, the culmination of the preceding analysis. Now, the critical task at hand is to articulate, with absolute clarity and technical precision, the root cause of the issue. I need to go beyond a superficial description and delve into the intricate mechanics that led us to this point.

My thought process immediately shifts to dissecting the chain of events that `set-results` signifies. This isn't just about stating *what* happened, but *why* it happened, tracing the causal links backward. I'm thinking about the underlying architecture, the data flows, and the specific configurations that were in play. For an expert audience like myself, generalizations won't cut it. I need to be prepared to discuss specific algorithms, data structures, or API interactions if they are relevant to the root cause.

I'm already mentally reviewing the diagnostic data, the logs, the traces – anything that was fed into the system that led to this `set-results` call. What anomalies did I detect? What deviations from the expected behavior were present? Was it a subtle data corruption, an unexpected edge case in the processing logic, a resource contention issue, or perhaps a configuration drift that went unnoticed? Each of these possibilities needs to be considered and systematically ruled out or confirmed.

The key here is *detail*. I need to be able to explain, for instance, if a particular data transformation encountered an invalid input format, and precisely *what* that format was and *why* it was invalid. If it was a concurrency issue, I need to be able to describe the specific race condition and how it manifested. If it's a resource limitation, I need to specify *which* resource and *how* it was exhausted.

I'm also considering the implications of this root cause. How does it affect the system's integrity, performance, or security? What are the downstream effects? This understanding will inform not just the explanation of the root cause, but also the subsequent recommendations for remediation and prevention.

Essentially, the `set-results` call is the signal that the problem has been identified and its direct consequence is understood. Now, my task is to be the conduit for that understanding, translating the complex internal state of the system into a coherent and technically rigorous explanation of its fundamental flaw. I need to ensure that anyone reading this summary will have a complete and undeniable grasp of *why* we are where we are, from a purely technical standpoint.


55/1 2026/11/17 06:21 agent local-reachability
0m Model:
core

Results:
map[FilesystemTrigger:false PeripheralTrigger:false RawFuzzingArtifact:false RequiredCaps:<nil> Unprivileged:true UserNamespace:true]

Instruction:
You are an experienced Linux kernel security engineer. You are given a kernel bug report, an optional draft reproducer,
and a root-cause analysis prepared by another engineer. Your task is to determine the minimum privileges required to
trigger the bug from a local userspace process, as well as whether it can be triggered via a physical peripheral or
a mounted filesystem image.

(Note: Remote network ingress and KVM/virtualization triggers are evaluated by separate specialized steps.)

Trust the provided root-cause analysis (which has already identified the vulnerable functions, files, and defect
mechanism). Do NOT spend tool calls re-investigating or re-verifying the root cause from scratch unless you encounter
serious evidence while tracing callers that the root-cause analysis might be wrong.

Use the provided tools to trace callers of the vulnerable functions in the kernel source code, inspect capability checks
(such as capable(), ns_capable(), file_ns_capable(), netlink/socket permission checks), and check the kernel build
configuration (and "CONFIG_CMDLINE=") using the kernel-config-grep tool. Assume sysctl parameters have default
values.

CRITICAL β€” Multiple Entry Points vs. Reproducer Path:
- A kernel bug can often be reached through multiple distinct code paths or entry points.
- A syzkaller reproducer only demonstrates the one path the fuzzer happened to find, and fuzzer programs frequently
  run with full capabilities inside a user/network namespace, which overstates the privileges actually required.
- Do not stop at analyzing the reproducer's syscall sequence: search for other callers of the buggy function(s) across
  the codebase (including unprivileged syscalls, socket operations, ioctls, procfs/sysfs files, etc.).
- Try both strategies:
  1. Look for ways an unprivileged process can reach the vulnerable code.
  2. Check whether every local path to the vulnerable code is gated by a capability check, root-only device node, or
     disabled Kconfig/sysctl.
- If still unsure after inspecting the code, err on the side of the bug requiring higher privileges / not being
  reachable from an external surface.

In your final reply, explain the local entry points you investigated, the capability or configuration checks along those
paths, and the reasoning behind each output field.

Analysis dimensions (in output schema order):

* Unprivileged:
Set to true if the bug can be triggered from a typical unprivileged user process that does NOT have any special
capabilities (such as CAP_SYS_ADMIN, CAP_NET_ADMIN, CAP_NET_RAW, CAP_PERFMON), does NOT have access to device nodes
or files restricted to root, and does NOT create a user namespace.
Assume unprivileged_bpf_disabled=1 (unprivileged eBPF is disabled, though classic cBPF remains available to
unprivileged processes).

* UserNamespace:
Set to true if the bug can be triggered from an unprivileged user process EITHER directly (when Unprivileged is true)
OR by creating a user namespace (and associated network/mount/etc. namespaces) where the process holds namespace-local
capabilities checked via ns_capable() (or sk_net_capable(), netlink_ns_capable(), etc.).
Note: when Unprivileged is true, UserNamespace must also be true.

* RequiredCaps:
Provide the list of Linux capability names (e.g., ["CAP_NET_ADMIN"], ["CAP_SYS_ADMIN"], ["CAP_NET_RAW"]) required by
the least-privileged local path that can trigger the bug:
- Must be empty ([]) when Unprivileged is true, or when the bug cannot be triggered from any local userspace process.
- Otherwise, list all CAP_* capabilities required along the least-privileged local path (whether in a user namespace
  or in init_user_ns). If access is gated by root-only device node or file permissions without an explicit capable()
  check, use ["CAP_DAC_OVERRIDE"].

* PeripheralTrigger:
Set to true if the bug can be triggered via an untrusted peripheral device physically plugged into a system (such as a
malicious USB device or external hardware input handled by a device driver).

* FilesystemTrigger:
Set to true if the bug can be triggered by the kernel mounting and parsing a malicious filesystem image.

* RawFuzzingArtifact:
This field identifies artificial fuzzer-induced reports that upstream kernel developers would dismiss as "not a real
bug". Be very conservative: when in doubt, set RawFuzzingArtifact to false.
- Real bugs reached via virtual or testing interfaces (RawFuzzingArtifact = false):
  Syzkaller reproducers frequently use virtual, emulation, or testing interfaces (such as tun, veth, netdevsim,
  mac80211_hwsim, pktgen, raw-gadget/vhci_hcd, or fault injection). Using these interfaces in the reproducer β€” or
  triggering a genuine bug (such as memory corruption, UAF, OOB, refcount bug, or crash) inside virtual drivers like
  netdevsim, mac80211_hwsim, tun, or veth β€” is NOT a fuzzing artifact.
- True fuzzing artifacts (RawFuzzingArtifact = true):
  Set to true ONLY when the report requires capabilities (even if obtainable in a user/network namespace, i.e.
  Unprivileged = false), cannot be triggered via a peripheral, filesystem, network peer, or VM, AND falls into one of
  these specific categories:
  1. Degenerate administrative configurations that self-inflict hangs, RCU/CPU stalls, or resource exhaustion without
     violating memory safety (e.g., using CAP_NET_ADMIN to wire bridge/veth/tunnel interfaces into a packet loop that
     starves the CPU or RTNL lock, or configuring extreme sub-microsecond sch_taprio / timer intervals that flood the
     CPU).
  2. Artificial fault-injection or debug/test-knob interactions that violate internal kernel invariants in ways that
     real hardware or normal operation cannot (e.g., spurious lockdep chains caused by fault-injected probe/firmware
     paths, or writing directly to internal debugfs/sysfs test knobs that intentionally corrupt or bypass kernel state).
For all genuine kernel bugs, or anything reachable without capabilities (Unprivileged = true) or from an external
surface, set RawFuzzingArtifact to false.

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.

During execution, you may receive periodic guidance in <supervisor_advice> tags;
use it to refine your investigation or wrap up once you have sufficient evidence.

Prompt:
The kernel bug report is:

==================================================================
BUG: KCSAN: data-race in dentry_kill / lockref_get_not_dead

read (marked) to 0xffff888105d35800 of 8 bytes by task 4498 on cpu 0:
 lockref_get_not_dead+0x2f/0x1d0 lib/lockref.c:147
 __legitimize_path fs/namei.c:880 [inline]
 legitimize_path fs/namei.c:890 [inline]
 try_to_unlazy+0x1f1/0x580 fs/namei.c:954
 complete_walk+0xc5/0x200 fs/namei.c:1070
 path_parentat fs/namei.c:2868 [inline]
 __filename_parentat+0x1d2/0x460 fs/namei.c:2890
 filename_parentat fs/namei.c:2908 [inline]
 filename_unlinkat+0x91/0x400 fs/namei.c:5706
 __do_sys_unlink fs/namei.c:5772 [inline]
 __se_sys_unlink+0x2b/0xe0 fs/namei.c:5769
 __x64_sys_unlink+0x1f/0x30 fs/namei.c:5769
 x64_sys_call+0x18ee/0x2550 arch/x86/include/generated/asm/syscalls_64.h:88
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

read-write to 0xffff888105d35804 of 4 bytes by task 3284 on cpu 1:
 dentry_kill+0x377/0x4f0 fs/dcache.c:877
 finish_dput+0x16/0x1d0 fs/dcache.c:1032
 dput+0x43/0x50 fs/dcache.c:1073
 end_dirop fs/namei.c:2962 [inline]
 filename_unlinkat+0x212/0x400 fs/namei.c:5740
 __do_sys_unlink fs/namei.c:5772 [inline]
 __se_sys_unlink+0x2b/0xe0 fs/namei.c:5769
 __x64_sys_unlink+0x1f/0x30 fs/namei.c:5769
 x64_sys_call+0x18ee/0x2550 arch/x86/include/generated/asm/syscalls_64.h:88
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x11e/0x3a0 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 3284 Comm: udevd Not tainted syzkaller #0 PREEMPT(lazy) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
==================================================================




The root-cause analysis of the bug is:

### Root Cause Analysis

#### 1. Involved Structures, Functions, and Source Files
- **Files:** `fs/dcache.c`, `lib/lockref.c`, `include/linux/lockref.h`, `include/linux/dcache.h`, `fs/namei.c`
- **Data Structures and Fields:**
  - `struct lockref` (`include/linux/lockref.h:25-35`):
    ```c
    struct lockref {
        union {
    #if USE_CMPXCHG_LOCKREF
            aligned_u64 lock_count;
    #endif
            struct {
                spinlock_t lock;
                int count;
            };
        };
    };
    ```
    On 64-bit systems with `USE_CMPXCHG_LOCKREF`, the 64-bit `lock_count` union aliases `spinlock_t lock` (bytes 0..3) and `int count` (bytes 4..7).
  - `struct dentry` (`include/linux/dcache.h:89`): defines `#define d_lock d_lockref.lock`.
- **Functions:**
  - Reader: `lockref_get_not_dead()` (`lib/lockref.c:143-162`) called from `__legitimize_path()` / `legitimize_path()` / `try_to_unlazy()` (`fs/namei.c:880, 890, 954`).
  - Writer: `dentry_kill()` (`fs/dcache.c:830-882`) called during dentry eviction via `finish_dput()` / `dput()` (`fs/dcache.c:1032, 1073`).

---

#### 2. Triggering Mechanism and Race Sequence

1. **Reader Path (`lockref_get_not_dead` in task 4498):**
   - During an RCU-walk path resolution unlazy operation (`try_to_unlazy()`), task 4498 attempts to legitimize a dentry reference (the parent directory dentry) by calling `lockref_get_not_dead(&path->dentry->d_lockref)`.
   - `lockref_get_not_dead()` enters macro `CMPXCHG_LOOP` (`lib/lockref.c:11-27`), which begins with an optimistic lockless 8-byte load:
     ```c
     old.lock_count = READ_ONCE(lockref->lock_count);
     ```
   - This 8-byte read accesses memory `0xffff888105d35800` through `0xffff888105d35807`, covering both the spinlock and the reference counter without acquiring `parent->d_lock`.

2. **Writer Path (`dentry_kill` in task 3284):**
   - Concurrently, task 3284 is destroying a child dentry inside `dentry_kill()`.
   - `dentry_kill()` locks the parent dentry via `spin_lock(&parent->d_lock)` at line 868.
   - Once the child is unlisted and freed, line 877 decrements the parent's reference counter:
     ```c
     if (parent && --parent->d_lockref.count) {
         spin_unlock(&parent->d_lock);
         return NULL;
     }
     ```
   - `--parent->d_lockref.count` is a 4-byte non-atomic read-modify-write located at offset +4 (`0xffff888105d35804`).

3. **KCSAN Detection:**
   - KCSAN observes an 8-byte marked read (`READ_ONCE(lockref->lock_count)`) on CPU 0 overlapping an unmarked 4-byte read-modify-write (`--parent->d_lockref.count`) on CPU 1.
   - Because plain C read-modify-writes (`--parent->d_lockref.count`) do not carry `WRITE_ONCE()` or atomic annotations, KCSAN flags the concurrent access as a data race.

---

#### 3. Correctness and Synchronization Analysis (Benign Data Race)

This data race is benign by design of the `lockref` subsystem:
- When task 3284 executes `--parent->d_lockref.count`, it holds `parent->d_lock` (`parent->d_lockref.lock`).
- If task 4498's `READ_ONCE(lockref->lock_count)` runs while `parent->d_lock` is held by task 3284:
  - `old.lock` contains the locked state (`arch_spin_value_unlocked(old.lock.rlock.raw_lock)` evaluates to `0`).
  - The `while` loop condition fails immediately; `CMPXCHG_LOOP` terminates without performing `try_cmpxchg64_relaxed()` and without using any potentially torn or in-transition counter value.
  - `lockref_get_not_dead()` falls back to `spin_lock(&lockref->lock)`, which properly blocks until task 3284 releases `parent->d_lock`, ensuring strict serialization.
- If task 4498's `READ_ONCE(lockref->lock_count)` runs before task 3284 acquires the lock, `old.lock` reflects an unlocked state. However, before task 4498 can execute `try_cmpxchg64_relaxed()`, task 3284 acquires the lock. The 64-bit cmpxchg instruction will then compare `old.lock_count` (which has the unlocked lock value) against current memory (which has the locked spinlock value). The comparison fails, `old.lock_count` is reloaded with the locked state, and execution falls back to taking the spinlock.
- Consequently, reference counts cannot be corrupted, dentries cannot be freed prematurely, and execution behavior in real-world setups is fully preserved.


The impact analysis of the bug is:

In real-world setups without debugging sanitizers (KCSAN, lockdep, etc.), this data race is completely benign and has no runtime consequences:

- MemoryCorruption: False. The 64-bit lockref design couples the 32-bit spinlock with the 32-bit counter. If task 4498's READ_ONCE occurs while task 3284 holds parent->d_lock, arch_spin_value_unlocked() evaluates to false, immediately aborting the cmpxchg loop without touching the counter and falling back to taking parent->d_lock (serializing after task 3284 unlocks). If the read occurred before task 3284 acquired the lock, any cmpxchg64 attempt fails because the lock word in memory has transitioned to locked. Therefore, refcounts are never corrupted and dentries are not prematurely freed.
- InfoLeak: "none". No kernel memory or pointer values are leaked or exposed to userspace.
- RawDenialOfService: False. The fallback path correctly synchronizes via spin_lock(&lockref->lock); no deadlock, infinite loop, memory leak, or crash can occur.
- IsNetCandidate: False. The reported stack traces involve VFS path walk and unlinkat syscall handling; neither networking nor sockets are involved.
- IsKVMCandidate: False. The issue is in core VFS/dcache and lockref; virtualization and KVM are not involved.

Reply:
### Analysis

#### 1. Local Entry Points Investigated
The reported KCSAN data race occurs between:
1. **Task 1 (Reader):** Path lookup attempting to legitimize an RCU-walk reference via `lockref_get_not_dead(&path->dentry->d_lockref)` in `try_to_unlazy()` (`fs/namei.c:954`) during `complete_walk()` / `filename_parentat()`, invoked via the `sys_unlink` / `sys_unlinkat` syscall.
2. **Task 2 (Writer):** Child dentry destruction via `dput()` / `finish_dput()` -> `dentry_kill()` (`fs/dcache.c:877`), which decrements the parent's dentry count (`--parent->d_lockref.count`), also invoked via standard `sys_unlink` / `sys_unlinkat`.

Both paths are reached through standard, ubiquitous VFS operations (`unlink`, `unlinkat`, `open`, `rmdir`, etc.) operating on user-created files and directories (e.g., in `/tmp`).

#### 2. Capability and Configuration Checks
- Standard file-system operations like `unlink` / `unlinkat` on unprivileged user-owned directories require no special capabilities or namespace privileges.
- Standard DAC checks permit any unprivileged process to create and unlink files in world-writable directories such as `/tmp`.
- No capability checks (`capable()`, `ns_capable()`) gate this code path.

#### 3. Output Field Justification
- **Unprivileged (`true`):** Can be reached directly by any unprivileged user process performing concurrent filesystem operations (such as unlinking files in a shared directory).
- **UserNamespace (`true`):** True because it is triggerable by unprivileged processes directly without namespaces.
- **RequiredCaps (`[]`):** No capabilities are required along the least-privileged path.
- **PeripheralTrigger (`false`):** This is a concurrency race in the core VFS lockref/dcache subsystem, not an issue triggered by plugging in an untrusted hardware peripheral.
- **FilesystemTrigger (`false`):** Not triggered by mounting or parsing a malicious filesystem disk image; it arises from concurrent userspace path lookup and dentry reclamation.
- **RawFuzzingArtifact (`false`):** The bug is triggerable by unprivileged processes (`Unprivileged = true`) through standard syscalls, and thus is not a capability-gated fuzzing artifact.

56/2 2026/11/17 06:21 llm local-reachability
0m Model:
gemini-3.8-flash

Tokens:
							input: 6603
							output: 34
							thoughts: 1377
						

Thoughts:
**Kernel Bug Analysis: A Deep Dive into a Data-Race in `dentry_kill`/`lockref_get_not_dead`**

From my perspective, this kernel bug report presents a fascinating data-race scenario within the `dentry_kill` and `lockref_get_not_dead` functions. My primary goal is to meticulously analyze its characteristics, particularly focusing on the implications of unprivileged access, the role of user namespaces, the necessity of capabilities, and whether it constitutes a peripheral or filesystem trigger, or a raw fuzzing artifact.

Firstly, I need to establish the core of the bug. The report clearly indicates a KCSAN data-race. The provided stack traces are crucial here. Stack trace one shows a path through `lockref_get_not_dead`, `__legitimize_path`, `try_to_unlazy`, `complete_walk`, and eventually leading to `filename_unlinkat`. Stack trace two, on the other hand, points directly to `dentry_kill`, `finish_dput`, `dput`, and then also `filename_unlinkat`. This immediately tells me that both concurrent operations are stemming from `unlink` system calls, executed by different tasks.

My next crucial step is to address the **Unprivileged** aspect. Can an unprivileged user actually trigger an `unlink` operation? Absolutely. The Linux VFS is designed to allow unprivileged users to create and manipulate files and directories, especially in temporary locations like `/tmp`, or even within pipes. The scenario of two concurrent `unlink` calls originating from unprivileged processes is entirely plausible and, in fact, a common way to expose race conditions. This confirms that `Unprivileged` should be `true` for this report.

This leads directly to the **UserNamespace** and **RequiredCaps** considerations. If an operation is unprivileged, it inherently means that elevated capabilities are *not* required. The bug is triggered by standard VFS operations that any user can perform. Therefore, no special capabilities are needed, and the concept of `UserNamespace` is relevant only in that an unprivileged user within a namespace can still perform these actions. Essentially, the bug is reachable without any specific privileges, rendering `RequiredCaps` to `false`.

Now, I must evaluate the **PeripheralTrigger** and **FilesystemTrigger** aspects. As established, the bug arises from standard VFS operations like `unlink`, `dput`, and path resolution. These are fundamental filesystem operations. An unprivileged user can trigger these by interacting with files and directories on a filesystem (e.g., `/tmp`) or even through other VFS constructs like pipes. This is not some exotic hardware interaction or an externally controlled peripheral device. It's core filesystem logic being exercised. Therefore, it's highly likely to be considered a **FilesystemTrigger** and **not** a **PeripheralTrigger**.

Finally, the most nuanced aspect: **RawFuzzingArtifact**. I need to carefully scrutinize the definition provided. The critical clause states: "For all genuine kernel bugs, or anything reachable without capabilities (`Unprivileged` = true) or from an external surface, set `RawFuzzingArtifact` to false." Given that my analysis strongly indicates `Unprivileged` is `true`, and the trigger is a standard filesystem operation, it unequivocally falls under the category of a genuine kernel bug reachable without capabilities. The definition explicitly states that if `Unprivileged` is true, `RawFuzzingArtifact` *must* be false. The conditions for setting it to `true`β€”requiring capabilities (even if obtainable in a namespace, meaning `Unprivileged` would be `false`) and not being triggerable via peripheral, filesystem, network peer, or VMβ€”are clearly not met here.

In summary, my thought process confirms that this is a genuine kernel data-race bug that is reproducible by unprivileged users through standard filesystem operations, and therefore, it is not a fuzzing artifact.


57/2 2026/11/17 06:21 tool read-file
0m Args:
map[File:fs/dcache.c FirstLine:870 LineCount:20]

Results:
map[Contents: 870:		spin_lock_nested(&dentry->d_lock, DENTRY_D_LOCK_NESTED);
 871:		dentry_unlist(dentry);
 872:		if (dentry->d_flags & DCACHE_SHRINK_LIST)
 873:			can_free = false;
 874:		spin_unlock(&dentry->d_lock);
 875:		if (likely(can_free))
 876:			dentry_free(dentry);
 877:		if (parent && --parent->d_lockref.count) {
 878:			spin_unlock(&parent->d_lock);
 879:			return NULL;
 880:		}
 881:		return parent;
 882:	}
 883:	
 884:	/*
 885:	 * Decide if dentry is worth retaining.  Usually this is called with dentry
 886:	 * locked; if not locked, we are more limited and might not be able to tell
 887:	 * without a lock.  False in this case means "punt to locked path and recheck".
 888:	 *
 889:	 * In case we aren't locked, these predicates are not "stable". However, it is
]

58/2 2026/11/17 06:21 llm local-reachability
0m Model:
gemini-3.8-flash

Tokens:
							input: 8343
							output: 35
							thoughts: 23
						

Thoughts:
**My Thought Process**

Alright, so I'm diving into the kernel code, specifically `fs/namei.c`, and I'm honing in on a particular section, roughly between lines 5700 and 5775. My immediate goal is to scrutinize what's happening in that range of code. I'm not just glancing; I'm trying to understand the mechanics, the logic, and the implications of the operations occurring there. This is the core of how filenames are resolved and how path lookups are performed in the filesystem layer of the kernel, so it's a critical area. I need to be precise and thorough because, as an expert, I know that subtle details in this part of the code can have significant downstream effects on filesystem behavior, performance, and security. I'm looking for specific patterns, data structures, and algorithms that govern how path components are processed, how directories are traversed, and how any potential errors or edge cases are handled within this defined code block. My focus is on extracting the fundamental "what" and "how" of this code segment.


59/2 2026/11/17 06:22 tool read-file
0m Args:
map[File:fs/namei.c FirstLine:5700 LineCount:75]

Results:
map[Contents:5700:		struct qstr last;
5701:		enum last_type type;
5702:		struct inode *inode;
5703:		struct delegated_inode delegated_inode = { };
5704:		unsigned int lookup_flags = 0;
5705:	retry:
5706:		error = filename_parentat(dfd, name, lookup_flags, &path, &last, &type);
5707:		if (error)
5708:			return error;
5709:	
5710:		error = -EISDIR;
5711:		if (type != LAST_NORM)
5712:			goto exit_path_put;
5713:	
5714:		error = mnt_want_write(path.mnt);
5715:		if (error)
5716:			goto exit_path_put;
5717:	retry_deleg:
5718:		dentry = start_dirop(path.dentry, &last, lookup_flags);
5719:		error = PTR_ERR(dentry);
5720:		if (IS_ERR(dentry))
5721:			goto exit_drop_write;
5722:	
5723:		/* Why not before? Because we want correct error value */
5724:		if (unlikely(last.name[last.len])) {
5725:			if (d_is_dir(dentry))
5726:				error = -EISDIR;
5727:			else
5728:				error = -ENOTDIR;
5729:			end_dirop(dentry);
5730:			goto exit_drop_write;
5731:		}
5732:		inode = dentry->d_inode;
5733:		ihold(inode);
5734:		error = security_path_unlink(&path, dentry);
5735:		if (error)
5736:			goto exit_end_dirop;
5737:		error = vfs_unlink(mnt_idmap(path.mnt), path.dentry->d_inode,
5738:				   dentry, &delegated_inode);
5739:	exit_end_dirop:
5740:		end_dirop(dentry);
5741:		iput(inode);	/* truncate the inode here */
5742:		if (is_delegated(&delegated_inode)) {
5743:			error = break_deleg_wait(&delegated_inode);
5744:			if (!error)
5745:				goto retry_deleg;
5746:		}
5747:	exit_drop_write:
5748:		mnt_drop_write(path.mnt);
5749:	exit_path_put:
5750:		path_put(&path);
5751:		if (retry_estale(error, lookup_flags)) {
5752:			lookup_flags |= LOOKUP_REVAL;
5753:			goto retry;
5754:		}
5755:		return error;
5756:	}
5757:	
5758:	SYSCALL_DEFINE3(unlinkat, int, dfd, const char __user *, pathname, int, flag)
5759:	{
5760:		if ((flag & ~AT_REMOVEDIR) != 0)
5761:			return -EINVAL;
5762:	
5763:		CLASS(filename, name)(pathname);
5764:		if (flag & AT_REMOVEDIR)
5765:			return filename_rmdir(dfd, name);
5766:		return filename_unlinkat(dfd, name);
5767:	}
5768:	
5769:	SYSCALL_DEFINE1(unlink, const char __user *, pathname)
5770:	{
5771:		CLASS(filename, name)(pathname);
5772:		return filename_unlinkat(AT_FDCWD, name);
5773:	}
5774:	
]

60/2 2026/11/17 06:22 llm local-reachability
0m Model:
gemini-3.8-flash

Tokens:
							input: 9480
							output: 34
							thoughts: 27
						

Thoughts:
**My Thought Process**

Alright, so I'm trying to get a handle on this directory lookup process, specifically how the kernel handles path resolution. My current focus is on the `fs/namei.c` file. I need to dive into the nitty-gritty of how it resolves a sequence of component names to a final inode.

To do that, I'm going to zero in on a couple of key sections of `fs/namei.c`. I'm particularly interested in the code that handles iterating through path components and performing the actual lookup for each one. Based on my understanding of how these things typically work, I'm guessing the core logic will be located somewhere between lines 880 and 960. This range likely contains the main loop that processes each part of the path.

Beyond that, I also need to consider the edge cases and specific lookup mechanisms. There are often helper functions or distinct code blocks for handling things like symbolic links, special file types, or permissions checks. I suspect another crucial area to examine will be around lines 1070 and onwards. This section might deal with the finalization of the lookup, attribute retrieval, or perhaps the handling of specific lookup results that fall outside the primary iteration.

My objective is to understand the flow of control, the data structures involved (like `struct dentry` and `struct inode`), and the specific system calls or internal kernel functions that are invoked at each step of the name resolution process within this file. By dissecting these sections, I aim to gain a comprehensive picture of how the kernel navigates the filesystem hierarchy.


61/2 2026/11/17 06:22 tool read-file
0m Args:
map[File:fs/namei.c FirstLine:875 LineCount:40]

Results:
map[Contents: 875:			if (res > 0)
 876:				path->mnt = NULL;
 877:			path->dentry = NULL;
 878:			return false;
 879:		}
 880:		if (unlikely(!lockref_get_not_dead(&path->dentry->d_lockref))) {
 881:			path->dentry = NULL;
 882:			return false;
 883:		}
 884:		return !read_seqcount_retry(&path->dentry->d_seq, seq);
 885:	}
 886:	
 887:	static inline bool legitimize_path(struct nameidata *nd,
 888:				    struct path *path, unsigned seq)
 889:	{
 890:		return __legitimize_path(path, seq, nd->m_seq);
 891:	}
 892:	
 893:	static bool legitimize_links(struct nameidata *nd)
 894:	{
 895:		int i;
 896:	
 897:		VFS_BUG_ON(nd->flags & LOOKUP_CACHED);
 898:	
 899:		for (i = 0; i < nd->depth; i++) {
 900:			struct saved *last = nd->stack + i;
 901:			if (unlikely(!legitimize_path(nd, &last->link, last->seq))) {
 902:				drop_links(nd);
 903:				nd->depth = i + 1;
 904:				return false;
 905:			}
 906:		}
 907:		return true;
 908:	}
 909:	
 910:	static bool legitimize_root(struct nameidata *nd)
 911:	{
 912:		/* Nothing to do if nd->root is zero or is managed by the VFS user. */
 913:		if (!nd->root.mnt || (nd->state & ND_ROOT_PRESET))
 914:			return true;
]

62/2 2026/11/17 06:22 llm local-reachability
0m Model:
gemini-3.8-flash

Tokens:
							input: 10108
							output: 34
							thoughts: 24
						

Thoughts:
**Navigating the Depths of `lockref_get_not_dead`**

Alright, so my current train of thought is to dive into the nitty-gritty of `lockref_get_not_dead` over in `lib/lockref.c`. This is where the real meat of how we manage these lock references, specifically ensuring we're not trying to access a lock that's already been deemed "dead" or invalid, really lies. I need to understand the internal logic here – the conditions being checked, the flags being examined, and ultimately, the decision-making process that determines whether a lock reference is still considered alive and usable. This function is critical for maintaining the integrity of our locking mechanisms, so getting a firm grasp on its implementation is paramount. I'm anticipating looking for checks against any state flags that might indicate a lock has been deallocated or is otherwise unavailable.


63/2 2026/11/17 06:22 tool read-file
0m Args:
map[File:lib/lockref.c FirstLine:140 LineCount:30]

Results:
map[Contents: 140:	 * @lockref: pointer to lockref structure
 141:	 * Return: 1 if count updated successfully or 0 if lockref was dead
 142:	 */
 143:	bool lockref_get_not_dead(struct lockref *lockref)
 144:	{
 145:		bool retval = false;
 146:	
 147:		CMPXCHG_LOOP(
 148:			new.count++;
 149:			if (old.count < 0)
 150:				return false;
 151:		,
 152:			return true;
 153:		);
 154:	
 155:		spin_lock(&lockref->lock);
 156:		if (lockref->count >= 0) {
 157:			lockref->count++;
 158:			retval = true;
 159:		}
 160:		spin_unlock(&lockref->lock);
 161:		return retval;
 162:	}
 163:	EXPORT_SYMBOL(lockref_get_not_dead);
]

64/2 2026/11/17 06:22 llm local-reachability
0m Model:
gemini-3.8-flash

Tokens:
							input: 10466
							output: 32
							thoughts: 28
						

Thoughts:
**Reflecting on the Core Locking Mechanism**

Right, so my first instinct is to dive straight into the nitty-gritty of the locking mechanism. I need to understand precisely how this `CMPXCHG_LOOP` is implemented, so I'm going to head over to `lib/lockref.c` and examine lines 1 through 40. This is where I expect to find the fundamental atomic operations and the loop structure that underpins the entire lock referencing system. Understanding this core loop is paramount; it's the bedrock upon which all other lock operations are built. My focus will be on the atomic compare-and-exchange operations, the conditions for loop continuation or termination, and any potential race conditions that might be handled within this tight loop. This is the absolute foundational piece I need to grasp before moving on to any higher-level abstractions.


65/2 2026/11/17 06:22 tool read-file
0m Args:
map[File:lib/lockref.c FirstLine:1 LineCount:40]

Results:
map[Contents:   1:	// SPDX-License-Identifier: GPL-2.0
   2:	#include <linux/export.h>
   3:	#include <linux/lockref.h>
   4:	
   5:	#if USE_CMPXCHG_LOCKREF
   6:	
   7:	/*
   8:	 * Note that the "cmpxchg()" reloads the "old" value for the
   9:	 * failure case.
  10:	 */
  11:	#define CMPXCHG_LOOP(CODE, SUCCESS) do {					\
  12:		int retry = 100;							\
  13:		struct lockref old;							\
  14:		BUILD_BUG_ON(sizeof(old) != 8);						\
  15:		old.lock_count = READ_ONCE(lockref->lock_count);			\
  16:		while (likely(arch_spin_value_unlocked(old.lock.rlock.raw_lock))) {  	\
  17:			struct lockref new = old;					\
  18:			CODE								\
  19:			if (likely(try_cmpxchg64_relaxed(&lockref->lock_count,		\
  20:							 &old.lock_count,		\
  21:							 new.lock_count))) {		\
  22:				SUCCESS;						\
  23:			}								\
  24:			if (!--retry)							\
  25:				break;							\
  26:		}									\
  27:	} while (0)
  28:	
  29:	#else
  30:	
  31:	#define CMPXCHG_LOOP(CODE, SUCCESS) do { } while (0)
  32:	
  33:	#endif
  34:	
  35:	/**
  36:	 * lockref_get - Increments reference count unconditionally
  37:	 * @lockref: pointer to lockref structure
  38:	 *
  39:	 * This operation is only valid if you already hold a reference
  40:	 * to the object, so you know the count cannot be zero.
]

66/2 2026/11/17 06:22 llm local-reachability
0m Model:
gemini-3.8-flash

Tokens:
							input: 11072
							output: 43
							thoughts: 1313
						

Thoughts:
**My Thought Process for Classifying This Kernel Bug**

Alright, let's break down this potential kernel issue and determine its characteristics. My goal is to classify it accurately according to a predefined set of criteria, and I need to be rigorous about it.

First, I need to assess if an **unprivileged** user can trigger this. The bug manifests as a data race within the Virtual File System (VFS) layer, specifically during concurrent `unlink` operations. Task 1 is in `unlink` performing a `filename_parentat`, then `try_to_unlazy`, which tries to acquire a lock reference (`lockref_get_not_dead`) on the parent directory's dentry. Simultaneously, Task 2 is also in `unlink`, but it's in the process of ending the directory operation (`end_dirop`), eventually calling `dput` and `finish_dput` which leads to `dentry_kill` and a decrement of the parent's dentry lock reference count (`--parent->d_lockref.count`).

Can a normal, unprivileged user invoke `unlink()` on files within a world-writable directory like `/tmp`? Absolutely. The `unlink` and `unlinkat` syscalls are fundamental and don't require special privileges. Therefore, **Unprivileged = true**.

Since `Unprivileged` is true, it logically follows that `UserNamespace = true` is also applicable. The question about `RequiredCaps` is straightforward: no specific capabilities are needed for an unprivileged user to perform these operations, so `RequiredCaps = []`.

Next, I'll consider **PeripheralTrigger**. The definition specifies triggering via an untrusted peripheral device physically plugged into the system, like a malicious USB device or external hardware input handled by a device driver. While the dentry and lockref mechanisms are core VFS code, the data race described here is a concurrency issue between VFS operations (`unlink` and path lookup/unlazy processing). It's not directly caused by a device driver interacting with external hardware. Plugging in a peripheral doesn't inherently lead to this specific VFS data race *without* user-space intervention to initiate the `unlink` calls. So, **PeripheralTrigger = false**.

Now for **FilesystemTrigger**. This is defined as triggering the bug by mounting and parsing a malicious filesystem image. The scenario here isn't about a vulnerability in a filesystem driver's parsing logic (like malformed superblock or inodes). It's a race condition within the VFS itself, happening *after* filesystems are mounted and during concurrent file removal and path traversal. Thus, **FilesystemTrigger = false**.

Finally, let's tackle **RawFuzzingArtifact**. The rule states: "For all genuine kernel bugs, or anything reachable without capabilities (`Unprivileged = true`) or from an external surface, set `RawFuzzingArtifact` to false." It explicitly says to set it to `true` ONLY when the report requires capabilities (`Unprivileged = false`), cannot be triggered by peripheral, filesystem, network peer, or VM, AND falls into specific categories like degenerate administrative configurations or artificial fault injection.

Since I've already established that `Unprivileged = true`, this automatically means **RawFuzzingArtifact = false**. There's no ambiguity here. The definition of `RawFuzzingArtifact = true` is very strict and requires `Unprivileged = false`. The prompt even emphasizes this: "Set to true ONLY when the report requires capabilities (even if obtainable in a user/network namespace, i.e. Unprivileged = false)..."

I've also re-evaluated my initial assessment of `PeripheralTrigger` and `FilesystemTrigger` to ensure no subtle interpretations were missed. Mounting a filesystem is just that – the act of mounting. The bug occurs during concurrent operations, not during the parsing of a malicious image. The VFS concurrency race isn't a "malicious filesystem trigger" in the sense of a vulnerable parser.

To recap my confirmed logic:
*   **Entry Points:** The bug is triggered by standard `sys_unlink` syscalls executed by unprivileged processes.
*   **Operations:** Concurrently, one process unlinks a file while another is performing path resolution that involves `try_to_unlazy`, leading to a race on the parent directory's dentry lock reference count.
*   **Requirements:** No special privileges, capabilities, or user namespaces beyond what an unprivileged user possesses are needed.
*   **Classification:**
    *   `Unprivileged = true`
    *   `UserNamespace = true`
    *   `RequiredCaps = []`
    *   `PeripheralTrigger = false`
    *   `FilesystemTrigger = false`
    *   `RawFuzzingArtifact = false`

With all these points confirmed, I'm ready to finalize the classification.


67/2 2026/11/17 06:22 tool set-results
0m Args:
map[FilesystemTrigger:false PeripheralTrigger:false RawFuzzingArtifact:false RequiredCaps:[] Unprivileged:true UserNamespace:true]

Results:
map[FilesystemTrigger:false PeripheralTrigger:false RawFuzzingArtifact:false RequiredCaps:<nil> Unprivileged:true UserNamespace:true]

68/2 2026/11/17 06:22 llm local-reachability
0m Model:
gemini-3.8-flash

Tokens:
							input: 12442
							output: 543
							thoughts: 85
						

Thoughts:
**My Explanations of the Unlinking Mechanisms**

Alright, the data's all here, now I need to articulate exactly what I've found. My goal is to provide a thorough breakdown of how unlinking operations function from a security and system perspective, focusing on the actual entry points into the kernel.

First, I'll detail the specific kernel interfaces I examined for performing unlinks. This includes the more direct, traditional `sys_unlink` and its more modern counterpart, `unlinkat`. Beyond these, I also delved into the internal path traversal mechanisms – specifically, how the kernel lazily walks directory entries – and how that plays a role, which I'm referring to as "path walk unlazy." Finally, I'll cover the internal kernel path related to the `dput` and `dentry_kill` operations, which are the underlying actions that actually free up directory entry structures.

Crucially, for each of these investigated paths, I need to clearly state what kind of capability or configuration checks are in place. My findings indicate that for these basic VFS (Virtual File System) syscalls that unlinking relies on, there are essentially *no* elevated capability or special configuration requirements. These are standard system calls that unprivileged users can, in principle, invoke.

Finally, and this is key for understanding the implications, I'll meticulously explain the reasoning behind each dimension of my output. This means articulating *why* these specific entry points are relevant, why the lack of stringent checks is significant, and how these factors combine to shape the overall security posture and behavior of file deletion within the system.


69/1 2026/11/17 06:22 action If
0m Args:
map[IsNetCandidate:false]

70/1 2026/11/17 06:22 action If
0m Args:
map[IsKVMCandidate:false]

71/1 2026/11/17 06:22 action combine-assessment
0m Results:
map[DenialOfService:false Explanation:Root Cause Analysis:

### Root Cause Analysis

#### 1. Involved Structures, Functions, and Source Files
- **Files:** `fs/dcache.c`, `lib/lockref.c`, `include/linux/lockref.h`,
`include/linux/dcache.h`, `fs/namei.c`
- **Data Structures and Fields:**
  - `struct lockref` (`include/linux/lockref.h:25-35`):
    ```c
    struct lockref {
        union {
    #if USE_CMPXCHG_LOCKREF
            aligned_u64 lock_count;
    #endif
            struct {
                spinlock_t lock;
                int count;
            };
        };
    };
    ```
    On 64-bit systems with `USE_CMPXCHG_LOCKREF`, the 64-bit `lock_count` union
    aliases `spinlock_t lock` (bytes 0..3) and `int count` (bytes 4..7).
  - `struct dentry` (`include/linux/dcache.h:89`): defines `#define d_lock
  d_lockref.lock`.
- **Functions:**
  - Reader: `lockref_get_not_dead()` (`lib/lockref.c:143-162`) called from
  `__legitimize_path()` / `legitimize_path()` / `try_to_unlazy()`
  (`fs/namei.c:880, 890, 954`).
  - Writer: `dentry_kill()` (`fs/dcache.c:830-882`) called during dentry
  eviction via `finish_dput()` / `dput()` (`fs/dcache.c:1032, 1073`).

---

#### 2. Triggering Mechanism and Race Sequence

1. **Reader Path (`lockref_get_not_dead` in task 4498):**
   - During an RCU-walk path resolution unlazy operation (`try_to_unlazy()`),
   task 4498 attempts to legitimize a dentry reference (the parent directory
   dentry) by calling `lockref_get_not_dead(&path->dentry->d_lockref)`.
   - `lockref_get_not_dead()` enters macro `CMPXCHG_LOOP`
   (`lib/lockref.c:11-27`), which begins with an optimistic lockless 8-byte
   load:
     ```c
     old.lock_count = READ_ONCE(lockref->lock_count);
     ```
   - This 8-byte read accesses memory `0xffff888105d35800` through
   `0xffff888105d35807`, covering both the spinlock and the reference counter
   without acquiring `parent->d_lock`.

2. **Writer Path (`dentry_kill` in task 3284):**
   - Concurrently, task 3284 is destroying a child dentry inside
   `dentry_kill()`.
   - `dentry_kill()` locks the parent dentry via `spin_lock(&parent->d_lock)` at
   line 868.
   - Once the child is unlisted and freed, line 877 decrements the parent's
   reference counter:
     ```c
     if (parent && --parent->d_lockref.count) {
         spin_unlock(&parent->d_lock);
         return NULL;
     }
     ```
   - `--parent->d_lockref.count` is a 4-byte non-atomic read-modify-write
   located at offset +4 (`0xffff888105d35804`).

3. **KCSAN Detection:**
   - KCSAN observes an 8-byte marked read (`READ_ONCE(lockref->lock_count)`) on
   CPU 0 overlapping an unmarked 4-byte read-modify-write
   (`--parent->d_lockref.count`) on CPU 1.
   - Because plain C read-modify-writes (`--parent->d_lockref.count`) do not
   carry `WRITE_ONCE()` or atomic annotations, KCSAN flags the concurrent access
   as a data race.

---

#### 3. Correctness and Synchronization Analysis (Benign Data Race)

This data race is benign by design of the `lockref` subsystem:
- When task 3284 executes `--parent->d_lockref.count`, it holds `parent->d_lock`
(`parent->d_lockref.lock`).
- If task 4498's `READ_ONCE(lockref->lock_count)` runs while `parent->d_lock` is
held by task 3284:
  - `old.lock` contains the locked state
  (`arch_spin_value_unlocked(old.lock.rlock.raw_lock)` evaluates to `0`).
  - The `while` loop condition fails immediately; `CMPXCHG_LOOP` terminates
  without performing `try_cmpxchg64_relaxed()` and without using any potentially
  torn or in-transition counter value.
  - `lockref_get_not_dead()` falls back to `spin_lock(&lockref->lock)`, which
  properly blocks until task 3284 releases `parent->d_lock`, ensuring strict
  serialization.
- If task 4498's `READ_ONCE(lockref->lock_count)` runs before task 3284 acquires
the lock, `old.lock` reflects an unlocked state. However, before task 4498 can
execute `try_cmpxchg64_relaxed()`, task 3284 acquires the lock. The 64-bit
cmpxchg instruction will then compare `old.lock_count` (which has the unlocked
lock value) against current memory (which has the locked spinlock value). The
comparison fails, `old.lock_count` is reloaded with the locked state, and
execution falls back to taking the spinlock.
- Consequently, reference counts cannot be corrupted, dentries cannot be freed
prematurely, and execution behavior in real-world setups is fully preserved.

Impact Analysis:

In real-world setups without debugging sanitizers (KCSAN, lockdep, etc.), this
data race is completely benign and has no runtime consequences:

- MemoryCorruption: False. The 64-bit lockref design couples the 32-bit spinlock
with the 32-bit counter. If task 4498's READ_ONCE occurs while task 3284 holds
parent->d_lock, arch_spin_value_unlocked() evaluates to false, immediately
aborting the cmpxchg loop without touching the counter and falling back to
taking parent->d_lock (serializing after task 3284 unlocks). If the read
occurred before task 3284 acquired the lock, any cmpxchg64 attempt fails because
the lock word in memory has transitioned to locked. Therefore, refcounts are
never corrupted and dentries are not prematurely freed.
- InfoLeak: "none". No kernel memory or pointer values are leaked or exposed to
userspace.
- RawDenialOfService: False. The fallback path correctly synchronizes via
spin_lock(&lockref->lock); no deadlock, infinite loop, memory leak, or crash can
occur.
- IsNetCandidate: False. The reported stack traces involve VFS path walk and
unlinkat syscall handling; neither networking nor sockets are involved.
- IsKVMCandidate: False. The issue is in core VFS/dcache and lockref;
virtualization and KVM are not involved.

Local Reachability Analysis:

### Analysis

#### 1. Local Entry Points Investigated
The reported KCSAN data race occurs between:
1. **Task 1 (Reader):** Path lookup attempting to legitimize an RCU-walk
reference via `lockref_get_not_dead(&path->dentry->d_lockref)` in
`try_to_unlazy()` (`fs/namei.c:954`) during `complete_walk()` /
`filename_parentat()`, invoked via the `sys_unlink` / `sys_unlinkat` syscall.
2. **Task 2 (Writer):** Child dentry destruction via `dput()` / `finish_dput()`
-> `dentry_kill()` (`fs/dcache.c:877`), which decrements the parent's dentry
count (`--parent->d_lockref.count`), also invoked via standard `sys_unlink` /
`sys_unlinkat`.

Both paths are reached through standard, ubiquitous VFS operations (`unlink`,
`unlinkat`, `open`, `rmdir`, etc.) operating on user-created files and
directories (e.g., in `/tmp`).

#### 2. Capability and Configuration Checks
- Standard file-system operations like `unlink` / `unlinkat` on unprivileged
user-owned directories require no special capabilities or namespace privileges.
- Standard DAC checks permit any unprivileged process to create and unlink files
in world-writable directories such as `/tmp`.
- No capability checks (`capable()`, `ns_capable()`) gate this code path.

#### 3. Output Field Justification
- **Unprivileged (`true`):** Can be reached directly by any unprivileged user
process performing concurrent filesystem operations (such as unlinking files in
a shared directory).
- **UserNamespace (`true`):** True because it is triggerable by unprivileged
processes directly without namespaces.
- **RequiredCaps (`[]`):** No capabilities are required along the
least-privileged path.
- **PeripheralTrigger (`false`):** This is a concurrency race in the core VFS
lockref/dcache subsystem, not an issue triggered by plugging in an untrusted
hardware peripheral.
- **FilesystemTrigger (`false`):** Not triggered by mounting or parsing a
malicious filesystem disk image; it arises from concurrent userspace path lookup
and dentry reclamation.
- **RawFuzzingArtifact (`false`):** The bug is triggerable by unprivileged
processes (`Unprivileged = true`) through standard syscalls, and thus is not a
capability-gated fuzzing artifact. Exploitable:false FuzzingArtifact:false]

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)