mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	Steffen Klassert <steffen.klassert@secunet.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Daniel Jordan <daniel.m.jordan@oracle.com>
Subject: [PATCH v2 0/5] padata lockdep, cpumask, and doc fixes
Date: Tue,  3 Dec 2019 14:31:09 -0500	[thread overview]
Message-ID: <20191203193114.238912-1-daniel.m.jordan@oracle.com> (raw)

This series depends on all of Herbert's recent padata fixes to reduce
merge conflicts on his end:

  crypto: pcrypt - Do not clear MAY_SLEEP flag in original request
  padata: Remove unused padata_remove_cpu
  [v3] crypto: pcrypt - Avoid deadlock by using per-instance padata queues
  crypto: pcrypt - Fix user-after-free on module unload
  padata: Remove broken queue flushing 

If this should be based on something else, please let me know.

Thanks,
Daniel

v2:
 - documentation patch RST-ized according to Jon's comments
 - "validate cpumask" patch added
 - rebased onto v5.4 and updated since Herbert's fixes have changed

Daniel Jordan (5):
  padata: validate cpumask without removed CPU during offline
  padata: always acquire cpu_hotplug_lock before pinst->lock
  padata: remove cpumask change notifier
  padata: remove reorder_objects
  padata: update documentation

 Documentation/core-api/index.rst  |   1 +
 Documentation/core-api/padata.rst | 169 ++++++++++++++++++++++++++++++
 Documentation/padata.txt          | 163 ----------------------------
 crypto/pcrypt.c                   |   1 -
 include/linux/cpuhotplug.h        |   1 +
 include/linux/padata.h            |  28 ++---
 kernel/padata.c                   | 124 ++++++++--------------
 7 files changed, 220 insertions(+), 267 deletions(-)
 create mode 100644 Documentation/core-api/padata.rst
 delete mode 100644 Documentation/padata.txt


base-commit: 219d54332a09e8d8741c1e1982f5eae56099de85
prerequisite-patch-id: e31e7b28eb12a2c7e1e04261f4e890f83a57bd19
prerequisite-patch-id: 00f7ca687bd9df6281e9ced0925a865b2fa7b297
prerequisite-patch-id: 9f3bb985b34d29ff30e44b8829545736de02186f
prerequisite-patch-id: fe09ee84131ee649b90ee291fbbeda32e90c42fe
prerequisite-patch-id: f2e5a29f78e2403677ad50d870d90022932bc2b6
-- 
2.24.0


             reply	other threads:[~2019-12-03 19:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 19:31 Daniel Jordan [this message]
2019-12-03 19:31 ` [PATCH v2 1/5] padata: validate cpumask without removed CPU during offline Daniel Jordan
2019-12-03 19:31 ` [PATCH v2 2/5] padata: always acquire cpu_hotplug_lock before pinst->lock Daniel Jordan
2019-12-03 19:31 ` [PATCH v2 3/5] padata: remove cpumask change notifier Daniel Jordan
2019-12-03 19:31 ` [PATCH v2 4/5] padata: remove reorder_objects Daniel Jordan
2019-12-03 19:31 ` [PATCH v2 5/5] padata: update documentation Daniel Jordan
2019-12-10 16:44   ` Daniel Jordan
2019-12-11  9:45     ` Herbert Xu
2019-12-11  9:44 ` [PATCH v2 0/5] padata lockdep, cpumask, and doc fixes Herbert Xu

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=20191203193114.238912-1-daniel.m.jordan@oracle.com \
    --to=daniel.m.jordan@oracle.com \
    --cc=corbet@lwn.net \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steffen.klassert@secunet.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

all inboxes | Powered by JetHome®