From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Lai Jiangshan <jiangshanlai@gmail.com>
Subject: [GIT PULL] workqueue changes for v6.4-rc1
Date: Thu, 27 Apr 2023 10:35:58 -1000 [thread overview]
Message-ID: <ZErcro8_Ylius4wC@slm.duckdns.org> (raw)
The following changes since commit 8d3c682a5e3d9dfc2448ecbb22f4cd48359b9e21:
Merge tag 'block-6.3-2023-03-16' of git://git.kernel.dk/linux (2023-03-17 11:20:27 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git/ tags/wq-for-6.4
for you to fetch changes up to 704bc669e1dda3eb8f6d5cb462b21e85558a3912:
workqueue: Introduce show_freezable_workqueues (2023-03-23 15:55:38 -1000)
----------------------------------------------------------------
workqueue changes for v6.4-rc1
Mostly changes from Petr to improve warning and error reporting. Workqueue
now reports more of the relevant failures with better context which should
help debugging.
----------------------------------------------------------------
Ammar Faizi (2):
MAINTAINERS: Add workqueue_internal.h to the WORKQUEUE entry
workqueue: Simplify a pr_warn() call in wq_select_unbound_cpu()
Jungseung Lee (1):
workqueue: Introduce show_freezable_workqueues
Petr Mladek (5):
workqueue: Fix hung time report of worker pools
workqueue: Warn when a new worker could not be created
workqueue: Interrupted create_worker() is not a repeated event
workqueue: Warn when a rescuer could not be created
workqueue: Print backtraces from CPUs with hung CPU bound workqueues
MAINTAINERS | 1 +
include/linux/workqueue.h | 1 +
kernel/power/process.c | 2 +-
kernel/workqueue.c | 134 +++++++++++++++++++++++++++++++++++++++++-----
4 files changed, 124 insertions(+), 14 deletions(-)
next reply other threads:[~2023-04-27 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 20:35 Tejun Heo [this message]
2023-04-29 18:20 ` pr-tracker-bot
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=ZErcro8_Ylius4wC@slm.duckdns.org \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®