From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: steve@sakoman.com, openembedded-core@lists.openembedded.org,
Bruce Ashfield <bruce.ashfield@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core][mickledore 00/18] Patch review
Date: Fri, 18 Aug 2023 18:36:50 -0400 [thread overview]
Message-ID: <ZN/ygrsJU3k18Vm4@windriver.com> (raw)
In-Reply-To: <177C5BF219AB3C22.3047@lists.openembedded.org>
[Re: [OE-core][mickledore 00/18] Patch review] On 17/08/2023 (Thu 23:17) Paul Gortmaker via lists.openembedded.org wrote:
> [Re: [OE-core][mickledore 00/18] Patch review] On 16/08/2023 (Wed 07:50) Steve Sakoman via lists.openembedded.org wrote:
>
> > On Tue, Aug 15, 2023 at 6:24???AM Steve Sakoman via
> > lists.openembedded.org <steve=sakoman.com@lists.openembedded.org>
> > wrote:
> > >
> > > Please review this set of changes for mickledore and have comments back by
> > > end of day Thursday, August 17.
>
> [...]
>
> > > Bruce Ashfield (2):
> > > linux-yocto/6.1: update to v6.1.41
> > > linux-yocto/6.1: update to v6.1.43
> >
> > I'm seeing intermittent failures with these 6.1 "stable" version bumps
> > (issues are also seen in master).
> >
> > So I am dropping these for now till we can fix the problem.
>
> aka "NOHZ tick-stop error: local softirq work is pending, handler #80!!!"
>
> For those not on IRC, the "cause" was tracked down to a v6.1.39 change:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/releases/6.1.39/tick-rcu-fix-bogus-ratelimit-condition.patch
>
> [linux-stable commit ID 77cc52f1b8d7 in v6.1]
>
> The bad news - when you look at that commit, you realize the softirq-80
> problem has been there for an as-yet undetermined length of time, but
> was never output because of the bogus/broken "less than 10" check.
>
> The "less than 10" was introduced in v5.18, so that sets a lower bound,
> but I've not yet tested if the pending-80 was there immediately at 5.18
> or appeared somewhere between v5.18 and v6.1 - stay tuned.
For the mail archives - it turns out the issue was there immediately at
v5.18, based on my testing results. - I'm optimistic (for once) that we
have this softirq-80 issue solved. But we'll have to wait and see.
If folks are interested, more details are in the commit log here:
https://lore.kernel.org/lkml/20230818200757.1808398-1-paul.gortmaker@windriver.com/
Paul.
--
>
> The same change/issue 1st appears in v6.4.4 stable kernel [7fe63c29cb].
>
> Paul.
> --
>
> >
> > I reran a-full without the version bumps and all tests passed:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5742
> >
> > Steve
> >
> > > Dmitry Baryshkov (1):
> > > linux-firmware: split platform-specific Adreno shaders to separate
> > > packages
> > >
> > > Joel Stanley (1):
> > > kernel: don't fail if Modules.symvers doesn't exist
> > >
> > > Marek Vasut (1):
> > > linux-firmware: Fix mediatek mt7601u firmware path
> > >
> > > Mark Hatle (1):
> > > tcf-agent: Update to 1.8.0 release
> > >
> > > Richard Purdie (1):
> > > oeqa/ssh: Further improve process exit handling
> > >
> > > Ross Burton (1):
> > > openssh: upgrade to 9.3p2
> > >
> > > Sudip Mukherjee (1):
> > > bind: upgrade to v9.18.17
> > >
> > > Yogita Urade (3):
> > > qemu: fix CVE-2023-3301
> > > qemu: fix CVE-2023-3255
> > > qemu: fix CVE-2023-2861
> > >
> > > sanjana (1):
> > > binutils: stable 2.40 branch updates
> > >
> > > meta/classes-recipe/kernel.bbclass | 4 +-
> > > meta/conf/distro/include/maintainers.inc | 2 +-
> > > meta/lib/oeqa/core/target/ssh.py | 5 +-
> > > ...1-avoid-start-failure-with-bind-user.patch | 0
> > > ...d-V-and-start-log-hide-build-options.patch | 0
> > > ...ching-for-json-headers-searches-sysr.patch | 0
> > > .../bind/{bind-9.18.16 => bind}/bind9 | 0
> > > .../bind/{bind-9.18.16 => bind}/conf.patch | 0
> > > .../generate-rndc-key.sh | 0
> > > ...t.d-add-support-for-read-only-rootfs.patch | 0
> > > .../make-etc-initd-bind-stop-work.patch | 0
> > > .../bind/{bind-9.18.16 => bind}/named.service | 0
> > > .../bind/{bind_9.18.16.bb => bind_9.18.17.bb} | 4 +-
> > > .../{openssh_9.3p1.bb => openssh_9.3p2.bb} | 2 +-
> > > meta/recipes-core/glibc/glibc-locale.inc | 8 +-
> > > .../binutils/binutils-2.40.inc | 2 +-
> > > meta/recipes-devtools/qemu/qemu.inc | 3 +
> > > .../qemu/qemu/CVE-2023-2861.patch | 171 ++++++++++++++++++
> > > .../qemu/qemu/CVE-2023-3255.patch | 65 +++++++
> > > .../qemu/qemu/CVE-2023-3301.patch | 65 +++++++
> > > .../tcf-agent/tcf-agent_git.bb | 4 +-
> > > .../linux-firmware/linux-firmware_20230625.bb | 28 ++-
> > > .../linux/linux-yocto-rt_6.1.bb | 6 +-
> > > .../linux/linux-yocto-tiny_6.1.bb | 6 +-
> > > meta/recipes-kernel/linux/linux-yocto_6.1.bb | 28 +--
> > > meta/recipes-support/curl/curl/disable-tests | 2 +
> > > meta/recipes-support/curl/curl/run-ptest | 2 +-
> > > scripts/lib/devtool/upgrade.py | 2 +
> > > 28 files changed, 366 insertions(+), 43 deletions(-)
> > > rename meta/recipes-connectivity/bind/{bind-9.18.16 => bind}/0001-avoid-start-failure-with-bind-user.patch (100%)
> > > rename meta/recipes-connectivity/bind/{bind-9.18.16 => bind}/0001-named-lwresd-V-and-start-log-hide-build-options.patch (100%)
> > > rename meta/recipes-connectivity/bind/{bind-9.18.16 => bind}/bind-ensure-searching-for-json-headers-searches-sysr.patch (100%)
> > > rename meta/recipes-connectivity/bind/{bind-9.18.16 => bind}/bind9 (100%)
> > > rename meta/recipes-connectivity/bind/{bind-9.18.16 => bind}/conf.patch (100%)
> > > rename meta/recipes-connectivity/bind/{bind-9.18.16 => bind}/generate-rndc-key.sh (100%)
> > > rename meta/recipes-connectivity/bind/{bind-9.18.16 => bind}/init.d-add-support-for-read-only-rootfs.patch (100%)
> > > rename meta/recipes-connectivity/bind/{bind-9.18.16 => bind}/make-etc-initd-bind-stop-work.patch (100%)
> > > rename meta/recipes-connectivity/bind/{bind-9.18.16 => bind}/named.service (100%)
> > > rename meta/recipes-connectivity/bind/{bind_9.18.16.bb => bind_9.18.17.bb} (96%)
> > > rename meta/recipes-connectivity/openssh/{openssh_9.3p1.bb => openssh_9.3p2.bb} (98%)
> > > create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-2861.patch
> > > create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-3255.patch
> > > create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-3301.patch
> > >
> > > --
> > > 2.34.1
> > >
> > >
> > >
> > >
>
> >
> >
> >
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#186343): https://lists.openembedded.org/g/openembedded-core/message/186343
> Mute This Topic: https://lists.openembedded.org/mt/100761429/6329300
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [paul.gortmaker@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2023-08-18 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <177B9B269D618F2D.8497@lists.openembedded.org>
2023-08-16 17:50 ` [OE-core][mickledore 00/18] Patch review Steve Sakoman
2023-08-18 3:17 ` Paul Gortmaker
[not found] ` <177C5BF219AB3C22.3047@lists.openembedded.org>
2023-08-18 22:36 ` Paul Gortmaker [this message]
2023-08-20 18:28 ` Bruce Ashfield
2023-08-15 16:24 Steve Sakoman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZN/ygrsJU3k18Vm4@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=steve@sakoman.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox