Review Results

Comment

The change only bumps pkgver in .SRCINFO from 7.2.pf1 to 7.2.pf2. No sources, checksums, build steps, install scripts, or permissions are altered in this diff, so there is no direct security impact visible here. Risk is minimal and limited to metadata/version tracking.

@@ -1,6 +1,6 @@
 pkgbase = linux-pf
 	pkgdesc = pf-kernel
-	pkgver = 7.2.pf1
+	pkgver = 7.2.pf2
 	pkgrel = 1
 	url = https://pfkernel.natalenko.name
 	arch = x86_64

Comment

Risk is low. This .SRCINFO-only change updates the package version and pins the source tarball to a different upstream commit on the same official Codeberg repository, with the corresponding b2sums updated. There are no new sources, no build-script changes, no install scripts, and no signs of network fetches or privilege-related behavior introduced by this diff. The main security consideration is simply that the package now tracks a newer upstream kernel snapshot, but the change itself does not add suspicious functionality.

@@ -26,10 +26,10 @@ pkgbase = linux-pf
 	makedepends = zstd
 	options = !debug
 	options = !strip
-	source = https://codeberg.org/pf-kernel/linux/archive/cd3c1bdc841c7a49ccb424e6b9920abdb633da75.tar.gz
+	source = https://codeberg.org/pf-kernel/linux/archive/e9705a97e2f4a4c595dc7da6e111874d9726ede5.tar.gz
 	source = config
 	b2sums = SKIP
-	b2sums = 7e68a183a4974de797cf43f03f0f621363aa69a5a6c6030980d7153777170892e0f5a054f900274d88be56412790eb4ec7c8fdec4cf9d5da066971442ec01555
+	b2sums = eb41395e84a7c75d07039d11dbfc99759328ba05e48941dc3013db0e2dceb51038a71c29d84f260c15ab1d7aea7ed027ec81235938c2073f8f1890b08f51d66e
 
 pkgname = linux-pf
 	pkgdesc = The pf-kernel and modules

Comment

Risk score 0. The change only updates the pinned upstream kernel revision from 7.2.pf1 to 7.2.pf2, refreshes the corresponding b2 checksum, and moves a log message inside an existing CONFIG_RUST conditional. The source remains an HTTPS tarball from the upstream Codeberg project, there are no new build-time downloads, scripts, privilege changes, or packaging/persistence behaviors introduced by this diff.

@@ -3,8 +3,8 @@
 pkgbase="linux-pf"
 _suffix=""
 pkgname=(${pkgbase}${_suffix} ${pkgbase}-headers${_suffix})
-_rev=cd3c1bdc841c7a49ccb424e6b9920abdb633da75
-pkgver=7.2.pf1
+_rev=e9705a97e2f4a4c595dc7da6e111874d9726ede5
+pkgver=7.2.pf2
 pkgrel=1
 pkgdesc="pf-kernel"
 arch=(x86_64)

Comment

The change is low risk. It updates the pinned upstream commit and corresponding b2 checksum for the kernel source tarball, which is the expected way to move to a new release. The only logic change is moving the Rust-file install message inside the CONFIG_RUST conditional; this does not alter what gets installed or introduce new execution, network, privilege, or persistence behavior. No suspicious sources, scripts, or packaging actions were added.

@@ -15,7 +15,7 @@ options=(!debug !strip)
 source=(https://codeberg.org/pf-kernel/linux/archive/${_rev}.tar.gz
 		config)
 b2sums=(SKIP
-		'7e68a183a4974de797cf43f03f0f621363aa69a5a6c6030980d7153777170892e0f5a054f900274d88be56412790eb4ec7c8fdec4cf9d5da066971442ec01555')
+		'eb41395e84a7c75d07039d11dbfc99759328ba05e48941dc3013db0e2dceb51038a71c29d84f260c15ab1d7aea7ed027ec81235938c2073f8f1890b08f51d66e')
 
 export KBUILD_BUILD_HOST=archlinux
 export KBUILD_BUILD_USER=${pkgbase}

Comment

The change is a minor control-flow adjustment in PKGBUILD: the Rust file installation message is moved inside the CONFIG_RUST conditional so it only prints when Rust artifacts are actually present. It does not alter what gets built or installed, does not introduce new sources, commands, network access, privilege changes, or packaging destinations, and has no security impact beyond log verbosity/accuracy.

@@ -125,8 +125,8 @@ _package-headers() {
 	echo "Installing Kconfig files..."
 	find . -name 'Kconfig*' -exec install -Dm644 {} "${builddir}/{}" \;
 
-	echo "Installing Rust files..."
 	if [[ $(scripts/config -s CONFIG_RUST) = y ]]; then
+		echo "Installing Rust files..."
 		install -Dt "${builddir}"/rust -m644 rust/*.rmeta
 		install -Dt "${builddir}"/rust rust/*.so
 	fi

Comment

The change is a one-line kernel config version bump from pf1 to pf2 in the generated config header. No build logic, source URLs, install scripts, permissions, or runtime behavior are altered, and there are no signs of added network access, privilege escalation, or persistence mechanisms in this diff hunk. Risk is therefore negligible.

@@ -1,6 +1,6 @@
 #
 # Automatically generated file; DO NOT EDIT.
-# Linux/x86 7.2.0-pf1 Kernel Configuration
+# Linux/x86 7.2.0-pf2 Kernel Configuration
 #
 CONFIG_CC_VERSION_TEXT="gcc (GCC) 16.1.1 20260625"
 CONFIG_CC_IS_GCC=y

Comment

The change is a one-line bump of CONFIG_RUSTC_VERSION from 109700 to 109701 in the kernel config metadata. This is a narrow version pin update with no evidence of added build-time execution, network access, privilege changes, or packaging behavior changes. I did not find any security-relevant red flags in this diff hunk alone.

@@ -11,7 +11,7 @@ CONFIG_AS_VERSION=24601
 CONFIG_LD_IS_BFD=y
 CONFIG_LD_VERSION=24601
 CONFIG_LLD_VERSION=0
-CONFIG_RUSTC_VERSION=109700
+CONFIG_RUSTC_VERSION=109701
 CONFIG_RUST_IS_AVAILABLE=y
 CONFIG_RUSTC_LLVM_VERSION=220108
 CONFIG_RUSTC_LLVM_MAJOR_VERSION=22

Comment

The change only updates the embedded Rust compiler version string in the kernel config from 1.97.0 to 1.97.1. This is metadata used for build/version checks, not an executable code path, and it does not introduce new sources, network access, privilege changes, or packaging behavior. No security concern is evident from this diff alone.

@@ -344,7 +344,7 @@ CONFIG_PERF_EVENTS=y
 CONFIG_SYSTEM_DATA_VERIFICATION=y
 CONFIG_PROFILING=y
 CONFIG_RUST=y
-CONFIG_RUSTC_VERSION_TEXT="rustc 1.97.0 (2d8144b78 2026-07-07) (Arch Linux rust 1:1.97.0-1)"
+CONFIG_RUSTC_VERSION_TEXT="rustc 1.97.1 (8bab26f4f 2026-07-14) (Arch Linux rust 1:1.97.1-1)"
 CONFIG_BINDGEN_VERSION_TEXT="bindgen 0.72.1"
 CONFIG_TRACEPOINTS=y
 

Comment

The change only flips CONFIG_SND_SOC_ACPI_AMD_SDCA_QUIRKS from a module to built-in in the kernel config. This is a small functional packaging change with no evidence of network access, privilege escalation, persistence, or suspicious code execution. It affects how an upstream kernel quirk driver is linked, but does not introduce new sources, scripts, or install-time behavior. Risk is therefore very low.

@@ -7764,7 +7764,7 @@ CONFIG_SND_SOC_AMD_YC_MACH=m
 CONFIG_SND_AMD_ACP_CONFIG=m
 CONFIG_SND_SOC_AMD_ACP_COMMON=m
 CONFIG_SND_SOC_ACPI_AMD_MATCH=m
-CONFIG_SND_SOC_ACPI_AMD_SDCA_QUIRKS=m
+CONFIG_SND_SOC_ACPI_AMD_SDCA_QUIRKS=y
 CONFIG_SND_SOC_AMD_ACP_PDM=m
 CONFIG_SND_SOC_AMD_ACP_LEGACY_COMMON=m
 CONFIG_SND_SOC_AMD_ACP_I2S=m