Adds Patch2013 backporting linux-6.12.y stable commit 591f1ac21742
("af_unix: Set gc_in_progress to true in unix_gc()."), the 6.12 backport
of mainline d82ba05263c6 by Kuniyuki Iwashima.
unix_schedule_gc()/wait_for_unix_gc() only set gc_in_progress before
queueing the GC work, so a second schedule racing an in-flight unix_gc()
could leave gc_in_progress false while GC is still running. unix_peek_fpl()
relies on that flag to avoid confusing GC via MSG_PEEK. The fix sets
gc_in_progress inside __unix_gc() itself.
Verified with --fuzz=0 against both the CentOS Stream 10
kernel-6.12.0-211.el10 tag and the extracted 6.12.0-211.34.1.el10_2 tree:
single hunk in net/unix/garbage.c, no fuzz (offset only), and the WRITE_ONCE
is not already present in __unix_gc(). No overlap with the other patches in
this config, which touch arch/x86/kvm, drivers/scsi, drivers/message/fusion,
drivers/net/ethernet/google and fs/btrfs packaging only.
Drops the previous Patch2013 (CVE-2026-64561, KVM: x86: check for
invalid/obsolete root after making MMU pages available), which was sourced
from the still-Draft CentOS Stream 10 MR 3068; the 2013 slot is reused.
Taken verbatim from CentOS Stream 10 merge request 3068, which cherry-picks
upstream commit 2abd5287f083 ("KVM: x86: Check for invalid/obsolete root
*after* making MMU pages available") by Sean Christopherson and Paolo
Bonzini.
If reclaiming shadow pages zaps an in-use root, KVM would go on to map
memory into a root already marked invalid. Child shadow pages inherit
their parent's role, so any children created during the map/fetch land on
the list of active MMU pages while flagged invalid, breaking the invariant
introduced in 5.9 that invalid pages are never on that list. The fix moves
the is_page_fault_stale() check to after make_mmu_pages_available().
Applies with --fuzz=0 against arch/x86/kvm/mmu/{mmu.c,paging_tmpl.h}, no
fuzz and no offsets. Verified against the centos-stream-10 main branch: the
el10_2 z-stream tree this kernel is built from (6.12.0-211.38.1.el10_2) is
not published as a branch or tag, but both hunks sit in direct_page_fault()
and FNAME(page_fault)(), which are unchanged across 6.12 z-streams.
Note that MR 3068 is still a Draft upstream. If Red Hat revises it before
merge, this patch needs to be re-synced.
JIRA: RHEL-224013
Add two upstream commits for the Google gVNIC (gve) driver:
07993df56091 gve: Update QPL page registration logic
a2f19184014f gve: Enable reading max ring size from the device in
DQO-QPL mode
Patches are taken as-is from rpms/kernel commit b4decc5e6c1b, where they
were already verified on the GCP branch. 07993df56091 needed a backport:
this 6.12 based kernel predates the split of gve_buffer_mgmt_dqo.c out
of gve_rx_dqo.c and the rename of the RX alloc cfg queue config field.
Those adjustments are documented in the patch header. a2f19184014f is
unchanged from upstream.
Both patches apply with --fuzz=0 on top of the AlmaLinux 10 kernel
6.12.0-211.38.1.el10_2 source, and the resulting driver builds clean,
including with W=1, against kernel-devel-6.12.0-211.38.1.el10_2.
Fixed three replace actions that broke when upstream added new Nvidia certs (SOURCE107/108), changed the SBAT suffix mechanism from shell variables to RPM macros, and already enabled Btrfs in several
