lttng-modules: update to 2.11.6
PATCH 1/3 lttng-modules: update to 2.11.6
Update to latest available.
---
.../{lttng-modules_2.11.2.bb => lttng-modules_2.11.6.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-kernel/lttng/{lttng-modules_2.11.2.bb => lttng-modules_2.11.6.bb} (92%)meta/recipes-kernel/lttng/lttng-modules_2.11.6.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.11.2.bb +2 -2
@@ -13,8 +13,8 @@ SRC_URI = "https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2 \ file://BUILD_RUNTIME_BUG_ON-vs-gcc7.patch \ " -SRC_URI[md5sum] = "2e3bc8cfb264fa13f374618b46f170e7" -SRC_URI[sha256sum] = "8a42240813b8fd1d001835cd6f5ec687f7d7f3b26070d4e21604c35a51a6441d" +SRC_URI[md5sum] = "8ef09fdfcdec669d33f7fc1c1c80f2c4" +SRC_URI[sha256sum] = "23372811cdcd2ac28ba8c9d09484ed5f9238cfbd0043f8c663ff3875ba9c8566" export INSTALL_MOD_DIR="kernel/lttng-modules"
Signature · 1 line
2.28.0
PATCH 2/3 lttng-tools: update to 2.11.5
Update to latest available.
---
.../lttng/{lttng-tools_2.11.2.bb => lttng-tools_2.11.5.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-kernel/lttng/{lttng-tools_2.11.2.bb => lttng-tools_2.11.5.bb} (98%)meta/recipes-kernel/lttng/lttng-tools_2.11.5.bb renamed from meta/recipes-kernel/lttng/lttng-tools_2.11.2.bb +2 -2
@@ -36,8 +36,8 @@ SRC_URI = "https://lttng.org/files/lttng-tools/lttng-tools-${PV}.tar.bz2 \ file://0001-tests-regression-disable-the-tools-live-tests.patch \ " -SRC_URI[md5sum] = "68ed78f7fa4235477ea577e48b3cd245" -SRC_URI[sha256sum] = "936477305b25f65c5dd22db9161287d30a309ce868b6180857b1fd1fb5e6a56b" +SRC_URI[md5sum] = "4bd983891f642d4139f80251f209ef81" +SRC_URI[sha256sum] = "38167b49e4d1bf78fdd5c3156d411123713fd8f04b0067d4b1cd03742d0edfaa" inherit autotools ptest pkgconfig useradd python3-dir manpages systemd
Signature · 1 line
2.28.0
PATCH 3/3 lttng-ust: update to 2.11.1
In reply to Marek VasutUpdate to latest available.
---
.../lttng/{lttng-ust_2.11.1.bb => lttng-ust_2.11.2.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-kernel/lttng/{lttng-ust_2.11.1.bb => lttng-ust_2.11.2.bb} (93%)meta/recipes-kernel/lttng/lttng-ust_2.11.2.bb renamed from meta/recipes-kernel/lttng/lttng-ust_2.11.1.bb +2 -2
@@ -31,8 +31,8 @@ SRC_URI = "https://lttng.org/files/lttng-ust/lttng-ust-${PV}.tar.bz2 \ file://0001-python-lttngust-Makefile.am-Add-install-lib-to-setup.patch \ " -SRC_URI[md5sum] = "7de04a8ff1f0a4effa09a42620ec4081" -SRC_URI[sha256sum] = "7fbab963d60741ffd4d8dd0a246f6cf168cdfe3b2385798bd90550f5f0bba869" +SRC_URI[md5sum] = "82556e4ab28c818c80db84296fc28bb3" +SRC_URI[sha256sum] = "6b481cec7fe748503c827319e3356137bceef4cce8adecbda3a94c6effcdd161" CVE_PRODUCT = "ust"
Signature · 1 line
2.28.0
Quoted 2 lines · Marek Vasut
Update to latest available.
Have you tested these patches with kernel versions 5.4.62+ ?
IIRC, Bruce said that the 2.11.x tree did not have the necessary patches to build with recent 5.4 kernels.
See his patch "lttng-modules: backport writeback.h changes from 2.12.x to fix kernel 5.4.62+"
Steve
Quoted 32 lines
Signed-off-by Marek Vasut <[email protected]>Cc Alexander Kanavin <[email protected]>Cc Richard Purdie <[email protected]>--- .../{lttng-modules_2.11.2.bb => lttng-modules_2.11.6.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-kernel/lttng/{lttng-modules_2.11.2.bb => lttng-modules_2.11.6.bb} (92%)meta/recipes-kernel/lttng/lttng-modules_2.11.6.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.11.2.bb +2
-3@@ -13,8 +13,8 @@ SRC_URI = "https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2 \ file://BUILD_RUNTIME_BUG_ON-vs-gcc7.patch \ " -SRC_URI[md5sum] = "2e3bc8cfb264fa13f374618b46f170e7" -SRC_URI[sha256sum] = "8a42240813b8fd1d001835cd6f5ec687f7d7f3b26070d4e21604c35a51a6441d" +SRC_URI[md5sum] = "8ef09fdfcdec669d33f7fc1c1c80f2c4" +SRC_URI[sha256sum] = "23372811cdcd2ac28ba8c9d09484ed5f9238cfbd0043f8c663ff3875ba9c8566" export INSTALL_MOD_DIR="kernel/lttng-modules" --2.28.0
Quoted 10 lines · Steve Sakoman
Quoted 2 lines · Marek Vasut
Update to latest available.
Have you tested these patches with kernel versions 5.4.62+ ?
IIRC, Bruce said that the 2.11.x tree did not have the necessary patches to build with recent 5.4 kernels.
Since I did that backport to keep us moving, the lttng project has added commits to the 2.11.x branch.
I see changes to the right files in the commits, so it should be good with this update, but I haven't tested it myself.
Bruce
Quoted 42 lines
See his patch "lttng-modules: backport
writeback.hchanges from 2.12.x to fix kernel 5.4.62+"Steve
Quoted 32 lines
Signed-off-by Marek Vasut <[email protected]>Cc Alexander Kanavin <[email protected]>Cc Richard Purdie <[email protected]>--- .../{lttng-modules_2.11.2.bb => lttng-modules_2.11.6.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-kernel/lttng/{lttng-modules_2.11.2.bb => lttng-modules_2.11.6.bb} (92%)meta/recipes-kernel/lttng/lttng-modules_2.11.6.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.11.2.bb +2
-3@@ -13,8 +13,8 @@ SRC_URI = "https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2 \ file://BUILD_RUNTIME_BUG_ON-vs-gcc7.patch \ " -SRC_URI[md5sum] = "2e3bc8cfb264fa13f374618b46f170e7" -SRC_URI[sha256sum] = "8a42240813b8fd1d001835cd6f5ec687f7d7f3b26070d4e21604c35a51a6441d" +SRC_URI[md5sum] = "8ef09fdfcdec669d33f7fc1c1c80f2c4" +SRC_URI[sha256sum] = "23372811cdcd2ac28ba8c9d09484ed5f9238cfbd0043f8c663ff3875ba9c8566" export INSTALL_MOD_DIR="kernel/lttng-modules" --2.28.0
Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
Quoted 13 lines · Bruce Ashfield
Quoted 10 lines · Steve Sakoman
Quoted 2 lines · Marek Vasut
Update to latest available.
Have you tested these patches with kernel versions 5.4.62+ ?
IIRC, Bruce said that the 2.11.x tree did not have the necessary patches to build with recent 5.4 kernels.
Quoted 5 lines
Since I did that backport to keep us moving, the lttng project has added commits to the 2.11.x branch.
I see changes to the right files in the commits, so it should be good with this update, but I haven't tested it myself.
Thanks for the quick response. Given that info I'll pull in these patches and start testing.
Steve
Quoted 48 lines
Quoted 31 lines
See his patch "lttng-modules: backport
writeback.hchanges from 2.12.x to fix kernel 5.4.62+"Steve
Quoted 24 lines
Signed-off-by Marek Vasut <[email protected]>Cc Alexander Kanavin <[email protected]>Cc Richard Purdie <[email protected]>--- .../{lttng-modules_2.11.2.bb => lttng-modules_2.11.6.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-kernel/lttng/{lttng-modules_2.11.2.bb => lttng-modules_2.11.6.bb} (92%)meta/recipes-kernel/lttng/lttng-modules_2.11.6.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.11.2.bb +2
-2@@ -13,8 +13,8 @@ SRC_URI = "https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2 \ file://BUILD_RUNTIME_BUG_ON-vs-gcc7.patch \ " -SRC_URI[md5sum] = "2e3bc8cfb264fa13f374618b46f170e7" -SRC_URI[sha256sum] = "8a42240813b8fd1d001835cd6f5ec687f7d7f3b26070d4e21604c35a51a6441d" +SRC_URI[md5sum] = "8ef09fdfcdec669d33f7fc1c1c80f2c4" +SRC_URI[sha256sum] = "23372811cdcd2ac28ba8c9d09484ed5f9238cfbd0043f8c663ff3875ba9c8566"Quoted 11 lines
Quoted 8 lines
meta/recipes-kernel/lttng/lttng-modules_2.11.6.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.11.2.bb +0
-1export INSTALL_MOD_DIR="kernel/lttng-modules" --2.28.0
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
Quoted 15 lines · Steve Sakoman
Quoted 13 lines · Bruce Ashfield
Quoted 10 lines · Steve Sakoman
Quoted 2 lines · Marek Vasut
Update to latest available.
Have you tested these patches with kernel versions 5.4.62+ ?
IIRC, Bruce said that the 2.11.x tree did not have the necessary patches to build with recent 5.4 kernels.
Quoted 8 lines
Quoted 5 lines
Since I did that backport to keep us moving, the lttng project has added commits to the 2.11.x branch.
I see changes to the right files in the commits, so it should be good with this update, but I haven't tested it myself.
Thanks for the quick response. Given that info I'll pull in these patches and start testing.
That being said. I'd expect that we should drop the backport that I did, but I don't see that in this commit. So that is worth checking into ..
Bruce
Quoted 51 lines
Steve
Quoted 48 lines
Quoted 31 lines
See his patch "lttng-modules: backport
writeback.hchanges from 2.12.x to fix kernel 5.4.62+"Steve
Quoted 24 lines
Signed-off-by Marek Vasut <[email protected]>Cc Alexander Kanavin <[email protected]>Cc Richard Purdie <[email protected]>--- .../{lttng-modules_2.11.2.bb => lttng-modules_2.11.6.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-kernel/lttng/{lttng-modules_2.11.2.bb => lttng-modules_2.11.6.bb} (92%)meta/recipes-kernel/lttng/lttng-modules_2.11.6.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.11.2.bb +2
-2@@ -13,8 +13,8 @@ SRC_URI = "https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2 \ file://BUILD_RUNTIME_BUG_ON-vs-gcc7.patch \ " -SRC_URI[md5sum] = "2e3bc8cfb264fa13f374618b46f170e7" -SRC_URI[sha256sum] = "8a42240813b8fd1d001835cd6f5ec687f7d7f3b26070d4e21604c35a51a6441d" +SRC_URI[md5sum] = "8ef09fdfcdec669d33f7fc1c1c80f2c4" +SRC_URI[sha256sum] = "23372811cdcd2ac28ba8c9d09484ed5f9238cfbd0043f8c663ff3875ba9c8566"Quoted 11 lines
Quoted 8 lines
meta/recipes-kernel/lttng/lttng-modules_2.11.6.bb renamed from meta/recipes-kernel/lttng/lttng-modules_2.11.2.bb +0
-1export INSTALL_MOD_DIR="kernel/lttng-modules" --2.28.0
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
Quoted 22 lines · Bruce Ashfield
Quoted 21 lines · Steve Sakoman
Quoted 18 lines · Bruce Ashfield
Quoted 10 lines · Steve Sakoman
Quoted 2 lines · Marek Vasut
Update to latest available.
Have you tested these patches with kernel versions 5.4.62+ ?
IIRC, Bruce said that the 2.11.x tree did not have the necessary patches to build with recent 5.4 kernels.
Since I did that backport to keep us moving, the lttng project has added commits to the 2.11.x branch.
I see changes to the right files in the commits, so it should be good with this update, but I haven't tested it myself.
Quoted 6 lines
Quoted 2 lines
Thanks for the quick response. Given that info I'll pull in these patches and start testing.
That being said. I'd expect that we should drop the backport that I did, but I don't see that in this commit. So that is worth checking into ..
I ran into the build issue with 5.4.69, so that's how these patches came to be. It could be that I didn't build the tools and ust if they are not built as part of the "standard" build run.
Quoted 27 lines · Marek Vasut
Quoted 25 lines · Bruce Ashfield
Quoted 23 lines · Steve Sakoman
Quoted 13 lines · Bruce Ashfield
Quoted 10 lines · Steve Sakoman
Quoted 2 lines · Marek Vasut
Update to latest available.
Have you tested these patches with kernel versions 5.4.62+ ?
IIRC, Bruce said that the 2.11.x tree did not have the necessary patches to build with recent 5.4 kernels.
Quoted 5 lines
Since I did that backport to keep us moving, the lttng project has added commits to the 2.11.x branch.
I see changes to the right files in the commits, so it should be good with this update, but I haven't tested it myself.
Thanks for the quick response. Given that info I'll pull in these patches and start testing.
Quoted 7 lines
Quoted 3 lines
That being said. I'd expect that we should drop the backport that I did, but I don't see that in this commit. So that is worth checking into ..
I ran into the build issue with 5.4.69, so that's how these patches came to be. It could be that I didn't build the tools and ust if they are not built as part of the "standard" build run.
No worries, I'll give the patches a thorough test. I do however need you to redo this patch so that it will apply cleanly on the current dunfell head (i.e. drop Bruce's backport)
Your other 3 patches seem fine.
Steve
Quoted 36 lines · Steve Sakoman
Quoted 27 lines · Marek Vasut
Quoted 25 lines · Bruce Ashfield
Quoted 23 lines · Steve Sakoman
Quoted 13 lines · Bruce Ashfield
Quoted 10 lines · Steve Sakoman
Quoted 2 lines · Marek Vasut
Update to latest available.
Have you tested these patches with kernel versions 5.4.62+ ?
IIRC, Bruce said that the 2.11.x tree did not have the necessary patches to build with recent 5.4 kernels.
Quoted 5 lines
Since I did that backport to keep us moving, the lttng project has added commits to the 2.11.x branch.
I see changes to the right files in the commits, so it should be good with this update, but I haven't tested it myself.
Thanks for the quick response. Given that info I'll pull in these patches and start testing.
Quoted 7 lines
Quoted 3 lines
That being said. I'd expect that we should drop the backport that I did, but I don't see that in this commit. So that is worth checking into ..
I ran into the build issue with 5.4.69, so that's how these patches came to be. It could be that I didn't build the tools and ust if they are not built as part of the "standard" build run.
Quoted 5 lines
No worries, I'll give the patches a thorough test. I do however need you to redo this patch so that it will apply cleanly on the current dunfell head (i.e. drop Bruce's backport)
Your other 3 patches seem fine.
Do you need me to repost it or can you fix it up yourself while at it ?
Quoted 38 lines · Marek Vasut
Quoted 36 lines · Steve Sakoman
Quoted 34 lines · Marek Vasut
Quoted 22 lines · Bruce Ashfield
Quoted 21 lines · Steve Sakoman
Quoted 18 lines · Bruce Ashfield
Quoted 10 lines · Steve Sakoman
Quoted 2 lines · Marek Vasut
Update to latest available.
Have you tested these patches with kernel versions 5.4.62+ ?
IIRC, Bruce said that the 2.11.x tree did not have the necessary patches to build with recent 5.4 kernels.
Since I did that backport to keep us moving, the lttng project has added commits to the 2.11.x branch.
I see changes to the right files in the commits, so it should be good with this update, but I haven't tested it myself.
Quoted 6 lines
Quoted 2 lines
Thanks for the quick response. Given that info I'll pull in these patches and start testing.
That being said. I'd expect that we should drop the backport that I did, but I don't see that in this commit. So that is worth checking into ..
I ran into the build issue with 5.4.69, so that's how these patches came to be. It could be that I didn't build the tools and ust if they are not built as part of the "standard" build run.
Quoted 7 lines
Quoted 5 lines
No worries, I'll give the patches a thorough test. I do however need you to redo this patch so that it will apply cleanly on the current dunfell head (i.e. drop Bruce's backport)
Your other 3 patches seem fine.
Do you need me to repost it or can you fix it up yourself while at it ?
I'm going to be out of the office for a few hours, so if you have the time to repost it would be much appreciated.
If not, I'll do a fixup when I return.
Steve