<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>eb13a1ff271b0d180687eebb30611b0b276d5193 - random: vDSO: avoid call to memset() when zeroing reserved parameter</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#eb13a1ff271b0d180687eebb30611b0b276d5193</link>
        <description>random: vDSO: avoid call to memset() when zeroing reserved parameterAfter a recent change in LLVM [1], builds with the random vDSOimplementation, such as PowerPC and RISC-V, fail when checking the vDSO:  arch/powerpc/kernel/vdso/vdso32.so.dbg: dynamic relocations are not supported  arch/riscv/kernel/vdso/vdso.so.dbg: dynamic relocations are not supportedmemset() is now generated when zeroing params-&gt;reserved for some buildsbecause LLVM has an optimization (now run in more instances) that canrecognize at compile time when it is assigning a static value to acontiguous area of memory and turn that into a call to memset(). Bothclang and GCC assume memset() is always available [2].Clang has an internal fiddly hook, -max-store-memset, which we can setto a high number, to disable generating out of line memset calls [3].Similarly, GCC has -finline-stringops=memset to do the same [4], shouldthis issue ever hit future version of GCC. While these options wouldn&apos;tmake sense for normal kernel code, it is fine for the extremely limitedand intentionally compact vDSO code.Link: https://github.com/llvm/llvm-project/commit/90cebef1411617fc3eedd359bdf00cb44b1c2439 [1]Link: https://gcc.gnu.org/onlinedocs/gcc-16.2.0/gcc/Standards.html#index-ffreestanding [2]Link: https://github.com/llvm/llvm-project/commit/b28eeb28bea39148738dc375e8a97072a1907e64 [3]Link: https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-finline-stringops [4]Closes: https://github.com/ClangBuiltLinux/linux/issues/2183Cc: stable@vger.kernel.org # v6.12+Signed-off-by: Nathan Chancellor &lt;nathan@kernel.org&gt;Signed-off-by: Jason A. Donenfeld &lt;Jason@zx2c4.com&gt;

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Fri, 25 Sep 2026 23:46:32 +0200</pubDate>
        <dc:creator>Nathan Chancellor &lt;nathan@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>5f5ef9c407cfdc524a1aaeb4196d933f61ecf21a - Merge tag &apos;bootconfig-v7.3&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#5f5ef9c407cfdc524a1aaeb4196d933f61ecf21a</link>
        <description>Merge tag &apos;bootconfig-v7.3&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-tracePull bootconfig updates from Masami Hiramatsu: - Support build-time command line building for embedded bootconfig - Fix xbc_snprint_cmdline() to render descendant keys when the root has   both a value and subkeys, and treats empty subtrees correctly. - Add build-time pipeline using tools/bootconfig -C to render the   embedded bootconfig &quot;kernel&quot; subtree into .init.rodata as a cmdline   string. - Clean build-time tools/bootconfig from make clean - Add helper to prepend embedded bootconfig cmdline into   boot_command_line early before parse_early_param() - Wire early prepend helper in x86 setup_arch() so early_param handlers   see values from the embedded bootconfig (currently x86 only) - Avoid duplicating &quot;kernel&quot; keys in setup_boot_config() - Refactor setup_boot_config() to share bootconfig_cmdline_requested() - Document CONFIG_CMDLINE_FROM_BOOTCONFIG usage, requirements, and   precedence* tag &apos;bootconfig-v7.3&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace:  init/main.c: use bootconfig_cmdline_requested() for the runtime opt-in  bootconfig: skip runtime kernel.* render once prepended early  x86/setup: prepend embedded bootconfig cmdline before parse_early_param  Documentation: bootconfig: document build-time cmdline rendering  bootconfig: add xbc_prepend_embedded_cmdline() helper  bootconfig: clean build-time tools/bootconfig from make clean  bootconfig: render embedded bootconfig as a kernel cmdline at build time  bootconfig: render descendant keys when xbc_snprint_cmdline() root has a value

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Tue, 25 Aug 2026 17:59:09 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>ed3b875bea55a3ec4837113356df2ead11115af9 - Merge tag &apos;mm-stable-2026-08-18-18-39&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#ed3b875bea55a3ec4837113356df2ead11115af9</link>
        <description>Merge tag &apos;mm-stable-2026-08-18-18-39&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mmPull MM updates from Andrew Morton: - &quot;mm: drop &quot;sub&quot; prefix from various places&quot; (Dev Jain)   page-&gt;folio conversion and a naming cleanup - &quot;mm/kasan: remove redundant initialization for kasan_flag_write_only&quot;   (Igor Putko)   KASAN cleanup work - &quot;mm/filemap: reduce unnecessary xarray lookups&quot; (Chi Zhiling)   Small speedup in the pagecaache read code - &quot;mm/percpu: Fix possible NOFS/NOIO reclaim recursion&quot; (Kaitao Cheng)   Improve the vmalloc code - mainly the avoidance of GFP_KERNEL   allocations when the caller asked for GFP_NOFS or GFP_NOIO - &quot;mm/kmemleak: avoid soft lockup when scanning task stacks&quot; (Breno   Leitao)   Avoid a soft lockup watchdog trigger from the kmemleak scanning code   in extreme situations - &quot;mm/page_owner: misc cleanups&quot; (Ye Liu)   Cleanups to the page_owner code. For some reason lots of people have   been working on the page_owner code this cycle. - &quot;mm: convert to walk_page_range_vma() to eliminate find_vma()&quot;   (Kefeng Wang)   Simplify and accelerate the page walking library function - &quot;mm/migrate: preparatory cleanups for batch copy and offload&quot;   (Shivank Garg)   Cleanups in the migration code - &quot;mm/page_owner: add per-fd filter infrastructure for print_mode and   NUMA filtering&quot; (Zhen Ni)   Per-fd filtering to page_owner in order to reduce the sometimes vast   amount of output it can produce - &quot;mm: Refactor bootmem gigantic hugepage allocation&quot; (Muchun Song)   Fixes and preparatory cleanups around bootmem HugeTLB handling,   sparse initialization ordering, and related vmemmap setup - &quot;mm/zsmalloc: reduce lock contention in zs_free()&quot; (Wenchao Hao)   Reduce lock contention in zs_free(), which dominates the unmap path   under memory pressure on Android (LMK kills) and on x86 servers   running zswap-heavy workloads.   Up to 1.83x improvement in microbenchmarking. - &quot;move alloc_tag.c file under mm/&quot; (Suren Baghdasaryan) - &quot;samples/damon: handle damon_{start,stop}() failures&quot; (SJ Park)   Fix improper handling of damon_start(), damon_stop(), and   damon_call() failures across DAMON sample modules to prevent   potential memory leaks, operation disruptions and use-after-free   bugs - &quot;mm/damon/sysfs: kobject_del() directories that users can   create/remove&quot; (SJ Park)   Fix delayed sysfs directory removal under DEBUG_KOBJECT_RELEASE   causeing creation failures due to duplicate directory names by adding   missing kobject_del() calls before creating new directories - &quot;mm: cleanup clear_not_present_full_ptes()&quot; (David Hildenbrand)   Clean up the core pte handling code - &quot;selftests/damon: misc fixes for test bugs&quot; (Kunwu Chan)   Fix several bugs in the DAMON selftests - &quot;selftests/damon: fix memcg_path staging handling&quot; (Cheng Nie)   Fix a bug in _damon_sysfs.py for damos_filter memcg_path setup, and   add a test case for it in sysfs.py. - &quot;selftests/damon: test kdamond refresh_ms&quot; (Ruslan Valiyev)   Selftest coverage for DAMON&apos;s refresh_ms sysfs feature by updating   the test control module and verifying that scheme stats update   automatically without manual intervention - &quot;mm/damon: five misc fixups&quot; (Akinobu Mita)   Miscellaneous DAMON fixups. - &quot;mm/damon/core: detect internal variation above max_nr_regions/2&quot;   (Jiayuan Chen)   Fix DAMON&apos;s region splitting behavior when region counts exceed half   the maximum budget by dynamically scaling down the split fraction as   the limit approaches, preventing large regions from staying un-split,   and add corresponding KUnit test coverage - &quot;mm: preparatory patches for PMD level swap entries&quot; (Usama Arif)   Refactor and clean up PMD softleaf helpers, call sites, and   architecture flags to lay the groundwork for a follow-up series that   introduces PMD page table swap entries - &quot;mm/damon: update, optimize, and clean up doc, tests, and code&quot; (SJ   Park)   Update DAMON design and ABI documentation, expands unit and selftest   coverage, optimize damon_commit_target_regions(), and clean up   recently added sysfs interface code for better readability - &quot;mm/vmpressure: reduce CPU, memory and code overhead on cgroup v2&quot;   (Usama Arif)   Optimize vmpressure() by skipping unnecessary work on cgroup v2 for   userspace event notifications and refactor v1-only eventfd handling   into mm/memcontrol-v1.c to reduce memory overhead and code complexity - &quot;selftests/mm: refactor pkey helpers and fix mmap error handling&quot;   (Hongfu Li)   Refactor pkeys shared tracing and assertion helpers into a common   file, unify protection key selftests to use consistent diagnostic   logging and assertions, and enforce standardized MAP_FAILED return   checks for mmap() calls across the tests - &quot;mm/damon: optimize out nr_accesses_bp&quot; (SJ Park)   Replace the error-prone, continuously updated nr_accesses_bp field in   damon_region with an on-demand moving sum function, reducing   structure memory overhead and avoiding state corruption bugs - &quot;Open HugeTLB allocation routine for more generic use&quot; (Ackerley Tng)   Decouple HugeTLB folio allocation from VMA dependencies by   introducing hugetlb_alloc_folio(), enabling subsystems like   guest_memfd to allocate HugeTLB folios without standard VMA   reservations or pseudo-VMAs - &quot;mm/damon: provide pseudo moving sum probe_hits&quot; (SJ Park)   Integrate DAMON&apos;s probe_hits attribute counter into the pseudo moving   sum infrastructure, enabling real-time, online monitoring without   waiting for full aggregation intervals - &quot;mm: Some cleanups for page allocator APIs&quot; (Brendan Jackman)   Simplify and refactor the page allocator entry points and flags by   unifying allocation paths, adding internal alloc_flags arguments, and   eliminating redundant __ prefixed alloc_pages variants. - &quot;Fix incorrect access of hugetlb pte entries&quot; (Dev Jain)   Enforce the consistent use of huge_ptep_get() instead of ptep_get()   for HugeTLB entries and fixes an unaligned address issue in arm64&apos;s   huge_ptep_get() implementation - &quot;mm/damon: validate all parameters in the core&quot; (SJ Park)   Consolidate parameter validation into the DAMON core specifically   within damon_start() and damon_commit_ctx() to centralize error   checking, eliminate caller-side redundant checks and to improve   maintenance efficiency - &quot;tools/mm/page_owner_sort: fix filtering and cleanup issues&quot; (Yichong   Chen)   Rename is_need() to filter_record() for clearer return semantics, fix   per-record allocation memory leaks and bound output copies in   search_pattern() to address an existing buffer issue - &quot;memcg: bail out reclaim when memcg is dying&quot; (Jiayuan Chen)   Mitigate a system-wide stall which occurs when a cgroup is removed   while one of its memory control files is doing synchronous reclaim - &quot;mm/memory-failure: add panic option for unrecoverable pages&quot; (Breno   Leitao)   Introduce an opt-in vm.panic_on_unrecoverable_memory_failure sysctl   that immediately panics the kernel on unrecoverable memory errors in   kernel-owned pages to preserve error context and prevent delayed,   silent data corruption - &quot;mm/damon: refactor damon_{start,stop,commit}() for simple error   handling&quot; (SJ Park)   Refactor the DAMON core API functions to guarantee that all contexts   are fully stopped when damon_start(), damon_stop(), or damon_commit()   fail, eliminating the need for complex and error-prone caller-side   cleanup code - &quot;Keep tail page private zero at free and folio split&quot; (Zi Yan)   Add checks to ensure tail_page-&gt;private is zero when freeing compound   or high-order pages and when promoting tail pages during large folio   splits. By validating these fields at free and split time, it allows   the removal of redundant private field clearing inside   prep_compound_tail() - &quot;mm: drop redundant lru_add_drain in anon folio reuse paths&quot; (Barry   Song)   Eliminate redundant lru_add_drain() calls in   wp_can_reuse_anon_folio() and do_swap_page() to reduce LRU lock   contention and system overhead   By validating folio refcounts against the LRU cache before draining   and removing unnecessary drains in the swap path, it achieves up to a   30.5% reduction in drain calls during heavy swap workloads - &quot;mm: clean up folio LRU and swap declarations&quot; (Jianyue Wu)   Reorganize folio LRU and swap code by relocating page-cluster state   to mm/swap_state.c, renaming mm/swap.c to mm/folio.c, and moving   MM-internal reclaim declarations into mm/internal.h. - &quot;userfaultfd: working set tracking for VM guest memory&quot; (Kiryl   Shutsemau)   Add userfaultfd support for tracking the working set of VM guest   memory, so a VMM can identify hot pages and reclaim cold ones to   tiered or remote storage - &quot;mm: remove CONFIG_HAVE_BOOTMEM_INFO_NODE (Part 2)&quot; (David   Hildenbrand)   Remove the remaining pieces of CONFIG_HAVE_BOOTMEM_INFO_NODE,   performing some smaller cleanups around freeing of reserved vmemmap   pages on the way. - &quot;mm/damon: update probe hits for runtime parameter commits&quot; (SJ Park)   Ensure that DAMON&apos;s probe_hits attribute counter is properly updated   when monitoring intervals are changed at runtime, matching the   behavior of nr_accesses. To achieve this, it refactors and renames   existing helper functions for shared use, applies the updates to   probe_hits, and handles edge cases in damon_probe_hits_mvsum() to   maintain measurement accuracy. - &quot;KSM: performance optimizations for rmap_walk_ksm&quot; (xu xin)   Resolve a severe KSM reverse-mapping performance bottleneck where   thousands of split VMAs sharing a single anon_vma cause extended lock   contention.   By adding an interval-filtering check during the rmap walk, it   reduces worst-case anon_vma lock hold times from over 500ms down to   under 2ms, preventing application freezes and latency spikes under   memory pressure. - &quot;mm: split a couple of headers from internal.h&quot; (Mike Rapoport)   Split declarations related to mm_init, memblock, vmalloc and sparse   into new headers - &quot;KSM: use linear_page_index in collect_procs_ksm()&quot; (xu xin)   Apply the interval tree optimization from rmap_walk_ksm() to   collect_procs_ksm() to avoid iterating over non-matching VMAs during   KSM memory error handling.   It hoists loop-invariant address initialization and restricts the   anon_vma_interval_tree_foreach walk to a targeted page offset range,   reducing redundant checks and improving lookup efficiency. - &quot;selftests/mm: avoid false failures in hugetlb and KSM tests&quot; (Sayali   Patil)   Fix issues in the hugetlb and KSM MM selftest categories that can   report failures when the prerequisites for the tests are not   satisfied - &quot;mm/damon: introduce data attributes only monitoring&quot; (SJ Park)   Introduce attribute-weighted region management in DAMON, allowing   users to prioritize specific data attributes (such as page sizes or   cgroups) over or instead of access monitoring.   By assigning weights to attribute probes, DAMON can completely   disable access tracking and adjust monitoring regions based on   weighted probe-hit counters to optimize monitoring quality for   attribute-focused workloads. - &quot;mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings&quot;   (Stanislav Kinsburskii)   Extend hmm_range_fault() to support userfaultfd-backed regions by   allowing the mmap lock to be dropped during fault handling via a new   hmm_range_fault_locked() helper.   By accepting a locked pointer and signaling retry status when lock   release occurs, it enables page fault resolution in userfaultfd   regions while preserving backward compatibility for existing callers. - &quot;mm: make VMA page offset handling more consistent&quot; (Lorenzo Stoakes)   Clean up and standardize how vma-&gt;vm_pgoff is accessed and   manipulated across file-backed and anonymous mappings in the kernel   It introduces dedicated helper functions such as vma_start_pgoff(),   vma_end_pgoff(), vma_set_pgoff() and linear_page_delta() while   renaming rmap interval tree helpers to better reflect their   functionality.   These changes establish a cleaner foundation for future work that   will unify virtual page offset indexing for all anonymous and CoW&apos;d   folios. - &quot;mm: handle device-private PMDs in walk callbacks&quot; (Usama Arif)   Address kernel panics and state corruption caused by MM walk   callbacks reaching non-present device-private PMD swap entries   created during HMM migrations   It ensures that functions which acquire pmd_trans_huge_lock()   properly recognize device-private PMDs instead of assuming a present   THP or a standard migration entry. - &quot;mm/rmap: Refactor try_to_unmap_one&quot; (Dev Jain)   Refactor try_to_unmap_one by modularizing Hugetlb,   anonymous-lazyfree, and anonymous-swapbacked logic into dedicated   functions, laying the structural groundwork for batched anonymous   large folio unmapping. - &quot;Docs/ABI/damon: sysfs ABI document fixes and additions&quot; (Song Hu)   Fix typos and fills in missing entries in the DAMON sysfs ABI   document - &quot;dax/kmem: atomic whole-device hotplug via sysfs&quot; (Gregory Price)   Introduce an atomic sysfs state attribute and supporting DAX/MM   infrastructure to prevent userland races when offlining and removing   entire memory regions   By adding an unplugged state alongside standard online modes, it   enables whole-device atomic hotplug control while preserving backward   compatibility. - &quot;mm: convert more vm_flags_t users to vma_flags_t&quot; (Lorenzo Stoakes)   Continue transitioning the kernel from the deprecated vm_flags_t type   to vma_flags_t across core memory management infrastructure.   It replaces legacy type usage in core functions such as do_mmap(),   unmapped area allocation, mm-&gt;def_vma_flags, and VMA operations like   mlock, mprotect, and mremap. - &quot;Two small patches to clean up mm/mm_slot.h&quot; (xu xin)   Refactor mm_slot.h by introducing mm_slot_remove() to unify duplicate   slot deletion sequences in khugepaged and KSM. It also adds code   documentation explaining why mm_slot_lookup and mm_slot_insert must   remain as preprocessor macros rather than static inline functions. - &quot;mm/damon/core: hide core-private struct fields&quot; (SJ Park)   Clean up DAMON core structures by consistently marking internal-only   fields with private: comment tags to prevent improper direct access   from outer layers.   It enforces encapsulation across core structures including   damon_region, damon_target, and damon_ctx and updates DAMON_SYSFS to   interact through approved access APIs instead of exposing raw struct   members. - &quot;mm/damon: unurgent fixes for infinite loop, NULL de-ref and races&quot;   (SJ Park)   Address potential infinite loops, NULL dereferences, and race   conditions identified in DAMON   It fixes an infinite loop triggered by extreme user configurations, a   NULL pointer dereference within unit tests and minor monitoring   accuracy degradation caused by subtle runtime races. - &quot;mm/page_alloc: fixes for free_pages_nolock() on RT/UP&quot; (Brendan   Jackman)   Fix an NMI safety flaw in __free_frozen_pages() where freeing pages   on non-SMP or PREEMPT_RT kernels can bypass can_spin_trylock() checks   via non-PCP or isolated migration paths.   It also resolves potential kernel crashes and privilege escalation   risks triggered when BPF tracing runs in NMI context alongside memory   hotplug or large allocation frees. - &quot;mm/page_alloc: couple of followups for recent cleanups&quot; (Brendan   Jackman)   Clean up and update page allocator nomenclature, documentation, and   debug assertions.   It aligns internal FPI_ flags with the public &quot;nolock&quot; naming   convention, removes outdated internal implementation details from   high-level page allocator comments, and eliminates obsolete   VM_BUG_ON() assertions in allocation paths. - &quot;mm/mseal: further cleanups&quot; (Lorenzo Stoakes)   Refactor and simplify the mseal implementation by clarifying API   boundaries and removing unnecessary code complexity.   It replaces generic do_mseal() usage outside the syscall with a   dedicated mseal_mmap_page_zero() helper for MMAP_PAGE_ZERO,   eliminates mm_struct parameters to enforce that sealing applies only   to current-&gt;mm, and streamlines overall logic and comments with no   functional changes intended. - &quot;mm/vmscan: fix swappiness=max and clean up per-node proactive   reclaim&quot; (Ridong Chen)   Resolve reclaim behavior bugs and clean up function parameters across   memory reclaim paths   It fixes swappiness=max in both standard reclaim and MGLRU so   unswappable anonymous memory no longer falls back to evicting page   cache, ensures reclaim_store() returns accurate error codes instead   of collapsing all failures into -EAGAIN, and removes the obsolete   gfp_mask parameter from __node_reclaim(). - &quot;mm: mincore: misc cleanups&quot; (Kefeng Wang)   Clean up and simplifies the mincore code. Most importantly, it   removes the historical special behavior that always reports VM_PFNMAP   pages as non-resident. - &quot;mm/huge_memory: drop dead split helper variants&quot; (Kiryl Shutsemau)   Two trivial cleanups in the folio split API - &quot;mm/damon: fix uninitialized DAMOS field and kunit exec expectation   bugs&quot; (SJ Park)   Resolve minor operational and testing bugs in DAMON identified by   Sashiko. It initializes the damos-&gt;last_applied field to prevent   occasional efficiency degradation and fixes invalid memory accesses   in DAMON KUnit tests during test failure handling. - &quot;cleanup for stable_page_flags()&quot; (Jinjiang Tu)   Clean up and refactor stable_page_flags() used by /proc/kpageflags   without altering functionality.   It uses BIT_ULL() to prevent shift-overflow warnings on 64-bit flag   bits, converts folio-specific flag checks to standard folio_test_*()   helpers, and removes redundant CONFIG_PAGE_IDLE_FLAG handling. - &quot;Batch unmap of uffd-wp file folios&quot; (Dev Jain)   Extend batched folio unmapping support to file folios within   userfaultfd write-protect (uffd-wp) VMAs by adding batching   capabilities to pte_install_uffd_wp_if_needed().   This removes special-case restrictions on uffd-wp VMAs in   try_to_unmap_one(), significantly simplifying the function&apos;s control   flow and complexity. - &quot;mm/early_ioremap: clarify and clean up early_ioremap_reset()&quot;   (Sang-Heon Jeon)   Clarify and clean up the architecture-specific usage of   __late_set_fixmap() and __late_clear_fixmap() after   early_ioremap_reset()   It adds explicit documentation regarding when early_ioremap_reset()   must be called and removes redundant macro definitions and reset   calls in the RISC-V and ARM64 architectures. - &quot;mm: fix reclaim storms in defrag_mode&quot; (Johannes Weiner)   Address severe performance regressions, swap storms, and spurious   OOMs caused by vm.defrag_mode=1 under high memory pressure in Meta   production   It updates the page allocator slowpath so non-movable allocation   requests actively trigger direct reclaim and direct compaction at   pageblock_order scale, allowing them to claim whole pageblocks rather   than spinning unproductively. - &quot;zram: lockmap tweaks&quot; (Sebastian Siewior)   Optimize and fix lockdep tracking for zram devices by consolidating   per-entry lockmaps and isolate lock classes across multiple instances   This reduces memory overhead by replacing per-entry lockdep_map   instances with a single map per struct zram, and assigns a dynamic   lock_class_key to each instance to prevent false deadlock reports   when different zram devices are backed by distinct filesystems.* tag &apos;mm-stable-2026-08-18-18-39&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (501 commits)  selftests/mm: thuge-gen: fix test_shmget() for PAGE_SIZE check  selftests/mm: unpoison pages in memory-failure teardown  mm/shmem: downgrade final i_blocks check in shmem_evict_inode() to pr_warn()  mm/khugepaged: replace mutex_lock/mutex_unlock usage with guard macro  mm/zsmalloc: fix release order of locks in zs_page_migrate()  Documentation: zram: remove sections numbering  ksm: stop iterating VMAs when ksm_test_exit returns true  mm: fold userfaultfd_rwp() to false without CONFIG_ARCH_HAS_PTE_PROTNONE  mm/migrate: report RCU-tasks quiescent states in migrate_pages_batch()  zram: use a custom key for each zram object  zram: move lockmap to be per-zram instead per table  selftests/mm: fix gup_longterm EINVAL error message  mm: page_alloc: fix non-movable reclaim storm in defrag_mode  mm: page_alloc: move capture_control to the page allocator  mm: compaction: support non-movable compaction for pageblock requests  mm: page_alloc: __GFP_FS lockdep annotation for direct compaction  hugetlb: evaluate subpool free state while locked  mm/damon: remove trailing semicolons after function definitions  mm/damon/ops-common: prevent migration fallback to non-target nodes  mm/damon: update outdated comment about DAMOS filter handling  ...

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Fri, 21 Aug 2026 03:17:08 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>9d2ed026f031f764e9450ac9aada2f46bc977397 - Merge tag &apos;sysctl-7.03-rc1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/sysctl/sysctl</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#9d2ed026f031f764e9450ac9aada2f46bc977397</link>
        <description>Merge tag &apos;sysctl-7.03-rc1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/sysctl/sysctlPull sysctl updates from Joel Granados: - Fix kernel-doc warnings by adjusting in file documentation - Consolidate do_proc_* function into do_proc_vec   Consolidate three slightly different implementations of applying a   converter on all elements of a vector. Fixes to this function now   propagate to the three types. - Replace CONFIG_PROC_SYSCTL with CONFIG_SYSCTL (they were the same)   and restrict cad_pid modifications to global root (GLOBAL_ROOT_UID)* tag &apos;sysctl-7.03-rc1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/sysctl/sysctl:  sysctl: remove CONFIG_PROC_SYSCTL, it just mirrors CONFIG_SYSCTL  sysctl: move the &quot;cad_pid&quot; entry from pid_table[] to kern_reboot_table[]  sysctl: repair some kernel-doc comments  sysctl: add Returns: kernel-doc for all functions  sysctl: Update API function documentation  sysctl: Rename proc_doulongvec_minmax_conv to proc_doulongvec_conv  sysctl: Group proc_handler declarations and document  sysctl: Replace do_proc_do{int,ulong,uint}vec with do_proc_vec  sysctl: Add negp parameter to douintvec converter functions  sysctl: Move default converter assignment out of do_proc_dointvec

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Thu, 20 Aug 2026 17:46:41 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>104a813376837da3b9651457d6fdc99596257fba - Merge tag &apos;timers-vdso-2026-08-17&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#104a813376837da3b9651457d6fdc99596257fba</link>
        <description>Merge tag &apos;timers-vdso-2026-08-17&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tipPull VDSO updates from Thomas Gleixner: - Consolidate the VDSO datastore further and provide support for   mlock_all() and prefaulting. - Provide 32-bit legacy time related functionality only if   CONFIG_COMPAT_32BIT_TIME is enabled. The config switch exists,   but architecture code still exposes the legacy functionality even   disabled.   Clean this up by adding the missing guards and validating at build   time that the VDSO is legacy free if disabled. - Consolidate the VDSO related config options in core and drivers,   which removes some non-sensical dependencies and quite an amount of   #ifdeffery. - Clean up the PAGE_SIZE definition maze* tag &apos;timers-vdso-2026-08-17&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (30 commits)  random: vDSO: Drop custom PAGE_SIZE definitions  LoongArch: Remove CONFIG_GENERIC_GETTIMEOFDAY ifdeffery  clocksource/drivers/timer-riscv: Remove CONFIG_GENERIC_GETTIMEOFDAY ifdeffery  clocksource/drivers/arm_arch_timer: Remove CONFIG_GENERIC_GETTIMEOFDAY ifdeffery  clocksource/drivers/mips-gic-timer: Remove CONFIG_GENERIC_GETTIMEOFDAY ifdeffery  MIPS: csrc-r4k: Remove CONFIG_GENERIC_GETTIMEOFDAY ifdeffery  vDSO: Make clockmode constants available without CONFIG_GENERIC_GETTIMEOFDAY  kbuild: Support generated asm-headers in subdirectories  vdso: Rename HAVE_GENERIC_VDSO to VDSO_DATASTORE  vdso: Drop HAVE_GENERIC_VDSO from architecture kconfig files  vdso: Automatically select HAVE_GENERIC_VDSO if necessary  MIPS: vdso: Stop using CONFIG_HAVE_GENERIC_VDSO  vdso: Remove the dependency on HAVE_GENERIC_VDSO from ARCH_HAS_VDSO_ARCH_DATA  futex: Remove dependency on HAVE_GENERIC_VDSO from FUTEX_ROBUST_UNLOCK  vdso/gettimeofday: Verify COMPAT_32BIT_TIME interactions  sparc: vdso: Respect COMPAT_32BIT_TIME  MIPS: VDSO: Respect COMPAT_32BIT_TIME  powerpc/vdso: Respect COMPAT_32BIT_TIME  ARM: VDSO: Respect COMPAT_32BIT_TIME  arm64: vdso32: Respect COMPAT_32BIT_TIME  ...

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Wed, 19 Aug 2026 01:56:25 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>3b4128b9f374b4219eb716f4ad8a307bc7eb3d84 - Merge tag &apos;timers-core-2026-08-17&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#3b4128b9f374b4219eb716f4ad8a307bc7eb3d84</link>
        <description>Merge tag &apos;timers-core-2026-08-17&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tipPull timer and timekeeping core updates from Thomas Gleixner: - Fix a subtly inconsistency in the timekeeping code, which fails to   account for the monotonicity adjustment in ntp_error.   For small changes of the clocksource multiplicator (+/-1) which are   typically used by the NTP PLL this is hard to observe. But for larger   adjustments, e.g. caused by a direct frequency setting through   adjtimex() the one-time uncompensated offset is significant.   Cure this by adjusting ntp_error with the resulting offset so that   the discrepancy is smoothed away over time - Make tick length calculations correct in NTP.   The timekeeping core takes the quantisation of the clocksource into   account when calculating the tick length to compensate for the   deviation of the nominal NTP_INTERVAL_LENGTH.   While timekeeping gets this right, NTP is not aware of that, which   means it operates on the nominal value and not on the actual value   which is determined by the clock source frequency. The rounding of a   coarse clocksource like the ACPI PM timer results in a +127 PPM   deviation.   Cure this by exposing the deviation to the NTP code so that it can   operate on the same data as the timekeeping core. This is purely   kernel internal. User space still sees the nominal tick lenght via   adjtimex(). - The accuracy of the NTP adjustments is fairly approximate as the code   assumes that the invocations are precisely in NTP interval frequency   ticks and the final adjustment can over and under-run.   Cure this by adjusting ntp_error by the intended skew on each tick to   achieve the desired rate. - Handle the two competing skews of time offset and time adjustment   correctly by calculating the conflict portion between the skews and   adjusting both accordingly. - A set of updates and improvements for the selftests - The usual small fixes and improvements all over the place* tag &apos;timers-core-2026-08-17&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (58 commits)  selftests: timers: nsleep-lat: Check all calls to clock_nanosleep() and clock_gettime()  selftests: timers: nsleep-lat: Reuse kselftest error numbers  selftests: timers: nsleep-lat: Explicitly list the tested clocks  selftests: timers: nsleep-lat: Use NSEC_PER_MSEC define for unreasonable latency  selftests: timers: nanosleep: Report each test separately  selftests: timers: nanosleep: Explicitly handle timer_delete() failure  selftests: timers: nanosleep: Move all single clock tests out of the loop in main()  selftests: timers: nanosleep: Reuse kselftest error numbers  selftests: timers: nanosleep: Explicitly list the tested clocks  selftests: timers: nanosleep: Drop output alignment  selftests: timers: Use clock_name() and constants from clock-helpers.h  selftests: Add clock-helpers.h  timer_list: Use ktime_t over nanoseconds  timer_list: Use standard &apos;long long&apos; format placeholders  hrtimer: Add a lockdep assertion to hrtimer_update_base()  timekeeping: Use u32 for clock_was_set_seq  timekeeping: Rename clockid_aux_valid() to clockid_is_aux_clock()  hrtimer: Account nr_retries on recovered interrupt retries  timers/itimer: Zero-init old itimerval before copy to userspace  nohz: Replace dead select with choice default  ...

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Wed, 19 Aug 2026 01:23:56 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>b17006b45283f012a6e166517f5ca3e1af2f806a - nohz: Replace dead select with choice default</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#b17006b45283f012a6e166517f5ca3e1af2f806a</link>
        <description>nohz: Replace dead select with choice default&apos;select&apos; does not work on config options in a &apos;choice&apos;, so currently the&apos;select VIRT_CPU_ACCOUNTING_GEN&apos; for NO_HZ_FULL is dead, with the choiceoption VIRT_CPU_ACCOUNTING_GEN only being enabled when NO_HZ_FULL=y becausethe other choice members depend on NO_HZ_FULL=n.Remove the dead select, and encode this relationship as a default of thechoice, instead.This dead select was found by kconfirm, a static analysis tool for Kconfig.Signed-off-by: Julian Braha &lt;julianbraha@gmail.com&gt;Signed-off-by: Thomas Gleixner &lt;tglx@kernel.org&gt;Reviewed-by: Bradley Morgan &lt;include@grrlz.net&gt;Reviewed-by: Nicolas Schier &lt;nsc@kernel.org&gt;Link: https://patch.msgid.link/20260801160140.2391000-1-julianbraha@gmail.com

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Sat, 01 Aug 2026 18:01:40 +0200</pubDate>
        <dc:creator>Julian Braha &lt;julianbraha@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>e474ac24a79211f83e214d856630829f77363459 - mm/mseal: fix mseal documentation for 32-bit kernels</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#e474ac24a79211f83e214d856630829f77363459</link>
        <description>mm/mseal: fix mseal documentation for 32-bit kernelsmseal.o is built only for 64-bit kernels, so 32-bit kernels fall back tosys_ni_syscall() and return -ENOSYS rather than -EPERM.Drop architecture description in mseal.rst, since the arch feature doc hasthe latest state of mseal for each architecture.Fix the CONFIG_MSEAL_SYSTEM_MAPPINGS typo in init/Kconfig.Link: https://lore.kernel.org/20260715131258.55499-1-leon.hwang@linux.devSigned-off-by: Leon Hwang &lt;leon.hwang@linux.dev&gt;Acked-by: Lance Yang &lt;lance.yang@linux.dev&gt;Cc: Alice Ryhl &lt;aliceryhl@google.com&gt;Cc: Anand Moon &lt;linux.amoon@gmail.com&gt;Cc: Doug Anderson &lt;dianders@chromium.org&gt;Cc: Gary Guo &lt;gary@garyguo.net&gt;Cc: Jann Horn &lt;jannh@google.com&gt;Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Cc: Leon Hwang &lt;leon.hwang@linux.dev&gt;Cc: Liam R. Howlett &lt;liam@infradead.org&gt;Cc: Lorenzo Stoakes &lt;ljs@kernel.org&gt;Cc: Miguel Ojeda &lt;ojeda@kernel.org&gt;Cc: Nathan Chancellor &lt;nathan@kernel.org&gt;Cc: Pedro Falcato &lt;pfalcato@suse.de&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Randy Dunlap &lt;rdunlap@infradead.org&gt;Cc: Thomas Wei&#223;schuh &lt;thomas.weissschuh@linutronix.de&gt;Cc: Vlastimil Babka &lt;vbabka@kernel.org&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Wed, 15 Jul 2026 15:12:58 +0200</pubDate>
        <dc:creator>Leon Hwang &lt;leon.hwang@linux.dev&gt;</dc:creator>
    </item>
<item>
        <title>8d75c338f0bcecaa6c9af67f86c176b67b6acf3e - sysctl: remove CONFIG_PROC_SYSCTL, it just mirrors CONFIG_SYSCTL</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#8d75c338f0bcecaa6c9af67f86c176b67b6acf3e</link>
        <description>sysctl: remove CONFIG_PROC_SYSCTL, it just mirrors CONFIG_SYSCTLCONFIG_SYSCTL used to make sense as a separate hidden bool before commit61a47c1ad3a4 (&quot;sysctl: Remove the sysctl system call&quot;); it was selectedby both CONFIG_SYSCTL_SYSCALL and CONFIG_PROC_SYSCTL.Today CONFIG_PROC_SYSCTL is the only selector, so the two are alwaysequal. Kill the hidden bool, rename the PROC_SYSCTL prompt to SYSCTL,and s/CONFIG_PROC_SYSCTL/CONFIG_SYSCTL/ tree-wide.Signed-off-by: Oleg Nesterov &lt;oleg@redhat.com&gt;Signed-off-by: Joel Granados &lt;joel.granados@kernel.org&gt;

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Mon, 27 Jul 2026 16:47:22 +0200</pubDate>
        <dc:creator>Oleg Nesterov &lt;oleg@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>c6f11553c067d7d9ed2dcffe1e01780441d4e6e2 - mm: decouple protnone helpers from CONFIG_NUMA_BALANCING</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#c6f11553c067d7d9ed2dcffe1e01780441d4e6e2</link>
        <description>mm: decouple protnone helpers from CONFIG_NUMA_BALANCINGPatch series &quot;userfaultfd: working set tracking for VM guest memory&quot;, v10.This series adds userfaultfd support for tracking the working set of VMguest memory, so a VMM can identify hot pages and reclaim cold ones totiered or remote storage.This patch (of 15):pte_protnone() and pmd_protnone() detect present-but-inaccessible pagetable entries.  This capability is useful beyond NUMA balancing -- forexample, userfaultfd working set tracking uses protnone PTEs to track pageaccess without unmapping pages.Introduce CONFIG_ARCH_HAS_PTE_PROTNONE to decouple the protnone PTEinfrastructure from CONFIG_NUMA_BALANCING.  The six architectures thatsupport protnone PTEs (x86_64, arm64, powerpc, s390, riscv, loongarch) nowselect this option, and CONFIG_NUMA_BALANCING depends on it.No functional change -- the same set of architectures continues to haveworking protnone support, but the infrastructure is now availableindependently of NUMA balancing.Link: https://lore.kernel.org/20260708111417.173443-1-kirill@shutemov.nameLink: https://lore.kernel.org/20260708111417.173443-2-kirill@shutemov.nameSigned-off-by: Kiryl Shutsemau (Meta) &lt;kas@kernel.org&gt;Assisted-by: Claude:claude-opus-4-6Acked-by: SeongJae Park &lt;sj@kernel.org&gt;Acked-by: Mike Rapoport (Microsoft) &lt;rppt@kernel.org&gt;Cc: Andrea Arcangeli &lt;aarcange@redhat.com&gt;Cc: David Hildenbrand &lt;david@kernel.org&gt;Cc: James Houghton &lt;jthoughton@google.com&gt;Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Cc: Liam Howlett &lt;liam@infradead.org&gt;Cc: Lorenzo Stoakes &lt;ljs@kernel.org&gt;Cc: Paolo Bonzini &lt;pbonzini@redhat.com&gt;Cc: Peter Xu &lt;peterx@redhat.com&gt;Cc: Sean Christopherson &lt;seanjc@google.com&gt;Cc: Suren Baghdasaryan &lt;surenb@google.com&gt;Cc: Vlastimil Babka &lt;vbabka@kernel.org&gt;Cc: Zi Yan &lt;ziy@nvidia.com&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Wed, 08 Jul 2026 13:14:02 +0200</pubDate>
        <dc:creator>Kiryl Shutsemau (Meta) &lt;kas@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>2558084d2b03e298e3ec04bbbcfad55c8d50b7db - futex: Remove dependency on HAVE_GENERIC_VDSO from FUTEX_ROBUST_UNLOCK</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#2558084d2b03e298e3ec04bbbcfad55c8d50b7db</link>
        <description>futex: Remove dependency on HAVE_GENERIC_VDSO from FUTEX_ROBUST_UNLOCKThe robust futex unlock functionality has no relation to the genericvDSO functionality.Remove the dependency.Signed-off-by: Thomas Wei&#223;schuh &lt;thomas.weissschuh@linutronix.de&gt;Signed-off-by: Thomas Gleixner &lt;tglx@kernel.org&gt;Reviewed-by: Vincenzo Frascino &lt;vincenzo.frascino@arm.com&gt;Link: https://patch.msgid.link/20260709-vdso-have_generic_vdso-v1-1-d2e1061f268b@linutronix.de

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Thu, 09 Jul 2026 09:28:37 +0200</pubDate>
        <dc:creator>Thomas Wei&#223;schuh &lt;thomas.weissschuh@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>fc9d90470463f165a95becbfbad21795fd9752bd - bootconfig: render embedded bootconfig as a kernel cmdline at build time</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#fc9d90470463f165a95becbfbad21795fd9752bd</link>
        <description>bootconfig: render embedded bootconfig as a kernel cmdline at build timeAdd the build-time pipeline that renders the &quot;kernel&quot; subtree ofCONFIG_BOOT_CONFIG_EMBED_FILE into a flat cmdline string and stashesit in .init.rodata as embedded_kernel_cmdline[]. A follow-up patchadds the runtime helper that prepends this string to boot_command_lineduring early architecture setup so parse_early_param() sees the values.The build wires up:  tools/bootconfig -C kernel - userspace tool already shared with                               lib/bootconfig.c, used here in -C mode                               to render a bootconfig file to a cmdline  lib/embedded-cmdline.S     - .incbin&apos;s the rendered text plus a NUL                               (listed under the EXTRA BOOT CONFIG                               MAINTAINERS entry)  lib/Makefile rule          - runs tools/bootconfig at build time  Makefile prepare dep       - ensures tools/bootconfig is built first,                               same pattern as tools/objtool and                               tools/bpf/resolve_btfidsDrop the test target from tools/bootconfig/Makefile&apos;s default &apos;all&apos;recipe so that hooking the binary into the kernel build does not runtest-bootconfig.sh on every prepare. The tests stay available as&apos;make -C tools/bootconfig test&apos;, matching the convention oftools/objtool and tools/bpf/resolve_btfids whose &apos;all&apos; targets onlybuild the binary.Require BOOT_CONFIG_EMBED_FILE to be non-empty before the new optioncan be enabled, otherwise tools/bootconfig -C runs against an emptyfile and prints a parse error on every kernel build.The feature gates on CONFIG_ARCH_SUPPORTS_CMDLINE_FROM_BOOTCONFIG, asilent symbol arches select once they&apos;ve wired the prepend call intosetup_arch(). No arch selects it in this patch, so the user-visibleCONFIG_CMDLINE_FROM_BOOTCONFIG is not yet enableable; when an archlater opts in, the runtime behavior is added by the follow-up patches.tools/bootconfig also installs on target systems, so its own Makefilekeeps $(CC) and stays cross-buildable as a standalone tool. The kernelbuild, which runs the tool on the build host during prepare, insteadforces CC=$(HOSTCC) from a dedicated tools/bootconfig rule and clearsCROSS_COMPILE= in the sub-make. Without that clear, an LLVM=1 crossbuild would inherit CROSS_COMPILE and tools/scripts/Makefile.includewould inject --target=/--sysroot= flags into the host clang invocation,producing a target binary that fails to exec (&quot;Exec format error&quot;).embedded-cmdline.S places the rendered string in its own .init.rodatasubsection (.init.rodata.embed_cmdline) with the &quot;a&quot; (allocatable,read-only) flag and %progbits. lib/bootconfig-data.S already placesthe embedded bootconfig blob in .init.rodata with the &quot;aw&quot; flag(xbc_init() rewrites separators in place, so that data must bewritable). Using a distinct subsection name avoids the ld.lld section-type mismatch that would otherwise arise from mixing &quot;a&quot; and &quot;aw&quot;under the same name; the linker&apos;s &quot;*(.init.rodata .init.rodata.*)&quot;glob still folds both into the init image and frees them after boot.A follow-up patch wires the build-time tools/bootconfig into thetop-level clean target.Link: https://lore.kernel.org/all/20260626-bootconfig_using_tools-v7-3-24ab72139c29@debian.org/Reviewed-by: Nicolas Schier &lt;n.schier@fritz.com&gt;Signed-off-by: Breno Leitao &lt;leitao@debian.org&gt;Signed-off-by: Masami Hiramatsu (Google) &lt;mhiramat@kernel.org&gt;

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Thu, 02 Jul 2026 14:15:45 +0200</pubDate>
        <dc:creator>Breno Leitao &lt;leitao@debian.org&gt;</dc:creator>
    </item>
