Linux IOMMU Development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: David Woodhouse <dwmw2@infradead.org>,
	Lu Baolu <baolu.lu@linux.intel.com>
Cc: iommu@lists.linux.dev
Subject: lack of permission checking with intel-iommu?
Date: Tue, 2 Jul 2024 00:46:59 -0700	[thread overview]
Message-ID: <ZoOwc7O5W0PUeja5@infradead.org> (raw)

Hi all,

we've recently had an interesting case where a device unexpectedly
modified a dma buffer passed to it.  On AMD systems this caused iommu
faults because the buffer was mapped read only (DMA_FROM_DEVICE), but
on an Intel system everything worked fine as the IOMMU did not trip up
on the device writes to that buffer.  Any idea why that could sneak
through?

             reply	other threads:[~2024-07-02  7:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02  7:46 Christoph Hellwig [this message]
2024-07-02  8:02 ` lack of permission checking with intel-iommu? Christoph Hellwig
2024-07-02  8:22   ` Baolu Lu
2024-07-02  8:25     ` Christoph Hellwig
2024-07-02  9:12       ` Baolu Lu
2024-07-02 11:42         ` Christoph Hellwig
2024-07-03  0:56         ` Tian, Kevin
2024-07-03  2:28           ` Baolu Lu
2024-07-02  8:47     ` Yi Liu
2024-07-02  9:07       ` Baolu Lu

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=ZoOwc7O5W0PUeja5@infradead.org \
    --to=hch@infradead.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux.dev \
    /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