From: Dan Williams <dan.j.williams@intel.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Compute Express Link (CXL) Fixes for 6.7-rc6
Date: Sun, 17 Dec 2023 00:05:59 -0800 [thread overview]
Message-ID: <657eabe7624f7_715492941c@dwillia2-mobl3.amr.corp.intel.com.notmuch> (raw)
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl tags/cxl-fixes-6.7-rc6
...to receive a collection of CXL fixes. The touch outside of
drivers/cxl/ is for a helper that allocates physical address space.
Device hotplug tests showed that the driver failed to utilize (skipped
over) valid capacity when allocating a new memory region. Outside of
that, new tests uncovered a small crop of lockdep reports. There is also
some miscellaneous error path and leak fixups that are not urgent, but
useful to cleanup now.
This has been available for the bots to chew on for a few days, but I do
not see it in linux-next. I will need to follow up with Stephen to see
why it missed the 12/15 linux-next. I do not foresee any issues.
---
The following changes since commit 98b1cc82c4affc16f5598d4fa14b1858671b2263:
Linux 6.7-rc2 (2023-11-19 15:02:14 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl tags/cxl-fixes-6.7-rc6
for you to fetch changes up to ef3d5cf9c59cccb012aa6b93d99f4c6eb5d6648e:
cxl/pmu: Ensure put_device on pmu devices (2023-12-14 21:54:45 -0800)
----------------------------------------------------------------
cxl fixes for 6.7-rc6
- Fix alloc_free_mem_region()'s scan for address space, prevent false
negative out-of-space events
- Fix sleeping lock acquisition from CXL trace event (atomic context)
- Fix put_device() like for the new CXL PMU driver
- Fix wrong pointer freed on error path
- Fixup several lockdep reports (missing lock hold) from new assertion
in cxl_num_decoders_committed() and new tests
----------------------------------------------------------------
Alison Schofield (3):
cxl/core: Always hold region_rwsem while reading poison lists
cxl/memdev: Hold region_rwsem during inject and clear poison ops
kernel/resource: Increment by align value in get_free_mem_region()
Dan Williams (1):
cxl/hdm: Fix dpa translation locking
Dave Jiang (2):
cxl/hdm: Fix a benign lockdep splat
cxl: Add cxl_num_decoders_committed() usage to cxl_test
Ira Weiny (2):
cxl/cdat: Free correct buffer on checksum error
cxl/pmu: Ensure put_device on pmu devices
drivers/cxl/core/hdm.c | 5 +++--
drivers/cxl/core/memdev.c | 27 ++++++++++++++++++++++++---
drivers/cxl/core/pci.c | 13 ++++++-------
drivers/cxl/core/pmu.c | 2 +-
drivers/cxl/core/port.c | 4 ++--
drivers/cxl/core/region.c | 5 -----
kernel/resource.c | 4 ++--
tools/testing/cxl/Kbuild | 1 +
tools/testing/cxl/cxl_core_exports.c | 7 +++++++
tools/testing/cxl/test/cxl.c | 5 +++--
10 files changed, 49 insertions(+), 24 deletions(-)
create mode 100644 tools/testing/cxl/cxl_core_exports.c
next reply other threads:[~2023-12-17 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 8:05 Dan Williams [this message]
2023-12-17 17:38 ` 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=657eabe7624f7_715492941c@dwillia2-mobl3.amr.corp.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--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®