From: alison.schofield@intel.com
To: Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: linux-cxl@vger.kernel.org
Subject: [PATCH 0/2] cxl/core: Hold region_rwsem during poison ops
Date: Sun, 26 Nov 2023 16:09:28 -0800 [thread overview]
Message-ID: <cover.1701041440.git.alison.schofield@intel.com> (raw)
From: Alison Schofield <alison.schofield@intel.com>
This work was previously posted as a single patch [1] and is reposted
here split into 2 patches. The first patch fixes up the poison list
and the second patch the poison inject and clear.
They both are cleaning up locking issues exposed by:
Commit 458ba8189cb4 ("cxl: Add cxl_decoders_committed() helper")
added a lockdep_assert_held() to make sure all callers hold the
region state stable while doing work that depends on the number
of committed decoders.
Changes since that single patch posting:
- Put back the _interruptible() on down_reads (DavidLohr, Dan)
- Split into 2 patches (Dan)
- Add impact statements in commit logs (Dan)
[1] https://lore.kernel.org/linux-cxl/20231114025342.1123681-1-alison.schofield@intel.com/
Alison Schofield (2):
cxl/core: Always hold region_rwsem while reading poison lists
cxl/memdev: Hold region_rwsem during inject and clear poison ops
drivers/cxl/core/memdev.c | 27 ++++++++++++++++++++++++---
drivers/cxl/core/region.c | 5 -----
2 files changed, 24 insertions(+), 8 deletions(-)
base-commit: b85ea95d086471afb4ad062012a4d73cd328fa86
--
2.37.3
next reply other threads:[~2023-11-27 0:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 0:09 alison.schofield [this message]
2023-11-27 0:09 ` [PATCH 1/2] cxl/core: Always hold region_rwsem while reading poison lists alison.schofield
2023-11-27 17:40 ` Dave Jiang
2023-11-27 21:20 ` Davidlohr Bueso
2023-11-30 1:21 ` Dan Williams
2023-11-27 0:09 ` [PATCH 2/2] cxl/memdev: Hold region_rwsem during inject and clear poison ops alison.schofield
2023-11-27 17:58 ` Dave Jiang
2023-11-28 0:58 ` Davidlohr Bueso
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=cover.1701041440.git.alison.schofield@intel.com \
--to=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@intel.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