mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v5.5-rc1
Date: Mon, 25 Nov 2019 08:03:14 -0800	[thread overview]
Message-ID: <20191125160314.GB2867037@devbig004.ftw2.facebook.com> (raw)

Hello,

There have been sporadic reports of sanity checks in
destroy_workqueue() failing spuriously over the years.  This pull
request contains the fix and its follow-up changes / fixes.  There's
also a RCU annotation improvement.

Thanks.

The following changes since commit f60c55a94e1d127186566f06294f2dadd966e9b4:

  Merge tag 'fsverity-for-linus' of git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt (2019-09-18 16:59:14 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-5.5

for you to fetch changes up to 49e9d1a9faf2f71fdfd80a30697ee9a15070626d:

  workqueue: Add RCU annotation for pwq list walk (2019-11-15 11:53:35 -0800)

----------------------------------------------------------------
Sebastian Andrzej Siewior (1):
      workqueue: Add RCU annotation for pwq list walk

Tejun Heo (5):
      workqueue: Fix spurious sanity check failures in destroy_workqueue()
      workqueue: Fix missing kfree(rescuer) in destroy_workqueue()
      workqueue: Minor follow-ups to the rescuer destruction change
      workqueue: more destroy_workqueue() fixes
      workqueue: Fix pwq ref leak in rescuer_thread()

 kernel/workqueue.c | 90 +++++++++++++++++++++++++++++++++++++++---------------
 1 file changed, 65 insertions(+), 25 deletions(-)

-- 
tejun

             reply	other threads:[~2019-11-25 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 16:03 Tejun Heo [this message]
2019-11-26  4:25 ` 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=20191125160314.GB2867037@devbig004.ftw2.facebook.com \
    --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®