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.9
Date: Sun, 24 Mar 2024 08:07:11 +0800 [thread overview]
Message-ID: <Zf9ur7uQA0JLleTU@infradead.org> (raw)
The following changes since commit b9fa16949d18e06bdf728a560f5c8af56d2bdcaf:
dma-direct: Leak pages on dma_set_decrypted() failure (2024-02-28 05:31:38 -0800)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.9-2024-03-24
for you to fetch changes up to 14cebf689a78e8a1c041138af221ef6eac6bc7da:
swiotlb: Reinstate page-alignment for mappings >= PAGE_SIZE (2024-03-13 11:39:34 -0700)
----------------------------------------------------------------
dma-mapping fixes for Linux 6.9
This has a set of swiotlb alignment fixes for sometimes very long
standing bugs from Will. We've been discussion them for a while and they
should be solid now.
----------------------------------------------------------------
Nicolin Chen (1):
iommu/dma: Force swiotlb_max_mapping_size on an untrusted device
Will Deacon (5):
swiotlb: Fix double-allocation of slots due to broken alignment handling
swiotlb: Enforce page alignment in swiotlb_alloc()
swiotlb: Honour dma_alloc_coherent() alignment in swiotlb_alloc()
swiotlb: Fix alignment checks when both allocation and DMA masks are present
swiotlb: Reinstate page-alignment for mappings >= PAGE_SIZE
drivers/iommu/dma-iommu.c | 9 +++++++++
kernel/dma/swiotlb.c | 45 +++++++++++++++++++++++++++++++++------------
2 files changed, 42 insertions(+), 12 deletions(-)
next reply other threads:[~2024-03-24 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 0:07 Christoph Hellwig [this message]
2024-03-24 18:26 ` 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=Zf9ur7uQA0JLleTU@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®