| Message ID | cover.1656616115.git.bruce.ashfield@gmail.com |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
On Thu, 2022-06-30 at 15:16 -0400, bruce.ashfield@gmail.com wrote: > With conference travel and issues with meta-virtualization, I've been > behind in sending this out .. but I have been queueing changes, I just > wanted to be around in case something breaks. > > Here are the -stable updates and the start of my efforts to bring > 5.19 in as the new reference kernel for the fall release. > > lttng-modules needed it's normal tweaks to work against the 5.19 source, > but otherwise, nothing significant has popped up. I have other parts > of that uprev under test (libc-headers, systemtap, etc). Thanks Bruce! Unfortunately there was one issue the autobuilder found, a reproducibility issue in perf: http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220630-53gdlqxv/packages/diff-html/ I've not looked into it other than looking at the above link but it seems some python paths are creeping into the binaries. Cheers, Richard
On Fri, 2022-07-01 at 10:59 +0100, Richard Purdie via lists.openembedded.org wrote: > On Thu, 2022-06-30 at 15:16 -0400, bruce.ashfield@gmail.com wrote: > > With conference travel and issues with meta-virtualization, I've been > > behind in sending this out .. but I have been queueing changes, I just > > wanted to be around in case something breaks. > > > > Here are the -stable updates and the start of my efforts to bring > > 5.19 in as the new reference kernel for the fall release. > > > > lttng-modules needed it's normal tweaks to work against the 5.19 source, > > but otherwise, nothing significant has popped up. I have other parts > > of that uprev under test (libc-headers, systemtap, etc). > > Thanks Bruce! > > Unfortunately there was one issue the autobuilder found, a > reproducibility issue in perf: > > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220630-53gdlqxv/packages/diff-html/ > > I've not looked into it other than looking at the above link but it > seems some python paths are creeping into the binaries. This looked a little suspicious to me: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=18f2967418d031a390a5befe855dd0faa8af70b9 Cheers, Richard
On Fri, 2022-07-01 at 13:52 +0100, Richard Purdie via lists.openembedded.org wrote: > On Fri, 2022-07-01 at 10:59 +0100, Richard Purdie via > lists.openembedded.org wrote: > > On Thu, 2022-06-30 at 15:16 -0400, bruce.ashfield@gmail.com wrote: > > > With conference travel and issues with meta-virtualization, I've been > > > behind in sending this out .. but I have been queueing changes, I just > > > wanted to be around in case something breaks. > > > > > > Here are the -stable updates and the start of my efforts to bring > > > 5.19 in as the new reference kernel for the fall release. > > > > > > lttng-modules needed it's normal tweaks to work against the 5.19 source, > > > but otherwise, nothing significant has popped up. I have other parts > > > of that uprev under test (libc-headers, systemtap, etc). > > > > Thanks Bruce! > > > > Unfortunately there was one issue the autobuilder found, a > > reproducibility issue in perf: > > > > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220630-53gdlqxv/packages/diff-html/ > > > > I've not looked into it other than looking at the above link but it > > seems some python paths are creeping into the binaries. > > This looked a little suspicious to me: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=18f2967418d031a390a5befe855dd0faa8af70b9 Confirmed that it is this change. Not sure why but at least we have an idea of where the isssue is. I've also sent a patch to insane.bbclass to change WARN_QA such that we can detect this kind of issue much earlier in people's local builds. It may expose issues in other layers but those issues probably do need exposing at this point too... Cheers, Richard
On Fri, 2022-07-01 at 15:10 +0100, Richard Purdie via lists.openembedded.org wrote: > On Fri, 2022-07-01 at 13:52 +0100, Richard Purdie via > lists.openembedded.org wrote: > > On Fri, 2022-07-01 at 10:59 +0100, Richard Purdie via > > lists.openembedded.org wrote: > > > On Thu, 2022-06-30 at 15:16 -0400, bruce.ashfield@gmail.com wrote: > > > > With conference travel and issues with meta-virtualization, I've been > > > > behind in sending this out .. but I have been queueing changes, I just > > > > wanted to be around in case something breaks. > > > > > > > > Here are the -stable updates and the start of my efforts to bring > > > > 5.19 in as the new reference kernel for the fall release. > > > > > > > > lttng-modules needed it's normal tweaks to work against the 5.19 source, > > > > but otherwise, nothing significant has popped up. I have other parts > > > > of that uprev under test (libc-headers, systemtap, etc). > > > > > > Thanks Bruce! > > > > > > Unfortunately there was one issue the autobuilder found, a > > > reproducibility issue in perf: > > > > > > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220630-53gdlqxv/packages/diff-html/ > > > > > > I've not looked into it other than looking at the above link but it > > > seems some python paths are creeping into the binaries. > > > > This looked a little suspicious to me: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=18f2967418d031a390a5befe855dd0faa8af70b9 > > Confirmed that it is this change. Not sure why but at least we have an > idea of where the isssue is. > > I've also sent a patch to insane.bbclass to change WARN_QA such that we > can detect this kind of issue much earlier in people's local builds. It > may expose issues in other layers but those issues probably do need > exposing at this point too... This breaks: override PYTHON := $(call get-executable-or-default,PYTHON,$(subst -config,,$(PYTHON_AUTO))) as somehow PYTHON is expanded to a full path, yet: override PYTHON := $(call get-executable-or-default,PYTHON,$(PYTHON_AUTO)) this works and doesn't expand PYTHON. I have no idea why, it doesn't make sense. Cheers, Richard
On Fri, Jul 1, 2022 at 10:49 AM Richard Purdie <richard.purdie@linuxfoundation.org> wrote: > > On Fri, 2022-07-01 at 15:10 +0100, Richard Purdie via > lists.openembedded.org wrote: > > On Fri, 2022-07-01 at 13:52 +0100, Richard Purdie via > > lists.openembedded.org wrote: > > > On Fri, 2022-07-01 at 10:59 +0100, Richard Purdie via > > > lists.openembedded.org wrote: > > > > On Thu, 2022-06-30 at 15:16 -0400, bruce.ashfield@gmail.com wrote: > > > > > With conference travel and issues with meta-virtualization, I've been > > > > > behind in sending this out .. but I have been queueing changes, I just > > > > > wanted to be around in case something breaks. > > > > > > > > > > Here are the -stable updates and the start of my efforts to bring > > > > > 5.19 in as the new reference kernel for the fall release. > > > > > > > > > > lttng-modules needed it's normal tweaks to work against the 5.19 source, > > > > > but otherwise, nothing significant has popped up. I have other parts > > > > > of that uprev under test (libc-headers, systemtap, etc). > > > > > > > > Thanks Bruce! > > > > > > > > Unfortunately there was one issue the autobuilder found, a > > > > reproducibility issue in perf: > > > > > > > > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220630-53gdlqxv/packages/diff-html/ > > > > > > > > I've not looked into it other than looking at the above link but it > > > > seems some python paths are creeping into the binaries. > > > > > > This looked a little suspicious to me: > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=18f2967418d031a390a5befe855dd0faa8af70b9 > > > > Confirmed that it is this change. Not sure why but at least we have an > > idea of where the isssue is. > > > > I've also sent a patch to insane.bbclass to change WARN_QA such that we > > can detect this kind of issue much earlier in people's local builds. It > > may expose issues in other layers but those issues probably do need > > exposing at this point too... > > This breaks: > > override PYTHON := $(call get-executable-or-default,PYTHON,$(subst -config,,$(PYTHON_AUTO))) > > as somehow PYTHON is expanded to a full path, yet: > > override PYTHON := $(call get-executable-or-default,PYTHON,$(PYTHON_AUTO)) > > this works and doesn't expand PYTHON. I have no idea why, it doesn't > make sense. > urk. I'm off today for a Stat holiday (and Monday as well), but will poke at this throughout the weekend to try and come up with ideas first step, get geared up to test reproducibility locally, step 0, find my old notes on the subject :) Bruce > Cheers, > > Richard >
On Fri, 2022-07-01 at 10:57 -0400, Bruce Ashfield wrote: > On Fri, Jul 1, 2022 at 10:49 AM Richard Purdie > <richard.purdie@linuxfoundation.org> wrote: > > > > On Fri, 2022-07-01 at 15:10 +0100, Richard Purdie via > > lists.openembedded.org wrote: > > > On Fri, 2022-07-01 at 13:52 +0100, Richard Purdie via > > > lists.openembedded.org wrote: > > > > On Fri, 2022-07-01 at 10:59 +0100, Richard Purdie via > > > > lists.openembedded.org wrote: > > > > > On Thu, 2022-06-30 at 15:16 -0400, bruce.ashfield@gmail.com wrote: > > > > > > With conference travel and issues with meta-virtualization, I've been > > > > > > behind in sending this out .. but I have been queueing changes, I just > > > > > > wanted to be around in case something breaks. > > > > > > > > > > > > Here are the -stable updates and the start of my efforts to bring > > > > > > 5.19 in as the new reference kernel for the fall release. > > > > > > > > > > > > lttng-modules needed it's normal tweaks to work against the 5.19 source, > > > > > > but otherwise, nothing significant has popped up. I have other parts > > > > > > of that uprev under test (libc-headers, systemtap, etc). > > > > > > > > > > Thanks Bruce! > > > > > > > > > > Unfortunately there was one issue the autobuilder found, a > > > > > reproducibility issue in perf: > > > > > > > > > > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220630-53gdlqxv/packages/diff-html/ > > > > > > > > > > I've not looked into it other than looking at the above link but it > > > > > seems some python paths are creeping into the binaries. > > > > > > > > This looked a little suspicious to me: > > > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=18f2967418d031a390a5befe855dd0faa8af70b9 > > > > > > Confirmed that it is this change. Not sure why but at least we have an > > > idea of where the isssue is. > > > > > > I've also sent a patch to insane.bbclass to change WARN_QA such that we > > > can detect this kind of issue much earlier in people's local builds. It > > > may expose issues in other layers but those issues probably do need > > > exposing at this point too... > > > > This breaks: > > > > override PYTHON := $(call get-executable-or-default,PYTHON,$(subst -config,,$(PYTHON_AUTO))) > > > > as somehow PYTHON is expanded to a full path, yet: > > > > override PYTHON := $(call get-executable-or-default,PYTHON,$(PYTHON_AUTO)) > > > > this works and doesn't expand PYTHON. I have no idea why, it doesn't > > make sense. > > > > urk. I'm off today for a Stat holiday (and Monday as well), but will > poke at this throughout the weekend to try and come up with ideas > > first step, get geared up to test reproducibility locally, step 0, > find my old notes on the subject :) The insane.bbclass change helps as you don't need a full reproducibility build test. It is basically looking for buildpaths (TOPDIR) in the binaries. In other words just do a "strings perf | grep python3" and if you see a full build path there, there is a problem. You can see if on the compile commandline with a -DPYTHON= definition too. If it is a full path, it is broken. Cheers, Richard
On Fri, Jul 1, 2022 at 11:01 AM Richard Purdie <richard.purdie@linuxfoundation.org> wrote: > > On Fri, 2022-07-01 at 10:57 -0400, Bruce Ashfield wrote: > > On Fri, Jul 1, 2022 at 10:49 AM Richard Purdie > > <richard.purdie@linuxfoundation.org> wrote: > > > > > > On Fri, 2022-07-01 at 15:10 +0100, Richard Purdie via > > > lists.openembedded.org wrote: > > > > On Fri, 2022-07-01 at 13:52 +0100, Richard Purdie via > > > > lists.openembedded.org wrote: > > > > > On Fri, 2022-07-01 at 10:59 +0100, Richard Purdie via > > > > > lists.openembedded.org wrote: > > > > > > On Thu, 2022-06-30 at 15:16 -0400, bruce.ashfield@gmail.com wrote: > > > > > > > With conference travel and issues with meta-virtualization, I've been > > > > > > > behind in sending this out .. but I have been queueing changes, I just > > > > > > > wanted to be around in case something breaks. > > > > > > > > > > > > > > Here are the -stable updates and the start of my efforts to bring > > > > > > > 5.19 in as the new reference kernel for the fall release. > > > > > > > > > > > > > > lttng-modules needed it's normal tweaks to work against the 5.19 source, > > > > > > > but otherwise, nothing significant has popped up. I have other parts > > > > > > > of that uprev under test (libc-headers, systemtap, etc). > > > > > > > > > > > > Thanks Bruce! > > > > > > > > > > > > Unfortunately there was one issue the autobuilder found, a > > > > > > reproducibility issue in perf: > > > > > > > > > > > > http://autobuilder.yocto.io/pub/repro-fail/oe-reproducible-20220630-53gdlqxv/packages/diff-html/ > > > > > > > > > > > > I've not looked into it other than looking at the above link but it > > > > > > seems some python paths are creeping into the binaries. > > > > > > > > > > This looked a little suspicious to me: > > > > > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=18f2967418d031a390a5befe855dd0faa8af70b9 > > > > > > > > Confirmed that it is this change. Not sure why but at least we have an > > > > idea of where the isssue is. > > > > > > > > I've also sent a patch to insane.bbclass to change WARN_QA such that we > > > > can detect this kind of issue much earlier in people's local builds. It > > > > may expose issues in other layers but those issues probably do need > > > > exposing at this point too... > > > > > > This breaks: > > > > > > override PYTHON := $(call get-executable-or-default,PYTHON,$(subst -config,,$(PYTHON_AUTO))) > > > > > > as somehow PYTHON is expanded to a full path, yet: > > > > > > override PYTHON := $(call get-executable-or-default,PYTHON,$(PYTHON_AUTO)) > > > > > > this works and doesn't expand PYTHON. I have no idea why, it doesn't > > > make sense. > > > > > > > urk. I'm off today for a Stat holiday (and Monday as well), but will > > poke at this throughout the weekend to try and come up with ideas > > > > first step, get geared up to test reproducibility locally, step 0, > > find my old notes on the subject :) > > The insane.bbclass change helps as you don't need a full > reproducibility build test. It is basically looking for buildpaths > (TOPDIR) in the binaries. > > In other words just do a "strings perf | grep python3" and if you see a > full build path there, there is a problem. > > You can see if on the compile commandline with a -DPYTHON= definition > too. If it is a full path, it is broken. Sounds good. I see the QA patch. I'm on it, and will follow up when I know more. Bruce > > Cheers, > > Richard > >
From: Bruce Ashfield <bruce.ashfield@gmail.com> Richard, With conference travel and issues with meta-virtualization, I've been behind in sending this out .. but I have been queueing changes, I just wanted to be around in case something breaks. Here are the -stable updates and the start of my efforts to bring 5.19 in as the new reference kernel for the fall release. lttng-modules needed it's normal tweaks to work against the 5.19 source, but otherwise, nothing significant has popped up. I have other parts of that uprev under test (libc-headers, systemtap, etc). Cheers, Bruce The following changes since commit 012c046628990ccb230dd92c32f470a087ff332e: dev-manual: improve screenshot resolution (2022-06-30 17:09:51 +0100) are available in the Git repository at: git://git.yoctoproject.org/poky-contrib zedd/kernel http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (7): linux-yocto/5.10: update to v5.10.121 linux-yocto/5.15: update to v5.15.46 linux-yocto/5.15: update to v5.15.48 linux-yocto/5.10: update to v5.10.123 linux-yocto-dev: bump to v5.19-rc linux-yocto/5.15: drop obselete GPIO sysfs ABI lttng-modules: fix 5.19+ build meta/recipes-kernel/linux/linux-yocto-dev.bb | 4 +- .../linux/linux-yocto-rt_5.10.bb | 6 +- .../linux/linux-yocto-rt_5.15.bb | 6 +- .../linux/linux-yocto-tiny_5.10.bb | 8 +- .../linux/linux-yocto-tiny_5.15.bb | 6 +- meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 ++-- meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 ++-- ...c-fix-tracepoint-mm_page_alloc_zone_.patch | 106 +++++++++++++++ ...ags-parameter-from-aops-write_begin-.patch | 76 +++++++++++ ...Fix-type-of-cpu-in-trace-event-v5.19.patch | 124 ++++++++++++++++++ .../lttng/lttng-modules_2.13.4.bb | 3 + 11 files changed, 349 insertions(+), 40 deletions(-) create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0001-fix-mm-page_alloc-fix-tracepoint-mm_page_alloc_zone_.patch create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0002-fix-fs-Remove-flags-parameter-from-aops-write_begin-.patch create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0003-fix-workqueue-Fix-type-of-cpu-in-trace-event-v5.19.patch