-
Notifications
You must be signed in to change notification settings - Fork 571
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bphilip/refactor version entangle check add release number #12817
Bphilip/refactor version entangle check add release number #12817
Conversation
770903c
to
892aab0
Compare
892aab0
to
26bff49
Compare
if verbose: | ||
print(f"Processing group: {group}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion: instead of repeating if verbose:
what do you think about creating a wrapper print_verbose
function?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small suggestion but looks good to me.
(['sdkver'], sdkver_matching_groups, {}), | ||
(['epoch', 'version', 'release'], version_release_matching_groups, {}), | ||
(['epoch', 'version'], version_matching_groups, {}), | ||
(['last-known-kernel'], oot_kmodule_matching_groups, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that I look at this again, can't I just pass only { tag: value } instead of a tag array and a tag: value dict? Hmm..
…12819) Co-authored-by: corvus-callidus <108946721+corvus-callidus@users.noreply.github.com>
This reverts commit 7cdbd37.
Adding slang-devel to kernel spec, enabling perf tui Perf's Makefile has a slang-devel check, which enables tui when slang is detected. (https://github.com/microsoft/CBL-Mariner-Linux-Kernel/blob/rolling-lts/mariner-3/6.6.78.1/tools/perf/Makefile.config#L765). Adding this package at built time will allow perf --tui support Co-authored-by: Andy Zaugg <azaugg@linkedin.com>
This reverts commit 389af4a.
…High] & CVE-2024-28180 CVE-2025-27144 [Medium] - branch 3.0-dev (#12875) Co-authored-by: Kanishk Bansal <103916909+Kanishk-Bansal@users.noreply.github.com>
… to 24.1.6 to fix CVE-2025-26594, CVE-2025-26595, CVE-2025-26596, CVE-2025-26597, CVE-2025-26598, CVE-2025-26599, CVE-2025-26600, CVE-2025-26601[High] - branch 3.0-dev (#12876)
…E-2025-27423 [High] - branch 3.0-dev (#12877)
Signed-off-by: Chris Co <chrco@microsoft.com>
License file got desynced due to 0de902e This change restores the LICENSES-MAP.md file. Signed-off-by: Chris Co <chrco@microsoft.com>
Starting in kernel v6.6.76, our automated testing encountered failures on specific bare-metal systems where, after a kernel panic, sometimes the kernel's panic message was not seen in the system's IPMI SEL. After bisecting the changes between v6.6.75 to v6.6.76, we isolated the offending commit to: serial: 8250: Adjust the timeout for FIFO mode To restore functionality, revert the offending commit. We will continue investigating the issue separately. Apply to both kernel and kernel-64k. Signed-off-by: Chris Co <chrco@microsoft.com>
Include new subpackages to access the official azure linux cloud-native package repository and preview package repository on packages.microsoft.com. Signed-off-by: Chris Co <chrco@microsoft.com>
Superseded by #12910 |
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-static
subpackages, etc.) have had theirRelease
tag incremented../cgmanifest.json
,./toolkit/scripts/toolchain/cgmanifest.json
,.github/workflows/cgmanifest.json
)./LICENSES-AND-NOTICES/SPECS/data/licenses.json
,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md
,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON
)*.signatures.json
filessudo make go-tidy-all
andsudo make go-test-coverage
passSummary
What does the PR accomplish, why was it needed?
MOFED and associated kernel modules did not include kernel minor version in the entangle check. check_entangle script did not provide enough details when it failed. Zeroing in on the exact mis-match needed additional effort. Added a unit test to make sure the script was indeed doing everything as expected.
There was some refactoring done to the script to make the workflow more compact.
Change Log
Does this affect the toolchain?
YES/NO
NO
Associated issues
Links to CVEs
Test Methodology