<item>
        <title>608045a91d9176d66b2114d0006bc8b57dff2ca9 - rust: allow `suspicious_runtime_symbol_definitions` lint for Rust &gt;= 1.98</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#608045a91d9176d66b2114d0006bc8b57dff2ca9</link>
        <description>rust: allow `suspicious_runtime_symbol_definitions` lint for Rust &gt;= 1.98Starting with Rust 1.98.0 (expected 2026-08-20), Rust is introducing acouple new lints, `invalid_runtime_symbol_definitions` (deny-by-default)and `suspicious_runtime_symbol_definitions` (warn-by-default), which checkthe signature of items whose symbol name is a runtime symbol expected by`core`.Our build hits the second one, i.e. the warning:    error: suspicious definition of the runtime `strlen` symbol used by the standard library         --&gt; rust/bindings/bindings_generated.rs:20018:5          |    20018 |     pub fn strlen(s: *const ffi::c_char) -&gt; usize;          |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^          |          = note: expected `unsafe extern &quot;C&quot; fn(*const i8) -&gt; usize`                  found    `unsafe extern &quot;C&quot; fn(*const u8) -&gt; usize`          = help: either fix the signature or remove any attributes like `#[unsafe(no_mangle)]`, `#[unsafe(export_name = &quot;strlen&quot;)]`, or `#[link_name = &quot;strlen&quot;]`          = help: allow this lint if the signature is compatible          = note: `-D suspicious-runtime-symbol-definitions` implied by `-D warnings`          = help: to override `-D warnings` add `#[allow(suspicious_runtime_symbol_definitions)]`    error: suspicious definition of the runtime `strlen` symbol used by the standard library         --&gt; rust/uapi/uapi_generated.rs:14236:5          |    14236 |     pub fn strlen(s: *const ffi::c_char) -&gt; usize;          |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^          |          = note: expected `unsafe extern &quot;C&quot; fn(*const i8) -&gt; usize`                  found    `unsafe extern &quot;C&quot; fn(*const u8) -&gt; usize`          = help: either fix the signature or remove any attributes like `#[unsafe(no_mangle)]`, `#[unsafe(export_name = &quot;strlen&quot;)]`, or `#[link_name = &quot;strlen&quot;]`          = help: allow this lint if the signature is compatible          = note: `-D suspicious-runtime-symbol-definitions` implied by `-D warnings`          = help: to override `-D warnings` add `#[allow(suspicious_runtime_symbol_definitions)]`Thus `allow` the lint in `bindings` and `uapi`.A more targeted alternative to avoid `allow`ing it would be to pass`--blocklist-function strlen` to `bindgen`, but we would perhaps needto adjust if other C headers end up adding more (or Rust checking more).Since it is just the less critical one that we hit, and since eventuallythis should be properly fixed by getting upstream Rust to provide a flaglike GCC/Clang&apos;s `-funsigned-char` [2][3], just `allow` it for now.Cc: Urgau &lt;urgau@numericable.fr&gt;Cc: stable@vger.kernel.org # Needed in 6.12.y and later (Rust is pinned in older LTSs).Link: https://github.com/rust-lang/rust/pull/155521 [1]Link: https://github.com/rust-lang/rust/issues/138446 [2]Link: https://github.com/Rust-for-Linux/linux/issues/355 [3]Reviewed-by: Gary Guo &lt;gary@garyguo.net&gt;Reviewed-by: Alice Ryhl &lt;aliceryhl@google.com&gt;Reviewed-by: Tamir Duberstein &lt;tamird@kernel.org&gt;Link: https://patch.msgid.link/20260615143225.471756-1-ojeda@kernel.orgSigned-off-by: Miguel Ojeda &lt;ojeda@kernel.org&gt;

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Mon, 15 Jun 2026 16:32:25 +0200</pubDate>
        <dc:creator>Miguel Ojeda &lt;ojeda@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>2e05544060b9fef5d4d0e0172944e6956c55080f - Merge tag &apos;mm-nonmm-stable-2026-06-21-10-22&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#2e05544060b9fef5d4d0e0172944e6956c55080f</link>
        <description>Merge tag &apos;mm-nonmm-stable-2026-06-21-10-22&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mmPull non-MM updates from Andrew Morton: - &quot;taskstats: fix TGID dead-thread stat retention&quot; (Yiyang Chen)   Fix a taskstats TGID aggregation bug where fields added in the TGID   query path were not preserved after thread exit, and adds a kselftest   covering the regression. - &quot;lib/tests: string_helpers: Slight improvements&quot; (Andy Shevchenko)   Improve lib/tests/string_helpers_kunit.c a little - &quot;lib/base64: decode fixes&quot; (Josh Law)   Address minor issues in lib/base64.c - &quot;selftests/filelock: Make output more kselftestish&quot; (Mark Brown)   Make the output from the ofdlocks test a bit easier for tooling to   work with. Also ignore the generated file - &quot;uaccess: unify inline vs outline copy_{from,to}_user() selection&quot;   (Yury Norov)   Simplify the usercopy code by removing the selectability of inlining   copy_{from,to}_user(). - &quot;ocfs2: validate inline xattr header consumers&quot; (ZhengYuan Huang)   Fix a number of possible issues in the ocfs2 xattr code - &quot;lib and lib/cmdline enhancements&quot; (Dmitry Antipov)   Provide additional robustness checking in the cmdline handling code   and its in-kernel testing and selftests - &quot;cleanup the RAID6 P/Q library&quot; (Christoph Hellwig)   Clean up the RAID6 P/Q library to match the recent updates to the   RAID 5 XOR library and other CRC/crypto libraries - &quot;ocfs2: harden inode validators against forged metadata&quot; (Michael   Bommarito)   Add three structural checks to OCFS2 dinode validation so malformed   on-disk fields are rejected before ocfs2_populate_inode() copies them   into the in-core inode - &quot;lib/raid: replace __get_free_pages() call with kmalloc()&quot; (Mike   Rapoport)   Clean up the lib/raid code by using kmalloc() in more places* tag &apos;mm-nonmm-stable-2026-06-21-10-22&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (108 commits)  ocfs2: fix circular locking dependency in ocfs2_dio_end_io_write  ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits  lib: interval_tree_test: validate benchmark parameters  ocfs2: avoid moving extents to occupied clusters  treewide: fix transposed &quot;sign&quot; typos and update spelling.txt  ocfs2: fix UBSAN array-index-out-of-bounds in ocfs2_sum_rightmost_rec  fat: reject BPB volumes whose data area starts beyond total sectors  selftests/uevent: increase __UEVENT_BUFFER_SIZE to avoid ENOBUFS on busy systems  lib/test_firmware: allocate the configured into_buf size  fs: efs: remove unneeded debug prints  checkpatch: cuppress warnings when Reported-by: is followed by Link:  MAINTAINERS: add Alexander as a kcov reviewer  mailmap: update Alexander Sverdlin&apos;s Email addresses  fs: fat: inode: replace sprintf() with scnprintf()  ocfs2: fix out-of-bounds write in ocfs2_remove_refcount_extent  ocfs2: fix race between ocfs2_control_install_private() and ocfs2_control_release()  ocfs2/dlm: require a ref for locking_state debugfs open  ocfs2: reject FITRIM ranges shorter than a cluster  ocfs2: validate fast symlink target during inode read  ocfs2: add journal NULL check in ocfs2_checkpoint_inode()  ...

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Sun, 21 Jun 2026 22:20:19 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>f8115f0e8a0585ef1c03d07a68b989023097d16c - Merge tag &apos;slab-for-7.2&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#f8115f0e8a0585ef1c03d07a68b989023097d16c</link>
        <description>Merge tag &apos;slab-for-7.2&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slabPull slab updates from Vlastimil Babka: - Support for &quot;allocation tokens&quot; (currently available in Clang 22+)   for smarter partitioning of kmalloc caches based on the allocated   object type, which can be enabled instead of the &quot;random&quot;   per-caller-address-hash partitioning.   It should be able to deterministically separate types containing a   pointer from those that do not (Marco Elver) - Improvements and simplification of the kmem_cache_alloc_bulk() and   mempool_alloc_bulk() API. This includes adaptation of callers   (Christoph Hellwig) - Performance improvements and cleanups related mostly to sheaves   refill (Hao Li, Shengming Hu, Vlastimil Babka) - Several fixups for the slabinfo tool (Xuewen Wang)* tag &apos;slab-for-7.2&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab:  mm/slab: do not limit zeroing to orig_size when only red zoning is enabled  mm/slub: preserve original size in _kmalloc_nolock_noprof retry path  mm: simplify the mempool_alloc_bulk API  mm/slab: improve kmem_cache_alloc_bulk  mm/slub: detach and reattach partial slabs in batch  mm/slub: introduce helpers for node partial slab state  mm/slub: use empty sheaf helpers for oversized sheaves  tools/mm/slabinfo: remove redundant slab-&gt;partial assignment  tools/mm/slabinfo: remove dead assignment in get_obj_and_str()  tools/mm/slabinfo: Fix trace disable logic inversion  MAINTAINERS: add slab-related scripts and tools to SLAB ALLOCATOR  mm/slub: fix typo in sheaves comment  mm, slab: simplify returning slab in __refill_objects_node()  mm, slab: add an optimistic __slab_try_return_freelist()  slab: fix kernel-docs for mm-api  slab: improve KMALLOC_PARTITION_RANDOM randomness  slab: support for compiler-assisted type-based slab cache partitioning  mm/slub: defer freelist construction until after bulk allocation from a new slab

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Tue, 16 Jun 2026 05:14:43 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>2cbf335f8ccc7a6418159858dc03e36df8e3e5cf - Merge tag &apos;sched-core-2026-06-14&apos; of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#2cbf335f8ccc7a6418159858dc03e36df8e3e5cf</link>
        <description>Merge tag &apos;sched-core-2026-06-14&apos; of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tipPull scheduler updates from Ingo Molnar: &quot;SMP load-balancing updates:   - A large series to introduce infrastructure for cache-aware load     balancing, with the goal of co-locating tasks that share data     within the same Last Level Cache (LLC) domain. By improving cache     locality, the scheduler can reduce cache bouncing and cache misses,     ultimately improving data access efficiency.     Implemented by Chen Yu and Tim Chen, based on early prototype work     by Peter Zijlstra, with fixes by Jianyong Wu, Peter Zijlstra and     Shrikanth Hegde.   - A series to simplify CONFIG_SCHED_SMT ifdef usage (Shrikanth Hegde)  Fair scheduler updates:   - A series to improve SD_ASYM_CPUCAPACITY scheduling by introducing     SMT awareness (Andrea Righi, K Prateek Nayak)   - A series to optimize cfs_rq and sched_entity allocation for better     data locality (Zecheng Li)   - A preparatory series to change fair/cgroup scheduling to a single     runqueue, without the final change (Peter Zijlstra)   - Auto-manage ext/fair dl_server bandwidth (Andrea Righi)   - Fix cpu_util runnable_avg arithmetic (Hongyan Xia)   - Optimize update_tg_load_avg()&apos;s rate-limiting code (Rik van Riel)   - Allow account_cfs_rq_runtime() to throttle current hierarchy     (K Prateek Nayak)   - Update util_est after updating util_avg during dequeue, to fix the     util signal update logic, which reduces signal noise (Vincent     Guittot)  Scheduler topology updates:   - Allow multiple domains to claim sched_domain_shared (K Prateek     Nayak)   - Add parameter to split LLC (Peter Zijlstra)  Core scheduler updates:   - Use trace_call__&lt;tp&gt;() to save a static branch (Gabriele Monaco)  Scheduler statistics updates:   - Drop now-stale mul_u64_u64_div_u64() cputime over-approximation     guard (Nicolas Pitre)  Deadline scheduler updates:   - Reject debugfs dl_server writes for offline CPUs (Andrea Righi)   - Fix replenishment logic for non-deferred servers (Yuri Andriaccio)  RT scheduling updates:   - Turn RT_PUSH_IPI default off for non PREEMPT_RT (Steven Rostedt)   - Update default bandwidth for real-time tasks to 1.0 (Yuri     Andriaccio)  Proxy scheduling updates:   - A series to implement Optimized Donor Migration for Proxy Execution     (John Stultz, Peter Zijlstra)   - Various proxy scheduling cleanups and fixes (Peter Zijlstra,     K Prateek Nayak)  Misc fixes, improvements and cleanups by Aaron Lu, Andrea Righi,  Zenghui Yu, Chen Yu, Guanyou.Chen, John Stultz, Shrikanth Hegde,  Peter Zijlstra, Liang Luo and Yiyang Chen&quot;* tag &apos;sched-core-2026-06-14&apos; of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip: (91 commits)  sched/fair: Fix newidle vs core-sched  sched/deadline: Use task_on_rq_migrating() helper  sched/core: Combine separate &apos;else&apos; and &apos;if&apos; statements  sched/fair: Fix cpu_util runnable_avg arithmetic  sched/fair: Unify cfs_rq throttling via account_cfs_rq_runtime()  sched/fair: Move the throttled tasks to a local list in tg_unthrottle_up()  sched/fair: Call update_curr() before unthrottling the hierarchy  sched/fair: Use throttled_csd_list for local unthrottle  sched/fair: Convert cfs bandwidth throttling to use guards  sched/fair: Allocate cfs_tg_state with percpu allocator  sched/fair: Remove task_group-&gt;se pointer array  sched/fair: Co-locate cfs_rq and sched_entity in cfs_tg_state  sched: restore timer_slack_ns when resetting RT policy on fork  MAINTAINERS: Fix spelling mistake in Peter&apos;s name  sched: Simplify ttwu_runnable()  sched/proxy: Remove superfluous clear_task_blocked_in()  sched/proxy: Remove PROXY_WAKING  sched/proxy: Switch proxy to use p-&gt;is_blocked  sched/proxy: Only return migrate when needed  sched: Be more strict about p-&gt;is_blocked  ...

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Mon, 15 Jun 2026 11:20:18 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>764e77d868a5b932c709e20ddb5993f9111a841c - Merge tag &apos;locking-core-2026-06-14&apos; of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#764e77d868a5b932c709e20ddb5993f9111a841c</link>
        <description>Merge tag &apos;locking-core-2026-06-14&apos; of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tipPull locking updates from Ingo Molnar: &quot;Futex updates:   - Optimize futex hash bucket access patterns (Peter Zijlstra)   - Large series to address the robust futex unlock race for real, by     Thomas Gleixner:      &quot;The robust futex unlock mechanism is racy in respect to the       clearing of the robust_list_head::list_op_pending pointer because       unlock and clearing the pointer are not atomic.       The race window is between the unlock and clearing the pending op       pointer. If the task is forced to exit in this window, exit will       access a potentially invalid pending op pointer when cleaning up       the robust list.       That happens if another task manages to unmap the object       containing the lock before the cleanup, which results in an UAF.       In the worst case this UAF can lead to memory corruption when       unrelated content has been mapped to the same address by the time       the access happens.       User space can&apos;t solve this problem without help from the kernel.       This series provides the kernel side infrastructure to help it       along:        1) Combined unlock, pointer clearing, wake-up for the           contended case        2) VDSO based unlock and pointer clearing helpers with a           fix-up function in the kernel when user space was interrupted           within the critical section.      ... with help by Andr&#233; Almeida:        - Add a note about robust list race condition (Andr&#233; Almeida)        - Add self-tests for robust release operations (Andr&#233; Almeida)  Context analysis updates:   - Implement context analysis for &apos;struct rt_mutex&apos;. (Bart Van Assche)   - Bump required Clang version to 23 (Marco Elver)  Guard infrastructure updates:   - Series to remove NULL check from unconditional guards (Dmitry     Ilvokhin)  Lockdep updates:   - Restore self-test migrate_disable() and sched_rt_mutex state on     PREEMPT_RT (Karl Mehltretter)  Membarriers updates:   - Use per-CPU mutexes for targeted commands (Aniket Gattani)   - Modernize membarrier_global_expedited with cleanup guards (Aniket     Gattani)   - Add rseq stress test for CFS throttle interactions (Aniket Gattani)  percpu-rwsems updates:   - Extract __percpu_up_read() to optimize inlining overhead (Dmitry     Ilvokhin)  Seqlocks updates:   - Allow UBSAN_ALIGNMENT to fail optimizing (Heiko Carstens)  Lock tracing:   - Add contended_release tracepoint to sleepable locks such as     mutexes, percpu-rwsems, rtmutexes, rwsems and semaphores (Dmitry     Ilvokhin)  MAINTAINERS updates:   - MAINTAINERS: Add RUST [SYNC] entry (Boqun Feng)  Misc updates and fixes by Randy Dunlap, YE WEI-HONG, Fabricio Parra,  Dmitry Ilvokhin and Peter Zijlstra&quot;* tag &apos;locking-core-2026-06-14&apos; of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip: (36 commits)  locking: Add contended_release tracepoint to sleepable locks  locking/percpu-rwsem: Extract __percpu_up_read()  tracing/lock: Remove unnecessary linux/sched.h include  futex: Optimize futex hash bucket access patterns  rust: sync: completion: Mark inline complete_all and wait_for_completion  MAINTAINERS: Add RUST [SYNC] entry  cleanup: Specify nonnull argument index  selftests: futex: Add tests for robust release operations  Documentation: futex: Add a note about robust list race condition  x86/vdso: Implement __vdso_futex_robust_try_unlock()  x86/vdso: Prepare for robust futex unlock support  futex: Provide infrastructure to plug the non contended robust futex unlock race  futex: Add robust futex unlock IP range  futex: Add support for unlocking robust futexes  futex: Cleanup UAPI defines  x86: Select ARCH_MEMORY_ORDER_TSO  uaccess: Provide unsafe_atomic_store_release_user()  futex: Provide UABI defines for robust list entry modifiers  futex: Move futex related mm_struct data into a struct  futex: Make futex_mm_init() void  ...

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Mon, 15 Jun 2026 10:51:14 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>b079329b8691768962aa514b8f8c9077ca352459 - Merge tag &apos;rust-7.2&apos; of gitolite.kernel.org:pub/scm/linux/kernel/git/ojeda/linux</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#b079329b8691768962aa514b8f8c9077ca352459</link>
        <description>Merge tag &apos;rust-7.2&apos; of gitolite.kernel.org:pub/scm/linux/kernel/git/ojeda/linuxPull Rust updates from Miguel Ojeda: &quot;This one is big due to the vendoring of the `zerocopy` library, which  allows us to replace a bunch of `unsafe` code dealing with conversions  between byte sequences and other types with safe alternatives. More  details on that below (and in its merge commit).  Toolchain and infrastructure:   - Introduce support for the &apos;zerocopy&apos; library [1][2]:         Fast, safe, compile error. Pick two.         Zerocopy makes zero-cost memory manipulation effortless. We write         `unsafe` so you don&apos;t have to.     It essentially provides derivable traits (e.g. &apos;FromBytes&apos;) and     macros (e.g. &apos;transmute!&apos;) for safely converting between byte     sequences and other types. Having such support allows us to remove     some &apos;unsafe&apos; code.     It is among the most downloaded Rust crates and it is also used by     the Rust compiler itself.     It is licensed under &quot;BSD-2-Clause OR Apache-2.0 OR MIT&quot;.     The crates are imported essentially as-is (only +2/-3 lines needed     to be adapted), plus SPDX identifiers. Upstream has since added the     SPDX identifiers as well as one of the tweaks at my request, thus     reducing our future diffs on updates -- I keep the details in one     of our usual live lists [3].     In total, it is about ~39k lines added, ~32k without counting     &apos;benches/&apos; which are just for documentation purposes.     The series includes a few Kbuild and rust-analyzer improvements and     an example patch using it in Nova, removing one &apos;unsafe impl&apos;.     I checked that the codegen of an isolated example function (similar     to the Nova patch on top) is essentially identical. It also turns     out that (for that particular case) the &apos;zerocopy&apos; version, even     with &apos;debug-assertions&apos; enabled, has no remaining panics, unlike a     few in the current code (since the compiler can prove the remaining     &apos;ub_checks&apos; statically).     So their &quot;fast, safe&quot; does indeed check out -- at least in that     case.   - Support AutoFDO. This allows Rust code to be profiled and optimized     based on the profile. Tested with Rust Binder: ~13% slower without     AutoFDO in the binderAddInts benchmark (using an app-launch     benchmark for the profile).   - Support Software Tag-Based KASAN.     In addition, fix KASAN Kconfig by requiring Clang.   - Add Kconfig options for each existing Rust KUnit test suite, such     as &apos;CONFIG_RUST_BITMAP_KUNIT_TEST&apos;.     They are placed within a new menu, &apos;CONFIG_RUST_KUNIT_TESTS&apos;, in     the new &apos;rust/kernel/Kconfig.test&apos; file.   - Support the upcoming Rust 1.98.0 release (expected 2026-08-20):     lint cleanups and an unstable flag rename.   - Disable &apos;rustdoc&apos; documentation inlining for all prelude items,     which bloats the generated documentation.   - Ignore (in Git) and clean (in Kbuild) the (rarely) &apos;rustc&apos;-generated     &apos;*.long-type-*.txt&apos; files.  &apos;kernel&apos; crate:   - Add new &apos;bitfield&apos; module with the &apos;bitfield!&apos; macro (extracted     from the existing &apos;register!&apos; one), which declares integer types     that are split into distinct bit fields of arbitrary length.     Each field is a &apos;Bounded&apos; of the appropriate bit width (ensuring     values are properly validated and avoiding implicit data loss) and     gets several generated getters and setters (infallible, &apos;const&apos; and     fallible) as well as associated constants (&apos;_MASK&apos;, &apos;_SHIFT&apos; and     &apos;_RANGE&apos;). It also supports fields that can be converted from/to     custom types, either fallibly (&apos;?=&gt;&apos;) or infallibly (&apos;=&gt;&apos;).     For instance:         bitfield! {             struct Rgb(u16) {                 15:11 blue;                 10:5 green;                 4:0 red;             }         }         // Compile-time checks.         let color = Rgb::zeroed().with_const_green::&lt;0x1f&gt;();         assert_eq!(color.green(), 0x1f);         assert_eq!(color.into_raw(), 0x1f &lt;&lt; Rgb::GREEN_SHIFT);     Add as well documentation and a test suite for it, as usual; and     update the &apos;register!&apos; macro to use it.     It will be maintained by Alexandre Courbot (with Yury Norov as     reviewer) under a new &apos;MAINTAINERS&apos; entry: &apos;RUST [BITFIELD]&apos;.   - &apos;ptr&apos; module: rework index projection syntax into keyworded syntax     and introduce panicking variant.     The keyword syntax (&apos;build:&apos;, &apos;try:&apos;, &apos;panic:&apos;) is more explicit     and paves the way of perhaps adding more flavors in the future,     e.g. an &apos;unsafe&apos; index projection.     For instance, projections now look like this:         fn f(p: *const [u8; 32]) -&gt; Result {             // Ok, within bounds, checked at build time.             project!(p, [build: 1]);             // Build error.             project!(p, [build: 128]);             // `OutOfBound` runtime error (convertible to `ERANGE`).             project!(p, [try: 128]);             // Runtime panic.             project!(p, [panic: 128]);             Ok(())         }     Update as well the users, which now look like e.g.         // Pointer to the first entry of the GSP message queue.         let data = project!(self.0.as_ptr(), .gspq.msgq.data[build: 0]);   - &apos;build_assert&apos; module: make the module the home of its macros     instead of rendering them twice.   - &apos;sync&apos; module: add &apos;UniqueArc::as_ptr()&apos; associated function.   - &apos;alloc&apos; module:       - Fix the &apos;Vec::reserve()&apos; doctest to properly account for the         existing vector length in the capacity assertion.       - Fix an incorrect operator in the &apos;Vec::extend_with()&apos; &apos;SAFETY&apos;         comment; add a doc test demonstrating basic usage and the         zero-length case.   - Clean imports across several modules to follow the &quot;kernel     vertical&quot; import style in order to minimize conflicts.  &apos;pin-init&apos; crate:   - User visible changes:       - Do not generate &apos;non_snake_case&apos; warnings for identifiers that         are syntactically just users of a field name. This would allow         all &apos;#[allow(non_snake_case)]&apos; in nova-core to be removed,         which Gary will send to the nova tree next cycle.       - Filter non-cfg attributes out properly in derived structs. This         improves pin-init compatibility with other derive macros.       - Insert projection types&apos; where clause properly.   - Other changes:       - Bump MSRV to 1.82, plus associated cleanups.       - Overhaul how init slots are projected. The new approach is         easier to justify with safety comments.       - Mark more functions as inline, which should help mitigate the         super-long symbol name issue due to lack of inlining.  rust-analyzer:   - Support &apos;--envs&apos; for passing env vars for crates like &apos;zerocopy&apos;.  &apos;MAINTAINERS&apos;:   - Add the following reviewers to the &apos;RUST&apos; entry:       - Daniel Almeida       - Tamir Duberstein       - Alexandre Courbot       - Onur &#214;zkan     They have been involved in the Rust for Linux project for about 7     collective years and bring expertise across several domains, which     will be very useful to have around in the future.     Thanks everyone for stepping up!  And some other fixes, cleanups and improvements&quot;Link: https://github.com/google/zerocopy [1]Link: https://docs.rs/zerocopy [2]Link: https://github.com/Rust-for-Linux/linux/issues/1239 [3]* tag &apos;rust-7.2&apos; of gitolite.kernel.org:pub/scm/linux/kernel/git/ojeda/linux: (86 commits)  MAINTAINERS: add Onur &#214;zkan as Rust reviewer  MAINTAINERS: add Alexandre Courbot as Rust reviewer  MAINTAINERS: add Tamir Duberstein as Rust reviewer  MAINTAINERS: add Daniel Almeida as Rust reviewer  kbuild: rust: clean `zerocopy-derive` in `mrproper`  rust: make `build_assert` module the home of related macros  rust: str: clean unused import for Rust &gt;= 1.98  rust: str: use the &quot;kernel vertical&quot; imports style  rust: aref: use the &quot;kernel vertical&quot; imports style  rust: page: use the &quot;kernel vertical&quot; imports style  gpu: nova-core: firmware: parse `FalconUCodeDescV2` via `zerocopy`  rust: prelude: add `zerocopy{,_derive}::FromBytes`  rust: zerocopy-derive: enable support in kbuild  rust: zerocopy-derive: add `README.md`  rust: zerocopy-derive: avoid generating non-ASCII identifiers  rust: zerocopy-derive: add SPDX License Identifiers  rust: zerocopy-derive: import crate  rust: zerocopy: enable support in kbuild  rust: zerocopy: add `README.md`  rust: zerocopy: remove float `Display` support  ...

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Mon, 15 Jun 2026 05:55:48 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>e74b7a3f5aee02c7df33c79991fd867ce421051b - rust: tests: add Kconfig for KUnit test</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#e74b7a3f5aee02c7df33c79991fd867ce421051b</link>
        <description>rust: tests: add Kconfig for KUnit testThere are 6 individual Rust KUnit test suites (plus the doctests one). Allthe tests are compiled unconditionally now, which adds ~200 kB to thekernel image for me on x86_64. As Rust matures, this bloating willinevitably grow.Add Kconfig.test which includes a RUST_KUNIT_TESTS menu, and allindividual tests under it.As usual, new tests are all enabled if KUNIT_ALL_TESTS=y.Suggested-by: Alice Ryhl &lt;aliceryhl@google.com&gt;Signed-off-by: Yury Norov &lt;ynorov@nvidia.com&gt;Reviewed-by: David Gow &lt;david@davidgow.net&gt;Acked-by: Gary Guo &lt;gary@garyguo.net&gt;Link: https://patch.msgid.link/20260417031531.315281-3-ynorov@nvidia.com[ Fixed capitalization. Used singular for &quot;API&quot; for consistency.  Reworded to clarify these are suites and that there exists  the doctests one (which is the biggest at the moment by  far). - Miguel ]Signed-off-by: Miguel Ojeda &lt;ojeda@kernel.org&gt;

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Fri, 17 Apr 2026 05:15:28 +0200</pubDate>
        <dc:creator>Yury Norov &lt;ynorov@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>042df0c1d48609a85580dcbaff498c95ced20a5f - futex: Add robust futex unlock IP range</title>
        <link>http://kernelsources.org:8080/source/history/linux/init/Kconfig#042df0c1d48609a85580dcbaff498c95ced20a5f</link>
        <description>futex: Add robust futex unlock IP rangeThere will be a VDSO function to unlock robust futexes in user space. Theunlock sequence is racy vs. clearing the list_pending_op pointer in thetasks robust list head. To plug this race the kernel needs to know theinstruction window. As the VDSO is per MM the addresses are stored inmm_struct::futex.Architectures which implement support for this have to update theseaddresses when the VDSO is (re)mapped and indicate the pending op pointersize which is matching the IP.Arguably this could be resolved by chasing mm-&gt;context-&gt;vdso-&gt;image, butthat&apos;s architecture specific and requires to touch quite some cachelines. Having it in mm::futex reduces the cache line impact and avoidshaving yet another set of architecture specific functionality.To support multi size robust list applications (gaming) this provides tworanges when COMPAT is enabled.Signed-off-by: Thomas Gleixner &lt;tglx@kernel.org&gt;Signed-off-by: Peter Zijlstra (Intel) &lt;peterz@infradead.org&gt;Reviewed-by: Andr&#233; Almeida &lt;andrealmeid@igalia.com&gt;Link: https://patch.msgid.link/20260602090535.718926819@kernel.org

            List of files:
            /linux/init/Kconfig</description>
        <pubDate>Tue, 02 Jun 2026 11:09:59 +0200</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
