From: Jon Hunter <jonathanh@nvidia.com>
To: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, florian.fainelli@broadcom.com,
pavel@denx.de,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 6.8 000/715] 6.8.2-rc1 review
Date: Wed, 3 Apr 2024 11:02:30 +0100 [thread overview]
Message-ID: <0cdbf4d6-3dce-42ee-8029-c486ec999fb5@nvidia.com> (raw)
In-Reply-To: <20240324223455.1342824-1-sashal@kernel.org>
Hi Sasha,
On 24/03/2024 22:22, Sasha Levin wrote:
>
> This is the start of the stable review cycle for the 6.8.2 release.
> There are 715 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Tue Mar 26 10:34:31 PM UTC 2024.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-6.8.y&id2=v6.8.1
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.8.y
> and the diffstat can be found below.
>
> Thanks,
> Sasha
...
> Tejun Heo (9):
> workqueue: Move pwq->max_active to wq->max_active
> workqueue: Factor out pwq_is_empty()
> workqueue: Replace pwq_activate_inactive_work() with
> [__]pwq_activate_work()
> workqueue: Move nr_active handling into helpers
> workqueue: Make wq_adjust_max_active() round-robin pwqs while
> activating
> workqueue: RCU protect wq->dfl_pwq and implement accessors for it
> workqueue: Introduce struct wq_node_nr_active
> workqueue: Implement system-wide nr_active enforcement for unbound
> workqueues
> workqueue: Don't call cpumask_test_cpu() with -1 CPU in
> wq_update_node_max_active()
Sorry I am late on this, but I was not copied and so did not see this. I
noticed a suspend regression on Tegra186 with v6.8.y and bisect is point
to commit "workqueue: Implement system-wide nr_active enforcement for
unbound workqueues".
Reverting commits "workqueue: Don't call cpumask_test_cpu() with -1 CPU
in wq_update_node_max_active()" and "workqueue: Implement system-wide
nr_active enforcement for unbound workqueues" does fix the problem.
Note that I am not seeing this regression on the mainline with v6.9-rc2
and so I am not sure if there is something else missing? I am also still
seeing the problem with v6.8.3-rc1.
Jon
--
nvpublic
next parent reply other threads:[~2024-04-03 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240324223455.1342824-1-sashal@kernel.org>
2024-04-03 10:02 ` Jon Hunter [this message]
2024-04-03 11:14 ` [PATCH 6.8 000/715] 6.8.2-rc1 review Linux regression tracking (Thorsten Leemhuis)
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=0cdbf4d6-3dce-42ee-8029-c486ec999fb5@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).