[AUTOPATCHER-kernel] Kernel upgrade to version 6.6.101.2 - branch 3.0-dev

[CBL-Mariner-Bot]

[AUTOPATCHER-kernel] Kernel upgrade to version 6.6.101.2 - branch 3.0-dev
Upgrade pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=904212&view=results

buddy build kernel,kernel-headers,hyperv-daemons,kernel,kernel-64k -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=904233&view=results

buddy build kernel-ipe -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=904320&view=results

[CBL-Mariner-Bot]

🚨 PR Check Failed - Critical Issues Found

Found 3 critical/error issue(s) that must be fixed.

🔍 Critical Issues Detected:

1. Missing Patch File (ERROR)
   • Patch file '0001-add-mstflint-kernel-%{mstflintver}.patch' is referenced in the spec but not found in the directory
   • 💡 Fix: Add the missing patch file or update the Patch reference
2. Missing Patch File (ERROR)
   • Patch file '0001-add-mstflint-kernel-%{mstflintver}.patch' is referenced in the spec but not found in the directory
   • 💡 Fix: Add the missing patch file or update the Patch reference
3. Missing Patch File (ERROR)
   • Patch file '0001-add-mstflint-kernel-%{mstflintver}.patch' is referenced in the spec but not found in the directory
   • 💡 Fix: Add the missing patch file or update the Patch reference

🤖 AI Analysis Summary:

Brief Analysis: The spec file changes upgrade the kernel version consistently and adjust some configuration options (for example, switching CONFIG_MULTIPLEXER from module to built‐in). The only patch file is the mstflint driver patch, and its file (“0001-add-mstflint-kernel-4.28.0.patch”) is present.

Critical Issues Found: No critical or error‐level security issues were identified. No explicit CVE patches in “CVE-YYYY-XXXXX.patch” format are referenced, so nothing is missing or mis‐named.

Recommended Actions:
• Ensure that any future security patches follow the CVE-YYYY-XXXXX naming pattern and are properly referenced in the spec.
• Verify that autosetup (%autosetup -p1) appropriately applies all patches.
• Expand changelog entries for CVE fixes with clear attribution and upstream reference if such patches are added in subsequent updates.

---

📋 For detailed analysis and recommendations, check the Azure DevOps pipeline logs.