)]}'
{
  "log": [
    {
      "commit": "f66469d9905b39d2c260a15d7d6db450f4db67c1",
      "tree": "ce6e028e57b075aabbc4e0e5cf6e039455fa12a9",
      "parents": [
        "2d2200551ccc3b9e444aecb59c4b53287e169266",
        "fafbc4051123d5459ea6950899cec08ed946e278"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 18:00:16 2026 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 18:00:16 2026 -0800"
      },
      "message": "Merge tag \u0027net-7.4-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net\n\nPull networking fixes from Paolo Abeni:\n \"Including fixes from Bluetooth, IPsec, WiFi and CAN.\n\n  Current release - regressions:\n\n    - eth: wwan: mhi_wwan_ctrl: send a DTR drop before it can be coalesced\n\n  Previous releases - regressions:\n\n    - core:\n       - use a dedicated flag to track disabled napi instances\n       - frags: limit the truesize of a reassembly queue\n       - reject a negative TCP header offset in qdisc_pkt_len_segs_init()y\n\n    - tcp:\n       - reject unhashed sockets during established lookups\n       - free ireq-\u003eipv6_opt after an RCU grace period\n\n    - ipv6:\n       - fix fib6 walker UAF on NLM_F_REPLACE\n       - raw: fix use-after-free in rawv6_send_hdrinc()\n\n    - wifi:\n       - mac80211: reinstate IEEE80211_TX_CTL_AMPDU, fix ath9k stall\n       - brcmfmac: map msgbuf RX packet IDs bidirectional, fix firmware\n         crash loop\n\n    - vsock: size receive SKBs from declared payload\n\n    - xfrm: fix use-after-free of migrated state in xfrm_do_migrate_state()\n\n    - bluetooth: hci_sync: copy the LE accept list under hdev-\u003elock\n\n    - ptp: fix use-after-free in extts_fifo_show() reading tsevqs unlocked\n\n    - can: protect the receive lists with a per-device lock\n\n    - eth:\n       - bnxt: don\u0027t keep MSI-X vectors added before FW reserves them\n       - vxlan: stop rejecting dynamic FDB entries with a nexthop ID\n\n  Previous releases - always broken:\n\n    - sched: sch_qfq: prevent aggregate self-replacement\n\n    - bridge: disable MRP ports before the FDB flush in del_nbp()\n\n    - mptcp: do not use fast open on MP_JOIN subflows\n\n    - ipv6: serialize multicast router socket ownership\n\n    - bluetooth: hci_core: keep link-key filtering inside RCU\n\n    - eth:\n       - atl1c: drop oversized RX frames instead of panicking\n       - stmmac: a bunch of XDP path fixes\n       - b53: enable IGMP and MLD control packet CPU copies\"\n\n* tag \u0027net-7.4-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net: (170 commits)\n  tcp: ipv6: free ireq-\u003eipv6_opt after an RCU grace period\n  mptcp: pm: kernel: use RCU to free endpoint listeners\n  tcp: initialize send sequence numbers before deferring TFO\n  net: bridge: disable MRP ports before the FDB flush in del_nbp()\n  net: stmmac: set XDP metadata length on the page_pool RX path\n  bonding: fix missing down path on speed/duplex failure after FAIL-\u003eUP\n  ip6mr: Serialize multicast router socket ownership\n  bonding: 3ad: don\u0027t set BOND_LINK_FAIL on a slave that is not up\n  net: ethernet: ti: am65-cpsw-nuss: Enable timestamping of unicast PTP packets\n  net: count last skb of each sk_backlog pass in __release_sock()\n  net: 8139cp: keep Rx masked while NAPI is scheduled\n  net/smc: don\u0027t spin in smc_rx_recvmsg() while a pipe holds spliced data\n  net: dsa: b53: restore the NSP IMP port 2 Gbps mode\n  net: ethernet: bgmac: preserve forced 2.5 Gbps link speed\n  l2tp: only return sessions of the given tunnel in l2tp_session_get()\n  tipc: raise the minimum bearer MTU to fit tunnel and crypto overhead\n  mptcp: do not use Fast Open on MP_JOIN subflows\n  tcp: ipv6: do not read ireq-\u003epktopts from tcp_v6_send_synack()\n  ipv4: Call rt_add_uncached_list() if !do_cache in ip_route_input_slow().\n  ipv6: Flush rt-\u003efrom in rt6_uncached_list_flush_dev().\n  ...\n"
    },
    {
      "commit": "2d2200551ccc3b9e444aecb59c4b53287e169266",
      "tree": "ba0fdc02abf88b45affba21916f7fadbed222632",
      "parents": [
        "eedaa7d61f1ec8ae053a9ece0d553785350ac486",
        "086aeca907789bd2604f16f07bfc073b19015015"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 17:32:20 2026 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 17:32:20 2026 -0800"
      },
      "message": "Merge tag \u0027platform-drivers-x86-v7.4-2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86\n\nPull platform driver fixes from Ilpo Järvinen:\n\n - arm64: asus-glymur-ec: Resolve config loop due to THERMAL symbol\n\n - uniwill-laptop: Add .hw_offloaded() to avoid leds subsystem warning\n   about missing callback\n\n* tag \u0027platform-drivers-x86-v7.4-2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86:\n  platform/x86: uniwill-laptop: Implement .hw_offloaded trigger callback\n  platform: arm64: drop the vacuous THERMAL dependency from EC_ASUS_GLYMUR\n"
    },
    {
      "commit": "eedaa7d61f1ec8ae053a9ece0d553785350ac486",
      "tree": "0dc683e608627133cbbf3910d485ee86e71058ea",
      "parents": [
        "3e516eae690b3f24c19168cc0fe605e1c610eb21",
        "2433db2af8e1482a3a50b8cefaf25cf7e4a9374d"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 16:51:29 2026 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 16:51:29 2026 -0800"
      },
      "message": "Merge tag \u0027chrome-platform-firmware-fixes-v7.4-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux\n\nPull chrome platform firmware fixes from Tzung-Bi Shih:\n\n - Don\u0027t skip CBMEM entries outside of known memory resources\n\n - Fix a Coccinelle warning for error-pointer handling in coreboot-cfr\n\n* tag \u0027chrome-platform-firmware-fixes-v7.4-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux:\n  firmware: coreboot: Fix CFR error-pointer handling warning\n  firmware: coreboot: Don\u0027t skip CBMEM entries outside of known memory\n"
    },
    {
      "commit": "3e516eae690b3f24c19168cc0fe605e1c610eb21",
      "tree": "0e43cabe52b1df9cc2abae2610c049f3875dc7c2",
      "parents": [
        "69e2b55fc3b4fa3639b8c320374c255f046ddda5",
        "e395bbf3ddf1b3175fd3bddaead63a2909b33694"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 16:37:21 2026 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 16:37:21 2026 -0800"
      },
      "message": "Merge tag \u0027hwmon-for-v7.4-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging\n\nPull hwmon fixes from Guenter Roeck:\n\n - acpi_power_meter: Check for 32-bit and 64-bit unknown ACPI values,\n   Fix missing locking in sysfs show callbacks and resume, and Prevent\n   spurious power alarm when power is unknown\n\n - aquacomputer_d5next: Avoid truncating scaled sensor readings, Check\n   maxcollection when probing AQUAERO devices, and reject short status\n   reports\n\n - asus_rog_ryujin: Fix pump control source on the Ryujin III, and Fix\n   timeout when reading 0% duty cycle\n\n - asus_wmi_sensors: Avoid global struct mutation\n\n - chipcap2: Series of fixes addressing various bugs in the driver\n\n - coretemp: Check for NULL platform device in hotplug callbacks, Fix\n   32-bit jiffies wraparound in show_temp() hnd Set nr_cores only after\n   core_data allocation succeeds\n\n - corsair-cpro: Cache fan target only after a successful command\n\n - gpd-fan: Reset both fans to automatic on duo boards, and Update the\n   speed cache before dropping the PM reference\n\n - hp-wmi-sensors: Avoid global struct mutation, Fix unbounded loops in\n   scale_numeric_sensor(), and Serialize alarm flag read-and-clear with\n   state-\u003elock\n\n - lm75: Fix setting polarity mask for chips with 16-bit config register\n\n - lm87: Fix drvdata type confusion in vrm_show() and vrm_store()\n\n - nct6683: Fix incorrect struct cast in show_pwm() and store_pwm()\n\n - peci/dimmtemp: Fix devres leak and UAF on concurrent unbind\n\n - pmbus core: Check return value from pmbus_thermal_add_sensor(),\n   Register the thermal sensors with a 0-based index, and Fix return\n   value check from thermal zone registration, and release devres\n   allocated memory after devm_thermal_of_zone_register error\n\n - pmbus/q54sj108a2: Add missing NULL pointer check\n\n - sht15: Stop deferred work before releasing its resources\n\n - sht4x: Convert update_interval to jiffies in pending data check\n\n - tmp108: Fix initial conversion delay and wait until ready\n\n* tag \u0027hwmon-for-v7.4-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging: (41 commits)\n  hwmon: (asus_rog_ryujin) Fix timeout when reading 0% duty cycle\n  hwmon: (hp-wmi-sensors) Serialize alarm flag read-and-clear with state-\u003elock\n  hwmon: (acpi_power_meter) Check for 32-bit and 64-bit unknown ACPI values\n  hwmon: (acpi_power_meter) Prevent spurious power alarm when power is unknown\n  hwmon: (acpi_power_meter) Fix missing locking in sysfs show callbacks and resume\n  hwmon: (aquacomputer_d5next) Avoid truncating scaled sensor readings\n  hwmon: (sht4x) Convert update_interval to jiffies in pending data check\n  hwmon: (coretemp) Fix 32-bit jiffies wraparound in show_temp()\n  hwmon: (coretemp) Set nr_cores only after core_data allocation succeeds\n  hwmon: (coretemp) Check for NULL platform device in hotplug callbacks\n  hwmon: (gpio-fan) Update the speed cache before dropping the PM reference\n  hwmon: (tmp108) Fix initial conversion delay and wait until ready\n  hwmon: (lm75) Fix setting polarity mask for chips with 16-bit config register\n  hwmon: (pmbus) Fix return value check from thermal zone registration\n  hwmon: (pmbus) Release devres allocated memory after devm_thermal_of_zone_register error\n  hwmon: (pmbus) Check return value from pmbus_thermal_add_sensor()\n  hwmon: (pmbus/q54sj108a2) Add missing NULL pointer check\n  hwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind\n  hwmon: (nct6683) Fix incorrect struct cast in show_pwm() and store_pwm()\n  hwmon: (lm87) Fix drvdata type confusion in vrm_show() and vrm_store()\n  ...\n"
    },
    {
      "commit": "69e2b55fc3b4fa3639b8c320374c255f046ddda5",
      "tree": "be00cb69e1108adf375e24fb307aab5b689d1a60",
      "parents": [
        "d68ce4e71248e1ff5af9654b407541d9260b3ba5",
        "1a577f9402c1780cc1e663f48d5dd54c02051b09"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 15:10:52 2026 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 15:10:52 2026 -0800"
      },
      "message": "Merge tag \u0027for_linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost\n\nPull virtio fixes from Michael Tsirkin:\n \"vhost, virtio, and vdpa bugfixes.\n\n  Just a bunch of fixes all over the place\"\n\n* tag \u0027for_linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost: (38 commits)\n  virtio_pci: don\u0027t take the MSI mutex under cpu_hotplug_lock\n  virtio_ring: Initialize id field in packed indirect descriptors\n  vhost-scsi: fix page reference leak in misaligned I/O fallback\n  vduse: fix VA/PA confusion in the coherent page fault path\n  hwrng: virtio - prevent use-after-free after a failed restore\n  virtio: use consistent virtqueue terminology\n  virtio_balloon: initialize wakeup_lock before virtqueues are set up\n  MAINTAINERS: add missing virtio/vdpa/vduse/vhost headers\n  vhost-vdpa: initialize state before publishing cdev\n  vhost: reject backend enable without a kick file\n  vhost-scsi: reject delayed virtqueue setup\n  virtio_ring: use shadow flags when detaching split descriptors\n  vhost-scsi: validate event queue descriptor direction\n  vhost-scsi: do not count PI bytes in the data length\n  vdpa/snet: Don\u0027t discard the DPU error in snet_send_ctrl_msg()\n  iommu/virtio: Reset device before deleting virtqueues on probe failure\n  vhost: fix used ring index wrap in vhost_add_used_n_in_order\n  vhost-scsi: zero misaligned I/O bounce pages\n  vringh: reject empty / undersized indirect descriptor tables\n  virtio_blk: Reset device on probe error paths after DRIVER_OK\n  ...\n"
    },
    {
      "commit": "d68ce4e71248e1ff5af9654b407541d9260b3ba5",
      "tree": "90d3a58f5651b3f3a78c0c753a9770e74b4dab6f",
      "parents": [
        "46a062865b6b6b9a2ba199101b44feb925455c66",
        "71555ae8c7572fd99158013ca2e29187c5d2508d"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 13:13:35 2026 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 13:13:35 2026 -0800"
      },
      "message": "Merge tag \u0027mm-core-7.4-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/mm/core\n\nPull core memory management fixes from David Hildenbrand:\n \"Here\u0027s a bigger set of MM fixes that we didn\u0027t manage to have ready\n  for -rc1. All fixes are stable-worthy; the majority fixes nasty\n  long-standing bugs instead of being purely hotfixes.\n\n  We have some more of these kinds of stable-worthy fixes in the\n  pipeline, but we\u0027ll focus on the really urgent fixes as we get closer\n  to the release.\n\n  (Leaving urgent MM fixes lurking for various weeks is not good, but\n  having too many changes close to the release is also not good, it\u0027s\n  tricky ...)\n\n  Most issues were reported by Anthropic. Others were found while\n  reworking proposed fixes, and of course some of the fixes were just\n  reported and fixed on the mailing list.\n\n  All fixes were in linux-next for several days without changes. Some\n  commit IDs changed recently when I had to drop some non-stable fixes,\n  rebased to -rc1 and picked up more trailers.\n\n  This includes fixes to:\n   - THP (Transparent Huge Pages)\n   - GUP (Get User Pages)\n   - KSM (Kernel Samepage Merging)\n   - USERFAULTFD\n   - SHARED MEMORY (shmem/tmpfs/memfd)\n   - HUGETLB\n   - Core MM, PAGE CACHE and MEMORY RECLAIM\n\n  The main changes are:\n\n   - Prevent information leaks through memfd pinning, and out-of bounds\n     writes in GUP.\n\n   - Fix data loss in shmem, THP collapse, KSM and memfd pinning.\n\n   - Fix corruption and reference-counting errors with huge PMD/PUD\n     mappings, and incorrect TLB flushing and unmapping.\n\n   - Fix various use-after-free bugs, deadlocks and unkillable loops,\n     witha a focus on shmem swap handling.\n\n   - Fix execution-seal enforcement for memfd (incl. hugetlb).\n\n  Other changes fix accounting, quota and userfaultfd (un)registration\n  handling\"\n\n* tag \u0027mm-core-7.4-rc2\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/mm/core: (61 commits)\n  mm/gup: check folio-\u003emapping under folio lock in memfd_pin_folios()\n  khugepaged: fix readahead lock inversion in collapse_file()\n  mm/huge_memory: set the mmu_gather page size in zap_huge_pud()\n  mm/memory-tiers: unregister empty tiers outside memory_tier_lock\n  mm/cma: don\u0027t release CMA pages still in use\n  mm/vma: don\u0027t leak the charge for stack growth\n  mm/huge_memory: split huge PUDs when adjusting VMA boundaries\n  mm/vma: call -\u003emay_split() before a partial merge\n  mm/ksm: check large swap-cache folios before mapping them\n  mm/ksm: fix use of a freed anon_vma at swap-in\n  mm/ksm: reset the unstable trees of all nodes\n  mm: fix deadlock of mremap() against UFFDIO_MOVE\n  mm: fix unkillable fault loop on MAP_DROPPABLE memory\n  mm: fix unmap_mapping_range() beyond 4 GiB on 32-bit\n  mm/memory: reject remote COW faults on PFN mappings\n  mm/madvise: fix data loss from MADV_FREE on a KSM page\n  mm/mremap: fix moving PUD leaves\n  mm/mremap: recheck PUDs under the page table lock\n  mm/mremap: use pudp_huge_get_and_clear() when moving huge PUDs\n  mm/mmu_notifier: set -\u003emm only after mmgrab()\n  ...\n"
    },
    {
      "commit": "46a062865b6b6b9a2ba199101b44feb925455c66",
      "tree": "e2949d7e0aeda38114a1df371b34893c46c145d5",
      "parents": [
        "afd661f6a26438c407bd9928ea16e80c14b121d9",
        "5b4696e0bfc358619adaeab25ad35b4979af8331"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 13:05:13 2026 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 13:05:13 2026 -0800"
      },
      "message": "Merge tag \u0027mm-nonmm-hotfixes-stable-2026-11-04-20-26\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm\n\nPull non-MM fixes from Andrew Morton:\n \"22 patches. 17 are cc:stable.\n\n  Most are OCFS2 fixes. These address extended-attribute corruption,\n  missing attributes and kernel BUGs, along with crashes during cluster\n  configuration, lock migration, recovery and unmount. Extent movement\n  is also fixed to validate its range against a stable file size.\n\n  Three FAT changes prevent a failed-write/FIBMAP race from spuriously\n  making the filesystem read-only, correct directory link counts after\n  rename, and speed up file expansion. The reported QEMU benchmarks show\n  particularly large improvements on synchronous mounts.\n\n  A taint-string fix prevents an out-of-bounds read which can expose\n  slab contents in the kernel log. There are also build fixes for\n  OpenRISC modules on CPUs without hardware multiply and for Clang 24\"\n\n* tag \u0027mm-nonmm-hotfixes-stable-2026-11-04-20-26\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (22 commits)\n  ocfs2: cache the mount context for dentry lock callbacks\n  ocfs2: wait for filecheck kobject release after a failed add\n  fat: fix parent link count when replacing a sibling directory\n  ocfs2/cluster: unlink socket containers before releasing resources\n  ocfs2: stop recovery before shutting down local allocators\n  ocfs2/dlm: serialize migration MLE cleanup on failure\n  panic: zero the dynamically allocated taint buffer\n  ocfs2: keep locking_state within the cluster connection lifetime\n  MAINTAINERS: mailmap: use Clément Léger\u0027s linux.dev mail address\n  MAINTAINERS: add an IPC entry\n  ocfs2: validate move extents against a stable EOF\n  fat: hold truncate_lock in fat_write_failed()\n  fat: preallocate space before expanding in fat_cont_expand()\n  ocfs2: do not read the entry array of an empty xattr block\n  ocfs2: do not index before the entry array when dividing an empty bucket\n  ocfs2: do not read the entry array of an empty xattr bucket\n  ocfs2: find the xattr entry again after converting a block to a bucket\n  ocfs2: find the xattr entry again after defragmenting a bucket\n  ocfs2: read the xattr entry hash before defragmenting the bucket\n  ocfs2/heartbeat: serialize concurrent writes to a region\u0027s dev attribute\n  ...\n"
    },
    {
      "commit": "afd661f6a26438c407bd9928ea16e80c14b121d9",
      "tree": "6ecd7744905f3e3949e4b5f07deb5bf79ff0fdfc",
      "parents": [
        "05441d697f7f9a927264f4058cbbc6a03dfcac9d",
        "19eab4cf787c917bfb7615460933e4ae894af65b"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 12:32:29 2026 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Nov 05 12:32:29 2026 -0800"
      },
      "message": "Merge tag \u0027mm-hotfixes-stable-2026-11-04-20-02\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm\n\nPull MM fixes from Andrew Morton:\n\n - \"mm: avoid losing atomic VMA flags\" (Lorenzo Stoakes):\n\n   Preserve guard-page and soft-dirty state across VMA changes. Prevent\n   fork and THP collapse from losing guard markers, and keep changes\n   visible to applications which track modified memory.\n\n - \"MAINTAINERS: MM updates\" (David Hildenbrand):\n\n   Start routing more MM components through mm/core.git and add Zi Yan\n   as a THP co-maintainer. Update component coverage and integration\n   branches as part of the transition to separate MM component trees.\n\n - \"mm/hugetlb: fix mremap bugs\" (Li Zhe):\n\n   Fix hugetlb mremap deadlocks and truncated move lengths. Prevent\n   userfaultfd poison markers from affecting other processes through\n   shared hugetlb page tables.\n\n - \"MAINTAINERS updates for page and slab allocators\" (Vlastimil Babka):\n\n   Add Johannes Weiner as a page allocator co-maintainer and update page\n   and slab allocator entries for their component trees and integration\n   through mm/linux.\n\n - \"mm/damon: fix three race bugs in sysfs and core\" (SJ Park):\n\n   Serialize DAMOS tuning updates and stop monitoring contexts from\n   sharing mutable state. Avoid interference between concurrent DAMON\n   instances and incorrect auto-tuning.\n\n - \"mm: page_alloc: fix reserve access for non-blocking requests\"\n   (Johannes Weiner):\n\n   Stop ordinary non-blocking allocations from consuming reserves or\n   bypassing watermarks. Avoid severe allocation stalls under memory\n   pressure and preserve reserves for requests entitled to use them.\n\n - \"mm/cma: accept memory of CMA areas reserved with memblock_reserve()\"\n   (Mike Rapoport):\n\n   Accept memory in fixed-address and multi-range CMA reservations.\n   Prevent fatal accesses to these pages in TDX and SEV-SNP guests.\n\n - Summary of singletons in this merge:\n\n   Several fixes address crashes and unsafe memory access. Failed THP\n   collapse now flushes stale translations before releasing pages which\n   another collapse can free. A truncation race with MADV_DONTNEED could\n   remove still-mapped shmem pages and hit a kernel BUG. Large-folio\n   page-table scans no longer wrap addresses and crash near\n   address-space boundaries. Hugetlb vmemmap optimization no longer\n   causes write faults from racing reference-count operations.\n   Memory-cgroup teardown is also protected against reclaim work\n   accessing released state.\n\n   KSM now preserves userfaultfd protection during merging and\n   unmerging, and retains soft-dirty information needed by incremental\n   memory dumpers. Reads of /proc/PID/maps and related files no longer\n   omit continuously mapped ranges during concurrent VMA changes. There\n   are also fixes for expanding mixed mappings with mremap() and\n   querying NUMA placement with tagged addresses. Swapoff checks for\n   signals while processing large address spaces and shmem files, so it\n   can be interrupted without holding up suspend until the whole object\n   is read.\n\n   Costly allocations with cheap smaller-order fallbacks avoid direct\n   reclaim and compaction. Reported arm64 PostgreSQL tests improved from\n   58,602 to 157,246 transactions per second with defrag_mode disabled;\n   this addresses a buffered-write regression under fragmentation.\n   Background reclaim can recover on the highest-numbered memory node\n   after it has given up, and 32-bit writeback threshold calculations no\n   longer overflow and assign incorrect dirty-memory limits.\n\n* tag \u0027mm-hotfixes-stable-2026-11-04-20-02\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (43 commits)\n  MAINTAINERS: move SLAB ALLOCATOR under MEMORY MANAGEMENT\n  MAINTAINERS: add Johannes as the page allocator co-maintainer\n  MAINTAINERS: route more MM changes through mm/core.git\n  MAINTAINERS: rename and move MEMORY HOT(UN)PLUG\n  MAINTAINERS: add missing files to MM component sections\n  MAINTAINERS: sort entries in MM sections\n  MAINTAINERS: add Zi Yan as co-maintainer for MEMORY MANAGEMENT - THP\n  MAINTAINERS: TMPFS (SHMEM FILESYSTEM) updates\n  MAINTAINERS: mention for-next branch in MEMORY MANAGEMENT - MEMORY MAP\n  mm: memcontrol: fix NULL pointer deref and UAF from high_work_func() on dying memcg\n  mm/cma: accept memory of CMA areas reserved at a fixed address\n  mm/cma: accept memory of multi-range CMA areas\n  mm/page_alloc: avoid direct reclaim and compaction for costly __GFP_NORETRY allocations\n  mm: page_alloc: remove ALLOC_NON_BLOCK from ALLOC_RESERVES\n  mm: page_alloc: do not give all non-blocking requests reserve access\n  mm/hugetlb_vmemmap: map the shared tail page writable\n  fs/proc/task_mmu: fix missed VMAs when reading /proc/PID/maps and friends\n  selftests/mm: fix khugepaged_race build with older glibc\n  mm/vma: update VMA iterator state on error in new VMA merge\n  mm/migrate: snapshot the source nid before the misplaced migration\n  ...\n"
    },
    {
      "commit": "fafbc4051123d5459ea6950899cec08ed946e278",
      "tree": "5ee02308dc7ba4452e49b702d960aed5b72ea468",
      "parents": [
        "49b09ae0bf57b4230187d4cdd0a370558e44a6e8"
      ],
      "author": {
        "name": "Eric Dumazet",
        "email": "edumazet@kernel.org",
        "time": "Tue Nov 03 10:00:11 2026 +0100"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 15:07:23 2026 +0100"
      },
      "message": "tcp: ipv6: free ireq-\u003eipv6_opt after an RCU grace period\n\nireq-\u003eipv6_opt is only set by calipso_req_setattr(), when a CALIPSO\nNetLabel mapping is configured.\n\nRequest socket migration (net.ipv4.tcp_migrate_req\u003d1, or a\nBPF_SK_REUSEPORT_SELECT_OR_MIGRATE program) clones the request\nsocket with inet_reqsk_clone(), so that the old request socket and\nits clone share the same ipv6_opt, then reqsk_migrate_reset() clears\nthe pointer in the old one.\n\nAnother cpu holding a reference on the old request socket can still\nbe using these options, sending a SYNACK from tcp_v6_send_synack()\nor creating a child in tcp_v6_syn_recv_sock(), when the clone\nis freed. tcp_v6_reqsk_destructor() frees ipv6_opt with a plain\nkfree(), leading to a use-after-free.\n\nBoth readers already run under RCU, like their IPv4 counterparts.\nUse kfree_rcu() in tcp_v6_reqsk_destructor(), as commit e3f33b0a1d89\n(\"ipv4: free inet_opt and ireq_opt after an RCU grace period\") did\nfor ireq_opt.\n\nFixes: c905dee62232 (\"tcp: Migrate TCP_NEW_SYN_RECV requests at retransmitting SYN+ACKs.\")\nReported-by: Sashiko \u003csashiko-bot@kernel.org\u003e\nCloses: https://lore.kernel.org/netdev/179369559062.488856.15441115725436277776@kernel.org/\nSigned-off-by: Eric Dumazet \u003cedumazet@kernel.org\u003e\nReviewed-by: Hangbin Liu \u003cliuhangbin@kylinos.cn\u003e\nReviewed-by: Jiayuan Chen \u003cjiayuan.chen@linux.dev\u003e\nReviewed-by: Kuniyuki Iwashima \u003ckuniyu@google.com\u003e\nTested-by: Linkui Xiao \u003cxiaolinkui@kylinos.cn\u003e\nLink: https://patch.msgid.link/20261103090011.4128420-1-edumazet@kernel.org\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "49b09ae0bf57b4230187d4cdd0a370558e44a6e8",
      "tree": "ce5eac15d5225510c288460a9309e427499bd8b7",
      "parents": [
        "57889a8f6d49fc153aa0017d13086ab736567f8a"
      ],
      "author": {
        "name": "Kyle Zeng",
        "email": "kylebot@openai.com",
        "time": "Thu Oct 29 21:22:55 2026 -0700"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 15:01:42 2026 +0100"
      },
      "message": "mptcp: pm: kernel: use RCU to free endpoint listeners\n\nmptcp_pm_nl_create_listen_socket() starts the TCP listener directly\ninstead of going through mptcp_listen(). It consequently misses setting\nSOCK_RCU_FREE on the parent MPTCP socket.\n\ntcp_child_process() can invoke the listener\u0027s subflow_data_ready()\ncallback without holding the MPTCP parent lock or a reference to the\nparent. An authenticated MP_JOIN racing with endpoint teardown can\ntherefore access the parent after its last reference has been dropped.\nThe ADD_ADDR error path can also close an already published listener.\n\nSet SOCK_RCU_FREE before __inet_listen_sk() publishes the TCP listener,\nmatching mptcp_listen(). This protects the parent on every subsequent\nclose path, including a failed endpoint addition.\n\nFixes: 1729cf186d8a (\"mptcp: create the listening socket for new port\")\nCc: stable@vger.kernel.org\nSigned-off-by: Kyle Zeng \u003ckylebot@openai.com\u003e\nReviewed-by: Matthieu Baerts (NGI0) \u003cmatttbe@kernel.org\u003e\nLink: https://patch.msgid.link/20261030042255.74216-1-kylebot@openai.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "57889a8f6d49fc153aa0017d13086ab736567f8a",
      "tree": "7100680ab8abb88ad7004414a283379c300cdefb",
      "parents": [
        "37dfd0efbfffc20a57e41c2eb349ac49b1ca1ff8"
      ],
      "author": {
        "name": "Qingfang Deng",
        "email": "qingfang.deng@linux.dev",
        "time": "Mon Nov 02 11:59:43 2026 +0800"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 12:36:46 2026 +0100"
      },
      "message": "tcp: initialize send sequence numbers before deferring TFO\n\nTCP_FASTOPEN_CONNECT can return from connect() before tcp_connect_init()\nwhen a cached cookie or cookieless Fast Open allows deferring the SYN.\nAt this point write_seq contains the initial sequence number, while\nsnd_una and snd_nxt have not been initialized to that sequence number.\n\nConsequently, inet_diag and /proc/net/tcp{,6} report the initial\nsequence number as the send queue length despite no SYN or payload being\nqueued.\n\nInitialize snd_una and snd_nxt to write_seq before marking the\nconnection as deferred. Both sequence-based queue lengths then remain\nzero until the first write starts the connection and runs\ntcp_connect_init().\n\nFixes: 19f6d3f3c842 (\"net/tcp-fastopen: Add new API support\")\nSigned-off-by: Qingfang Deng \u003cqingfang.deng@linux.dev\u003e\nReviewed-by: Eric Dumazet \u003cedumazet@kernel.org\u003e\nReviewed-by: Kuniyuki Iwashima \u003ckuniyu@google.com\u003e\nReviewed-by: Kuniyuki Iwashima \u003ckuniyu@google.com\u003e\nReviewed-by: Neal Cardwell \u003cncardwell@google.com\u003e\nLink: https://patch.msgid.link/20261102035943.9700-1-qingfang.deng@linux.dev\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "37dfd0efbfffc20a57e41c2eb349ac49b1ca1ff8",
      "tree": "93660a34fd000cd14f4a2e6a0e1a9b6c5c89718b",
      "parents": [
        "6d9b7c85af57305ec2bd5907124478867edcc60b"
      ],
      "author": {
        "name": "Cheng Yongkang",
        "email": "teel4res@gmail.com",
        "time": "Sat Oct 31 21:48:40 2026 -0700"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 12:14:28 2026 +0100"
      },
      "message": "net: bridge: disable MRP ports before the FDB flush in del_nbp()\n\ndel_nbp() flushes the port\u0027s FDB entries before it unregisters the RX\nhandler. For a normal port, br_stp_disable_port() moves the port to\nBR_STATE_DISABLED before this cleanup.\n\nThat does not hold for an MRP ring port. br_set_state() ignores state\nchanges while BR_MRP_AWARE_BIT is set, so br_stp_disable_port() leaves\nthe port state alone. br_mrp_port_del() then restores forwarding when\nthe bridge is up before clearing the bit. A frame received between\nbr_fdb_cleanup_by_dst() and netdev_rx_handler_unregister() can therefore\ncreate a new FDB entry referencing the dying port. Nothing removes that\nentry before destroy_nbp_rcu() frees the port, so a later frame to the\nlearned MAC can be forwarded through the freed port.\n\nRemove the MRP and CFM instances before disabling the port, so that\nbr_stp_disable_port() actually transitions it to BR_STATE_DISABLED.\nWith CONFIG_BRIDGE_VLAN_FILTERING\u003dy, synchronize_net() in\nnbp_vlan_group_unpublish() also drains receive paths that could still\nlearn with the old state before the final FDB cleanup.\n\nFound through an LLM-assisted source code analysis workflow and\nreproduced on net with KASAN and CONFIG_BRIDGE_VLAN_FILTERING\u003dy in QEMU.\nA diagnostic switchdev module accepts MRP objects and delays the\nNETDEV_CHANGEUPPER callback for 1.5 s, holding del_nbp() after the FDB\ncleanup and before RX handler removal. The reproducer floods the MRP\nport with rotating source MACs, waits for the port\u0027s RCU callback\nthrough the module\u0027s rcu_barrier(), then sends frames to those MACs\nfrom another port. The unpatched kernel reports:\n\n  BUG: KASAN: slab-use-after-free in br_forward+0xb1/0x820\n  Call Trace:\n   \u003cIRQ\u003e\n   br_forward+0xb1/0x820\n   br_handle_frame_finish+0x148b/0x1e50\n   br_handle_frame+0x90a/0x15c0\n\nWith this patch, three runs of six cycles each reach the delay without\na KASAN report.\n\nFixes: 6536993371fa (\"bridge: mrp: Integrate MRP into the bridge\")\nSuggested-by: Ido Schimmel \u003cidosch@nvidia.com\u003e\nLink: https://lore.kernel.org/netdev/20261012123051.GA714215@shredder/\nCloses: https://lore.kernel.org/netdev/20261022090431.3641707-1-teel4res@gmail.com/\nSigned-off-by: Cheng Yongkang \u003cteel4res@gmail.com\u003e\nReviewed-by: Ido Schimmel \u003cidosch@nvidia.com\u003e\nLink: https://patch.msgid.link/20261101044840.1595584-1-1020691186@qq.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "6d9b7c85af57305ec2bd5907124478867edcc60b",
      "tree": "6ffe993f5f39a17450365125285d95d580bec24f",
      "parents": [
        "a76ab5e733b41dede6f238a691eefb4374f99f79"
      ],
      "author": {
        "name": "Lorenzo Bianconi",
        "email": "lorenzo.bianconi@oss.qualcomm.com",
        "time": "Mon Nov 02 12:46:04 2026 +0100"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 12:08:32 2026 +0100"
      },
      "message": "net: stmmac: set XDP metadata length on the page_pool RX path\n\nstmmac_rx() initializes the XDP buffer with the metadata area valid, so\nan XDP program can reserve metadata with bpf_xdp_adjust_meta() and write\nit in [xdp-\u003edata_meta, xdp-\u003edata), for example to export the RX hardware\ntimestamp obtained from the metadata kfunc. When such a frame is passed\nto the stack, the skb is built in place around the same page with\nnapi_build_skb(), but skb_metadata_set() is never called.\n\nnapi_build_skb() clears skb_shared_info up to dataref, which includes\nmeta_len, so skb_metadata_len() stays zero. The stack and TC BPF then see\nan empty metadata range even though the bytes are present in the skb\nheadroom. The AF_XDP zero-copy path already records the length in\nstmmac_construct_skb_zc().\n\nRecord the metadata length after reserving the headroom and adding the\nframe data. No copy is needed because the skb is built over the buffer the\nXDP program wrote to. With the length recorded, the software VLAN\nstripping path can move the metadata together with the MAC header, as it\nalready does for zero-copy frames.\n\nFixes: e3f9c3e34840 (\"net: stmmac: add Rx HWTS metadata to XDP receive pkt\")\nSigned-off-by: Lorenzo Bianconi \u003clorenzo.bianconi@oss.qualcomm.com\u003e\nReviewed-by: Daniel Machon \u003cdaniel.machon@microchip.com\u003e\nReviewed-by: Nicolai Buchwitz \u003cnb@tipi-net.de\u003e\nReviewed-by: Maxime Chevallier \u003cmaxime.chevallier@bootlin.com\u003e\nLink: https://patch.msgid.link/20261102-stmmac_meatada_pp_path-v1-1-d93cc4f9a864@oss.qualcomm.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "a76ab5e733b41dede6f238a691eefb4374f99f79",
      "tree": "87cc489029a1535be33c1462f83550d1ace4f5e5",
      "parents": [
        "c6b41de4dd9f2d6856d8d8d292348f7961034152"
      ],
      "author": {
        "name": "Timur Stukan",
        "email": "timur.stukan.linux@gmail.com",
        "time": "Sun Nov 01 17:02:39 2026 +0200"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 11:53:05 2026 +0100"
      },
      "message": "bonding: fix missing down path on speed/duplex failure after FAIL-\u003eUP\n\nIn bond_miimon_commit(), when a slave is proposed as BOND_LINK_UP but\nbond_update_speed_duplex() fails in bonding mode that needs speed/duplex\n(802.3ad, tlb, alb), the slave is set to BOND_LINK_DOWN directly. This\nbypasses bond_set_slave_link_state(), bond_miimon_link_change() and\nfailover.\n\nThis is fine for slave that coming from BOND_LINK_BACK, which was never\nbrought up and is not in use. But since commit 1899bb325149 (\"bonding:\nfix state transition issue in link monitoring\") the commit phase also\nhandles BOND_LINK_FAIL -\u003e BOND_LINK_UP which means a slave that is still\nin use and may be curr_active_slave.\n\nIf the link recovers within downdelay and goes down again before the\ncommit phase reads speed/duplex, the slave is silently marked down while\nremaining the active slave in worst cases. In alb/tlb the bond MAC stays\non the dead port, no failover happens and TLB/RLB state is not cleaned,\nso the bond stops passing traffic until that link comes back even though\nother slaves are up. A non-active slave is affected too, in alb, RLB\nclients assigned to it are not reassigned and become unreachable.\n\nReproduced in tlb and alb mode with miimon\u003d100 and downdelay\u003d10000 by\nflapping a slave within downdelay and dropping it again before commit\n(a longer delay was added between inspect and commit to make window\nwider and easier to test):\n  bond0: (slave enp0s3): link status down for interface, disabling it in 10000 ms\n  bond0: (slave enp0s3): link status up again after 3400 ms\n  bond0: (slave enp0s3): failed to get link speed/duplex\n\nprocfs then shows the active slave with \"MII Status: down\" and \"Link\nFailure Count: 0\", and all traffic is lost.\n\nFix this by dropping the loop in bond_mii_monitor() that applied all\nproposed link states before bond_miimon_commit(). bond_miimon_commit()\nnow applies each state itself: UP after the speed/duplex check, as it\nalready did, DOWN in the down path, and FAIL/BACK directly. So when the\nspeed/duplex check runs, slave-\u003elink still holds the previous state. If\nthe check fails for a slave that is FAIL or UP, take it through the\nregular down path, including failover. DOWN and BACK slaves were\nnever brought up and are still just reverted to DOWN. The down path is\nmoved into bond_miimon_slave_down() so both callers share it.\n\nAfter the fix:\n  bond0: (slave enp0s3): failed to get link speed/duplex\n  bond0: (slave enp0s3): link status definitely down, disabling slave\n  bond0: (slave enp0s4): making interface the new active one\n\nFixes: 1899bb325149 (\"bonding: fix state transition issue in link monitoring\")\nSigned-off-by: Timur Stukan \u003ctimur.stukan.linux@gmail.com\u003e\nReviewed-by: Hangbin Liu \u003cliuhangbin@kylinos.cn\u003e\nLink: https://patch.msgid.link/20261101150240.66292-1-timur.stukan.linux@gmail.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "c6b41de4dd9f2d6856d8d8d292348f7961034152",
      "tree": "cbd1f87f78b68760d7db07c584b80209eedeb008",
      "parents": [
        "9a65b9c2a97594bcaaf393329807653eff895bbf"
      ],
      "author": {
        "name": "Kyle Zeng",
        "email": "kylebot@openai.com",
        "time": "Thu Oct 29 21:22:21 2026 -0700"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 11:33:48 2026 +0100"
      },
      "message": "ip6mr: Serialize multicast router socket ownership\n\nMRT6_TABLE checks whether the socket owns its current table before\nacquiring RTNL. MRT6_INIT also looks up its table before taking RTNL.\nConsequently, concurrent TABLE and INIT calls can initialize the old\ntable and then change the socket\u0027s selected table. Another INIT can\nregister the same socket in the new table.\n\nrawv6_close() calls ip6mr_sk_done(), which clears only the first table\nowned by the socket. After the socket\u0027s RCU-delayed free, the other\ntable retains a dangling mroute_sk pointer. A subsequent multicast cache\nreport passes that pointer to sock_queue_rcv_skb_reason(). This produces\na KASAN slab-use-after-free in sk_filter_trim_cap().\n\nLook up the selected table in ip6mr_sk_init() after acquiring RTNL.\nLikewise, re-read the current table and check its owner under RTNL in\nMRT6_TABLE before updating the selection. This preserves the single-table\nownership invariant shared with ip6mr_sk_done(), without changing the\nlocking of the other multicast socket options.\n\nFixes: d1db275dd3f6 (\"ipv6: ip6mr: support multiple tables\")\nSigned-off-by: Kyle Zeng \u003ckylebot@openai.com\u003e\nReviewed-by: Ido Schimmel \u003cidosch@nvidia.com\u003e\nLink: https://patch.msgid.link/20261030042221.73996-1-kylebot@openai.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "9a65b9c2a97594bcaaf393329807653eff895bbf",
      "tree": "53775dd15e782cc1c46d669989782fe8123b7e0e",
      "parents": [
        "6887a8f98244ba4c0fbe2d2461b9b8f8a300e326"
      ],
      "author": {
        "name": "Timur Stukan",
        "email": "timur.stukan.linux@gmail.com",
        "time": "Sun Nov 01 16:56:53 2026 +0200"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 11:26:32 2026 +0100"
      },
      "message": "bonding: 3ad: don\u0027t set BOND_LINK_FAIL on a slave that is not up\n\nIn 802.3ad mode, when bond_update_speed_duplex() fails on NETDEV_UP or\nNETDEV_CHANGE, bond_slave_netdev_event() sets the slave link to FAIL if\nthe slave has ever been up (last_link_up !\u003d 0), and to DOWN otherwise,\nso that miimon can set it right once speed/duplex are valid.\n\nlast_link_up is never cleared, so a slave that is currently DOWN but\nwas up before is set to FAIL as well. miimon then treats it as a slave\nthat is still in use and takes it through the full down path again:\nthe link failure count is incremented, \"link status definitely down\"\nis logged and the 802.3ad port is disabled a second time, although the\nslave has not been up since it went down.\n\nReproduced in 802.3ad mode with miimon\u003d100 by setting a slave down and\nup again. On NETDEV_UP the speed is still unknown, so the notifier sets\nFAIL, and the next miimon pass sees no carrier and proposes DOWN:\n\n\tip link add bond0 type bond mode 802.3ad miimon 100 lacp_rate 1\n\tip link set enp0s3 down\n\tip link set enp0s4 down\n\tip link set enp0s3 master bond0\n\tip link set enp0s4 master bond0\n\tip link set enp0s3 up\n\tip link set enp0s4 up\n\tip link set bond0 up\n\t# wait for LACP to settle\n\tip link set enp0s3 down\n\tip link set enp0s3 up\n\nprocfs then shows \"Link Failure Count: 2\" in enp0s3 slave part. Also in\ndmesg wrote twice: \"link status definitely down, disabling slave\".\n\nFix this by setting FAIL only for a slave that is currently UP and\nleaving other states alone. An up slave that loses speed/duplex still\ngoes through FAIL as before, and DOWN/BACK slaves are left to miimon,\nas in the other modes.\n\nFixes: ea53abfab960 (\"bonding/802.3ad: fix link_failure_count tracking\")\nSigned-off-by: Timur Stukan \u003ctimur.stukan.linux@gmail.com\u003e\nReviewed-by: Hangbin Liu \u003cliuhangbin@kylinos.cn\u003e\nLink: https://patch.msgid.link/20261101145653.63648-1-timur.stukan.linux@gmail.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "6887a8f98244ba4c0fbe2d2461b9b8f8a300e326",
      "tree": "2233a6724cce217a0982dd9ce481406bfd804616",
      "parents": [
        "c4e4056b21355356f6a95bcdf03a850edd9f49e7"
      ],
      "author": {
        "name": "James Clark",
        "email": "jjc@jclark.com",
        "time": "Mon Nov 02 20:51:17 2026 +0700"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 11:20:32 2026 +0100"
      },
      "message": "net: ethernet: ti: am65-cpsw-nuss: Enable timestamping of unicast PTP packets\n\nOn a BeagleY-AI (J722S), ptp4l as a unicast master (unicast_listen) logs\n\"received DELAY_REQ without timestamp\" for each unicast Delay_Req, and\nits port goes to FAULTY after \"timed out while polling for tx timestamp\"\nfor the first unicast Sync.\n\nam65_cpsw_nuss_hwtstamp_set() does not set the TS_UNI_EN bit (bit 24) of\nthe port\u0027s TS_CTL_LTYPE2 register. According to the TRM (J722S TRM\nSPRUJB3D, 12.2.1.4.7.13.5.1 Ethernet Port Receive Event and\n12.2.1.4.7.13.5.2 Ethernet Port Transmit Event), this bit must be set\nfor the port to timestamp PTP event messages over UDP sent to a unicast\naddress; without it, only messages sent to the PTP multicast addresses\nselected by the TS_107 and TS_129 to TS_132 bits are timestamped. TI\u0027s\nnetcp_ethss driver for the Keystone 2 Ethernet switch, which has the\nsame timestamping registers, always sets TS_UNI_EN.\n\nSet TS_UNI_EN along with the other bits. With this change, ptp4l in the\nsame setup gets timestamps for the unicast Delay_Req and Sync messages.\n\nFixes: b1f66a5bee07 (\"net: ethernet: ti: am65-cpsw-nuss: enable packet timestamping support\")\nCc: stable@vger.kernel.org\nSigned-off-by: James Clark \u003cjjc@jclark.com\u003e\nReviewed-by: Sebastian Andrzej Siewior \u003cbigeasy@linutronix.de\u003e\nLink: https://patch.msgid.link/20261102135117.419539-1-jjc@jclark.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "c4e4056b21355356f6a95bcdf03a850edd9f49e7",
      "tree": "669ffa725a9285f3a0067907642ca0fbee79d9f4",
      "parents": [
        "547b1ae5ec50b7d81b05b4219e0db7e56279d65f"
      ],
      "author": {
        "name": "Ray Zhang",
        "email": "sgzhang@google.com",
        "time": "Sun Nov 01 00:51:45 2026 -0700"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 11:16:38 2026 +0100"
      },
      "message": "net: count last skb of each sk_backlog pass in __release_sock()\n\nRunning 500 concurrent TCPv6 streams (neper \"tcp_stream -6 -T 1 -F 500\")\non a 2-core Cortex-A53 (CONFIG_PREEMPT_NONE\u003dy, HZ\u003d1000, LATENCY_WARN)\ntriggers resched_latency_warn() in __release_sock():\n\n  [ 3655.311821] sched: CPU 0 need_resched set for \u003e 100006892 ns (100 ticks) without schedule\n  [ 3655.311889] Call trace:\n  ...\n  [ 3655.311944]  resched_latency_warn+0x7c/0x88\n  [ 3655.311958]  sched_tick+0x1c0/0x418\n  ...\n  [ 3655.312578]  net_rx_action+0x238/0x438\n  ...\n  [ 3655.312641]  do_softirq+0x4c/0x90\n  [ 3655.312651]  __local_bh_enable_ip+0x84/0x90\n  [ 3655.312663]  local_bh_enable+0x1c/0x28\n  [ 3655.312674]  __dev_queue_xmit+0x4a8/0xb00\n  ...\n  [ 3655.312782]  tcp_v6_do_rcv+0x240/0x5f8\n  [ 3655.312793]  __release_sock+0x9c/0x188\n  [ 3655.312806]  release_sock+0x150/0x168\n  [ 3655.312817]  tcp_sendmsg+0x4c/0x70\n\n__release_sock() can loop past 100 ms without calling cond_resched():\n\n- Each outer-loop pass drains sk_backlog, but \"if (!skb) break;\" runs\n  before \"++nb\", so a pass of B skbs only adds B - 1 to nb (0 for 1 skb).\n- With 500 TCPv6 streams and NAPI sharing two Cortex-A53 cores, runnable\n  tasks keep TIF_NEED_RESCHED set on CPU 0.\n- During spin_unlock_bh() and TX softirqs (__dev_queue_xmit() -\u003e\n  local_bh_enable()), tcp_add_backlog() coalesces arriving pure ACKs into\n  a single tail skb.\n- Repeated 1-skb passes never advance nb or call cond_resched(),\n  triggering resched_latency_warn() after 100 ticks.\n\nRestore the do-while loop and drop \"if (!skb) break;\" so every skb\nincrements nb across passes and calls cond_resched() every 16 skbs.\n\nReproduced the issue and verified the fix on two 2-core Cortex-A53 hosts\n(CONFIG_PREEMPT_NONE\u003dy, HZ\u003d1000, LATENCY_WARN, latency_warn_once\u003d0) with\na userspace reproducer over /dev/net/tun:\n\n- CPU 0 runs a TCPv6 sender and a second runnable task while CPU 1 writes\n  pure ACKs to /dev/net/tun (~30k TCPBacklogCoalesce/run), sustaining\n  1-skb sk_backlog refills in __release_sock() for ~400 ms (ftrace).\n- Before: CPU 0 stayed unscheduled in __release_sock(), hitting\n  resched_latency_warn() 293 and 275 times on the two hosts (\u003e 100.9 ms).\n- After: cond_resched() yielded CPU 0 inside __release_sock(), with\n  0 resched_latency_warn() hits on both hosts.\n- Also observed no regression with the workload from\n  commit 16c610162d1f (\"net: call cond_resched() less often in\n  __release_sock()\"), \"super_netperf 4 -H srv -T,10 -l 3000 \u0026\".\n\nFixes: 16c610162d1f (\"net: call cond_resched() less often in __release_sock()\")\nCc: stable@vger.kernel.org\nSigned-off-by: Ray Zhang \u003csgzhang@google.com\u003e\nReviewed-by: Kuniyuki Iwashima \u003ckuniyu@google.com\u003e\nReviewed-by: Eric Dumazet \u003cedumazet@kernel.org\u003e\nLink: https://patch.msgid.link/20261101075145.698399-1-sgzhang@google.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "547b1ae5ec50b7d81b05b4219e0db7e56279d65f",
      "tree": "e973fdd24e1530181ba0e98a77aa83c14d30ba35",
      "parents": [
        "8288ba942cfd20621c05e16978b7c3da91513ae1"
      ],
      "author": {
        "name": "Colton Pawielski",
        "email": "colton.pawielski@gmail.com",
        "time": "Sat Oct 31 11:47:23 2026 -0500"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 11:09:42 2026 +0100"
      },
      "message": "net: 8139cp: keep Rx masked while NAPI is scheduled\n\ncp_rx_poll() calls napi_complete_done() and only then takes cp-\u003elock\nwith interrupts disabled to unmask the Rx interrupts. An interrupt\nthat is not masked while polling (TxOK, TxErr, ...) can arrive in\nbetween. cp_interrupt() then sees the Rx status bits, which are still\nset, finds NAPI no longer scheduled, masks Rx and schedules NAPI again.\ncp_rx_poll() then carries on and unmasks Rx anyway.\n\nFrom that point Rx interrupts are enabled while NAPI is scheduled:\ncp_interrupt() leaves the Rx bits for the poll routine, does not mask\nthem because napi_schedule_prep() fails, and the level-triggered\ninterrupt fires again as soon as it returns. On an SH7751 LANDISK\nunder combined Tx/Rx load this interrupt storm was captured with a RAM\ntrace right before the board locked up hard.\n\nMask Rx in cp_interrupt() whenever Rx status is pending, not only when\nNAPI gets scheduled. If the race leaves Rx unmasked, the next interrupt\nmasks it again, and the pending poll unmasks it when it completes.\n\nFixes: ab1e7e1d2666 (\"8139cp: use napi_complete_done()\")\nSigned-off-by: Colton Pawielski \u003ccolton.pawielski@gmail.com\u003e\nReviewed-by: Daniel Machon \u003cdaniel.machon@microchip.com\u003e\nLink: https://patch.msgid.link/20261031-b4-8139cp-napi-v2-1-5824797c0fe6@gmail.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "8288ba942cfd20621c05e16978b7c3da91513ae1",
      "tree": "3808f8737881e929393542d8b5de4437f845e6fc",
      "parents": [
        "6c1c41effa342a94221e5d92c2a5aae8fe7d1c04"
      ],
      "author": {
        "name": "Bryam Vargas",
        "email": "hexlabsecurity@proton.me",
        "time": "Thu Oct 29 03:03:33 2026 -0500"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 11:06:27 2026 +0100"
      },
      "message": "net/smc: don\u0027t spin in smc_rx_recvmsg() while a pipe holds spliced data\n\nWhile bytes spliced off the RMB are still in a pipe, recvmsg() waits\nfor the pipe to release them before it copies the data behind them.\nThe path to that wait skips the timeout and signal checks, and\nsmc_rx_wait() returns at once on RCV_SHUTDOWN. With a signal pending,\nafter SHUT_RD, or once the peer closes or shuts down writing,\nrecvmsg() spins on a CPU until the pipe is drained, and SIGKILL cannot\nstop it. MSG_DONTWAIT and an expired SO_RCVTIMEO wait there too\ninstead of returning -EAGAIN.\n\nCheck the timeout and signals before that wait, and end it when the\npipe releases the data or the connection is killed, not on RCV_SHUTDOWN.\nA zero-length read returns 0 without waiting for the pipe; a\nnon-blocking one returns -EAGAIN while poll() still reports the socket\nreadable (splice() can still take those bytes). The wait sets\nSOCKWQ_ASYNC_WAITDATA like smc_rx_wait(), so a byte arriving behind\nthe pipe raises no SIGIO on a reader already asleep for it, and a full\nbarrier orders its wait queue entry before its read of splice_pending,\nso no wake is lost.\n\nFixes: 9014db202cb7 (\"smc: add support for splice()\")\nCc: stable@vger.kernel.org\nSigned-off-by: Bryam Vargas \u003chexlabsecurity@proton.me\u003e\nReviewed-by: Dust Li \u003cdust.li@linux.alibaba.com\u003e\nLink: https://patch.msgid.link/20261029-b4-disp-da7f8e6a-v2-1-9052904adf72@proton.me\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "6c1c41effa342a94221e5d92c2a5aae8fe7d1c04",
      "tree": "4de356bd78b1074c5da0cb2d36e86a5d4b2942e2",
      "parents": [
        "6baae996ecf6a3f57b08ea6f6786e29af9260f51",
        "2d4c272e816a5b784f1fc7899256f8826df34edb"
      ],
      "author": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 09:21:42 2026 +0100"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Thu Nov 05 09:21:43 2026 +0100"
      },
      "message": "Merge tag \u0027linux-can-fixes-for-7.4-20261103\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can\n\nMarc Kleine-Budde says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\npull-request: can 2026-11-03\n\nthis is a pull request of 15 patches for net/main.\n\nThe first patch is by Vincent Mailhol and drops CAN-XL frames on non\nCAN-XL devices.\n\nA patch by Kaixuan Li for the CAN ISOTP protocol improves the check\nfor the correct CAN CC/FD frames.\n\nThe next 3 patches are by Cunhao Lu and make CAN skb freeing safe in\nany context in several CAN helper functions.\n\nA series by Oliver Hartkopp et al fixes several problems in the CAN\nnet-layer:\n\nOliver Hartkopp contributes a patch to convert the unreliable\nARPHRD_CAN type check to the robust can_get_ml_priv(). Further a patch\nthat adds missing error checking to the bind callback of the CAN\nISO-TP protocol. Followed by converting the CAN RAW, BCM and ISO-TP\nprotocol to protect the receive lists with a per-device lock. Then the\nRAW and ISO-TP protocols are converted to copy the socket options\noutside of lock_sock().\n\n3 patches target the CAN procfs: A patch by Runyu Xiao resets the CAN\npkg_stats using atomics, a patch by Oliver Hartkopp fixes the stats\ncalculation after a statistics reset. Followed by a patch to remove\nkernel pointers from the output.\n\nChunYuZhiQiang contributes 2 patches for the CAN netlink interfaces,\nto prevent waking up the CAN device, if the interface is down.\n\nThe last patch is by Liu Changjie and fixes the decoding of bulk USB\nURBs in the Peak USB CAN driver.\n\nlinux-can-fixes-for-7.4-20261103\n\n* tag \u0027linux-can-fixes-for-7.4-20261103\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can:\n  can: peak_usb: pcan_usb_fd_decode_buf(): accept short uCAN end-of-list records\n  can: dev: can_tdc_fill_info(): don\u0027t read automatic TDCV if interface is down\n  can: dev: can_fill_info(): don\u0027t wake up controller if interface is down\n  can: proc: remove pointers from CAN specific proc output\n  can: proc: skip stats calculation after reset in can_stat_update()\n  can: proc: reset pkg_stats atomics individually\n  can: raw, isotp: copy socket options outside of lock_sock()\n  can: protect the receive lists with a per-device lock\n  can: isotp: check the return values of can_rx_register() in isotp_bind()\n  can: replace ARPHRD_CAN type checks with can_get_ml_priv()\n  can: dev: can_put_echo_skb(): free skb on invalid echo index\n  can: skb: make CAN skb allocation failure paths IRQ-safe\n  can: skb: make echo skb freeing safe in any IRQ context\n  can: isotp: check the frame type, not just the length\n  can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nLink: https://patch.msgid.link/20261103204305.3211144-1-mkl@pengutronix.de\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "6baae996ecf6a3f57b08ea6f6786e29af9260f51",
      "tree": "6274b7ab77f5b1f29bcf1a277e916624c561e804",
      "parents": [
        "a75facf4bb3e866103ddca4f47a6f3ca4b090d8b",
        "41af38324341df9d769641d6485abb67fd5209ed"
      ],
      "author": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 22:18:46 2026 +0100"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 22:18:47 2026 +0100"
      },
      "message": "Merge branch \u0027fix-tcp-retransmissions-on-ns-nsp-socs\u0027\n\nFlorian Fainelli says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nFix TCP retransmissions on NS/NSP SoCs\n\nOn Northstar and Northstar Plus SoCs we would see about 1000 TCP\nretransmissions per second due to a rate mismatch between bgmac and b53,\nmake sure that we run at the same speed on both side to avoid dropping\npackets on the floor.\n\nThis issue was found during testing on a Northstar Plus reference board\n(BCM958625HR) while running iperf3 to a test machine and noticing\nretranmsisions:\n\nConnecting to host 192.168.3.1, port 5201\n[  4] local 192.168.3.204 port 49856 connected to 192.168.3.1 port 5201\n[ ID] Interval           Transfer     Bitrate         Retr  Cwnd\n[  4]   0.00-1.00   sec   111 MBytes   933 Mbits/sec  915   99.0 KBytes\n[  4]   1.00-2.00   sec   111 MBytes   928 Mbits/sec  909    109 KBytes\n[  4]   2.00-3.00   sec   110 MBytes   925 Mbits/sec  1097   99.0 KBytes\n[  4]   3.00-4.00   sec   111 MBytes   928 Mbits/sec  814   58.0 KBytes\n[  4]   4.00-5.00   sec   111 MBytes   930 Mbits/sec  1187    109 KBytes\n[  4]   5.00-6.00   sec   110 MBytes   923 Mbits/sec  893   72.1 KBytes\n[  4]   6.00-7.00   sec   111 MBytes   929 Mbits/sec  843   67.9 KBytes\n[  4]   7.00-8.00   sec   111 MBytes   928 Mbits/sec  920   79.2 KBytes\n[  4]   8.00-9.00   sec   111 MBytes   929 Mbits/sec  1109   66.5 KBytes\n[  4]   9.00-10.00  sec   111 MBytes   930 Mbits/sec  1055   63.6 KBytes\n- - - - - - - - - - - - - - - - - - - - - - - - -\n[ ID] Interval           Transfer     Bitrate         Retr\n[  4]   0.00-10.00  sec  1.09 GBytes   933 Mbits/sec  9742\nsender\n[  4]   0.00-10.01  sec  1.09 GBytes   933 Mbits/sec\nreceiver\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nLink: https://patch.msgid.link/20261029211540.4123250-1-florian.fainelli@broadcom.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "41af38324341df9d769641d6485abb67fd5209ed",
      "tree": "6274b7ab77f5b1f29bcf1a277e916624c561e804",
      "parents": [
        "d4f3d2c04624854d27aa948cd7bfc9d946faaac5"
      ],
      "author": {
        "name": "Florian Fainelli",
        "email": "florian.fainelli@broadcom.com",
        "time": "Thu Oct 29 14:15:40 2026 -0700"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 22:18:44 2026 +0100"
      },
      "message": "net: dsa: b53: restore the NSP IMP port 2 Gbps mode\n\nThe Northstar Plus IMP port uses the switch\u0027s proprietary 2 Gbps mode for\nits internal link to the AMAC.  Its fixed-link description reports 1 Gbps,\nso applying that speed clears PORT_OVERRIDE_SPEED_2000M and leaves the two\nends of the internal link configured at different speeds.\n\nForce the 2 Gbps mode and flow control for BCM5301x and NSP CPU ports.  The\nmismatch caused switch output queue discards on both copper and SerDes\nports, with one discard for every TCP retransmission.  With both ends\nrestored to their high-speed modes, iperf3 reports no retransmissions.\n\nFixes: b6a8a5477fe9 (\"net: dsa: b53: fix resetting speed and pause on forced link\")\nSigned-off-by: Florian Fainelli \u003cflorian.fainelli@broadcom.com\u003e\nReviewed-by: Simon Horman \u003chorms@kernel.org\u003e\nLink: https://patch.msgid.link/20261029211540.4123250-3-florian.fainelli@broadcom.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "d4f3d2c04624854d27aa948cd7bfc9d946faaac5",
      "tree": "05d49b9f78374be490dbdf22340d060230383c5c",
      "parents": [
        "a75facf4bb3e866103ddca4f47a6f3ca4b090d8b"
      ],
      "author": {
        "name": "Florian Fainelli",
        "email": "florian.fainelli@broadcom.com",
        "time": "Thu Oct 29 14:15:39 2026 -0700"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 22:18:44 2026 +0100"
      },
      "message": "net: ethernet: bgmac: preserve forced 2.5 Gbps link speed\n\nNorthstar and Northstar Plus use a 2.5 Gbps internal link between the\nAMAC and the switch.  BGMAC_FEAT_FORCE_SPEED_2500 makes bgmac_miiconfig()\nconfigure that speed, but bgmac_adjust_link() subsequently replaces it\nwith the synthetic fixed PHY\u0027s 1 Gbps speed.\n\nUse the forced speed when processing link changes so the MAC remains at\n2.5 Gbps.  Together with configuring the switch IMP port for its 2 Gbps\nmode, this eliminates the output queue discards that caused approximately\n1000 TCP retransmissions per second during an iperf3 transmit test.\n\nRestrict the platform forced-speed flag to Northstar Plus using the SoC\ncompatible, since Hurricane2 shares the AMAC compatible. Other platform\nAMACs without a phy-handle must continue following the fixed PHY speed.\nThe BCMA path already selects the flag only for the Northstar family.\n\nFixes: f6a95a24957a (\"net: ethernet: bgmac: Add platform device support\")\nSigned-off-by: Florian Fainelli \u003cflorian.fainelli@broadcom.com\u003e\nReviewed-by: Simon Horman \u003chorms@kernel.org\u003e\nLink: https://patch.msgid.link/20261029211540.4123250-2-florian.fainelli@broadcom.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "a75facf4bb3e866103ddca4f47a6f3ca4b090d8b",
      "tree": "79d521d8d2f837fbb21aab6724d574834fc541da",
      "parents": [
        "03897066069fd47caf2908183edf3b22b822ea73"
      ],
      "author": {
        "name": "Hengyu Liang",
        "email": "hengyul@cs.unc.edu",
        "time": "Thu Oct 29 23:26:17 2026 -0400"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 22:11:09 2026 +0100"
      },
      "message": "l2tp: only return sessions of the given tunnel in l2tp_session_get()\n\nCommit 5f77c18ea556 (\"l2tp: use IDR for all session lookups\") made\npppol2tp_connect() and the netlink session commands find sessions with\nl2tp_session_get(), passing the socket of the tunnel they name.\n\nL2TPv3 session IDs are unique per network namespace, except that\nsessions carried over UDP are only unique per UDP socket, the socket of\ntheir tunnel. However, l2tp_v3_session_get() only checks the socket when\nanother session has the same session ID. Otherwise it returns the\nsession, whichever tunnel it belongs to. As of now, a session command\nthat names the wrong tunnel acts on a session of another tunnel, and a\nPPPoL2TP socket for a second L2TPv3 tunnel fails with EEXIST, because it\nfinds session 0 of the first tunnel.\n\nThe issue can be reproduced with:\n\n    ip l2tp add tunnel tunnel_id 3 peer_tunnel_id 3 encap udp \\\n        local 127.0.0.1 remote 127.0.0.1 udp_sport 5003 udp_dport 6003\n    ip l2tp add tunnel tunnel_id 4 peer_tunnel_id 4 encap udp \\\n        local 127.0.0.1 remote 127.0.0.1 udp_sport 5004 udp_dport 6004\n    ip l2tp add session tunnel_id 3 session_id 7 peer_session_id 7\n    ip l2tp del session tunnel_id 4 session_id 7\n    ip l2tp show session\n\nBefore that commit, the delete fails with \"No such device\", and session\n7 of tunnel 3 is still listed. After that commit, the delete succeeds,\nand session 7 of tunnel 3 is gone.\n\nThis patch will make l2tp_session_get() return NULL when the L2TPv3\nsession it finds does not belong to the given socket. The receive path\ncalls l2tp_v3_session_get() directly and is not changed.\n\nFixes: 5f77c18ea556 (\"l2tp: use IDR for all session lookups\")\nCc: stable@vger.kernel.org\nSigned-off-by: Hengyu Liang \u003chengyul@cs.unc.edu\u003e\nAcked-by: Guillaume Nault \u003cgnault@redhat.com\u003e\nLink: https://patch.msgid.link/20261030032617.4065353-1-hengyul@cs.unc.edu\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "03897066069fd47caf2908183edf3b22b822ea73",
      "tree": "444b64b7d4ceeb218d5154c53fff8880cd25e472",
      "parents": [
        "6d2cf411aba2aa0bd641b49be5b1964ac5097a50"
      ],
      "author": {
        "name": "Joas Antonio dos Santos",
        "email": "joasantonio108@gmail.com",
        "time": "Fri Oct 30 20:53:04 2026 -0300"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:55:53 2026 +0100"
      },
      "message": "tipc: raise the minimum bearer MTU to fit tunnel and crypto overhead\n\nA peer can lower the link MTU to TIPC_MIN_BEARER_MTU (100 bytes, plus\nthe UDP encapsulation header) with the max_pkt field of a RESET or\nACTIVATE message; tipc_link_proto_rcv() only checks the lower bound\nreturned by tipc_bearer_min_mtu().  The same bound is applied to the\ndevice MTU when a bearer is enabled.\n\nThat bound predates two later reductions of the link MSS:\n\n  tipc_link_mss() \u003d mtu - INT_H_SIZE                    (tunnel header)\n                         - EMSG_OVERHEAD               (CONFIG_TIPC_CRYPTO)\n\nWith CONFIG_TIPC_CRYPTO\u003dy, which is the default, an MTU of 100 gives an\nMSS of 28.  Once the link comes up, tipc_named_node_up() calls\nnamed_distribute(), which computes\n\n  msg_dsz \u003d ((tipc_node_get_mtu() - INT_H_SIZE) / ITEM_SIZE) * ITEM_SIZE;\n\nFor an MSS of 28 the subtraction is negative and the result truncates to\n0xfffffff0; for an MSS between 40 and 59 it is 0.  named_prepare_buf()\nthen allocates a buffer with no room for any item (the u32 size wraps),\nand msg_rem never reaches zero, so every cluster-scope publication on\nthe node is written with publ_to_item() past the end of that one skb,\nover skb_shared_info and into adjacent memory.\n\nWithout crypto the MSS is at least 60, which still does not hold the\nfirst fragment built by tipc_msg_build(): INT_H_SIZE fragment header\nplus a message header of up to MAX_H_SIZE.  With pktmax below that, the\nheader copies run past the pktmax bytes allocated for the fragment.\n\nRaise TIPC_MIN_BEARER_MTU to MAX_H_SIZE + 2 * INT_H_SIZE so the MSS can\nalways hold INT_H_SIZE + MAX_H_SIZE, which also leaves room for name\ntable items, and add tipc_bearer_mtu_floor(), which adds EMSG_OVERHEAD\non top for CONFIG_TIPC_CRYPTO\u003dy.  Use it for the device MTU check\n(tipc_mtu_bad()), the UDP MTU check, the netlink MTU setting and\ntipc_bearer_min_mtu(), which also bounds the max_pkt negotiation.\n\nFound by manual code review and reproduced with KASAN using two network\nnamespaces joined by a veth pair (see below).\n\nFixes: fc1b6d6de220 (\"tipc: introduce TIPC encryption \u0026 authentication\")\nFixes: 2320bcdae628 (\"tipc: fix changeover issues due to large packet\")\nSuggested-by: Tung Nguyen \u003ctung.quang.nguyen@est.tech\u003e\nSigned-off-by: Joas Antonio dos Santos \u003cjoasantonio108@gmail.com\u003e\nReviewed-by: Tung Nguyen \u003ctung.quang.nguyen@est.tech\u003e\nLink: https://patch.msgid.link/179340438471.4412.6707287163192409104@gmail.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "6d2cf411aba2aa0bd641b49be5b1964ac5097a50",
      "tree": "77e530d688357d82ea63785dac50cb40d7b239e5",
      "parents": [
        "8e069fd3fd396b89af417e50b359bc9892dd41cd"
      ],
      "author": {
        "name": "Yilin Zhang",
        "email": "yilinzhang@moonshot.ai",
        "time": "Fri Oct 30 23:03:51 2026 +0100"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:49:14 2026 +0100"
      },
      "message": "mptcp: do not use Fast Open on MP_JOIN subflows\n\ntcp_fastopen_create_child() hands the SYN packet itself to\nsubflow_syn_recv_sock(). For an MP_JOIN request this takes the\nfatal fallback: the cloned child is destroyed and handed back with\ndrop_req flagged, but tcp_fastopen_create_child() does not check\nthe flag and queues it, so accept() can expose the freed child.\n\nMP_JOIN cannot use Fast Open: data on a subflow requires the\ncompleted HMAC exchange (RFC 8684, sec. 3.2). Refuse it (only the\nTFO path passes a SYN skb here) and let tcp_conn_request() fall\nback to the regular MP_JOIN handshake; also strip the Fast Open\ncookie from MP_JOIN SYN/ACKs.\n\nFixes: 90bf45134d55 (\"mptcp: add new sock flag to deal with join subflows\")\nCc: stable@vger.kernel.org\nReported-by: Kimi Security Team \u003cbug-report@moonshot.ai\u003e\nSuggested-by: Jiayuan Chen \u003cjiayuan.chen@linux.dev\u003e\nSuggested-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\nSigned-off-by: Yilin Zhang \u003cyilinzhang@moonshot.ai\u003e\n[ Moving code to avoid clearing TS and consolidating checks. ]\nSigned-off-by: Matthieu Baerts (NGI0) \u003cmatttbe@kernel.org\u003e\nLink: https://patch.msgid.link/20261030-mptcp-tfo-mpj-v4-1-e6eff2027342@kernel.org\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "e395bbf3ddf1b3175fd3bddaead63a2909b33694",
      "tree": "d4f9abb982022e034c4cf44a8f7108315d4f8ee5",
      "parents": [
        "e6b96b76d7074ae64f0d37d880794c71d3ce277e"
      ],
      "author": {
        "name": "Guenter Roeck",
        "email": "linux@roeck-us.net",
        "time": "Tue Nov 03 19:45:08 2026 -0800"
      },
      "committer": {
        "name": "Guenter Roeck",
        "email": "linux@roeck-us.net",
        "time": "Wed Nov 04 06:43:35 2026 -0800"
      },
      "message": "hwmon: (asus_rog_ryujin) Fix timeout when reading 0% duty cycle\n\nThe device uses the same zero-duty report format for both legitimate 0%\nduty GET responses and SET confirmation ACKs on cooler and controller\nduty channels. To distinguish them, rog_ryujin_raw_event() checks\n!completion_done() on cooler_duty_set and controller_duty_set, assuming\nthis is only true while a SET command is awaiting confirmation.\n\nHowever, init_completion() initializes the completion count to zero, so\n!completion_done() evaluates to true from probe until the first SET\ncommand completes. Likewise, if rog_ryujin_execute_cmd() fails to send a\ncommand, times out, or is interrupted after reinit_completion(), the\ncompletion remains uncompleted. When a valid 0% duty GET response then\narrives, rog_ryujin_raw_event() consumes it as a SET confirmation and\nleaves the pending *_duty_received completion uncompleted, causing\nrog_ryujin_execute_cmd() to wait 1.5 seconds and fail with -ETIMEDOUT.\n\nMark all completions as done with complete_all() after initialization in\nrog_ryujin_probe(), and complete status_completion on error in\nrog_ryujin_execute_cmd(), so !completion_done() is only true while a\ncommand is actively awaiting a response.\n\nFixes: ed3e03790c5c (\"hwmon: Add driver for ASUS ROG RYUJIN II 360 AIO cooler\")\nCc: Aleksa Savic \u003csavicaleksa83@gmail.com\u003e\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\n"
    },
    {
      "commit": "8e069fd3fd396b89af417e50b359bc9892dd41cd",
      "tree": "9c96664a703d98b51c8b4486b80cb0e46c69a867",
      "parents": [
        "58fa96691c1b63bce27b58f32d2b490e89441d5e"
      ],
      "author": {
        "name": "Eric Dumazet",
        "email": "edumazet@kernel.org",
        "time": "Mon Nov 02 08:54:41 2026 +0100"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:42:05 2026 +0100"
      },
      "message": "tcp: ipv6: do not read ireq-\u003epktopts from tcp_v6_send_synack()\n\nWhen IPV6_FL_F_REFLECT is set on a listener, or the\nnet.ipv6.flowlabel_reflect sysctl has FLOWLABEL_REFLECT_ESTABLISHED,\ntcp_v6_send_synack() reflects the flowlabel of the SYN packet,\nreading it from the skb stored in ireq-\u003epktopts.\n\nSince commit 079096f103fa (\"tcp/dccp: install syn_recv requests\ninto ehash table\"), request sockets are processed without holding\nthe listener lock. A cpu can then process a retransmitted SYN for a\nrequest socket, and send a SYNACK from tcp_check_req(), while another\ncpu receives the ACK completing the 3WHS. tcp_v6_syn_recv_sock()\nconsumes ireq-\u003epktopts when it wins the hashdance, and the first cpu\nreads a freed skb:\n\n  BUG: KASAN: slab-use-after-free in tcp_v6_send_synack (include/linux/skbuff.h:3152 include/linux/ipv6.h:110 net/ipv6/tcp_ipv6.c:582)\n  Read of size 8 at addr ffff88802b08b608 by task poc-ipv6-pktopt/5076\n\n  Call Trace:\n   \u003cIRQ\u003e\n   tcp_v6_send_synack (include/linux/skbuff.h:3152 include/linux/ipv6.h:110 net/ipv6/tcp_ipv6.c:582)\n   tcp_rtx_synack (net/ipv4/tcp_output.c:4719)\n   tcp_check_req (net/ipv4/tcp_minisocks.c:762)\n   tcp_v6_rcv (net/ipv6/tcp_ipv6.c:1826)\n   ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:479)\n   ip6_input_finish (net/ipv6/ip6_input.c:534)\n   ip6_input (include/linux/netfilter.h:325 include/linux/netfilter.h:319 net/ipv6/ip6_input.c:545)\n   ipv6_rcv (include/net/dst.h:481 net/ipv6/ip6_input.c:119 include/linux/netfilter.h:325 include/linux/netfilter.h:319 net/ipv6/ip6_input.c:351)\n\n  Freed by task 5074 on cpu 0 at 15.412249s:\n   kmem_cache_free (include/linux/kasan.h:235 mm/slub.c:2780 mm/slub.c:6630 mm/slub.c:6757)\n   tcp_v6_syn_recv_sock (net/ipv6/tcp_ipv6.c:1528)\n   tcp_check_req (net/ipv4/tcp_minisocks.c:934)\n   tcp_v6_rcv (net/ipv6/tcp_ipv6.c:1826)\n   ip6_protocol_deliver_rcu (net/ipv6/ip6_input.c:479)\n   ip6_input_finish (net/ipv6/ip6_input.c:534)\n\nRequest socket migration has the same issue: reqsk_migrate_reset()\ntransfers ireq-\u003epktopts to the clone, which can be freed while\nanother cpu holding a reference on the old request socket is still\nsending a SYNACK.\n\nThe SYNACK timer itself is not an issue, because\ninet_csk_reqsk_queue_drop() calls timer_delete_sync().\n\nSave the flowlabel of the SYN in the request socket instead, so that\ntcp_v6_send_synack() no longer needs ireq-\u003epktopts.\n\nAs a side effect, the flowlabel is also reflected for SYN packets\nreusing a TIME_WAIT socket, as ireq-\u003epktopts is not set in this case.\n\nFixes: e994b2f0fb92 (\"tcp: do not lock listener to process SYN packets\")\nFixes: 079096f103fa (\"tcp/dccp: install syn_recv requests into ehash table\")\nFixes: c905dee62232 (\"tcp: Migrate TCP_NEW_SYN_RECV requests at retransmitting SYN+ACKs.\")\nReported-by: Anvik Loitongbam \u003cpermissiontogallop@gmail.com\u003e\nReported-by: Yingjie Wang \u003cx-professor@outlook.com\u003e\nCloses: https://lore.kernel.org/netdev/82c31e4d5043f3dbd11b44177cfba779d335aae3.1793599929.git.x-professor@outlook.com/\nSigned-off-by: Eric Dumazet \u003cedumazet@kernel.org\u003e\nReviewed-by: Jiayuan Chen \u003cjiayuan.chen@linux.dev\u003e\nReviewed-by: Neal Cardwell \u003cncardwell@google.com\u003e\nReviewed-by: Kuniyuki Iwashima \u003ckuniyu@google.com\u003e\nLink: https://patch.msgid.link/20261102075441.3771550-1-edumazet@kernel.org\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "58fa96691c1b63bce27b58f32d2b490e89441d5e",
      "tree": "965093fccbda20157737b2454c99492eb3fcdb67",
      "parents": [
        "d5e912448cd98b261eba8e35ab838f2dc69a79f5",
        "4019af3afd72864ec6abbfde2d76e416a64456c2"
      ],
      "author": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:34:53 2026 +0100"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:34:53 2026 +0100"
      },
      "message": "Merge branch \u0027ip-fix-route-leak-and-unregister_netdevice-stuck\u0027\n\nKuniyuki Iwashima says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nip: Fix route leak and unregister_netdevice() stuck.\n\nJason Zhang fed commit 0346ec2f080b (\"ipv6: Prevent\nrt6_insert_exception() for dying fib6_info.\") to LLM to\nfind tricks to cause the same symptom:\n\n  unregister_netdevice: waiting for gre6 to become free. Usage count \u003d 4\n  ref_tracker: netdev@000000009652f190 has 1/3 users at\n       dst_alloc+0x14b/0x490\n       ip6_rt_cache_alloc+0x27b/0x670\n       __ip6_rt_update_pmtu+0x572/0x850\n\nThis series treats them.\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nLink: https://patch.msgid.link/20261101064418.2055158-1-kuniyu@google.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "4019af3afd72864ec6abbfde2d76e416a64456c2",
      "tree": "965093fccbda20157737b2454c99492eb3fcdb67",
      "parents": [
        "a0fe1a3f390a75152c7395fdf63fc39da77d7838"
      ],
      "author": {
        "name": "Kuniyuki Iwashima",
        "email": "kuniyu@google.com",
        "time": "Sun Nov 01 06:35:24 2026 +0000"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:34:50 2026 +0100"
      },
      "message": "ipv4: Call rt_add_uncached_list() if !do_cache in ip_route_input_slow().\n\nSince the cited commit, ip_route_input_slow() could call\nrt_dst_alloc() with vrf in the local_input: path.\n\nIf res-\u003efi !\u003d NULL and one of the following is true,\n\n  - a non-zero itag from fib_validate_source_reason()\n    (realms/classid)\n  - RTN_BROADCAST with BC_FORWARDING enabled\n\ndo_cache is set to false.\n\nThen, the route is not added to rt_uncached_list, so the\nroute cannot be removed from rt_flush_dev().\n\nIf the route is cached in sk-\u003esk_rx_dst, removing the\nvrf device gets stuck. [0]\n\nLet\u0027s call rt_add_uncached_list() if !do_cache in\nip_route_input_slow().\n\n[0]:\nunregister_netdevice: waiting for vrf0 to become free. Usage count \u003d 2\nref_tracker: netdev@000000008b304ac4 has 1/1 users at\n     dst_alloc+0x14b/0x490\n     ip_route_input_rcu+0x1540/0x2530\n     ip_route_input_noref+0x5a/0x90\n     ip_rcv_finish_core+0x4b0/0x1140\n     ip_rcv_finish+0xe6/0x190\n     ip_rcv+0x6c/0x130\n     __netif_receive_skb+0x121/0x300\n     process_backlog+0x2df/0x5e0\n     __napi_poll+0x8c/0x380\n     net_rx_action+0x43c/0xab0\n     handle_softirqs+0x19f/0x520\n     do_softirq+0x46/0x60\n     __local_bh_enable_ip+0x79/0x80\n     __dev_queue_xmit+0x1b0e/0x24c0\n     ip_finish_output2+0x8b2/0xcd0\n     ip_output+0xf2/0x1e0\n\nFixes: f5a0aab84b74 (\"net: ipv4: dst for local input routes should use l3mdev if relevant\")\nReported-by: Jason Zhang \u003cjdz@google.com\u003e\nSigned-off-by: Kuniyuki Iwashima \u003ckuniyu@google.com\u003e\nLink: https://patch.msgid.link/20261101064418.2055158-4-kuniyu@google.com\nReviewed-by: Ido Schimmel \u003cidosch@nvidia.com\u003e\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "a0fe1a3f390a75152c7395fdf63fc39da77d7838",
      "tree": "7f0a38ff69c51ba0c86227baf46f65fa3fc5a3fd",
      "parents": [
        "9401b428b5d4dfe1fd5752973fd02b4e9cd05536"
      ],
      "author": {
        "name": "Kuniyuki Iwashima",
        "email": "kuniyu@google.com",
        "time": "Sun Nov 01 06:35:23 2026 +0000"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:34:50 2026 +0100"
      },
      "message": "ipv6: Flush rt-\u003efrom in rt6_uncached_list_flush_dev().\n\nWhen a device is unregistered, rt6_uncached_list_flush_dev()\niterates over uncached routes and switches the dying dev\nwith blackhole_netdev.\n\nHowever, rt-\u003efrom could be cached via sk-\u003esk_rx_dst and\nhold the device reference.\n\nThen, unregister_netdevice() gets stuck with the splat\nbelow. [0]\n\nLet\u0027s release rt-\u003efrom in rt6_uncached_list_flush_dev().\n\nNote that ip6_rt_copy_init() could set rt-\u003efrom even if\nin6_dev_get() returns NULL (e.g. mtu \u003c IPV6_MIN_MTU is\nset concurrently).\n\nAlso, rt-\u003efrom-\u003enh could be replaced with another device\nthan rt_dev and rt_idev-\u003edev, and in such a case,\nnexthop_flush_dev() sets fib6_destroying before\nrt6_uncached_list_flush_dev().\n\n[0]:\nunregister_netdevice: waiting for dummy2 to become free. Usage count \u003d 2\nref_tracker: netdev@000000006fb9da8c has 1/1 users at\n     netdev_get_by_index+0x14c/0x170\n     fib6_nh_init+0x1ae/0x1950\n     ip6_route_info_create_nh+0x15d/0x780\n     ip6_route_add+0x55/0x150\n     inet6_rtm_newroute+0x15d/0x1360\n     rtnetlink_rcv_msg+0x606/0x710\n     netlink_rcv_skb+0x14f/0x2f0\n     netlink_unicast+0x71b/0x940\n     netlink_sendmsg+0x595/0x840\n     __sock_sendmsg+0x119/0x150\n     ____sys_sendmsg+0x3e9/0x5c0\n     ___sys_sendmsg+0x157/0x1a0\n     __x64_sys_sendmsg+0x119/0x170\n     do_syscall_64+0x109/0x330\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFixes: 93531c674315 (\"net/ipv6: separate handling of FIB entries from dst based routes\")\nReported-by: Jason Zhang \u003cjdz@google.com\u003e\nSigned-off-by: Kuniyuki Iwashima \u003ckuniyu@google.com\u003e\nLink: https://patch.msgid.link/20261101064418.2055158-3-kuniyu@google.com\nReviewed-by: Ido Schimmel \u003cidosch@nvidia.com\u003e\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "9401b428b5d4dfe1fd5752973fd02b4e9cd05536",
      "tree": "3313c7b2fc132418b3f0ac0258f6e7ae35289b31",
      "parents": [
        "d5e912448cd98b261eba8e35ab838f2dc69a79f5"
      ],
      "author": {
        "name": "Kuniyuki Iwashima",
        "email": "kuniyu@google.com",
        "time": "Sun Nov 01 06:35:22 2026 +0000"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:34:50 2026 +0100"
      },
      "message": "ipv6: Flush exception route while replacing nexthop.\n\nThe following creates a cyclic reference between IPv6 route\nand nexthop:\n\n  1. create a nexthop A\n  2. create a nexthop group w/ A\n  3. create an IPv6 route with the nexthop group\n  4. create an exception route w/ A\n  5. replace A with a new nexthop B in the nexthop group\n  6. remove the IPv6 route\n  7. replace B with A in the nexthop group\n  8. remove the nexthop group\n\nThen, removing a device tied to the route gets stuck and\ntriggers the splat below. [0]\n\nAt 5., fib6_nh_release_dsts() is called, but it does not\nflush exception routes, so the nexthop A continues to grab\nthe IPv6 route reference.\n\n  nh_A-\u003ert6i_exception_bucket[] -\u003e rt6_ex-\u003ert6i-\u003efrom\n\nAt 6., fib6_purge_rt() calls rt6_flush_exceptions(), but it\nonly purges exceptions tied to nexthop B.  Also, the route is\nunlinked from the nexthop group by list_del_init(\u0026rt-\u003enh_list).\n\n  -\u003e f6i-\u003enh -\u003e nhg-\u003enh_entries[]\n\nAt 8., __remove_nexthop_fib() cannot find the IPv6 route, and\nremove_nexthop_group() calls list_del_init(\u0026nhge-\u003enh_list) to\nunlink the group from the nexthop A\u0027s nhe-\u003egrp_list.\n\n  nhg-\u003enh_entries[] -\u003e nh_A -\u003e ... -\u003e f6i\n\nHere, the nexthop A is reachable from net-\u003enexthop.devhash[],\nbut remove_nexthop_from_groups() cannot find the nexthop group,\nleaking the whole chain.\n\nLet\u0027s call fib6_nh_flush_exceptions() in fib6_nh_release_dsts().\n\n[0]:\nunregister_netdevice: waiting for gre6 to become free. Usage count \u003d 4\nref_tracker: netdev@000000009652f190 has 1/3 users at\n     dst_alloc+0x14b/0x490\n     ip6_rt_cache_alloc+0x27b/0x670\n     __ip6_rt_update_pmtu+0x572/0x850\n     ip6_tnl_xmit+0x8c5/0x1b70\n     __gre6_xmit+0x7af/0xaa0\n     ip6gre_tunnel_xmit+0x685/0xdc0\n     dev_hard_start_xmit+0x204/0x5a0\n     __dev_queue_xmit+0xe8a/0x2550\n     ip6_finish_output+0x232/0x570\n     ip6_output+0x226/0x3b0\n     ip6_send_skb+0x133/0x250\n     rawv6_push_pending_frames+0x503/0x6f0\n     rawv6_sendmsg+0xdf0/0x1310\n     sock_sendmsg_nosec+0xde/0x130\n     __sys_sendto+0x27f/0x320\n     __x64_sys_sendto+0xd9/0xf0\n\nFixes: 7bf4796dd099 (\"nexthops: add support for replace\")\nReported-by: Jason Zhang \u003cjdz@google.com\u003e\nSigned-off-by: Kuniyuki Iwashima \u003ckuniyu@google.com\u003e\nLink: https://patch.msgid.link/20261101064418.2055158-2-kuniyu@google.com\nReviewed-by: Ido Schimmel \u003cidosch@nvidia.com\u003e\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "d5e912448cd98b261eba8e35ab838f2dc69a79f5",
      "tree": "391b9cbfbd20f86fa8a25b723ed11321a0fdd965",
      "parents": [
        "24614e72df484ad50ecba98aaa88c7df2448c122"
      ],
      "author": {
        "name": "Daehyeon Ko",
        "email": "4ncienth@gmail.com",
        "time": "Mon Oct 05 08:51:01 2026 +0900"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:23:27 2026 +0100"
      },
      "message": "vhost/vsock: size receive SKBs from declared payload\n\nvhost_vsock_alloc_skb() sizes the skb from iov_length(), the total guest\ndescriptor length.  virtio_transport_inc_rx_pkt() instead adds hdr-\u003elen to\nrx_bytes and buf_used, and budgets each queued skb as SKB_TRUESIZE(0).  The\nguest controls the descriptor length and hdr-\u003elen independently.\n\nA guest can therefore provide a 64 KiB descriptor while declaring a zero\npayload.  The descriptor-sized skb remains queued, rx_bytes and buf_used\nremain unchanged, and only the fixed queue-entry budget limits retention.\nThis is not a lifetime leak: the skb is freed when dequeued or at socket\nteardown.  Repeating this across connections can nevertheless exhaust host\nmemory.  On Linux v7.2, 455 such descriptors retained 30,255,680 bytes for\na 262,144-byte receive buffer; a full-payload control retained 265,984\nbytes.\n\nVhost previously read hdr-\u003elen and allocated pkt-\u003ebuf from that value.  The\nconversion from virtio_vsock_pkt to sk_buff instead allocated receive skbs\nfrom the descriptor length, introducing the allocation-accounting mismatch.\n\nCopy the header into a stack object and validate hdr-\u003elen before allocating\nthe skb.  Size the allocation as sizeof(hdr) + payload_len so descriptor\ncapacity no longer determines queued memory.  Check payload_len against\nlen - sizeof(hdr) to avoid addition overflow on 32-bit hosts.\n\nFixes: 71dc9ec9ac7d (\"virtio/vsock: replace virtio_vsock_pkt with sk_buff\")\nCc: stable@vger.kernel.org\nSigned-off-by: Daehyeon Ko \u003c4ncienth@gmail.com\u003e\nReviewed-by: Stefano Garzarella \u003csgarzare@redhat.com\u003e\nAcked-by: Michael S. Tsirkin \u003cmst@redhat.com\u003e\nLink: https://patch.msgid.link/20261004235101.1464007-1-4ncienth@gmail.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "24614e72df484ad50ecba98aaa88c7df2448c122",
      "tree": "f9e31a312e979483740ed35d2e31da1e6716bf12",
      "parents": [
        "c4328134f3f7c2ce141121a8f82a5ec0cc8a709c"
      ],
      "author": {
        "name": "Avi Weiss",
        "email": "thnkslprpt@gmail.com",
        "time": "Sat Oct 31 13:41:35 2026 +0200"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:21:07 2026 +0100"
      },
      "message": "net: skbuff: reject zero MPLS TTL before decrementing\n\nskb_mpls_dec_ttl() decrements the u8 TTL before checking whether it\nexpired. An incoming TTL of zero wraps to 255, causing the TC MPLS\ndec_ttl action to pass an expired packet instead of dropping it.\n\nReject a zero TTL before the decrement while preserving the existing\nbehavior for TTL one and valid TTL values.\n\nFixes: 2a2ea50870ba (\"net: sched: add mpls manipulation actions to TC\")\nSigned-off-by: Avi Weiss \u003cthnkslprpt@gmail.com\u003e\nReviewed-by: Xia Yan \u003cyanxia@cmss.chinamobile.com\u003e\nReviewed-by: Simon Horman \u003chorms@kernel.org\u003e\nLink: https://patch.msgid.link/20261031114135.3784868-2-thnkslprpt@gmail.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "c4328134f3f7c2ce141121a8f82a5ec0cc8a709c",
      "tree": "5466f349364e948811db63cc227002b85fb845d5",
      "parents": [
        "11140c51df12e594d6bf2c8d2af5dec63b0219ac",
        "25e73f1d6868c759c8eb56cad4e411692c5341b4"
      ],
      "author": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:00:49 2026 +0100"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 15:00:50 2026 +0100"
      },
      "message": "Merge tag \u0027wireless-2026-11-02\u0027 of https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless\n\nJohannes Berg says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nA few fixes to start with:\n - wext: fix notifier netns interaction\n - rsi: avoid TID OOB access\n - mac80211: reload pointer, fix A-MPDU flags\n - brcmfmac: fix DMA regression\n - cfg80211: fix regdb validation\n\n* tag \u0027wireless-2026-11-02\u0027 of https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless:\n  wifi: mac80211: reinstate IEEE80211_TX_CTL_AMPDU flag in ieee80211_tx_prep_agg()\n  wifi: cfg80211: fix out-of-bounds read in valid_rule()\n  wifi: rsi: Skip TX aggregation setup for non-QoS frames\n  wifi: wext: Limit notifier event flushes to the device\u0027s netns\n  wifi: brcmfmac: map msgbuf RX packet IDs bidirectional\n  wifi: mac80211: reload TDLS header pointer after skb_linearize()\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nLink: https://patch.msgid.link/20261102104649.727621-3-johannes@sipsolutions.net\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "11140c51df12e594d6bf2c8d2af5dec63b0219ac",
      "tree": "06459ab6d7a345438be4b09e7845d10b0bc7ccd3",
      "parents": [
        "35d2d6e5ac0d22428b2a0216061f3330c095393c"
      ],
      "author": {
        "name": "Guillaume Nault",
        "email": "gnault@redhat.com",
        "time": "Wed Oct 28 21:32:35 2026 +0100"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 14:46:35 2026 +0100"
      },
      "message": "tcp: Fix dup-ack detection on non-SACK bidirectional data transfer.\n\nWhen receiving a pure ack from a peer that also sends data, we can\nhave SEG.SEQ \u003e SND.WL1, even though the segment contains no data. This\nmakes tcp_may_update_window() return true (because of the\n\"after(ack_seq, tp-\u003esnd_wl1)\" condition), and tcp_ack_update_window()\nthen adds FLAG_WIN_UPDATE to the segment set of flags, even when\nthere\u0027s no window update.\n\nSince FLAG_WIN_UPDATE prevents the segment from being considered as\ndup-ack (as it\u0027s part of FLAG_NOT_DUP), this can inhibit fast\nretransmit on non-SACK connections, making recovery very slow as it\nnow entirely relies on RTO.\n\nThe \"DUPLICATE ACKNOWLEDGMENT\" definition of RFC 5681, section 2,\nsays that lack of window update is a necessary condition for a dup ack:\n\"(e) the advertised window in the incoming acknowledgment equals the\nadvertised window in the last incoming acknowledgment.\". Spurious\nwindow updates can thus prevent dup ack detection and, in the end, fast\nretransmit.\n\nAvoid this scenario by setting FLAG_WIN_UPDATE only when a window\nupdate actually occurs. Pure acks with SEG.SEQ \u003e SND.WL1 can now\nbe detected as dup-ack and trigger fast retransmission.\n\nAlso, stop setting FLAG_WIN_UPDATE in tcp_ack()\u0027s header prediction\npath. One of the conditions for header prediction to happen is that\nreceived segments don\u0027t trigger a window update. This flag update was\nthus wrong to begin with. Now that tcp_ack_update_window() sets\nFLAG_WIN_UPDATE only if a window update actually occurred, we need the\nheader prediction path to stop reporting spurious window updates too.\nOtherwise BPF programs would get inconsistent window update information\n(CA_ACK_WIN_UPDATE) between fast an slow paths.\n\nFinally, add FLAG_SND_UNA_ADVANCED to the definition of FLAG_NOT_DUP.\nThis is necessary for the case where an incoming segment acknowledges\nless than a full segment of the retransmit queue. Such segments were\nnot considered dubious by tcp_ack_is_dubious() because of the spurious\nFLAG_WIN_UPDATE flag, which prevented the segment from being seen as a\nduplicate ack. Now that FLAG_WIN_UPDATE doesn\u0027t cover this scenario\nanymore, we need another way to mark these acks as non-duplicate.\nAdding FLAG_SND_UNA_ADVANCED to FLAG_NOT_DUP is the natural way of\ndoing this, since, by definition, a segment advancing SND.UNA, even by\na small amount, cannot be a duplicate ack.\n\nA side effect of this patch is that repeated zero window acks received\nfrom peer can now be considered duplicate acks (because of the the\n\"|| !win\" condition in tcp_may_update_window()). Therefore, they can\nnow trigger fast retransmission and fast recovery, including congestion\nwindow reduction, when the peer is stalled. This is RFC compliant and\nshouldn\u0027t have any negative effect.\n\nAdd packetdrill selftest. Before this patch, the 1001:2001 segment was\nretransmitted upon RTO, now it\u0027s sent right after reception of the\nthird duplicate ack.\n\nThanks to Tom Williams for the investigation help and initial\nreproducer.\n\nReported-by: Tom Williams \u003cTom.D.Williams@MorganStanley.com\u003e\nFixes: 1da177e4c3f4 (\"Linux-2.6.12-rc2\")\nSigned-off-by: Guillaume Nault \u003cgnault@redhat.com\u003e\nReviewed-by: Kuniyuki Iwashima \u003ckuniyu@google.com\u003e\nReviewed-by: Neal Cardwell \u003cncardwell@google.com\u003e\nReviewed-by: Eric Dumazet \u003cedumazet@kernel.org\u003e\nLink: https://patch.msgid.link/6426d558e45fc6ab724c40af62e4a8793215dd8a.1793219189.git.gnault@redhat.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "35d2d6e5ac0d22428b2a0216061f3330c095393c",
      "tree": "79ddc7f70087396a6f589c5ab2311d8aa2e315a4",
      "parents": [
        "241dec6f9ab74d8c3ef246764f3611666b96b9e1"
      ],
      "author": {
        "name": "Alexei Starovoitov",
        "email": "ast@kernel.org",
        "time": "Sun Nov 01 19:44:33 2026 +0000"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Wed Nov 04 13:25:05 2026 +0100"
      },
      "message": "net: reject a negative TCP header offset in qdisc_pkt_len_segs_init()\n\nqdisc_pkt_len_segs_init() stores skb_transport_offset(), or the inner\noffset, in the unsigned hdr_len. A header in front of skb-\u003edata gives a\nnegative offset. For an offset a little below zero, pskb_may_pull() gets a\nsmall length and succeeds. Then a 64-bit kernel reads the TCP header far\nafter the skb and can crash. Further below zero pskb_may_pull() fails.\n\nCommit 28a57fb2c5df (\"net: iptunnel: fix stale transport header during\ntunnel decapsulation\") fixed one source of such offsets. Other code that\nremoves bytes from the front of a packet can leave the same stale header.\n\nReturn SKB_DROP_REASON_SKB_BAD_GSO for a negative offset in the TCP branch.\nSKB_GSO_UDP_L4 and the other GSO types read no header and still get a wrong\nqdisc_pkt_len(). On a 64-bit kernel only packets that cause the read after\nthe skb today get a new result. Then __dev_queue_xmit() drops them and\nreturns -EINVAL, but sch_handle_ingress() ignores the result. Their content\ncan be valid. Thus the code that leaves the header stale needs its own fix.\n\nFixes: 7fb4c1967011 (\"net: pull headers in qdisc_pkt_len_segs_init()\")\nSigned-off-by: Alexei Starovoitov \u003cast@kernel.org\u003e\nReviewed-by: Eric Dumazet \u003cedumazet@kernel.org\u003e\nAcked-by: Michael S. Tsirkin \u003cmst@redhat.com\u003e\nCC: stable@vger.kernel.org\nLink: https://patch.msgid.link/20261101194433.2637113-1-alexei.starovoitov@gmail.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "241dec6f9ab74d8c3ef246764f3611666b96b9e1",
      "tree": "96b19cc438c9d6d74cc476c1972158fe0bc1dbbc",
      "parents": [
        "3f1054a0cb09552dd54db024694f74747f9f1d49"
      ],
      "author": {
        "name": "Joseph Kain",
        "email": "jkain@nuro.ai",
        "time": "Thu Oct 29 14:11:01 2026 -0700"
      },
      "committer": {
        "name": "Dave Miller",
        "email": "davem@davem-thinkpadp1gen8.ibmlond.csb",
        "time": "Wed Nov 04 08:43:21 2026 +0000"
      },
      "message": "net: stop defer_count outliving the deferred-free list\n\nAfter the llist conversion, rejected frees retain their counter\nincrements. A producer racing the counter reset and list detach can\nalso leave a count for an skb already drained. Deferred freeing can\nthen remain disabled while the list is empty.\n\nUndo rejected reservations and subtract only the number of skbs\ndrained. Allow admission up to the configured limit. Retain the\nhalfway notification and also notify when the reserved count reaches\nthe limit, covering reservations published after an earlier purge.\n\nFixes: 844c9db7f7f5 (\"net: use llist for sd-\u003edefer_list\")\nSigned-off-by: Joseph Kain \u003cjkain@nuro.ai\u003e\nAssisted-by: LLM\nSigned-off-by: Dave Miller \u003cdavem@davem-thinkpadp1gen8.ibmlond.csb\u003e\n"
    },
    {
      "commit": "3f1054a0cb09552dd54db024694f74747f9f1d49",
      "tree": "b508807b670ba6ac5cf8fae5a8c9d09c98e1a7f3",
      "parents": [
        "787268686c64be60023743b527645a907e38ccca"
      ],
      "author": {
        "name": "James Clark",
        "email": "jjc@jclark.com",
        "time": "Thu Oct 29 20:55:56 2026 +0700"
      },
      "committer": {
        "name": "Dave Miller",
        "email": "davem@davem-thinkpadp1gen8.ibmlond.csb",
        "time": "Wed Nov 04 07:57:26 2026 +0000"
      },
      "message": "net: ethernet: ti: am65-cpts: adjust perout genf following ptp changes\n\nA periodic output requested by PTP_PEROUT_REQUEST2 drifts away from\nthe PHC as soon as the PHC frequency is adjusted, for example by ptp4l\nor ts2phc: at +10 ppm each edge is 10 us later than the one before.\n\nThe GenF that generates the output counts its period in ref_clk\ncycles, which the PPM correction of the CPTS clock does not reach;\neach GenF has its own PPM registers. am65_cpts_ptp_adjfine() programs\nthem only for the GenF used for PPS, and am65_cpts_perout_enable_hw()\nstarts every GenF with them cleared, so a GenF used for a periodic\noutput is never corrected.\n\nCommit eb9233ce6751 (\"net: ethernet: ti: am65-cpts: adjust pps following\nptp changes\") added the correction for the PPS GenF, and\ncommit 7849c42da2ca (\"net: ethernet: ti: am65-cpts: adjust estf following\nptp changes\") passed the same values to the ESTFs.\n\nIn am65_cpts_ptp_adjfine(), update every enabled GenF the way the PPS\nGenF was updated: read its control register, set or clear the PPM\ndirection bit and write it back with the PPM value. The PPS GenF and the\nESTFs get exactly the values they got before. In\nam65_cpts_perout_enable_hw(), start a GenF with the current correction\ninstead of none; this applies to the PPS GenF too.\n\nTested on a BeagleY-AI (J722S) with the GENF0 output looped back to\nthe HW1_TS_PUSH input (EXTTS 0). With the PHC frequency adjusted by\n+10 ppm before the periodic output is started, the edges drift 10 us\nper second against the PHC without this patch (290 us after 29 s);\nwith it, they stay 20 to 23 ns after the PHC second. This also works\nif the frequency is adjusted after the periodic output has started.\n\nFixes: f6bd59526ca5 (\"net: ethernet: ti: introduce am654 common platform time sync driver\")\nSigned-off-by: James Clark \u003cjjc@jclark.com\u003e\nReviewed-by: Jacob Keller \u003cJacob.e.keller@intel.com\u003e\nSigned-off-by: Dave Miller \u003cdavem@davem-thinkpadp1gen8.ibmlond.csb\u003e\n"
    },
    {
      "commit": "787268686c64be60023743b527645a907e38ccca",
      "tree": "ce307ad5d1d35014218ce1a50db26cb9e0884418",
      "parents": [
        "f19f2b308beb158d0e6f6eb806ced636e4ebf6ce"
      ],
      "author": {
        "name": "Eric Dumazet",
        "email": "edumazet@kernel.org",
        "time": "Fri Oct 30 10:23:03 2026 +0100"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Tue Nov 03 22:30:55 2026 +0100"
      },
      "message": "ipmr, ip6mr: queue netlink route queries out of band\n\nipmr_get_route() and ip6mr_get_route() queue synthetic skbs on the\nunresolved MFC entry to answer RTM_GETROUTE requests once the route\nis resolved. These skbs carry a fake IP header with version 0, and\nipmr_cache_resolve(), ipmr_destroy_unres(), ip6mr_cache_resolve()\nand ip6mr_destroy_unres() rely on this in-band tag to tell them\napart from regular packets queued by the input and output paths.\n\nThe IP version is only validated once, in ip_rcv_core() and\nip6_rcv_core(). A netfilter hook running later, for instance an\nnftables payload statement in a PREROUTING chain owned by an\nunprivileged user namespace, can rewrite the first header byte to\nzero. The SRv6 End.DX6 action also passes the decapsulated packet\nto ip6_mr_input() without checking that the inner header version\nis 6. If no MFC entry exists, the packet is queued and later handled\nas a netlink request: its payload is treated as an nlmsghdr and\nwritten to, mr_fill_mroute() may call skb_put() on a nonlinear skb\n(hitting SKB_LINEAR_ASSERT()), and the skb is unicast to a netlink\nportid taken from stale IPCB/IP6CB bytes in skb-\u003ecb[].\n\nipmr_cache_report() also relies on the same tag since\ncommit 94a6736bb5ab (\"ipmr: only copy pktinfo to cache reports\").\n\nStop trusting packet contents: queue route queries on a dedicated\nnl_queries list in the unresolved MFC entry, and pass an explicit\nnl_query flag from the callers.\n\nThe per-entry limit of four queued skbs now applies to both lists\ncombined, as before. The synthetic header keeps version 0, since it\nis copied into the NOCACHE report delivered to the mroute socket.\n\nFixes: 1da177e4c3f4 (\"Linux-2.6.12-rc2\")\nFixes: 7bc570c8b4f7 (\"[IPV6] MROUTE: Support multicast forwarding.\")\nReported-by: Katherine Leaver \u003ckleaver@janestreet.com\u003e\nSigned-off-by: Eric Dumazet \u003cedumazet@kernel.org\u003e\nReviewed-by: Ido Schimmel \u003cidosch@nvidia.com\u003e\nLink: https://patch.msgid.link/20261030092303.2749386-1-edumazet@kernel.org\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "f19f2b308beb158d0e6f6eb806ced636e4ebf6ce",
      "tree": "5988ef5799ba38b0f589a82042ca5a063bbe5162",
      "parents": [
        "bc53aab4881adc134f495092034e9e7c0791d84c"
      ],
      "author": {
        "name": "Jamal Hadi Salim",
        "email": "jhs@mojatatu.com",
        "time": "Thu Oct 29 16:36:31 2026 -0400"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Tue Nov 03 22:29:23 2026 +0100"
      },
      "message": "net/sched: clamp skb-\u003equeue_mapping before indexing the tx queue\n\nThis issue was caught by Sashiko (nipa). A producer-side path cap is\nalready merged (ea4d4b5dddb5); this patch adds the matching consumer-side\ncaps.\n\nThe issue:\nThe tx queue is picked and capped in netdev_core_pick_tx() before the\n__dev_xmit_skb() qdisc enqueue path. A tc BPF program running inside an\negress qdisc (not clsact) can then change __sk_buff-\u003equeue_mapping; that\nstore is never re-checked. bpf_convert_ctx_access() bounds it only by\nNO_QUEUE_MAPPING, not by the device\u0027s queue count.\n\nTwo consumers read the stale value:\n\n  - On dequeue, qdisc_restart() calls netdev_get_tx_queue(), which\n    indexes dev-\u003e_tx[]. netdev_get_tx_queue() guards it with just a\n    DEBUG_NET_WARN_ON_ONCE, so sch_direct_xmit() takes the out-of-bounds\n    txq-\u003e_xmit_lock and writes txq-\u003exmit_lock_owner past the end of the\n    allocation on non-lltx devices such as ifb. Drivers that index their\n    rings from skb_get_queue_mapping() (ex: ifb) go out of range the same\n    way.\n\n  - On enqueue, taprio_enqueue() indexes q-\u003eqdiscs[] with the same value;\n    the array is sized dev-\u003enum_tx_queues. A duplicating netem on a child\n    qdisc clones the skb and re-enqueues the clone at the taprio root\n    (qdisc_root_bh()) through a direct rootq-\u003eenqueue() call, so the value\n    reaches taprio_enqueue() before any dequeue cap runs.\n\nThe Fix:\nCap the mapping at the consumers and write the capped value back, so the\nqdisc\u0027s _tx[] lookup, the taprio q-\u003eqdiscs[] lookup and any later driver\nread stay in range.\n\nOn the dequeue side the cap folds into the dequeue path instead of a\nseparate walk over the returned list: dequeue_skb() caps the head, and\neach bulk helper caps the element it appends. For a qdisc that is not\nTCQ_F_ONETXQUEUE, netdev_cap_txqueue() logs a ratelimited notice and\nselects queue 0.\n\nA TCQ_F_ONETXQUEUE qdisc is bound to a single tx queue: dequeue_skb() uses\nq-\u003edev_queue for the frozen check, the BQL limit and the trace point, while\nqdisc_restart() transmits on the skb\u0027s queue. Capping an out-of-range\nmapping to queue 0 would therefore send a per-queue child\u0027s skb through a\ndifferent queue than the one it was dequeued for. On mq, mqprio, taprio and\nhtb offload children, a stopped queue 0 could then park the list in\nq-\u003egso_skb, and the later wake would schedule queue 0\u0027s own child instead\nof this qdisc. Pin a TCQ_F_ONETXQUEUE mapping to the qdisc\u0027s own queue to\nkeep the documented invariant.\n\nThe pin covers every mapping, not only an out-of-range one: an in-range\nmapping that a filter sets on one of those per-queue children is rewritten\nto the child\u0027s own queue, and this path does not call netdev_cap_txqueue(),\nso it logs no notice. On a single-queue device qdisc_create() sets\nTCQ_F_ONETXQUEUE, so the one-queue trigger described below also takes this\nbranch and is corrected without a notice.\n\nThat also keeps a bulk list on one queue by construction: every element of\na TCQ_F_ONETXQUEUE qdisc, including a follower changed by a filter, is\npinned to q-\u003edev_queue before it is appended. The fast bulk helper\ntherefore needs no head comparison and no skb_bad_txq requeue; the slow\nhelper, used only by non-ONETXQUEUE qdiscs, still compares and requeues a\nmismatched follower, where a wake on any queue reschedules q.\n\nOn the enqueue side taprio_enqueue() caps the mapping against\nreal_num_tx_queues and writes it back before selecting q-\u003eqdiscs[queue], so\na duplicating child cannot steer the clone out of the array.\n\nConditions to recreate the bug:\nThe dequeue path: load a SCHED_CLS or SCHED_ACT program that stores\n__sk_buff-\u003equeue_mapping (a tc BPF action is enough), attach it to a\ntransmit qdisc (for example a matchall filter on a prio root), and send a\npacket. With a 1-queue device a store of 1 indexes one past dev-\u003e_tx[].\nUnder KASAN with panic_on_warn\u003d1 the unfixed kernel faults with \"BUG:\nKASAN: slab-out-of-bounds in sch_direct_xmit\". Loading the program needs\nCAP_BPF/CAP_SYS_ADMIN, so the trigger is root.\n\nThe enqueue path: on a multi-queue device, install a software taprio root,\ngraft a prio child with a duplicating netem on every class, and store an\nout-of-range queue_mapping from a matchall+bpf filter on the prio. The\nduplicate is re-enqueued at the taprio root and indexes q-\u003eqdiscs[] past\ndev-\u003enum_tx_queues; the unfixed kernel faults in taprio_enqueue_one().\nSame CAP_BPF/CAP_SYS_ADMIN requirement.\n\nFixes: 74e31ca850c1 (\"bpf: add skb-\u003equeue_mapping write access from tc clsact\")\nReported-by: Sashiko (nipa) \u003csashiko-bot@kernel.org\u003e\nCloses: https://lore.kernel.org/netdev/179033713973.2160803.4914570693994398206@kernel.org/\nLink: https://lore.kernel.org/netdev/179329777513.3134.12135506558709584471@kernel.org/\nLink: https://lore.kernel.org/netdev/179293123940.3134.1149128679923234677@kernel.org/\nLink: https://netdev-ai.bots.linux.dev/sashiko/#/patchset/QDISC-MD1X.v4.r0.20261021042722-1%40mojatatu.com\nLink: https://netdev-ai.bots.linux.dev/sashiko/#/patchset/QDISC-MD1X.v3.r0.20261015165943-1%40mojatatu.com\nLink: https://netdev-ai.bots.linux.dev/sashiko/#/patchset/QDISC-MD1X.v1.20261005193231%40mojatatu.com\nLink: https://lore.kernel.org/netdev/20261015125822.GH83879@horms.kernel.org/\nCc: stable@vger.kernel.org\nSigned-off-by: Jamal Hadi Salim \u003cjhs@mojatatu.com\u003e\nReviewed-by: Simon Horman \u003chorms@kernel.org\u003e\nLink: https://patch.msgid.link/QDISC-MD1X.v6.r0.20261029162633-1@mojatatu.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "bc53aab4881adc134f495092034e9e7c0791d84c",
      "tree": "593e41e6365cc13af6b9a8fa6ad9bced35419606",
      "parents": [
        "34cc22a9ce6ae0228dcd09a57df23aea62e22b04"
      ],
      "author": {
        "name": "Xia Yan",
        "email": "yanxia@cmss.chinamobile.com",
        "time": "Thu Oct 29 21:58:22 2026 +0800"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Tue Nov 03 22:14:43 2026 +0100"
      },
      "message": "ipv6: fix device binding after failed datagram connect\n\n__ip6_datagram_connect() can change sk_bound_dev_if when connecting to\nan address that needs a scope ID. If ip6_datagram_dst_update() fails,\nthe old peer address and port are restored, but the new device binding\nis left behind.\n\nA UDP socket can then keep reporting its original peer while sends and\nattempts to reconnect to that peer fail with ENETUNREACH. Replies to the\nsocket are also dropped by the device match. The same problem occurs\nwhen a scoped multicast destination picks up np-\u003emcast_oif.\n\nSave the original binding before processing the scope and restore it\nalong with the peer information on failure. This completes the rollback\nin commit 2f987a76a977 (\"net: ipv6: keep sk status consistent after\ndatagram connect failure\") and preserves the new binding on success.\n\nFound while reviewing scope-ID handling in __ip6_datagram_connect().\n\nConfirmed by exchanging UDP traffic over ::1, then attempting a link-local\nconnect with a nonexistent scope ifindex or a down interface. After that\nconnect fails, the original peer is still reported but communication and\nreconnecting to it fail.\n\nTested before and after the fix in UML for three rounds, covering explicit\nscopes, multicast interface fallback, initially unconnected sockets and\nexisting bindings. With the fix, the old binding and peer are retained,\nand traffic and reconnection to the original peer work. Also built on\nx86_64 with W\u003d1 using adjusted allmodconfig and allyesconfig\nconfigurations, with no new warnings.\n\nFixes: 2f987a76a977 (\"net: ipv6: keep sk status consistent after datagram connect failure\")\nCc: stable@vger.kernel.org\nSigned-off-by: Xia Yan \u003cyanxia@cmss.chinamobile.com\u003e\nLink: https://patch.msgid.link/20261029135822.448299-1-yanxia@cmss.chinamobile.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "34cc22a9ce6ae0228dcd09a57df23aea62e22b04",
      "tree": "2a878954de8744a6cee452af3040a24314116979",
      "parents": [
        "3362cb822ea750399a15b741713181fd8560bd17"
      ],
      "author": {
        "name": "Alexander Goodkind",
        "email": "alex@goodkind.io",
        "time": "Thu Oct 29 18:05:17 2026 -0700"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Tue Nov 03 22:06:53 2026 +0100"
      },
      "message": "net: ethernet: mediatek: preserve sibling PPE bindings\n\n__mtk_ppe_check_skb() clears entry-\u003ehash for flows bound to other\nhardware slots in the same software hash bucket. mtk_flow_offload_stats()\nthen skips their hardware counter updates. L2 cleanup also frees sibling\nsubflows without invalidating their hardware rules.\n\nRestrict both cleanup paths to entries assigned to the inspected slot.\n\nTwo UDP trials reproduced the counter failure on a GL-MT3000/MT7981\nrunning unmodified OpenWrt 25.12.5 with Linux 6.12.94:\n\n1. Start a UDP connection.\n2. Add a control connection in a different hash bucket.\n3. Add a connection in the first connection\u0027s hash bucket.\n\nAI code review of the original patch identified the cleanup problem\nin L2 subflows.\n\nFull ARM64 builds with allmodconfig and allyesconfig passed before\nand after the patch using GCC 14.2.0 and W\u003d1, without new warnings.\nThe builds used CONFIG_WERROR\u003dn because the unmodified ARM64 kernel\nalready emits warnings. Hardware testing has not run for this revision.\n\nFixes: c4f033d9e03e (\"net: ethernet: mtk_eth_soc: rework hardware flow table management\")\nFixes: 33fc42de3327 (\"net: ethernet: mtk_eth_soc: support creating mac address based offload entries\")\nLink: https://github.com/openwrt/openwrt/pull/26107\nSigned-off-by: Alexander Goodkind \u003calex@goodkind.io\u003e\nReviewed-by: Simon Horman \u003chorms@kernel.org\u003e\nLink: https://patch.msgid.link/20261030010517.45639-1-alex@goodkind.io\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "3362cb822ea750399a15b741713181fd8560bd17",
      "tree": "abebbc82c8b406782c90a3293a9411814a8ce7ac",
      "parents": [
        "647b81ddefc6364290e67bf33c89d54971f8995e"
      ],
      "author": {
        "name": "Florian Fainelli",
        "email": "florian.fainelli@broadcom.com",
        "time": "Wed Oct 28 16:50:59 2026 -0700"
      },
      "committer": {
        "name": "Paolo Abeni",
        "email": "pabeni@redhat.com",
        "time": "Tue Nov 03 21:49:02 2026 +0100"
      },
      "message": "net: dsa: b53: Enable IGMP and MLD control packet CPU copies\n\nIGMPv2 reports and MLDv1 reports are addressed to the multicast group\nitself. Once the first listener is installed in the ARL table, subsequent\nreports can follow that entry without reaching the CPU. The bridge then\nfails to learn additional listeners, although static MDB forwarding works.\n\nEnable the high-level protocol classifiers so that IGMP and MLD control\npackets are copied to the CPU independently of the multicast ARL lookup.\nRetain normal L2 forwarding by clearing the CPU-only forwarding modes,\nand preserve unrelated protocol-control fields.\n\nHandle the BCM5395\u0027s 16-bit register and different classifier fields\nseparately from the 32-bit layout on the BCM531xx, BCM5301x and newer\nintegrated RoboSwitch families, including BCM7445, BCM7278 and BCM4908.\nExport the helper and call it from bcm_sf2_sw_setup() as well, since SF2\nuses its own setup operation instead of b53_setup(). This also restores\nthe classifiers after the switch reset on resume. Leave older devices\nwith different IGMP controls untouched, and propagate register access\nfailures during setup.\n\nThe SF2 setup integration and BCM4908 chip gate were updated with\nassistance from OpenAI Codex in response to review feedback.\n\nFixes: 5d65b64a3d97 (\"net: dsa: b53: Add support for MDB\")\nSigned-off-by: Florian Fainelli \u003cflorian.fainelli@broadcom.com\u003e\nLink: https://patch.msgid.link/20261028235100.3892374-2-florian.fainelli@broadcom.com\nSigned-off-by: Paolo Abeni \u003cpabeni@redhat.com\u003e\n"
    },
    {
      "commit": "e6b96b76d7074ae64f0d37d880794c71d3ce277e",
      "tree": "2a5fe416f518d58ab26d135b0a3b7000842f408d",
      "parents": [
        "fe23bad2156f1d5f0df8ae4a79ee590b79efc13a"
      ],
      "author": {
        "name": "Guenter Roeck",
        "email": "linux@roeck-us.net",
        "time": "Tue Nov 03 10:26:15 2026 -0800"
      },
      "committer": {
        "name": "Guenter Roeck",
        "email": "linux@roeck-us.net",
        "time": "Tue Nov 03 11:32:45 2026 -0800"
      },
      "message": "hwmon: (hp-wmi-sensors) Serialize alarm flag read-and-clear with state-\u003elock\n\nIn hp_wmi_hwmon_read(), temperature and fan alarm flags (info-\u003ealarm)\nare evaluated and cleared without acquiring state-\u003elock, while only the\nhwmon subsystem lock is held by the hwmon core. Meanwhile, the\nasynchronous WMI event handler hp_wmi_notify() sets info-\u003ealarm under\nstate-\u003elock. If hp_wmi_notify() sets info-\u003ealarm between the read and\nthe subsequent clear in hp_wmi_hwmon_read(), the newly reported fan\nstall or critical temperature alarm is overwritten with false and\npermanently lost.\n\nThe driver-local state-\u003elock cannot be replaced with the hwmon\nsubsystem lock (hwmon_lock()):\n- When no connected hwmon-supported sensors are present (!count), the\n  driver operates in debugfs-only mode without registering a hwmon\n  device, while debugfs attributes (fungible_show()) still require\n  state-\u003elock to serialize WMI queries and sensor state updates.\n- Even when sensors are connected, add_event_handler() must subscribe\n  to WMI events before make_chip_info() and\n  devm_hwmon_device_register_with_info() because visibility of alarm\n  and intrusion attributes depends on whether event registration\n  succeeded. As a result, hp_wmi_notify() can run before the hwmon\n  device exists during probe and after devm unregisters and frees the\n  hwmon device during removal.\n\nAcquire state-\u003elock in hp_wmi_hwmon_read() around reading and clearing\ninfo-\u003ealarm to prevent losing WMI alarm events.\n\nFixes: 23902f98f8d4 (\"hwmon: add HP WMI Sensors driver\")\nCc: James Seo \u003cjames@equiv.tech\u003e\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\n"
    },
    {
      "commit": "71555ae8c7572fd99158013ca2e29187c5d2508d",
      "tree": "6fffba8ad18ac8dd88ae282de03c6bb06ea6980d",
      "parents": [
        "eadce52a9ef657d561b3e76c9b5f178bd99735f5"
      ],
      "author": {
        "name": "Samiullah Khawaja",
        "email": "skhawaja@google.com",
        "time": "Sat Oct 31 20:35:40 2026 +0000"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/gup: check folio-\u003emapping under folio lock in memfd_pin_folios()\n\nmemfd_pin_folios() pins folios from the page cache without taking the\nfolio lock. khugepaged or MADV_COLLAPSE can therefore replace a folio\nafter checking its refcount while memfd_pin_folios() still pins the old\nfolio. The caller then receives a folio which is no longer part of the\nmemfd.\n\nFor udmabuf and iommufd, this can cause data corruption: DMA accesses\nthe detached folio rather than the live memfd contents. DMA reads can\nreturn stale data, while DMA writes update the detached copy and are\nlost from the live memfd. The detached folio remains pinned, so these\naccesses do not constitute a use-after-free or target another\napplication\u0027s memory. For memfd live update, the stale contents can\nreappear in the memfd after handover.\n\nLock the folio and recheck folio-\u003emapping before pinning it, like other\npage cache users do. If the folio was removed, retry the folio lookup\nfrom the index that was removed.\n\nFixes: 89c1905d9c14 (\"mm/gup: introduce memfd_pin_folios() for pinning memfd folios\")\nReported-by: Andy Lutomirski \u003cluto@amacapital.net\u003e\nCloses: https://lore.kernel.org/all/CALCETrV5eqg6d9\u003d+BQhCpRwBNe3aCQiut8vxPBs8b7PToqjaHg@mail.gmail.com/\nCc: stable@vger.kernel.org\nSigned-off-by: Samiullah Khawaja \u003cskhawaja@google.com\u003e\nReviewed-by: Andy Lutomirski \u003cluto@amacapital.net\u003e\nLink: https://patch.msgid.link/20261031203540.2282507-1-skhawaja@google.com\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "eadce52a9ef657d561b3e76c9b5f178bd99735f5",
      "tree": "e37046ed56981ae481ffa7136a9d81101a87d003",
      "parents": [
        "466d6844c8f19fba16b668b49861bdb8d7ded282"
      ],
      "author": {
        "name": "Lance Yang",
        "email": "lance.yang@linux.dev",
        "time": "Mon Oct 26 23:20:13 2026 +0800"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "khugepaged: fix readahead lock inversion in collapse_file()\n\ncollapse_file() can call page_cache_sync_readahead() while still holding\nsource folios locked. If truncate holds mapping-\u003einvalidate_lock\nexclusively and waits for one of those folios, readahead waits for\ninvalidate_lock and neither side can make progress.\n\nWe need to release those folio locks before starting readahead. On a page\ncache miss, roll back first, populate the collapse range, and retry once.\nDoing readahead after rollback avoids an extra pass when all folios are\nalready present. If another miss occurs on retry, give up rather than keep\nretrying while truncate or reclaim removes folios.\n\nKeep page_cache_sync_readahead() and wait for read I/O with\nfilemap_lock_folio(), releasing each folio before moving to the next. The\nexisting uptodate check during collapse still handles read errors.\n\nShmem uses shmem_get_folio() for swapin and fallocated folios without\ntaking mapping-\u003einvalidate_lock, so it is unaffected.\n\nReported-by: syzbot+16bf7cd0ebeb1de93aa5@syzkaller.appspotmail.com\nCloses: https://syzkaller.appspot.com/bug?extid\u003d16bf7cd0ebeb1de93aa5\nFixes: 730633f0b7f9 (\"mm: Protect operations adding pages to page cache with invalidate_lock\")\nCc: stable@vger.kernel.org\nSigned-off-by: Lance Yang \u003clance.yang@linux.dev\u003e\nReviewed-by: Pedro Falcato \u003cpfalcato@suse.de\u003e\nAcked-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\nAcked-by: Zi Yan \u003cziy@nvidia.com\u003e\nReviewed-by: Baolin Wang \u003cbaolin.wang@linux.alibaba.com\u003e\nLink: https://patch.msgid.link/20261026152013.10511-1-lance.yang@linux.dev\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "466d6844c8f19fba16b668b49861bdb8d7ded282",
      "tree": "adcfa34285e65cc96a2aa75e474673d240f3a6f5",
      "parents": [
        "500624f28eca441e35f978979ccfb373202fefd3"
      ],
      "author": {
        "name": "Ritesh Harjani (IBM)",
        "email": "ritesh.list@gmail.com",
        "time": "Fri Oct 30 05:37:36 2026 +0530"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/huge_memory: set the mmu_gather page size in zap_huge_pud()\n\nUnmapping a device-dax mapping with 1G alignment on powerpc radix kernel\nbuilt with CONFIG_DEBUG_VM triggers this warning on every munmap:\n\n    WARNING: mm/mmu_gather.c:176 at __tlb_remove_folio_pages_size+0x38/0x230\n    NIP [c00000000063d508] __tlb_remove_folio_pages_size+0x38/0x230\n    LR [c0000000006fb688] zap_huge_pud+0x1b8/0x2d0\n    Call Trace:\n     zap_huge_pud+0x170/0x2d0 (unreliable)\n     __zap_vma_range+0x1604/0x1e20\n     unmap_vmas+0xa0/0x1f0\n     unmap_region+0xb0/0x130\n     vms_complete_munmap_vmas+0x120/0x310\n     do_vmi_align_munmap+0x1ec/0x240\n     __vm_munmap+0x148/0x220\n     sys_munmap+0x28/0x40\n\nTo trigger this - it is enough to mmap() /dev/dax0.0, touch the first\nbyte so that the whole 1G is mapped by a single PUD and then munmap()\nit.\n\nPowerPC needs MMU_GATHER_PAGE_SIZE in which mmu_gather needs to record\nthe page size for which tlb flush is needed. zap_huge_pmd(),\nzap_pte_range(), change_huge_pud() etc all do this already. However,\nsince commit:\n  dbe54153296d (\"mm/huge_memory: add vmf_insert_folio_pud()\")\n\na device-dax PUD maps a real folio and zap_huge_pud() now hands it to\ntlb_remove_page_size(tlb, page, HPAGE_PUD_SIZE). At that point\ntlb-\u003epage_size is still whatever the previous user left behind, which is\n0 for the fresh gather set up by munmap() and so the check fires.\n\nFix this in the same way like how other similar paths do.\n\nFixes: dbe54153296d0 (\"mm/huge_memory: add vmf_insert_folio_pud()\")\nCc: stable@vger.kernel.org\nReported-by: Pavithra \u003cpavrampu@linux.ibm.com\u003e\nSigned-off-by: Ritesh Harjani (IBM) \u003critesh.list@gmail.com\u003e\nAcked-by: Zi Yan \u003cziy@nvidia.com\u003e\nAcked-by: Muchun Song \u003cmuchun.song@linux.dev\u003e\nTested-by: Pavithra Prakash \u003cpavrampu@linux.ibm.com\u003e\nLink: https://patch.msgid.link/8b853e5f9f16145859407b28af654b0f79e12642.1793318297.git.ritesh.list@gmail.com\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "500624f28eca441e35f978979ccfb373202fefd3",
      "tree": "0aa1aae7f012a0992860445de56c6186ec9e665a",
      "parents": [
        "e8abc61d8a549a91c8fa639f68be2ef13d5fa63b"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:40:15 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/memory-tiers: unregister empty tiers outside memory_tier_lock\n\nWhen offlining a node\u0027s last memory empties its tier,\nclear_node_memory_tier() calls device_unregister() while holding\nmemory_tier_lock. A concurrent sysfs read can hold a kernfs active\nreference and block in nodelist_show() on that mutex. device_unregister()\nthen waits in kernfs_drain() for the read to finish and release its active\nreference, while the reader waits for the offlining task to release the\nmutex.\n\nReturn the node\u0027s former tier from clear_node_memory_tier(), making the\nhelper more similar to set_node_memory_tier(), which also returns a\nmemory_tier pointer. Let the caller unlink an empty tier under\nmemory_tier_lock before rebuilding demotion targets, then unregister its\ndevice after dropping the lock.\n\nFixes: 9832fb87834e (\"mm/demotion: expose memory tier details via sysfs\")\nCc: stable@vger.kernel.org\nReported-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nReviewed-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-46-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "e8abc61d8a549a91c8fa639f68be2ef13d5fa63b",
      "tree": "c38aa6a31290c2625c2d780ba982f265d2771d65",
      "parents": [
        "b1ee87802111156e27557e82acc31fa7dfc76e2a"
      ],
      "author": {
        "name": "Rik van Riel",
        "email": "riel@surriel.com",
        "time": "Sat Oct 31 10:40:14 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/cma: don\u0027t release CMA pages still in use\n\nWhen a driver calls dma_free_contiguous() before quiescing DMA, the\npage might still have a reference from the device.\nput_page_testzero() there returns false, WARN fires, but the code proceeds\nto free_contig_frozen_range() putting a live page onto buddy and clearing\nthe bitmap. A subsequent allocation can hand the same PFN to a new\nowner while the original holder still references it.\n\nA concurrent put_page() that drops the last reference between the\ntestzero loop and free_contig_frozen_range() can double-queue the page\nvia page-\u003elru, corrupting buddy lists.\n\nAvoid the corruption by not freeing a CMA region if any of the\npages inside are still in use.\n\nMake it explicit in the warning that the driver allowed a leak.\n\nWhile at it, use page_ref_freeze() to make the semantics clearer and\nswitch to pr_warn_ratelimited().\n\nFixes: 9bda131c6093 (\"mm: cma: add cma_alloc_frozen{_compound}()\")\nCc: stable@vger.kernel.org\nSigned-off-by: Rik van Riel \u003criel@surriel.com\u003e\nLink: https://patch.msgid.link/20260811132045.5f114772@fangorn\n[ david: use page_ref_freeze() + pr_warn_ratelimited() ]\nAcked-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nAcked-by: Muchun Song \u003cmuchun.song@linux.dev\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-45-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "b1ee87802111156e27557e82acc31fa7dfc76e2a",
      "tree": "706f78f58b9848b33a053a8a80044fb85791f4c4",
      "parents": [
        "23e570927421d569fdc510d5f3f29542a43eeda5"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:40:13 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/vma: don\u0027t leak the charge for stack growth\n\nacct_stack_growth() charges stack expansion even without VM_ACCOUNT.\nThis can happen for read-only or MAP_NORESERVE mappings created with\nMAP_GROWSDOWN. Unmapping these VMAs does not release the charge, leaking\nCommitted_AS.\n\nOnly check and charge growth for VM_ACCOUNT VMAs, matching mremap().\nUnaccounted growth skips the overcommit check while remaining subject\nto the other stack-growth limits.\n\nFixes: 1da177e4c3f4 (\"Linux-2.6.12-rc2\")\nCc: stable@vger.kernel.org\nReported-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nReviewed-by: Pedro Falcato \u003cpfalcato@suse.de\u003e\nReviewed-by: Harry Yoo (Meta) \u003charry@kernel.org\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-44-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "23e570927421d569fdc510d5f3f29542a43eeda5",
      "tree": "19ab5e611989a7caffadd899b9409c27b7f59294",
      "parents": [
        "0193e83368022a308d19ee0293f55a4f5d548e40"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:40:12 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/huge_memory: split huge PUDs when adjusting VMA boundaries\n\nPFN mappings such as VFIO PCI BAR mappings can use PUD leaves while\nallowing VMA splits at page granularity. However, vma_adjust_trans_huge()\nonly handles PMDs.\n\nAfter faulting a writable PUD-sized VFIO BAR mapping, changing its first\npage to read-only with mprotect() makes the PMD walk treat the PUD leaf\nas a PMD table. Applying MADV_DONTFORK to the first PMD-sized chunk leaves\nthe PUD spanning two VMAs: the PMD-aligned boundary skips splitting.\n\nWalk the page tables once at each adjusted boundary and split a huge\nPUD or PMD leaf as needed. Handle PUD leaves even when the boundary is\nPMD-aligned.\n\nFixes: f9e54c3a2f5b7 (\"vfio/pci: implement huge_fault support\")\nCc: stable@vger.kernel.org\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nReviewed-by: Kiryl Shutsemau (Meta) \u003ckas@kernel.org\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-43-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "0193e83368022a308d19ee0293f55a4f5d548e40",
      "tree": "413a9554c085b1457db3446c5f3ecb69a4b2f889",
      "parents": [
        "7f2c000ffb1047b476cbf267f741272c389d3e31"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:40:11 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/vma: call -\u003emay_split() before a partial merge\n\nA driver can use the -\u003emay_split() hook to forbid a VMA boundary at\ncertain addresses.\n\nA device-dax device is a character device that gives raw access to a\nrange of memory through mmap(). device-dax refuses any address that is not\na multiple of the device\u0027s alignment through vm_ops-\u003emay_split.\n\nvma_merge_existing_range() can move boundaries, but does not call\nvm_ops-\u003emay_split.\n\nIf a range at the edge of a VMA gets the attributes of the adjacent VMA,\nthe function moves only that range over to the neighbour: one VMA shrinks\nand the other grows. This is a partial merge, and vma_modify() tries it\nbefore any split.\n\nTake a device-dax VMA that lies next to another VMA of the same file.\nThe user calls mprotect() on the one page of the first VMA that touches\nthe second VMA, and asks for the protection that the second VMA already\nhas. The result is a partial merge. It puts the boundary inside a 1 GiB\nmapping, which is a single leaf entry at the PUD level.\n\nAs part of the merge, the kernel looks for a huge PMD to split at the\nnew boundary. That code does not expect a PUD leaf:\n\n    vma_merge_existing_range()\n      commit_merge()\n        vma_adjust_trans_huge()\n          split_huge_pmd_address()\n            mm_find_pmd()\n              treats the PUD leaf as a pointer to a PMD table,\n              so the \"table\" is the device memory that the leaf maps\n            __split_huge_pmd()\n              reads a PMD that the user wrote to the device memory\n              folio_put() on the folio that this PMD names\n\nBad. While the code must at some point be taught to split PUD entries as\nwell, the issue here is that we move VMA boundaries such that they are\nincompatible with the driver.\n\nFix this by calling -\u003emay_split() on the address that a partial merge\nwould move the boundary to, and by abandoning the merge if the driver\nrefuses. vma_modify() then tries the split, which fails with -EINVAL.\n\nFactor out existing split handling into check_split() and reuse it.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\nFixes: 38607c62b34b (\"fs/dax: properly refcount fs dax pages\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\n[ david: improve description; cleanup the code ]\nReviewed-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nSigned-off-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-42-d6437171ecc3@kernel.org\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "7f2c000ffb1047b476cbf267f741272c389d3e31",
      "tree": "ba628ef099209ea9cf45ed74f1908a295c49eb7c",
      "parents": [
        "4c2dec1dce368ad9e9b1814307cb5ef3832fa07e"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:40:10 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/ksm: check large swap-cache folios before mapping them\n\nKSM folios are always small, but their shared swap slots can be read\nback as part of a large folio in the swap cache. ksm_might_need_to_copy()\nskips large folios, so another process can map a page with an incompatible\nanon_vma or page index. Reverse mapping then cannot find the new\nmapping, preventing migration or reclaim.\n\nApply the same compatibility checks to large folios as to small ones.\nPass the page corresponding to the swap entry and copy only that page\nwhen necessary. In do_swap_page()\u0027s copy path, decrement only that slot\u0027s\nswap count, because the source swap-cache folio can now be large.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\nFixes: f1879e8a0c60 (\"mm, swap: never bypass the swap cache even for SWP_SYNCHRONOUS_IO\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-41-d6437171ecc3@kernel.org\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "4c2dec1dce368ad9e9b1814307cb5ef3832fa07e",
      "tree": "4b1162709d22d0a7627c5b939b5c50eb6809d6a8",
      "parents": [
        "890e118e95bfc2aae4432ec2a95192d6f9193211"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:40:09 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/ksm: fix use of a freed anon_vma at swap-in\n\nA folio read from a swap slot previously shared by KSM can remain in the\nswap cache after the process that first mapped it exits. Its anon_vma\ncan then be freed, so ksm_might_need_to_copy() must not dereference it\nto compare roots.\n\nDoing so can result in some false-positives, resulting in the reverse\nmapping missing the new folio mapping, preventing migration and reclaim.\n\nSLAB_TYPESAFE_BY_RCU allows individual anon_vma objects to be reused\nimmediately after freeing. A stale pointer can then refer to another\nanon_vma whose root matches, even though the target VMA is not linked\nto that anon_vma.\n\nMove the anonymous rmap compatibility checks into\nfolio_anon_rmap_compatible(). Keep the page-index check and compare the\nfolio\u0027s anon_vma pointer against the VMA\u0027s own anon_vma and root first.\n\nIf neither matches, bite the bullet and walk the VMA\u0027s anon_vma_chain.\nThe VMA keeps these anon_vmas alive, and finding a match guarantees that\nreverse mapping can find the new mapping.\n\nLorenzo Stoakes says in a private discussion:\n\n  \"This isn\u0027t quite equivalent to the existing check.\n\n  Every anon_vma in an anon_vma_chain shares the same root, but if you\n  split a VMA then fork both of them like this:\n\n                  VMA A\n               /        \\         \u003csplit\u003e\n            VMA B      VMA C\n               \\        /\n        root \u003c- anon_vma 1\n               ----^ ^----        \u003cfork\u003e\n              /   parent  \\\n        anon_vma 2   anon_vma 3\n             |            |\n           VMA D        VMA E\n\n  VMA\u0027s D and E both get their own new\n  anon_vma\u0027s such that:\n\n  VMA D: anon_vma 2 -\u003e anon_vma 1 -\u003e root\n  VMA E: anon_vma 3 -\u003e anon_vma 1 -\u003e root\n\n  And if you found a folio referencing anon_vma 2, the existing check:\n\n\tanon_vma-\u003eroot \u003d\u003d vma-\u003eanon-vma-\u003eroot\n\n  Would be true for VMA\u0027s B, C, D \u0026 E.\n\n  However after your change it\u0027d be true for VMA D only, as it\u0027s the only\n  one with anon_vma 2 in its anon_vma_chain.\n\n  Whether or not that could actually happen in practice... 🙂 I don\u0027t\n  know.\n\n  [...] after your change it\u0027d be true for VMA D only, as it\u0027s the only\n  one with anon_vma 2 in its anon_vma_chain. [...] I would [...] say that\n  you are making the test stricter but more correct.\n\"\n\nIf this affects performance when KSM was never even involved, we could\njust track whether KSM ever merged anything and just skip these checks.\n\nThere isn\u0027t really a lot we can do otherwise: for mapped folios we might\nbe able to use folio_get_anon_vma(), but for unmapped folios there really\nis no easy way to see if the anon_vma is still valid.\n\nDocument the (confusing) lifetime requirements of folio_anon_vma().\n\nFixes: ba6f0ff3981e (\"ksm: fix ksm swapin time optimization\")\nCc: stable@vger.kernel.org\nReported-by: Chris Mason \u003cmason@kernel.org\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nAcked-by: Xu Xin \u003cxu.xin@linux.dev\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-40-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "890e118e95bfc2aae4432ec2a95192d6f9193211",
      "tree": "0340d6d0169bf812b90cba9e6f7566a23b425a85",
      "parents": [
        "d03df42ddae196f20e9cfb775704e60269eb6b44"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:40:08 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/ksm: reset the unstable trees of all nodes\n\nEach full scan resets ksm_nr_node_ids unstable tree roots. Enabling\nmerge_across_nodes resets this count to 1, even if per-node roots were\npreviously allocated.\n\nSo when toggling \"merge_across_nodes\" 0 -\u003e 1 -\u003e 0, a scan that starts\nwhile the setting is 1 and continues after switching back to 0 can\nencounter stale unstable tree roots, resulting in UAF.\n\nOnly root is allowed to change \"merge_across_nodes\", and the documented\nsequence is: \"merge_across_nodes setting can be changed only when there\nare no ksm shared pages in the system: set run 2 to unmerge pages first,\nthen to 1 after changing merge_across_nodes, to remerge according to the\nnew setting.\"\n\nLet\u0027s fix it by tracking in ksm_nr_node_ids the actual number of\nallocated tree roots.\n\nremove_all_stable_nodes() and ksm_check_stable_tree() will now scan\nmore tree roots (skipping the empty ones), which is harmless.\n\nFixes: ef53d16cded7 (\"ksm: allocate roots when needed\")\nCc: stable@vger.kernel.org\nReported-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nAcked-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nReviewed-by: Pasha Tatashin \u003cpasha.tatashin@soleen.com\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-39-d6437171ecc3@kernel.org\nReviewed-by: Xu Xin \u003cxu.xin@linux.dev\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "d03df42ddae196f20e9cfb775704e60269eb6b44",
      "tree": "c894a09e828909aad4ff12c8261f1cb2cfe893eb",
      "parents": [
        "9f02ca8c15a74bc9e4e8e05ec089f63cb87cbf75"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:40:07 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm: fix deadlock of mremap() against UFFDIO_MOVE\n\nWith per-VMA locks, UFFDIO_MOVE can run concurrently with mremap()\non different VMAs in the same mm. Those VMAs can share page tables, so\nboth operations can acquire the same pair of page-table locks.\n\nUFFDIO_MOVE orders the locks by address, while mremap() takes the source\nlock first. These conflicting orders can deadlock; mremap() holding\nmmap_lock for writing no longer helps.\n\nMove double_pt_lock() and double_pt_unlock() to mm/internal.h and use\nthem for all page-table moves in mremap(). Preserve the source entry\nchecks after acquiring both locks. Remove the comments claiming that\nexclusive mmap_lock makes lock ordering irrelevant.\n\nIn move_ptes(), make sure to just recheck source and destination PMD\nafter taking the locks and drop the overly-long comment.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\n[ david: use new helpers consistently; simplify description and comments;\n         move_ptes() fixup ]\n\nFixes: 867a43a34ff8 (\"userfaultfd: use per-vma locks in userfaultfd operations\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nAcked-by: Muchun Song \u003cmuchun.song@linux.dev\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-38-d6437171ecc3@kernel.org\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "9f02ca8c15a74bc9e4e8e05ec089f63cb87cbf75",
      "tree": "a163746c12739327d0fb0d6e3007334d3707fa06",
      "parents": [
        "7a81bc23dade8082187be6d9cc36e4be4b7207e2"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:40:06 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm: fix unkillable fault loop on MAP_DROPPABLE memory\n\nhandle_mm_fault() suppresses VM_FAULT_OOM for VM_DROPPABLE mappings.\n\nFor user-mode faults, pending signals are processed before retrying the\naccess. Kernel-mode faults on user buffers instead return directly to\nthe faulting instruction.\n\nWith persistent allocation failures (esp. memcg limits), a syscall,\nsuch as write(), can therefore loop while not dropping locks.\n\nOnly suppress VM_FAULT_OOM when FAULT_FLAG_USER is set, allowing\nkernel-mode faults and GUP to fail and signal allocation errors.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\nFixes: 9651fcedf7b9 (\"mm: add MAP_DROPPABLE for designating always lazily freeable mappings\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\n[ david: simplify description ]\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-37-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "7a81bc23dade8082187be6d9cc36e4be4b7207e2",
      "tree": "ba6e226809ac86db705290ea9da055e9eba02741",
      "parents": [
        "8db6921cc07b74197a3866d62ed262b68aeadcf3"
      ],
      "author": {
        "name": "Josef Bacik",
        "email": "josef@toxicpanda.com",
        "time": "Sat Oct 31 10:40:05 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm: fix unmap_mapping_range() beyond 4 GiB on 32-bit\n\nCommit 9eab0421fa94 (\"mm: fix unmap_mapping_range high bits shift bug\")\nmade holebegin and holelen unsigned before they are shifted, by casting\nthem to pgoff_t. That is an unsigned long: on a 32-bit kernel the cast\ncuts off the upper half of the two loff_t values, so a hole which begins\nat 4 GiB or beyond is taken for one in the first 4 GiB of the file.\n\ntruncate_pagecache() passes the new size of the file and asks for private\nCOWed pages to be unmapped as well. If a file of 6 GiB is truncated to\n5 GiB, everything from 1 GiB on is unmapped, and what a process has\nwritten to a private mapping of the range between 1 GiB and 5 GiB is\nlost: it reads the contents of the file again.\n\nWhere the range has an end, the wrong range is unmapped instead of the\nright one. The page cache copes with that, as it unmaps every folio that\nit removes. The callers which only have unmap_mapping_range() to get\nrid of user mappings do not, for example drm_vma_node_unmap(), whose fake\noffsets reach beyond 4 GiB on 32-bit, and revoke_iomem() with physical\naddresses of more than 32 bits.\n\nCast to u64 instead. Nothing changes for 64-bit kernels.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\nFixes: 9eab0421fa94 (\"mm: fix unmap_mapping_range high bits shift bug\")\nCc: stable@vger.kernel.org\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nAcked-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nReviewed-by: Pedro Falcato \u003cpfalcato@suse.de\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-36-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "8db6921cc07b74197a3866d62ed262b68aeadcf3",
      "tree": "3fb15fb1256daf1f6973f7f68a483c12de1905e2",
      "parents": [
        "22d043c1da48d6c7274f9dd900714b6d58b7b9c6"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:40:04 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/memory: reject remote COW faults on PFN mappings\n\nWhen handling a COW fault without a normal source page (PFN mappings),\n__wp_page_copy_user() copies from the faulting user address. For remote\nfaults, this accesses the wrong address space, resulting in wrong data\ngetting copied.\n\nFor example, user_events updates an enable bit in the registering\nprocess\u0027s memory. If that memory needs to be faulted in,\nuser_event_enabler_fault_fixup() calls fixup_user_fault() from a work\nitem. Placing the enable bit in a private PFN mapping can trigger this\nremote COW path.\n\nReject these faults with VM_FAULT_SIGBUS when the target mm differs from\ncurrent-\u003emm: remote faults. Ordinary (non-PFN) mappings are not affected.\n\nThe user-address copy dates back to commit 6aab341e0a28 (\"mm: re-architect\nthe VM_UNPAGED logic\"); likely, actual ways to get remote faults in\nthere on COW PFN mappings appeared afterwards. But the fix is simple and\nstraight forward.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\nFixes: 6aab341e0a28 (\"mm: re-architect the VM_UNPAGED logic\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\n[ david: simplify comment and description ]\nReviewed-by: Pedro Falcato \u003cpfalcato@suse.de\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-35-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "22d043c1da48d6c7274f9dd900714b6d58b7b9c6",
      "tree": "eac15fbe1d5248e0c15c2968a25f6595753155ef",
      "parents": [
        "440c8779757f09f290770b1d361dc1516a9d0b3e"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:40:03 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/madvise: fix data loss from MADV_FREE on a KSM page\n\nMADV_FREE can clear the dirty flag of a singly mapped KSM folio. The\nfolio remains in the stable tree and can gain new mappings without being\ndirtied again. Once marked lazyfree, reclaim can discard data that those\nmappings still need.\n\nKSM always marks a folio dirty when converting it to a KSM folio in\ntry_to_merge_one_page(). Marking a folio lazyfree clears PG_swapbacked\nbut leaves PG_dirty unchanged. Preserving PG_dirty makes reclaim restore\nPG_swapbacked instead of discarding the folio. This also protects folios\nthat were already lazyfree when KSM converted them.\n\nSkip KSM folios before clearing their dirty flag, checking under the\nfolio lock to serialize with KSM conversion.\n\nFixes: 854e9ed09ded (\"mm: support madvise(MADV_FREE)\")\nCc: stable@vger.kernel.org\nReported-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nReviewed-by: Xu Xin \u003cxu.xin@linux.dev\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-34-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "440c8779757f09f290770b1d361dc1516a9d0b3e",
      "tree": "f93201e51f3a3e809b087ac49446801540ab6b3b",
      "parents": [
        "402882943dfa8bab5c2bcc66189f9fb2828f248e"
      ],
      "author": {
        "name": "Josef Bacik",
        "email": "josef@toxicpanda.com",
        "time": "Sat Oct 31 10:40:01 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:53 2026 +0100"
      },
      "message": "mm/mremap: fix moving PUD leaves\n\npud_none_or_clear_bad() only really works on page tables. PUD leaves\nconfuse the check and make us clear the page table entry and print a\nwarning.\n\nSince commit aed877c2b4257 (\"device/dax: properly refcount device dax pages\nwhen mapping\"), this also leaks device-DAX folio references, mapcounts\nand RSS accounting, resulting in \"Bad rss-counter state\" warnings on exit.\n\nAllow PUD leaves in get_old_pud(). If a PUD leaf cannot be moved as a\nwhole or the move fails, split it. This unmaps it with proper accounting\ninstead of treating the leaf entry as a PMD table.\n\nKeep using pud_trans_huge() for now, in the future this code should be\ncleaned up to just check for PUD leaves.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\nFixes: a00cc7d9dd93 (\"mm, x86: add support for PUD-sized transparent hugepages\")\nCc: stable@vger.kernel.org\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\n[ david: fallthrough after splitting ]\nReviewed-by: Pedro Falcato \u003cpfalcato@suse.de\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-32-d6437171ecc3@kernel.org\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "402882943dfa8bab5c2bcc66189f9fb2828f248e",
      "tree": "497bdab33083f041ad1c3483a257aeb3bb0bb335",
      "parents": [
        "b4417d08034a7b4a3083e0e2d95429d4542524f2"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:40:00 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/mremap: recheck PUDs under the page table lock\n\nOnce get_old_pud() is fixed to accept PUD leaves, unmap_mapping_range() can\nclear a leaf between the lookup and the move. Holding mmap_lock in write\nmode does not prevent this.\n\nIf the zap happens before move_page_tables() tests the entry, an empty\nPUD can reach move_normal_pud(), where pud_populate() turns it into a\npresent page table entry. If it happens after the test, move_huge_pud()\ncan instead try to move an empty entry, triggering CONFIG_DEBUG_VM\nwarnings on powerpc.\n\nRecheck the source under the page table lock in both helpers. Treat an\nempty source in move_normal_pud() as a completed move, and use\n__pud_trans_huge_lock() in move_huge_pud().\n\nIn the future we should likely have the code lookup a PUD/PMD lockless\nonce, instead of multiple times, because one of the problematic bits\nhere is the:\n\n\tpud_trans_huge(*old_pud)\n\nFixes: 0881ace292b6 (\"mm/mremap: use pmd/pud_poplulate to update page table entries\")\nCc: stable@vger.kernel.org\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nReviewed-by: Pedro Falcato \u003cpfalcato@suse.de\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-31-d6437171ecc3@kernel.org\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "b4417d08034a7b4a3083e0e2d95429d4542524f2",
      "tree": "566f5476e6a987b4cc45f3a105104e8c68fcd43c",
      "parents": [
        "5ad9e4b0f1104f5dbfb41125c34bb30ea6dc7a94"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:39:59 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/mremap: use pudp_huge_get_and_clear() when moving huge PUDs\n\nmove_huge_pud() reads the old PUD and clears it in separate operations.\nHardware accessed or dirty updates between those operations can be lost\nwhen the saved entry is installed at the new address.\n\nThe raw pud_clear() also bypasses page_table_check_pud_clear(), while\nset_pud_at() accounts for the destination mapping. This leaves the\nchecker counts unbalanced for mappings tracked by page table checking.\n\nTo fix it, simply use pudp_huge_get_and_clear().\n\nFixes: 7d846db7d0e2 (\"mm/mremap: convert huge PUD move to separate helper\")\nCc: stable@vger.kernel.org\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nReviewed-by: Pedro Falcato \u003cpfalcato@suse.de\u003e\nReviewed-by: Dev Jain \u003cdev.jain@arm.com\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-30-d6437171ecc3@kernel.org\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "5ad9e4b0f1104f5dbfb41125c34bb30ea6dc7a94",
      "tree": "01ea476e281b7e8eaa7eac75df345c780bd9a5ce",
      "parents": [
        "6d65925777ecae9d7a571a327e41c63f3940a0c7"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:39:58 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/mmu_notifier: set -\u003emm only after mmgrab()\n\nRadeon uses a non-NULL notifier-\u003emm to decide whether to call\nmmu_interval_notifier_remove() when freeing a buffer object.\n__mmu_interval_notifier_insert() sets -\u003emm before validating the range,\nso a wrapping userptr range can leave -\u003emm set after insertion fails.\nCleanup then tries to remove an unregistered notifier for which no mm\nreference was acquired.\n\nSet -\u003emm only after mmgrab(), once insertion can no longer fail. While\nwe could fix radeon\u0027s code instead, setting -\u003emm on success only makes\nthe code more robust.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\nFixes: 3506ff69c3ec (\"drm/radeon: use mmu_interval_notifier_insert\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\n[ david: simplify description ]\nReviewed-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-29-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "6d65925777ecae9d7a571a327e41c63f3940a0c7",
      "tree": "c78517ff4e7a56486901b5924644b8291081dbd5",
      "parents": [
        "64ae7959a1df8af8eec504e31df2ec9670424a4e"
      ],
      "author": {
        "name": "Josef Bacik",
        "email": "josef@toxicpanda.com",
        "time": "Sat Oct 31 10:39:57 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/mmu_notifier: finish non-blocking interval invalidation on error\n\nWhen an ordinary MMU notifier rejects a non-blocking invalidation, the\ninterval invalidation started beforehand is left unfinished: the caller\nskips mmu_notifier_invalidate_range_end(). Subsequent interval notifier\noperations can then wait forever.\n\nThe only in-tree trigger is nouveau SVM, which uses both notifier types\nand rejects non-blocking invalidations. Reaping via the OOM reaper or\nprocess_mrelease() can therefore leave the GPU fault worker stuck,\nholding a reference that prevents the dying process\u0027s address space\nand memory from being freed.\n\nEnd the interval invalidation when an ordinary notifier fails a\nnon-blocking invalidation, like mn_itree_invalidate() already does when\nan interval notifier fails. Make that handling clearer in the\ndocumentation of mmu_notifier_invalidate_range_start_nonblock().\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\nFixes: 99cb252f5e68 (\"mm/mmu_notifier: add an interval tree notifier\")\nCc: stable@vger.kernel.org\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\n[ david: simplify description, update function doc ]\nAcked-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-28-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "64ae7959a1df8af8eec504e31df2ec9670424a4e",
      "tree": "17c3723625280b82a872fba1c1be4e95eebf9c14",
      "parents": [
        "05f64f211a25f7d9771d4fde109aad97174a1cf3"
      ],
      "author": {
        "name": "Josef Bacik",
        "email": "josef@toxicpanda.com",
        "time": "Sat Oct 31 10:39:56 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/mmu_gather: fix flushing ranges with 4 GiB or larger\n\n__tlb_adjust_range() takes the size of the range which has to be flushed\nas an unsigned int. Its callers, tlb_flush_{pte,pmd,pud,p4d}_range(), get\nand pass an unsigned long. Consequently, a range that is 4 GiB or larger\ngets truncated, possibly to 0.\n\nOn arm64 with hugetlb, a 64k kernel can have 16 GiB hugetlb folios\nmapped contiguously at the PMD level and flush them when unmapping, and a\n16k kernel can flush 64 GiB PUDs through tlb_unshare_pmd_ptdesc(). So\nat least these two scenarios are affected.\n\nFix it by flushing the proper range instead of the truncated one by\nproperly using \"unsigned long\" for range_size.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\nFixes: b528e4b6405b (\"mm/hugetlb: add tlb_remove_hugetlb_entry for handling hugetlb pages\")\nFixes: 8ce720d5bd91 (\"mm/hugetlb: fix excessive IPI broadcasts when unsharing PMD tables using mmu_gather\")\nCc: stable@vger.kernel.org\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nAcked-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\n[ david: use two-tab indent, simplify description ]\nReviewed-by: Qi Zheng \u003cqi.zheng@linux.dev\u003e\nReviewed-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nReviewed-by: Dev Jain \u003cdev.jain@arm.com\u003e\nReviewed-by: Muchun Song \u003cmuchun.song@linux.dev\u003e\nReviewed-by: Pedro Falcato \u003cpfalcato@suse.de\u003e\nReviewed-by: SJ Park \u003csj@kernel.org\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-27-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "05f64f211a25f7d9771d4fde109aad97174a1cf3",
      "tree": "ec1386396c4adeec8314f891c227dfaa3518ce6b",
      "parents": [
        "4eee9c389b072e161549d46dcb1ae10b0222717e"
      ],
      "author": {
        "name": "Gregory Price",
        "email": "gourry@gourry.net",
        "time": "Sat Oct 31 10:39:55 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/userfaultfd: compare exact registration modes before skipping\n\nChanging registration from MISSING|WP to WP returns success but leaves\nMISSING enabled. The no-op check sees that WP is already set and skips\nthe update, so later accesses to missing pages still wait for userspace.\n\nSkip the update only when the current and requested UFFD modes match\nexactly.\n\nFixes: 63b2d4174c4a (\"userfaultfd: wp: add the writeprotect API to userfaultfd ioctl\")\nCc: stable@vger.kernel.org\nSigned-off-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\n[ david: apply fixup from Lorenzo ]\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-26-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "4eee9c389b072e161549d46dcb1ae10b0222717e",
      "tree": "8d71cdefab65cf4dfed0a1a24675e60c0ee2dc4d",
      "parents": [
        "3afb19d68cc5e7851fdb1069c8094af97bd80417"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:39:54 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/userfaultfd: wake waiters when registration modes are removed\n\nUFFDIO_REGISTER can replace MISSING or MINOR tracking without waking\nfaults that are already queued. For example, switching an anonymous\nrange from MISSING to WP leaves a missing-fault waiter asleep until\nuserspace explicitly wakes it.\n\nWhen a registration change removes a UFFD mode, wake waiters in the\naffected interval after updating the VMA. The VMA is write-locked at\nthis point, so no new faults can queue under the old modes and woken\nthreads cannot retry until mmap_write_unlock(). Waiters for retained\nmodes in the same interval may also wake and refault.\n\nThe hang reproduces for MISSING-to-WP and MINOR-to-MISSING transitions,\nwith both read and unread fault events.\n\nFixes: 63b2d4174c4a (\"userfaultfd: wp: add the writeprotect API to userfaultfd ioctl\")\nCc: stable@vger.kernel.org\nReviewed-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nSigned-off-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nReviewed-by: Mike Rapoport (Microsoft) \u003crppt@kernel.org\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-25-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "3afb19d68cc5e7851fdb1069c8094af97bd80417",
      "tree": "7b3e9aa960eb31fb3fed470440ac11a9b1273948",
      "parents": [
        "35f7ecd55ce7e51cb6d5ef49e6dd51f3c80f61e4"
      ],
      "author": {
        "name": "Josef Bacik",
        "email": "josef@toxicpanda.com",
        "time": "Sat Oct 31 10:39:53 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/userfaultfd: wake all waiters on unregister\n\nUFFDIO_UNREGISTER only wakes pending faults if VM_UFFD_MISSING is set.\nThreads waiting on write-protect, minor or RWP faults can therefore remain\nasleep after unregistering a range that does not track missing faults.\n\nWake pending faults regardless of the registration mode so they can retry\nwithout an explicit UFFDIO_WAKE or closing the userfaultfd. This matches\nthe existing behavior for missing faults, including removing unread fault\nmessages for the woken waiters.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\nFixes: 63b2d4174c4a (\"userfaultfd: wp: add the writeprotect API to userfaultfd ioctl\")\nCc: stable@vger.kernel.org\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\n[ david: rebase; simplify description ]\nReviewed-by: Mike Rapoport (Microsoft) \u003crppt@kernel.org\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-24-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "35f7ecd55ce7e51cb6d5ef49e6dd51f3c80f61e4",
      "tree": "65fe0e71826939f66f2d1c9fb9c08d412696eb5c",
      "parents": [
        "21a3888d3d2f87b7f15ccea1f0befd57346fe899"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:39:52 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/userfaultfd: write-lock the VMA before waking waiters when unregistering\n\nuserfaultfd_unregister() wakes pending missing faults before clearing the\nVMA\u0027s userfaultfd registration. With per-VMA fault locking, holding\nmmap_lock for write does not prevent another fault from queuing after\nthe wakeup but before userfaultfd_clear_vma() write-locks the VMA. That\nwaiter can then remain asleep indefinitely.\n\nCall vma_start_write() before waking waiters. Existing fault handlers\nqueue themselves before dropping the VMA read lock, and new readers are\nexcluded until mmap_write_unlock().\n\nFixes: 29a22b9e08d7 (\"mm: handle userfaults under VMA lock\")\nCc: stable@vger.kernel.org\nReported-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nReviewed-by: Mike Rapoport (Microsoft) \u003crppt@kernel.org\u003e\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nReviewed-by: Suren Baghdasaryan \u003csurenb@google.com\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-23-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "21a3888d3d2f87b7f15ccea1f0befd57346fe899",
      "tree": "79d03b36a5e209c94250d7bcbb046b32a08d08ef",
      "parents": [
        "1dfe4b276c23189394afb42d114ee8a54cc3aff2"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:39:51 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/gup: check for overflow when converting nr_pages to bytes in GUP-fast\n\nThe overflow check in gup_fast_fallback() only covers the addition to\nstart. The preceding nr_pages \u003c\u003c PAGE_SHIFT can already have truncated\nthe length on 32bit.\n\nUsers such as RapidIO\u0027s rio_dma_transfer() can derive such page counts\nfrom a 64-bit userspace length.\n\nLet\u0027s just check_shl_overflow() to reject any such overflow with\n-EOVERFLOW early.\n\nFixes: c28b1fc70390 (\"mm/gup: reorganize internal_get_user_pages_fast()\")\nCc: stable@vger.kernel.org\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nAcked-by: Muchun Song \u003cmuchun.song@linux.dev\u003e\nReviewed-by: Barry Song \u003cbaohua@kernel.org\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-22-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "1dfe4b276c23189394afb42d114ee8a54cc3aff2",
      "tree": "90ebd4f5ebd72e633ad6a0246bdefbe8de1058eb",
      "parents": [
        "c83ee2fa5a94edb2e04102b9dd4f1ee0eeb2b932"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:39:50 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/gup: fix out-of-bounds write for nr_pages \u003d\u003d 0 in GUP-fast\n\nWith nr_pages \u003d\u003d 0, GUP-fast still enters its page table walk and can\nwrite past the caller\u0027s page array. The old end \u003c\u003d start check caught\nempty ranges, but was replaced with an overflow check.\n\nUsers such as OrangeFS can pass a zero page count derived from a\nuserspace-supplied length. So let\u0027s return zero for nr_pages \u003d\u003d 0 before\nstarting the walk, just like GUP-slow.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\nFixes: c28b1fc70390 (\"mm/gup: reorganize internal_get_user_pages_fast()\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\n[ david: simplify description ]\nReviewed-by: Lorenzo Stoakes (ARM) \u003cljs@kernel.org\u003e\nAcked-by: Muchun Song \u003cmuchun.song@linux.dev\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-21-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "c83ee2fa5a94edb2e04102b9dd4f1ee0eeb2b932",
      "tree": "ab36b1ec7001bf997d9436b880ce1625f41a07c3",
      "parents": [
        "79cb51d538abc459f74e046d27797d36b133ce0e"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:39:49 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/gup: fix clearing folios in memfd_pin_folios()\n\nmemfd_pin_folios() pins folios obtained directly from the page cache\nwithout checking whether they are uptodate. However, shmem fallocate()\ncan leave newly allocated folios uncleared and not uptodate. Callers\nsuch as udmabuf can then expose uninitialized memory to userspace.\n\nClear non-uptodate folios and mark them uptodate under the folio lock\nbefore returning them to the caller.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\nFixes: 89c1905d9c14 (\"mm/gup: introduce memfd_pin_folios() for pinning memfd folios\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\n[ david: simplify description and comment ]\nReviewed-by: Pratyush Yadav (Google) \u003cpratyush@kernel.org\u003e\nReviewed-by: Samiullah Khawaja \u003cskhawaja@google.com\u003e\nTested-by: Samiullah Khawaja \u003cskhawaja@google.com\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-20-d6437171ecc3@kernel.org\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "79cb51d538abc459f74e046d27797d36b133ce0e",
      "tree": "e123d25149e9e567631042af7f07d24ea7cec366",
      "parents": [
        "fe2817e3d5ea347214342c9a5cd8bcbff20c0574"
      ],
      "author": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Sat Oct 31 10:39:48 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/gup: recheck the PUD under PTL in follow_pud_mask()\n\nfollow_pud_mask() reads the PUD without a lock. If it is a leaf, it takes\nthe lock and calls follow_huge_pud(), which reads the entry again, but\nonly tests whether it is present.\n\nA leaf can be zapped concurrently and a page fault can fill the empty\nentry with a page table.\n\nThis currently only applies when device-dax makes use of PUD entries,\nand the fault after e.g., MADV_DONTNEED would find THPs to be disabled.\n\nThat requires a sequence like\n\n1) Fault in the PUD\n2) Disable THP\n3) Have GUP race against concurrent MADV_DONTNEED + refault\n\nWhich is rather unlikely to happen in practice, which is why we never\nreceived a report about such a problem.\n\nBefore commit 1b1676180246 (\"mm/gup: handle huge pud for\nfollow_pud_mask()\"), we performed that check in follow_devmap_pud() by\ntesting for pud_devmap().\n\nLet\u0027s fix it by just structuring follow_pud_mask() similar to\nfollow_pmd_mask(), minus protnone stuff that does not apply and minus\nFOLL_SPLIT_PMD handling. That makes it much easier to spot any such\ninconsistencies.\n\nPerform the pud_bad() check early in follow_pmd_mask() and just forward\nthe PUD value. We can drop the pud_present() check in follow_huge_pud(),\njust like we have in follow_huge_pmd().\n\nEven though we are performing more changes than strictly necessary, the\nfix should be easy to backport.\n\nFixes: 1b1676180246 (\"mm/gup: handle huge pud for follow_pud_mask()\")\nCc: stable@vger.kernel.org\nReported-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-19-d6437171ecc3@kernel.org\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "fe2817e3d5ea347214342c9a5cd8bcbff20c0574",
      "tree": "1366349eaacabc6a4252600e625a53316bb90ffa",
      "parents": [
        "db38b902307e687219ec765ef51a6ef459746c87"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:39:46 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/khugepaged: preserve dirty bits when collapsing PTE-mapped THPs\n\ntry_collapse_pte_mapped_thp() clears PTEs without transferring their dirty\nbits to the folio. A shmem read fault can map a clean folio writable, so\na later store only dirties the PTE. Losing that dirty bit allows reclaim\nto discard modified data.\n\nThe assumption that regular files are read-only is also obsolete since\ncommit 1b6444331bebb (\"mm/khugepaged: enable clean pagecache folio collapse\nfor writable files\"). In any case, transferring PTE dirty bits to the folio\nwhen removing mappings (and while the folio is still mapped) is the right\nthing to do.\n\nUse get_and_clear_ptes() to collect the dirty bits and mark the folio\ndirty before unmapping it. Update the comment.\n\nThis was reproduced with shmem using MADV_COLLAPSE followed by\nMADV_PAGEOUT.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\nFixes: 27e1f8273113 (\"khugepaged: enable collapse pmd for pte-mapped THP\")\nFixes: 1b6444331bebb (\"mm/khugepaged: enable clean pagecache folio collapse for writable files\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\n[ david: adjust comment; simplify description; cover file-thp as well ]\nReviewed-by: Pedro Falcato \u003cpfalcato@suse.de\u003e\nReviewed-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-17-d6437171ecc3@kernel.org\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nReviewed-by: Baolin Wang \u003cbaolin.wang@linux.alibaba.com\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "db38b902307e687219ec765ef51a6ef459746c87",
      "tree": "09f14f91b0231e0af8de97b36ce396871e21b878",
      "parents": [
        "aa72cf34d90da7019591ab67533a8ece8b41da2d"
      ],
      "author": {
        "name": "Josef Bacik",
        "email": "josef@toxicpanda.com",
        "time": "Sat Oct 31 10:39:45 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/khugepaged: fix PMD table lock leak in try_collapse_pte_mapped_thp()\n\nFor a private mapping with userfaultfd, try_collapse_pte_mapped_thp()\ntakes the PMD table lock before it maps the page table for the second time.\nIf that (pte_offset_map_rw_nolock) fails, because the page table vanished\nin the meantime due to concurrent page table reclaim, it leaves through\nthe abort label, where the PMD table lock is unlocked if it differs from\nPTE table lock.\n\nIn case the PMD table lock and the PTE table lock match, which is the\ncase without CONFIG_SPLIT_PTE_PTLOCKS after pte_offset_map_rw_nolock()\nfailed, we miss to unlock the PMD table.\n\nTo fix it, forget the PTE table lock when we unmap+unlock the PTE table.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\nFixes: 6375e95f381e (\"mm: pgtable: reclaim empty PTE page in madvise(MADV_DONTNEED)\")\nCc: stable@vger.kernel.org\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\n[ david: move the ptl \u003d NULL handling; rewrite description, drop wrong comments ]\nReviewed-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-16-d6437171ecc3@kernel.org\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nReviewed-by: Baolin Wang \u003cbaolin.wang@linux.alibaba.com\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "aa72cf34d90da7019591ab67533a8ece8b41da2d",
      "tree": "7f45168fce45db2082cc16573d7c16db876f210e",
      "parents": [
        "63a940541358d09cc9f02d40b71eb8d3917a21c0"
      ],
      "author": {
        "name": "Josef Bacik",
        "email": "josef@toxicpanda.com",
        "time": "Sat Oct 31 10:39:44 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:52 2026 +0100"
      },
      "message": "mm/khugepaged: always recheck the pmd in try_collapse_pte_mapped_thp()\n\ntry_collapse_pte_mapped_thp() drops the PTE lock after it has cleared the\npage table, and takes the PMD lock and the PTE lock to remove it.\n\nIn between, MADV_DONTNEED with CONFIG_PT_RECLAIM can reclaim the\npage table. The pmd_same() check is supposed to handle this, but it is\nonly done with CONFIG_SPLIT_PTE_PTLOCKS.\n\nFix it by performing the check unconditionally.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\nFixes: 6375e95f381e (\"mm: pgtable: reclaim empty PTE page in madvise(MADV_DONTNEED)\")\nCc: stable@vger.kernel.org\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\n[ david: adjust description ]\nReviewed-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-15-d6437171ecc3@kernel.org\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nReviewed-by: Baolin Wang \u003cbaolin.wang@linux.alibaba.com\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "63a940541358d09cc9f02d40b71eb8d3917a21c0",
      "tree": "30b8646073d946a11f712db726cb632e8c722398",
      "parents": [
        "e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:39:43 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:51 2026 +0100"
      },
      "message": "mm/huge_memory: fix zapping migration entries for device-private THPs\n\nA PMD migration entry can refer to a device-private folio.\nzap_huge_pmd_folio() checks the folio type instead of the entry type,\nso it treats such a migration entry as a device-private entry.\n\nInstalling the migration entry already removed the reverse mapping and\ndropped the mapping reference. Zapping it must not repeat those\noperations. Concurrent MADV_DONTNEED during migration back to system\nmemory can trigger this.\n\nCheck the PMD entry type using pmd_is_device_private_entry().\n\nFix generated by an LLM and sent by Chris Mason in private.\n\nFixes: 368076f52ebe (\"mm/huge_memory: add device-private THP support to PMD operations\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\n[ david: simplify description ]\nReviewed-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-14-d6437171ecc3@kernel.org\nReviewed-by: Zi Yan \u003cziy@nvidia.com\u003e\nReviewed-by: Lance Yang \u003clance.yang@linux.dev\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "e6a07d29b0a60f3a4cfe77fe34eeb4b3fb38d6c4",
      "tree": "d4298fe402fae983d67a5d66eb0f604adc485c89",
      "parents": [
        "d90bdc02e36ec08d8248ebc6cdc52e12043eb28c"
      ],
      "author": {
        "name": "Chris Mason",
        "email": "mason@kernel.org",
        "time": "Sat Oct 31 10:39:42 2026 +0100"
      },
      "committer": {
        "name": "David Hildenbrand (Arm)",
        "email": "david@kernel.org",
        "time": "Tue Nov 03 20:20:51 2026 +0100"
      },
      "message": "mm/huge_memory: fix truncate racing with PMD zapping\n\nzap_huge_pmd_folio() removes the rmap before calling folio_mark_dirty().\nIf this was the last mapping, truncation can skip unmapping the folio\nand proceed without waiting for the PMD lock, racing with dirtying.\n\nifs_set_range_dirty() can oops if MADV_DONTNEED races with\nftruncate() on XFS, when we get the folio set dirty after it was found\nto not be mapped anymore.\n\nMove folio_mark_dirty() and folio_mark_accessed() before rmap removal,\nmatching the PTE zap path. This keeps the folio mapped while updating\nits state, so truncation must wait for the page table lock.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\nFixes: fe6cf984939d (\"mm/huge_memory: transfer the pmd dirty bit to the folio on zap\")\nCc: stable@vger.kernel.org\nSigned-off-by: Chris Mason \u003cmason@kernel.org\u003e\n[ david: simplify comment and description ]\nReviewed-by: Gregory Price (Meta) \u003cgourry@gourry.net\u003e\nTested-by: Muhammad Usama Anjum \u003cusama.anjum@arm.com\u003e\nLink: https://patch.msgid.link/20261031-fixes_core-v3-13-d6437171ecc3@kernel.org\nReviewed-by: Zi Yan \u003cziy@nvidia.com\u003e\nReviewed-by: Baolin Wang \u003cbaolin.wang@linux.alibaba.com\u003e\nSigned-off-by: David Hildenbrand (Arm) \u003cdavid@kernel.org\u003e\n"
    },
    {
      "commit": "2d4c272e816a5b784f1fc7899256f8826df34edb",
      "tree": "683a399805e69a9dcf8b3323c4c03c8523db686a",
      "parents": [
        "54195bf371997d9c858f28b697450bbbfb8006d8"
      ],
      "author": {
        "name": "Liu Changjie",
        "email": "liucj1228@outlook.com",
        "time": "Mon Oct 19 00:46:34 2026 +0800"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:30 2026 +0100"
      },
      "message": "can: peak_usb: pcan_usb_fd_decode_buf(): accept short uCAN end-of-list records\n\nA PCAN-USB FD v2 running firmware 3.2.0 sends a 16-byte status record\nfollowed by a four-byte zero-size end marker.\n\nSince commit 93fcab2c6968 (\"can: peak_usb: validate uCAN receive record\nlengths\") these transfers cause repeated receive-buffer dumps while the\ninterface is up.\n\nThis has been observed on Linux 7.2.11-arch1-1 with matching kernel\nheaders:\n- Classic CAN, 500 kbit/s: 25 decoder errors in 5 s before the fix; none in\n  15 s after.\n- CAN FD, 500 kbit/s nominal and 2 Mbit/s data: 26 decoder errors in 5 s\n  before the fix; none in 60 s after.\n- Three additional down/up cycles: no decoder errors.\n\npcan_usb_fd_decode_buf() requires a complete 12-byte struct pucan_msg\nbefore checking the size field, so it rejects the end marker with -EBADMSG.\n\nCheck that the size field is present before testing for an end marker.\nRequire the full header for nonzero-size records and keep the remaining\nrecord and payload length checks.\n\nThis patch was created with LLM assistance.\n\nFixes: 93fcab2c6968 (\"can: peak_usb: validate uCAN receive record lengths\")\nSigned-off-by: Liu Changjie \u003cliucj1228@outlook.com\u003e\nReviewed-by: Stéphane Grosjean \u003cs.grosjean@peak-system.fr\u003e\nLink: https://patch.msgid.link/CH5PR19MB997156AB3BE253C3BE445223B0AC992@CH5PR19MB997156.namprd19.prod.outlook.com\nCc: stable@vger.kernel.org\n[mkl: copy additional info to commit message]\n[mkl: convert Assisted-by: tag to prose]\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n---\nBuilt and tested the original and patched peak_usb modules on Arch\nLinux 7.2.11-arch1-1 with matching kernel headers.\n\n  - Classic CAN, 500 kbit/s: 25 decoder errors in 5 s before the fix;\n    none in 15 s after.\n  - CAN FD, 500 kbit/s nominal and 2 Mbit/s data: 26 decoder errors\n    in 5 s before the fix; none in 60 s after.\n  - Three additional down/up cycles: no decoder errors.\n\nUSB captures during the patched tests contained 406 packets with\nshort end markers. Neither receive-buffer dump recurred.\n\nThe CAN bus was disconnected; external TX/RX was not tested.\nOne startup \"can_change_state: oops, state did not change\" message and\nan RX dropped count reaching 2 were observed during the patched tests.\nTheir causes remain undetermined.\n"
    },
    {
      "commit": "54195bf371997d9c858f28b697450bbbfb8006d8",
      "tree": "a0cd96f6087470c9980e1d2ceca78bee671709af",
      "parents": [
        "493719574532a0630d4a9debd5ce01a8a3fd570d",
        "f5128a76726105f398d7ee70ee523dd4f68d62f4"
      ],
      "author": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Oct 27 10:09:29 2026 +0100"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:30 2026 +0100"
      },
      "message": "Merge patch series \"can: dev: can_fill_info(): don\u0027t wake up controller if interface is down\"\n\nThis series prevents the CAN controller from being activated by netlink\nqueries as long as the interface is down.\n\nLink: https://patch.msgid.link/20261027065012.191348-1-chunyuzhiqiang@yinhe.ht\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "f5128a76726105f398d7ee70ee523dd4f68d62f4",
      "tree": "a0cd96f6087470c9980e1d2ceca78bee671709af",
      "parents": [
        "75332c410c8190d61499001c5516af977ca426c3"
      ],
      "author": {
        "name": "ChunYuZhiQiang",
        "email": "chunyuzhiqiang@yinhe.ht",
        "time": "Tue Oct 27 14:50:12 2026 +0800"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:30 2026 +0100"
      },
      "message": "can: dev: can_tdc_fill_info(): don\u0027t read automatic TDCV if interface is down\n\nThe automatic TDCV readback calls into the driver via do_get_auto_tdcv().\nSome drivers, such as xcan_get_auto_tdcv(), read controller registers\nwithout taking a runtime PM reference, so calling this while the\ninterface is down can touch registers whose clocks are gated.\n\nGate do_get_auto_tdcv() on netif_running() in can_tdc_fill_info() and\nadjust can_tdc_get_size() and can_data_bittiming_get_size() so that only\nthe automatic TDCV size is skipped when the interface is down. The other\nTDC parameters are still reported, as they are meaningful while the\ninterface is down.\n\nThis is a defensive hardening based on code inspection; the automatic\nTDCV path has not been triggered on hardware.\n\nSigned-off-by: ChunYuZhiQiang \u003cchunyuzhiqiang@yinhe.ht\u003e\nReviewed-by: Vincent Mailhol \u003cmailhol@kernel.org\u003e\nFixes: e8060f08cd69 (\"can: netlink: add can_priv::do_get_auto_tdcv() to retrieve tdcv from device\")\nLink: https://patch.msgid.link/20261027065012.191348-2-chunyuzhiqiang@yinhe.ht\n[mkl: fix open parenthesis alignment]\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "75332c410c8190d61499001c5516af977ca426c3",
      "tree": "4964d050b2e97dae6837f77b7c90f78e7afe21cf",
      "parents": [
        "493719574532a0630d4a9debd5ce01a8a3fd570d"
      ],
      "author": {
        "name": "ChunYuZhiQiang",
        "email": "chunyuzhiqiang@yinhe.ht",
        "time": "Tue Oct 27 14:50:11 2026 +0800"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:30 2026 +0100"
      },
      "message": "can: dev: can_fill_info(): don\u0027t wake up controller if interface is down\n\nIf the interface is down, the CAN controller might be powered down and\nits clocks gated. Don\u0027t call do_get_berr_counter() to read the bus error\ncounters if the interface is down, and adjust can_get_size() to match.\n\nThis removes one trigger for a synchronous external abort seen on\ni.MX8QXP when \"ip link show\" is run on a flexcan interface that was\nnever brought up. The underlying cause is platform-specific: on i.MX8QXP\nthe CAN clocks are gated through the SCU LPCG and the subsystem shares\nthe IMX_SC_R_CAN_0 power domain, and there is a window after\npm_runtime_resume_and_get() returns where the clock has not reached the\nmodule yet. This patch avoids the netlink query path while the interface\nis down, but does not root-cause the LPCG window itself.\n\nAs a result, IFLA_CAN_BERR_COUNTER is no longer reported for down\ninterfaces. Userspace must treat the attribute as optional.\n\nThe issue was triggered on an i.MX8QXP board by running \"ip link show\"\nwithout ever bringing the interface up:\n\n    Internal error: synchronous external abort: 0000000096000210\n\n    pc : flexcan_read_le+0x0/0x18\n    lr : flexcan_get_berr_counter+0x4c/0x8c\n    Call trace:\n     flexcan_read_le+0x0/0x18\n     flexcan_get_berr_counter+0x4c/0x8c\n     can_fill_info+0x1f8/0x434\n     rtnl_fill_ifinfo+0x8fc/0xbb4\n     rtnl_dump_ifinfo+0x364/0x448\n\nThis is the same class of problem fixed for m_can in\ncommit 91a55c72a821 (\"can: m_can: m_can_get_berr_counter(): don\u0027t\nwake up controller if interface is down\").\n\nFixes: ec56acfef2af1 (\"can: flexcan: flexcan_get_berr_counter(): switch on clocks before accessing ecr register\")\nCc: stable@vger.kernel.org\nSigned-off-by: ChunYuZhiQiang \u003cchunyuzhiqiang@yinhe.ht\u003e\nReviewed-by: Vincent Mailhol \u003cmailhol@kernel.org\u003e\nLink: https://patch.msgid.link/20261027065012.191348-1-chunyuzhiqiang@yinhe.ht\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "493719574532a0630d4a9debd5ce01a8a3fd570d",
      "tree": "772e9f7f5c829afdc465cc559dc5cda94b393b43",
      "parents": [
        "d3592ab8a1911ea25b6efa3d5b85def73c69f060",
        "b98179a6e1948c87539f77b387ac785beb5802c6"
      ],
      "author": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:26:49 2026 +0100"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:29 2026 +0100"
      },
      "message": "Merge patch series \"can: protect the receive lists with a per-device lock\"\n\nOliver Hartkopp \u003csocketcan@hartkopp.net\u003e says:\n\nThis series fixes a use-after-free in CAN_ISOTP and CAN_BCM that can be\ntriggered when a CAN device is moved to another network namespace while\na socket bound to this device is released [1].\n\nPatch 2 makes isotp_bind() check the return values of can_rx_register(),\nso that bind() does not succeed with missing receivers.\n\nPatch 4 copies the CAN_RAW and CAN_ISOTP specific socket options from\nand to user space outside of lock_sock(), so that a stalled copy can not\nblock raw_notify() waiting for lock_sock() under RTNL.\n\nPatches 5 and 6 fix the reset and the calculation of the CAN statistics.\n\nPatch 7 removes the pointers from the CAN specific proc output. As it\nchanges the proc output ABI it is not intended for stable and has been\nmoved to the end of the series, so that patches 1-6 can be backported\nwithout it.\n\nThe code of patches 1 and 5-7 is unchanged since v4, apart from the\nrebase of patch 7 in v12. Only the commit message of patch 1 has been\nupdated after the Sashiko review of v4 to describe the actual NULL\npointer dereference in can_rx_unregister() and the CAN_ISOTP path that\nreaches it.\n\nThe series is based on net/main.\n\nThe idea behind patch 3:\n\nThe receive lists of a CAN device are located in the device\u0027s\ncan_ml_priv and travel with the device when it is moved to another\nnetwork namespace. But they are protected by the per-netns\nrcvlists_lock, so the lock that protects a device\u0027s lists depends on\nthe namespace the caller passes to can_rx_register() and\ncan_rx_unregister(). can_rx_unregister() silently returns when this\nnamespace does not match dev_net(dev) anymore.\n\nisotp_release() and bcm_release() leave the netdev notifier list before\nthey can serialize against the notifier. When the device changes its\nnamespace in this window, their filters are not removed and the\nremaining receivers point to the freed socket or bcm op.\n\nTaking RTNL in these release paths is no option, as CAN_RAW already\nholds RTNL while adding and removing up to CAN_RAW_FILTER_MAX filters\nper socket, which unprivileged users can trigger repeatedly.\n\nInstead, patch 3 protects the receive lists where they are located: A\nspinlock in struct can_dev_rcv_lists protects the lists of a CAN device\n(initialized in can_set_ml_priv()) or the \u0027any\u0027 CAN device lists of a\nnamespace (initialized in can_pernet_init()). can_rx_unregister() then\nfinds the subscription independently of the current namespace of the\ndevice, which is kept accessible by the tracked device references the\nprotocols already hold. The per-netns rcvlists_lock only protects the\nreceive list statistics, for which CAN_RAW, CAN_BCM and CAN_ISOTP pass\nthe namespace that has been used for can_rx_register().\n\nAs a consequence, CAN_RAW and CAN_ISOTP do not need RTNL in bind(),\nsetsockopt() and release() anymore. bind() is serialized against\nNETDEV_UNREGISTER by publishing the device inside the RCU section of\nits lookup, as unlist_netdevice() and synchronize_net() precede\nNETDEV_UNREGISTER both on unregistration and on a namespace change.\nThe notifiers recheck the binding under lock_sock(). As RTNL does not\nkeep NETDEV_DOWN out of bind() anymore, bind() checks IFF_UP after\npublishing the bound device, with an smp_mb() pair against the\nnotifiers, so a down transition during bind() is still reported with\nENETDOWN.\n\nLink: https://patch.msgid.link/20261027-can-rx-lock-v12-0-eb5afc2d8b9b@hartkopp.net\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "d3592ab8a1911ea25b6efa3d5b85def73c69f060",
      "tree": "5d46fac7d68e6db9e097e2f4e9eb72081ddf483c",
      "parents": [
        "933bf0fcb325e67b19c86c9c4da7f029878d5170",
        "b4ebcbbf66ba6c5816dfe229effb4641c46e4b4c"
      ],
      "author": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Mon Sep 28 13:01:30 2026 +0200"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:29 2026 +0100"
      },
      "message": "Merge patch series \"can: skb: make echo skb freeing safe in any IRQ context\"\n\nCunhao Lu \u003c1579567540@qq.com\u003e says:\n\ncan_put_echo_skb() and the CAN skb allocation helpers may release skbs in\nhardware interrupt context or while hardware interrupts are disabled. This\nseries makes the affected public helper paths safe in either context and\nfixes the invalid echo-index skb leak.\n\nLink: https://patch.msgid.link/tencent_CD05F020BAFB2537F5D1F4CBB425588EA80A@qq.com\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "b98179a6e1948c87539f77b387ac785beb5802c6",
      "tree": "772e9f7f5c829afdc465cc559dc5cda94b393b43",
      "parents": [
        "01b19ed9fa031a649f3dd103ebe6e0102602e542"
      ],
      "author": {
        "name": "Oliver Hartkopp",
        "email": "socketcan@hartkopp.net",
        "time": "Tue Oct 27 15:31:11 2026 +0100"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:29 2026 +0100"
      },
      "message": "can: proc: remove pointers from CAN specific proc output\n\nThe proc content in /proc/net/can/ and /proc/net/can-bcm/ is intended to\ncheck the internal filter lists (af_can, can_raw) and the efficiency and\nfunctionality of can_bcm jobs. While exposing kernel addresses was\nacceptable when this code was written the times have changed and multiple\nattempts have been made to hash or remove such now sensitive data.\n\nThis patch removes the disclosure of pointers and instead provides the\nfunction names and sock inode numbers when available. When the function\nname can not be resolved (e.g. KALLSYMS\u003dn or stripped module symbols)\n%ps would fall back to the raw text address. Therefore (unknown) is\nprinted instead in this case. As there\u0027s no known tooling around the CAN\nspecific proc output breaking the ABI with this rework creates no issue.\n\nSuggested-by: Sebastian Andrzej Siewior \u003cbigeasy@linutronix.de\u003e\nSigned-off-by: Oliver Hartkopp \u003csocketcan@hartkopp.net\u003e\nLink: https://patch.msgid.link/20261027-can-rx-lock-v12-7-eb5afc2d8b9b@hartkopp.net\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "01b19ed9fa031a649f3dd103ebe6e0102602e542",
      "tree": "86d0e82e1ceb08e84406fb9ca3866c3805bc6991",
      "parents": [
        "12297f855bbd943847cb8893a3614caef5a9c2a8"
      ],
      "author": {
        "name": "Oliver Hartkopp",
        "email": "socketcan@hartkopp.net",
        "time": "Tue Oct 27 15:31:10 2026 +0100"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:29 2026 +0100"
      },
      "message": "can: proc: skip stats calculation after reset in can_stat_update()\n\nCommit 80b5f90158d1 (\"can: statistics: use atomic access in hot path\")\nintroduced local snapshots of the statistics counters at the beginning\nof can_stat_update(). When can_init_stats() resets the statistics, these\nstale pre-reset snapshots are still used for the following total/current\n/max calculations and overwrite the freshly reset values. Additionally a\njiffies tick between the snapshot and the reset could trigger a second\ncan_init_stats() call.\n\nMerge the reset conditions into a single check and skip the calculation\nfor the current interval when the statistics have been reset.\n\nFixes: 80b5f90158d1 (\"can: statistics: use atomic access in hot path\")\nCc: stable@vger.kernel.org\nSigned-off-by: Oliver Hartkopp \u003csocketcan@hartkopp.net\u003e\nLink: https://patch.msgid.link/20261027-can-rx-lock-v12-6-eb5afc2d8b9b@hartkopp.net\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "12297f855bbd943847cb8893a3614caef5a9c2a8",
      "tree": "fb158c1800ddfea95c36c51263b4b39d1f5f824d",
      "parents": [
        "43c973a0887d3d7b2ee0a446603c97bf0f38c58e"
      ],
      "author": {
        "name": "Runyu Xiao",
        "email": "runyu.xiao@seu.edu.cn",
        "time": "Tue Oct 27 15:31:09 2026 +0100"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:29 2026 +0100"
      },
      "message": "can: proc: reset pkg_stats atomics individually\n\nCommit 80b5f90158d1 (\"can: statistics: use atomic access in hot path\")\nconverted several members of struct can_pkg_stats to atomic_long_t and\nupdated the hot TX/RX and procfs read paths to use atomic_long_*()\nhelpers. However, can_init_stats() still clears the whole struct with\nmemset().\n\ncan_init_stats() is reached from can_stat_update() in timer context and\nalso from the procfs reset path. Those paths can run while the TX/RX hot\npaths are concurrently updating rx_frames, tx_frames, matches and their\n*_delta counters. Hitting the whole-struct memset() in that window\nperforms plain writes to fields that otherwise follow an atomic_long_t\naccess contract, which can lose or mix live statistics updates.\n\nThis issue was found by source-level API-misuse analysis looking for\nwhole-object resets left behind after atomic_long_t conversions, then\nmanually audited on Linux v6.18.21.\n\nReplace the whole-struct memset() with a helper that resets the\natomic_long_t counters via atomic_long_set() and clears the derived\nscalar statistics explicitly. This preserves the existing reset\nsemantics for scalar fields while restoring atomic access discipline for\nthe live counters.\n\nBuild-tested by compiling net/can/proc.o on x86_64 netdev/main.\nRuntime-tested with a QEMU + vcan setup on Linux v6.18.21 by driving\nconcurrent traffic and reset_stats reads, which reproduced inconsistent\nexported statistics before the fix.\n\n[Hartkopp] can_stat_update() also read the *_delta counters at the\nbeginning and cleared them with atomic_long_set() at the end. Increments\nfrom the hot path in between were lost for both the current and the next\ninterval. Use atomic_long_xchg() to fetch and clear the *_delta counters\nin one atomic step instead.\n\nOn x86_64 atomic_long_set() is a plain store like memset(), so the\nmemset() is an actual problem only on architectures with lock-based\natomics (e.g. parisc). The inconsistencies seen on x86_64 come from the\n*_delta handling and from the stale snapshots, which are fixed in \"can:\nproc: skip stats calculation after reset in can_stat_update()\". As\nbefore, the counters are reset one at a time and the derived scalar\nstatistics use plain stores.\n\nFixes: 80b5f90158d1 (\"can: statistics: use atomic access in hot path\")\nCc: stable@vger.kernel.org\nSigned-off-by: Runyu Xiao \u003crunyu.xiao@seu.edu.cn\u003e\nAcked-by: Oliver Hartkopp \u003csocketcan@hartkopp.net\u003e\nSigned-off-by: Oliver Hartkopp \u003csocketcan@hartkopp.net\u003e\nLink: https://patch.msgid.link/20261027-can-rx-lock-v12-5-eb5afc2d8b9b@hartkopp.net\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "43c973a0887d3d7b2ee0a446603c97bf0f38c58e",
      "tree": "bcbebe7d56effabc1433aeb37bec35dc9c53b0d2",
      "parents": [
        "0f3ad9ab40e3dad06d5c0693806e07935ceedbc3"
      ],
      "author": {
        "name": "Oliver Hartkopp",
        "email": "socketcan@hartkopp.net",
        "time": "Tue Oct 27 15:31:08 2026 +0100"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:29 2026 +0100"
      },
      "message": "can: raw, isotp: copy socket options outside of lock_sock()\n\nThe CAN_RAW and CAN_ISOTP specific socket options are copied from and\nto user space while holding lock_sock(). A copy that faults or stalls,\ne.g. on a userfaultfd or FUSE backed mapping, holds lock_sock() for its\nwhole duration.\n\nraw_notify() and isotp_notify() take lock_sock() of a socket that is\nbound to the vanishing device while holding RTNL. As the CAN_RAW\noptions can also be changed on a bound socket, a stalled copy can block\nRTNL on an unregistration or namespace change of the bound device.\nBefore \"can: protect the receive lists with a per-device lock\",\nraw_setsockopt() even held RTNL itself during the copy. CAN_ISOTP only\ncopies its options for unbound sockets, which isotp_notify() skips\nwithout taking lock_sock().\n\nKeep the user space copies out of the locked sections: Check the option\nname and length and copy the option values, including the CAN_RAW_FILTER\nfilters, to kernel memory before lock_sock(). raw_setsockopt_locked()\nand isotp_setsockopt_locked() get the copied values directly and drop\ntheir now redundant length checks and copies. As a side effect, a\nfailing copy can not leave partially overwritten options behind\nanymore. In raw_getsockopt() duplicate the filters under lock_sock() and\ncopy them to user space after release_sock().\n\nAs the option name and length are now checked before lock_sock(), the\norder of the checks in isotp_setsockopt() and accordingly the order of\nthe returned error values changes. This is in line with POSIX, which\ndoes not define an order in which multiple error conditions are\ndetected and reported.\n\nThe generic SOL_SOCKET options in sk_setsockopt() are not affected by\nthis patch.\n\nFixes: c18ce101f2e4 (\"[CAN]: Add raw protocol\")\nFixes: 1e5185c09058 (\"can: raw: add locking for raw flags bitfield\")\nCc: stable@vger.kernel.org # depends on \"can: protect the receive lists with a per-device lock\"\nSigned-off-by: Oliver Hartkopp \u003csocketcan@hartkopp.net\u003e\nLink: https://patch.msgid.link/20261027-can-rx-lock-v12-4-eb5afc2d8b9b@hartkopp.net\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "0f3ad9ab40e3dad06d5c0693806e07935ceedbc3",
      "tree": "28f48dfa731e43b6572a32fe69b33a8e1613c656",
      "parents": [
        "874f5f14cf626f72477071eff381c8485554250d"
      ],
      "author": {
        "name": "Oliver Hartkopp",
        "email": "socketcan@hartkopp.net",
        "time": "Tue Oct 27 15:31:07 2026 +0100"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:29 2026 +0100"
      },
      "message": "can: protect the receive lists with a per-device lock\n\nThe receive lists of a CAN device are located in the device\u0027s\ncan_ml_priv and travel with the device when it is moved to another\nnetwork namespace. But they are protected by the per-netns\nrcvlists_lock. So can_rx_unregister() needs dev_net(dev) to pick the\nright lock and silently returns when the passed namespace does not\nmatch dev_net(dev) anymore.\n\nisotp_release() and bcm_release() leave their notifier list before they\ntake any lock that serializes against the netdev notifier, which runs\nunder RTNL. When the bound device is moved to another namespace in this\nwindow, the notifier skips the socket and the release path has to remove\nthe filters itself. isotp_release() passes the socket\u0027s namespace, which\ndoes not match dev_net(dev) anymore. bcm_rx_unreg() passes dev_net(dev),\nwhich can_rx_unregister() reads again for its check, so a namespace\nchange between both reads makes the check fail as well. In both cases\ncan_rx_unregister() silently returns. As can_rx_register() stores\nrcv-\u003esk without a reference, the remaining receivers point to the freed\nsocket (isotp) or the freed op (bcm):\n\n  BUG: KASAN: use-after-free in isotp_rcv+0x1570/0x24d0\n  Read of size 1 at addr ffff888118130552 by task isotp_ns_uaf/578\n   can_rcv_filter+0x4af/0x8c0\n   can_receive+0x28d/0x3c0\n   can_rcv+0x2a9/0x310\n   __netif_receive_skb_one_core+0x21a/0x260\n   process_backlog+0x210/0x760\n\nBesides this, the lists of a device are protected by the rcvlists_lock\nof the namespace that is passed in. Callers which pass dev_net(dev) read\nit at different times, so the same lists may be modified under the locks\nof different namespaces while the device is moved.\n\nTaking RTNL in these release paths is no option: raw_bind(),\nraw_setsockopt() and raw_release() already hold RTNL while adding and\nremoving up to CAN_RAW_FILTER_MAX filters per socket, which unprivileged\nusers can trigger repeatedly and which makes RTNL a global bottleneck.\n\nInstead fix the root cause and add a spinlock to struct\ncan_dev_rcv_lists, which protects the receive lists of a CAN device or\nthe \u0027any\u0027 CAN device lists of a namespace. It is initialized in\ncan_set_ml_priv(), which is used by all CAN network devices. With this,\ncan_rx_unregister() finds the subscription independently of the\ncurrent namespace of the device. The protocols keep the device valid\nwith their tracked references. The per-netns rcvlists_lock only protects\nthe receive list statistics anymore, and CAN_RAW, CAN_BCM and CAN_ISOTP\npass the namespace that has been used for can_rx_register().\n\nSo isotp_release() and bcm_release() now remove their filters correctly\nwithout RTNL, and raw_release(), raw_setsockopt(), raw_bind() and\nisotp_bind() do not need RTNL anymore and add and remove their filters\nunder lock_sock(). To serialize bind() with NETDEV_UNREGISTER, bind()\npublishes the device inside the RCU section of its lookup, and\nraw_notify() and isotp_notify() recheck the bound device under lock_sock().\nAs RTNL does not keep NETDEV_DOWN out of bind() anymore, bind() checks\nIFF_UP after publishing the bound device, with a barrier pair against\nraw_notify() and isotp_notify(), so a down transition during bind() is\nstill reported with ENETDOWN.\n\nFixes: 20bab8b88baa (\"can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER\")\nFixes: 8e8cda6d737d (\"can: initial support for network namespaces\")\nReported-by: Norbert Szetei \u003cnorbert@doyensec.com\u003e\nLink: https://lore.kernel.org/linux-can/CEA6A38A-2646-4ADA-95B4-CBAE2F301A8E@doyensec.com/\nCc: stable@vger.kernel.org\nSigned-off-by: Oliver Hartkopp \u003csocketcan@hartkopp.net\u003e\nLink: https://patch.msgid.link/20261027-can-rx-lock-v12-3-eb5afc2d8b9b@hartkopp.net\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "874f5f14cf626f72477071eff381c8485554250d",
      "tree": "772edf692e21eefaebb43298416a0e7695b9b5c0",
      "parents": [
        "962947b69589881167054bae5accc8abfd5aa4b6"
      ],
      "author": {
        "name": "Oliver Hartkopp",
        "email": "socketcan@hartkopp.net",
        "time": "Tue Oct 27 15:31:06 2026 +0100"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:29 2026 +0100"
      },
      "message": "can: isotp: check the return values of can_rx_register() in isotp_bind()\n\nisotp_bind() ignores the return values of can_rx_register() for the RX\nand the echo receiver and binds the socket anyway. When a receiver can\nnot be allocated, bind() succeeds without this receiver, so the socket\ndoes not receive frames or its transmissions time out. isotp_release()\nand isotp_notify() later try to remove the missing receiver, which\ntriggers the \"receive list entry not found\" warning in\ncan_rx_unregister().\n\nAs the device has been checked before and RTNL prevents a namespace\nchange during bind(), only -ENOMEM can be returned here.\n\nCheck the return values and register the RX receiver as the last step.\nThe echo receiver is registered first, as it only handles the socket\u0027s\nown echo frames and does nothing while no transmission is in progress.\nSo a failed RX registration only needs to remove the echo receiver, and\nisotp_rcv() has never processed a frame for this socket.\n\nSet so-\u003eifindex before the registrations, so that a First Frame received\nbefore so-\u003ebound is set can be answered with a Flow Control frame and\nthe RX timeout is started as usual. As the RX receiver is registered\nlast, this can only happen for a bind() that succeeds. Reset so-\u003eifindex\nwhen bind() fails.\n\nCheck IFF_UP only after the receivers have been registered, so that a\nbind() that fails on a down device does not report ENETDOWN. As bind()\nholds RTNL, the device state can not change in between.\n\nFixes: e057dd3fc20f (\"can: add ISO 15765-2:2016 transport protocol\")\nCc: stable@vger.kernel.org\nSigned-off-by: Oliver Hartkopp \u003csocketcan@hartkopp.net\u003e\nLink: https://patch.msgid.link/20261027-can-rx-lock-v12-2-eb5afc2d8b9b@hartkopp.net\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "962947b69589881167054bae5accc8abfd5aa4b6",
      "tree": "bf940b7d33a488621b5adb68c0317fdd1efef222",
      "parents": [
        "d3592ab8a1911ea25b6efa3d5b85def73c69f060"
      ],
      "author": {
        "name": "Oliver Hartkopp",
        "email": "socketcan@hartkopp.net",
        "time": "Tue Oct 27 15:31:05 2026 +0100"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:29 2026 +0100"
      },
      "message": "can: replace ARPHRD_CAN type checks with can_get_ml_priv()\n\nCommit 4e096a18867a (\"net: introduce CAN specific pointer in the struct\nnet_device\") introduced an explicit way to assign the midlayer private\npointer (dev-\u003eml_priv) to named users like ML_PRIV_CAN. A valid pointer\nreturned by can_get_ml_priv() therefore identifies a real CAN device.\n\nThe referenced commit only converted the j1939 and proc code to this\ncheck, while the other parts of the CAN subsystem still rely on\ndev-\u003etype \u003d\u003d ARPHRD_CAN.\n\nThe TUNSETLINK ioctl allows a down TUN/TAP device to set its hardware\ntype to ARPHRD_CAN while dev-\u003eml_priv remains NULL. Such a repurposed\nnetdevice passes the ARPHRD_CAN checks.\n\nCommit 8aa59e355949 (\"can: af_can: fix NULL pointer dereference in\ncan_rx_register()\") already made can_rx_register() reject such devices.\nBut can_rx_unregister() still only checks dev-\u003etype and dereferences\nthe NULL ml_priv when it walks the receive lists of the device.\n\nCAN_ISOTP reaches this path: isotp_bind() ignores the return values of\ncan_rx_register() and binds the socket anyway. When the socket is\nreleased or the device is unregistered, isotp_release() and\nisotp_notify() remove the filters that have never been registered and\ntrigger the NULL pointer dereference in can_rx_unregister(). This only\nrequires owning a TUN/TAP device or CAP_NET_ADMIN in an unprivileged\nuser namespace.\n\nConvert the remaining ARPHRD_CAN checks in af_can, bcm, gw, isotp and\nraw to can_get_ml_priv().\n\nFixes: 4e096a18867a (\"net: introduce CAN specific pointer in the struct net_device\")\nCc: stable@vger.kernel.org\nCc: Oleksij Rempel \u003co.rempel@pengutronix.de\u003e\nSigned-off-by: Oliver Hartkopp \u003csocketcan@hartkopp.net\u003e\nLink: https://patch.msgid.link/20261027-can-rx-lock-v12-1-eb5afc2d8b9b@hartkopp.net\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "b4ebcbbf66ba6c5816dfe229effb4641c46e4b4c",
      "tree": "5d46fac7d68e6db9e097e2f4e9eb72081ddf483c",
      "parents": [
        "d4b616a38118e81cfb206babd052db260d7abf6c"
      ],
      "author": {
        "name": "Cunhao Lu",
        "email": "1579567540@qq.com",
        "time": "Fri Jul 31 17:45:02 2026 +0800"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:28 2026 +0100"
      },
      "message": "can: dev: can_put_echo_skb(): free skb on invalid echo index\n\ncan_put_echo_skb() consumes the skb on all paths except when the echo\nindex is out of bounds. This leaves ownership with the caller on -EINVAL,\nunlike the other error paths, and can leak the skb if the caller expects\nconsistent semantics.\n\nFree the skb before returning -EINVAL so that all return paths consume it.\n\nFixes: 6411959c10fe (\"can: dev: can_put_echo_skb(): don\u0027t crash kernel if can_priv::echo_skb is accessed out of bounds\")\nCc: stable@vger.kernel.org\nReviewed-by: Vincent Mailhol \u003cmailhol@kernel.org\u003e\nSigned-off-by: Cunhao Lu \u003c1579567540@qq.com\u003e\nLink: https://patch.msgid.link/tencent_683AA16E643DE00211CD2FB62991264DC605@qq.com\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n\n---\n\nFAQ:\n\nQ: `can_skb_init_valid()` directly modifies `skb-\u003edata` without checking if\n   the SKB is cloned or shared. Is this violating SKB shared buffer rules and\n   causing data corruption?\n\nA: The finding about can_skb_init_valid() modifying skb-\u003edata on a\n   potentially shared buffer is not relevant for this (correct) patch.\n\n   The FDF-flag write in can_skb_init_valid() only matters for PF_PACKET\n   use: PF_CAN allocators already set CANFD_FDF. The write exists to\n   normalize frames for PF_PACKET observers (tcpdump/Wireshark) so they can\n   distinguish classic CAN from CAN FD at the netdev level, and to\n   compensate for PF_PACKET senders that omit the bit. That normalization\n   is functionally required.\n\n   The shared-buffer concern only becomes realistic through a specific\n   chain: a PF_PACKET sender injects a CANFD-sized frame, the CAN driver\u0027s\n   loopback puts an echo skb back into can_rcv(), and cgw (without\n   modfuncs) clones it for forwarding to another interface. Only on that\n   second can_skb_init_valid() call is the skb cloned. By then the bit was\n   already set on the exclusive skb during the initial xmit path, so the\n   flags |\u003d CANFD_FDF write is strictly idempotent for any parallel\n   consumer of the shared buffer - no memory-safety or\n   information-disclosure consequence. It\u0027s a formal violation of the skb\n   sharing rules without an observable effect, so the current code can stay\n   as-is.\n\nLink: https://lore.kernel.org/all/54a3cc01-abcf-4a33-b932-39bb1f68cdd5@hartkopp.net/\n[mkl: convert Oliver\u0027s mail to FAQ section]\n"
    },
    {
      "commit": "d4b616a38118e81cfb206babd052db260d7abf6c",
      "tree": "5b0fd9a1682107efca9763a40a9d70112849f32f",
      "parents": [
        "d743071964920c92af598c87a9e6f4369263ee09"
      ],
      "author": {
        "name": "Cunhao Lu",
        "email": "1579567540@qq.com",
        "time": "Fri Jul 31 17:45:01 2026 +0800"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:28 2026 +0100"
      },
      "message": "can: skb: make CAN skb allocation failure paths IRQ-safe\n\nThe CAN skb allocation helpers are used from hardware interrupt receive\nhandlers. If can_skb_ext_add() fails, they release the newly allocated skb\nwith kfree_skb(), which is not safe in hardware interrupt context.\n\nUse dev_kfree_skb_any() for the allocation failure paths in\nalloc_can_skb(), alloc_canfd_skb(), and alloc_canxl_skb().\n\nFixes: 96ea3a1e2d31 (\"can: add CAN skb extension infrastructure\")\nSigned-off-by: Cunhao Lu \u003c1579567540@qq.com\u003e\nLink: https://patch.msgid.link/tencent_C825C17D442F801351CE2FBC4984064B4605@qq.com\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "d743071964920c92af598c87a9e6f4369263ee09",
      "tree": "689eecb6a81897d502946c792a8601c26c3ba408",
      "parents": [
        "933bf0fcb325e67b19c86c9c4da7f029878d5170"
      ],
      "author": {
        "name": "Cunhao Lu",
        "email": "1579567540@qq.com",
        "time": "Fri Jul 31 17:45:00 2026 +0800"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:54:28 2026 +0100"
      },
      "message": "can: skb: make echo skb freeing safe in any IRQ context\n\ncan_put_echo_skb() can be called with hardware interrupts disabled. Its\ndirect drop paths use kfree_skb(), while can_create_echo_skb() uses\nkfree_skb() when cloning fails and consume_skb() after a successful clone.\nNone of these helpers is safe in every IRQ context.\n\nUse dev_kfree_skb_any() for all drop paths and dev_consume_skb_any() when\nconsuming a successfully cloned skb. This preserves the respective skb drop\nand consumed semantics regardless of the caller IRQ context.\n\nSigned-off-by: Cunhao Lu \u003c1579567540@qq.com\u003e\nLink: https://patch.msgid.link/tencent_E84809CF236D0137885E7E4E4D58340B3208@qq.com\nCc: stable@kernel.org\nFixes: ae64438be192 (\"can: dev: fix skb drop check\")\nFixes: 0ae89beb283a (\"can: add destructor for self generated skbs\")\nFixes: 3ccd4c6167d3 (\"can: Unify droping of invalid tx skbs and netdev stats\")\nFixes: 39549eef3587 (\"can: CAN Network device driver and Netlink interface\")\n[mkl: also convert can_dropped_invalid_skb(), can_dev_dropped_skb()]\n[mkl: add stable on Cc + add Fixes tags]\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n\n---\n\nFAQ:\n\nQ: What about the comment in drivers/net/can/virtio_can.c\n   virtio_can_start_xmit()? The error handling for virtqueue_add_sgs()\n   mentions that can_put_echo_skb() consumes the skb via consume_skb().\n\nA: The comment in virtio_can.c will be updated in a separate series, to\n   ease backporting of this patch.\n\n[mkl: add FAQ section]\n"
    },
    {
      "commit": "933bf0fcb325e67b19c86c9c4da7f029878d5170",
      "tree": "633de9e9f3da82cb43a62de6d90c5b37068b291b",
      "parents": [
        "0fce44e29fce4b07642491b098afb41bd571e4f2"
      ],
      "author": {
        "name": "Kaixuan Li",
        "email": "kaixuanli0131@gmail.com",
        "time": "Sun Sep 20 11:56:26 2026 +0800"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:49:14 2026 +0100"
      },
      "message": "can: isotp: check the frame type, not just the length\n\nisotp_rcv() separates Classic CAN from CAN FD by skb-\u003elen alone:\n\n\tif (skb-\u003elen !\u003d so-\u003ell.mtu)\n\t\treturn;\n\n\tcf \u003d (struct canfd_frame *)skb-\u003edata;\n\nA CAN XL frame with cxl-\u003elen 4 is CAN_MTU bytes, so it passes, and is then\nread as a canfd_frame whose len comes out of canxl_frame.flags: at least\n0x80.\n\nOf the paths that follow, only the flow control one uses that length\nwithout bounding it first, so check_pad() walks to 255 over a 16-byte\nframe and the caller reports EBADMSG on an unrelated socket.\n\nbcm_rx_handler(), j1939_can_recv(), can_can_gw_rcv() and raw_rcv() check\nthe frame type here, and can_dropped_invalid_skb() switches on\nskb-\u003eprotocol on the transmit side. isotp_rcv() is the gap.\n\nFixes: fb08cba12b52 (\"can: canxl: update CAN infrastructure for CAN XL frames\")\nSigned-off-by: Kaixuan Li \u003ckaixuanli0131@gmail.com\u003e\nReviewed-by: Oliver Hartkopp \u003csocketcan@hartkopp.net\u003e\nAcked-by: Oliver Hartkopp \u003csocketcan@hartkopp.net\u003e\nReviewed-by: Quchaosheng \u003cquchaosheng000406@163.com\u003e\nLink: https://patch.msgid.link/20260920035626.2581040-1-kaixuanli0131@gmail.com\nCc: stable@vger.kernel.org\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "0fce44e29fce4b07642491b098afb41bd571e4f2",
      "tree": "24cbcc85d1c3c6f77830e19b08ccd18f2908309a",
      "parents": [
        "647b81ddefc6364290e67bf33c89d54971f8995e"
      ],
      "author": {
        "name": "Vincent Mailhol",
        "email": "mailhol@kernel.org",
        "time": "Fri Jul 31 18:29:44 2026 +0200"
      },
      "committer": {
        "name": "Marc Kleine-Budde",
        "email": "mkl@pengutronix.de",
        "time": "Tue Nov 03 19:48:36 2026 +0100"
      },
      "message": "can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices\n\nSending a PF_PACKET bypasses the CAN framework logic and can directly\nreach a CAN driver\u0027s xmit() function. The PF_PACKET framework only\nchecks that skb-\u003elen does not exceed the net_device MTU.\n\nFor a CAN device that is not CAN XL capable, anything above CANFD_MTU\n(72 bytes) is therefore dropped before it reaches the driver. However,\nCAN XL frames are variable length. can_is_canxl_skb() accepts lengths in\nthe range CANXL_HDR_SIZE + CANXL_MIN_DLEN up to CANXL_MTU, i.e. 13 to\n2060 bytes.\n\nAs a result, an ETH_P_CANXL skb with a length between 13 and 72 bytes\ncan pass both the MTU and the can_dropped_invalid_skb() checks.\n\nA driver that does not support CAN XL will interpret canxl_frame-\u003eflags\nas a length because of the overlap with can_frame-\u003elen. And because\nCANXL_XLF is set, the resulting length is between 128 and 255. For\ndrivers that do not check can_frame-\u003elen before copying can_frame-\u003edata,\nas most drivers do, this results in a buffer overflow of up to 247\nbytes.\n\nDrop ETH_P_CANXL skbs if the device does not have the CAN_CAP_XL\ncapability. Keep can_is_canxl_skb() for the validation of CAN XL skbs.\n\nCloses: https://sashiko.dev/#/patchset/20260731-master-v5-0-5b27029dee20@qq.com?part\u003d1\nFixes: fb08cba12b52 (\"can: canxl: update CAN infrastructure for CAN XL frames\")\nSigned-off-by: Vincent Mailhol \u003cmailhol@kernel.org\u003e\nLink: https://patch.msgid.link/20260731-drop_canxl_frames-v1-1-7387b70353b3@kernel.org\nCc: stable@kernel.org\nSigned-off-by: Marc Kleine-Budde \u003cmkl@pengutronix.de\u003e\n"
    },
    {
      "commit": "fe23bad2156f1d5f0df8ae4a79ee590b79efc13a",
      "tree": "e352bb0bff2c0bf38cf9f457d4fef176ca1289fb",
      "parents": [
        "847ec34ec2ad5a317f1aa254781dded9e7b5faa9"
      ],
      "author": {
        "name": "Guenter Roeck",
        "email": "linux@roeck-us.net",
        "time": "Sat Oct 31 09:22:24 2026 -0700"
      },
      "committer": {
        "name": "Guenter Roeck",
        "email": "linux@roeck-us.net",
        "time": "Tue Nov 03 09:40:35 2026 -0800"
      },
      "message": "hwmon: (acpi_power_meter) Check for 32-bit and 64-bit unknown ACPI values\n\nAccording to the ACPI specification (Section 10.4), ACPI Power Meter\nobjects (_PMC capability fields, _PMM, _GHL, _PAI) report unknown or\nunavailable integer values using an integer with all bits set, which can\nbe either U32_MAX (0xffffffff) or U64_MAX (0xffffffffffffffff) depending\non the DSDT revision.\n\nCurrently, only hwmon_power_average checks both 32-bit and 64-bit\nunknown sentinels:\n- power1_cap_hyst_show() only compares res-\u003ecaps.hysteresis against the\n  32-bit UNKNOWN_HYSTERESIS (0xffffffff), so a 64-bit U64_MAX sentinel\n  bypasses the check, overflows when multiplied by 1000, and emits a\n  bogus number instead of \"unknown\".\n- power1_accuracy_show() does not check for unknown sentinels at all,\n  formatting 0xffffffff as \"4294967.295%\".\n- power_meter_read() does not check min_avg_interval, max_avg_interval,\n  avg_interval, min_cap, max_cap, or cap for unknown sentinels, exposing\n  scaled or overflowed values (or negative values when cast to signed\n  long) to userspace instead of returning -ENODATA.\n- get_power_alarm_state() does not check whether resource-\u003ecap is\n  unknown before comparing resource-\u003epower \u003e resource-\u003ecap.\n- update_meter() passes an unknown caps.sampling_time directly to\n  msecs_to_jiffies(), caching sensor readings for weeks on 64-bit builds.\n\nIntroduce acpi_power_meter_is_unknown() to check for both U32_MAX and\nU64_MAX, and use it across sysfs attribute handlers and meter updates:\n- Return -ENODATA in power_meter_read() when numeric power, interval, or\n  cap attributes report an unknown value.\n- Emit \"unknown\" in power1_cap_hyst_show() and power1_accuracy_show()\n  when hysteresis or accuracy is unknown.\n- Avoid comparing against an unknown cap in get_power_alarm_state(),\n  returning 0 (no alarm, no error) unless a hardware capping\n  notification was latched.\n- Skip the sampling_time cache window in update_meter() when\n  sampling_time is unknown.\n\nReported-by: Sashiko \u003csashiko-bot@kernel.org\u003e\nFixes: de584afa5e18 (\"hwmon driver for ACPI 4.0 power meters\")\nSigned-off-by: Guenter Roeck \u003clinux@roeck-us.net\u003e\n"
    }
  ],
  "next": "847ec34ec2ad5a317f1aa254781dded9e7b5faa9"
}
