From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [GIT PULL] dma-mapping fixes for Linux 6.7
Date: Fri, 10 Nov 2023 07:59:59 +0100 [thread overview]
Message-ID: <ZU3U759SwIC4Vv-F@infradead.org> (raw)
The following changes since commit 8f6f76a6a29f36d2f3e4510d0bde5046672f6924:
Merge tag 'mm-nonmm-stable-2023-11-02-14-08' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2023-11-02 20:53:31 -1000)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.7-2023-11-10
for you to fetch changes up to 53c87e846e335e3c18044c397cc35178163d7827:
swiotlb: fix out-of-bounds TLB allocations with CONFIG_SWIOTLB_DYNAMIC (2023-11-08 16:27:05 +0100)
----------------------------------------------------------------
ma-mapping fixes for Linux 6.7
- don't leave pages decrypted for DMA in encrypted memory setups linger
around on failure (Petr Tesarik)
- fix an out of bounds access in the new dynamic swiotlb code (Petr Tesarik)
- fix dma_addressing_limited for systems with weird physical memory layouts
(Jia He)
----------------------------------------------------------------
Jia He (2):
dma-mapping: move dma_addressing_limited() out of line
dma-mapping: fix dma_addressing_limited() if dma_range_map can't cover all system RAM
Petr Tesarik (2):
swiotlb: do not free decrypted pages if dynamic
swiotlb: fix out-of-bounds TLB allocations with CONFIG_SWIOTLB_DYNAMIC
include/linux/dma-mapping.h | 19 +++++--------------
kernel/dma/direct.c | 40 ++++++++++++++++++++++++++++++++++++++++
kernel/dma/direct.h | 1 +
kernel/dma/mapping.c | 22 ++++++++++++++++++++++
kernel/dma/swiotlb.c | 28 ++++++++++++++++++----------
5 files changed, 86 insertions(+), 24 deletions(-)
next reply other threads:[~2023-11-10 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 6:59 Christoph Hellwig [this message]
2023-11-10 19:28 ` 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=ZU3U759SwIC4Vv-F@infradead.org \
--to=hch@infradead.org \
--cc=iommu@lists.linux.dev \
--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®