From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
Will Deacon <will@kernel.org>,
linux-arch@vger.kernel.org, catalin.marinas@arm.com,
maz@kernel.org, mark.rutland@arm.com, hch@lst.de,
vgupta@kernel.org, arnd@arndb.de, bcain@quicinc.com,
geert@linux-m68k.org, monstr@monstr.eu, dinguyen@kernel.org,
shorne@gmail.com, mpe@ellerman.id.au, dalias@libc.org
Subject: Re: Cache maintenance for non-coherent DMA in arch_sync_dma_for_device()
Date: Wed, 8 Jun 2022 10:49:51 +0200 [thread overview]
Message-ID: <20220608084951.GB17806@lst.de> (raw)
In-Reply-To: <1a8cc7af-87ac-b0e7-7fb9-d11a5eebef55@arm.com>
On Mon, Jun 06, 2022 at 05:02:50PM +0100, Robin Murphy wrote:
> No, partial DMA writes can sometimes effectively be expected behaviour, see
> the whole SWIOTLB CVE fiasco for the most recent discussion on that:
Yes, and I still have a TODO list item for interfaces that deal
with the case of a transfer smaller than the mapping sanely, but
I haven't managed to get to it yet.
next prev parent reply other threads:[~2022-06-08 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 15:21 Cache maintenance for non-coherent DMA in arch_sync_dma_for_device() Will Deacon
2022-06-06 15:35 ` Russell King (Oracle)
2022-06-06 16:02 ` Robin Murphy
2022-06-06 16:16 ` Russell King (Oracle)
2022-06-08 8:49 ` Christoph Hellwig [this message]
2022-06-06 16:13 ` Catalin Marinas
2022-06-06 16:15 ` Ard Biesheuvel
2022-06-08 16:51 ` Catalin Marinas
2022-06-08 8:48 ` Christoph Hellwig
2022-06-08 12:02 ` Russell King (Oracle)
2022-06-08 15:14 ` Christoph Hellwig
2022-06-09 13:59 ` Will Deacon
2022-06-09 14:18 ` Christoph Hellwig
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=20220608084951.GB17806@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=bcain@quicinc.com \
--cc=catalin.marinas@arm.com \
--cc=dalias@libc.org \
--cc=dinguyen@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=robin.murphy@arm.com \
--cc=shorne@gmail.com \
--cc=vgupta@kernel.org \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).