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 fixes for v6.11-rc4
Date: Fri, 23 Aug 2024 14:44:55 -1000 [thread overview]
Message-ID: <ZsktB3D_K-80uc35@slm.duckdns.org> (raw)
The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:
Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git/ tags/wq-for-6.11-rc4-fixes
for you to fetch changes up to c4c8f369b6a6d21ce27286de1501137771e01dc3:
workqueue: Correct declaration of cpu_pwq in struct workqueue_struct (2024-08-05 18:34:02 -1000)
----------------------------------------------------------------
workqueue: Fixes for v6.11-rc4
Nothing too interesting. One patch to remove spurious warning and others to
address static checker warnings.
----------------------------------------------------------------
Lai Jiangshan (1):
workqueue: Remove incorrect "WARN_ON_ONCE(!list_empty(&worker->entry));" from dying worker
Nikita Shubin (1):
workqueue: doc: Fix function name, remove markers
Tejun Heo (1):
workqueue: Fix spruious data race in __flush_work()
Uros Bizjak (1):
workqueue: Correct declaration of cpu_pwq in struct workqueue_struct
Will Deacon (1):
workqueue: Fix UBSAN 'subtraction overflow' error in shift_and_mask()
Documentation/core-api/workqueue.rst | 2 +-
kernel/workqueue.c | 50 +++++++++++++++++++-----------------
2 files changed, 28 insertions(+), 24 deletions(-)
next reply other threads:[~2024-08-24 0:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 0:44 Tejun Heo [this message]
2024-08-24 2:46 ` pr-tracker-bot
2024-08-24 0:59 [GIT PULL] workqueue: Fixes " Tejun Heo
2024-08-24 2:44 ` Linus Torvalds
2024-08-24 2:56 ` Tejun Heo
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=ZsktB3D_K-80uc35@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®