DLPX-96594 fix linux-kernel updates to 6.17: export tcp symbols needed by connstat#56
Draft
DLPX-96594 fix linux-kernel updates to 6.17: export tcp symbols needed by connstat#56
Conversation
Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
…el-versions (main/d2025.10.13) BugLink: https://bugs.launchpad.net/bugs/1786013 Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
All rust compiler package have to be at least version 1.82 to allow enabling rust for amd64 and arm64. Change the make rules file and also the dependencies in the control file. Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Create a new baseline config with the differences between the old HWE kernel and the new one. Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Starting with 25.10/questing the generic kernel no longer splits modules into linux-modules and linux-modules-extra. This was done by changing the setup but also ripped out all generic code to produce modules-extra. This is a problem for HWE kernels because those should match the packaging of the GA kernel of their target series. This patch reverts the generic changes made in questing by: 168ea3c ("UBUNTU: [Packaging] Drop support for modules-extra") Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Sync the inclusion list to the last state of the parent kernel before it got removed. Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Some options changed to be arm64 only. This causes some drivers to be no longer available for armhf. This results in warnings when running updateconfigs. Should be fixed in the parent kernel but for now add the modifications to the HWE kernel. Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Turn back on production of linux-modules-extra on those arches which had them on in the noble series. Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Bump the versions used by local mangle to the ones pre-set by setting up the new HWE kernel. Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
BugLink: https://bugs.launchpad.net/bugs/2129944 Properties: no-test-build Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
…l in SRCPKGNAME-tools-$(abi_release) BugLink: https://bugs.launchpad.net/bugs/2117147 The tools perf and bpftool are not built on Noble HWE 6.14 kernels because the kernel packaging rules introduced in Plucky on which Noble HWE 6.14 kernels are based expect perf and bpftool to be split out into their own packages linux-perf and bpftool, which are only built by the primary kernel. Resolve this by adding a flag `do_tools_noble_hwe` to return to building perf and bpftool into the SRCPKGNAME-tools-$(abi_release) package, which are exec'd by the wrapper scripts provided by the linux-tools-common package produced by the Noble primary kernel. Signed-off-by: Jacob Martin <jacob.martin@canonical.com> [smb: Imported from hwe-6.14] Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
BugLink: https://bugs.launchpad.net/bugs/2117147 Enable do_tools_noble_hwe to build bpftool and perf tools into the linux-hwe-6.17-tools-$(abi_release) package so they can be used by the linux-tools-common wrapper scripts in Noble. Signed-off-by: Jacob Martin <jacob.martin@canonical.com> [smb: Also added to mangle script to make the change persist] [smb: Imported from hwe-6.14] Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
BugLink: https://bugs.launchpad.net/bugs/2131154 This reverts commit 14a0781 as this would require newer kexec tools in Noble. This was found with backported nvidia kernels but also affects the HWE kernel. Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
We reverted that change from the parent because it causes issues in the Noble context. This should happen for each crank now. Pre-syncing to see that it works as intended. Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
The changes made in Questing to enable cross compiling the tools do not work with the current test compile infrastrucure. This appears to be an issue with the package resolver used. So at least for the time being lets change back to allow cross compiling only for the kernel and not the tools. Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
BugLink: https://bugs.launchpad.net/bugs/2132312 For some odd reason trying to pass an "(int) * (size_t)" to malloc is throwing an exeption in the argument checking for malloc. This only happens on s390x and ppc64el. Until properly understood we are hacking around this by casting the return value of sizeof() to an unsigned int. Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
BugLink: https://bugs.launchpad.net/bugs/1786013 Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
BugLink: https://bugs.launchpad.net/bugs/1786013 Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
An upstream stable change in the parent questing:linux kernel caused CONFIG_QCS_DISPCC_615 to select CONFIG_QCS_GCC (which is valid only for arm64). That made QCS_GCC_615 to come back as 'm' for armhf at least for the annotations (updateconfigs would again emit warnings about unreachable elements). So explicitly enable QCS_DISPCC_615 only for arm64 to prevent this. Ignore: yes Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
BugLink: https://bugs.launchpad.net/bugs/2137847 Properties: no-test-build Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
…el-versions (main/2026.01.12) BugLink: https://bugs.launchpad.net/bugs/1786013 Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
This is a placeholder commit to separate the Ubuntu kernel source and our patches. Used by kernel_merge_with_upstream() in the linux-pkg repo.
…operly started (#14)
delphix-devops-bot
force-pushed
the
develop
branch
from
4d5103a to
5940cca
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Provide a clear description of the high-level problem you are trying to
solve. The problem statement should be written in terms of a specific
symptom that affects users or the business. The problem statement should
not be written in terms of the solution. If possible, include a minimal
reproducible example (MRE) with steps to reproduce, expected results,
and actual results.
Solution
Provide a clear description of the high-level solution you have chosen.
If there were other possible solutions that you considered and rejected,
mention those along with the corresponding reasoning. Do not describe
implementation details when writing about the solution; these should go
into the implementation section instead.
Testing Done
Provide a clear description of how this change was tested. At minimum
this should include proof that a computer has executed the changed
lines. Ideally this should include an automated test or an explanation
as to why this pull request has no tests.