From: Greg KH <gregkh@linuxfoundation.org>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: stable@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Doug Gilbert <dgilbert@interlog.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
Thiago Jung Bauermann <bauerman@linux.ibm.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH for 5.10.x 2/2] swiotlb: rework "fix info leak with DMA_FROM_DEVICE"
Date: Tue, 22 Mar 2022 11:28:12 +0100 [thread overview]
Message-ID: <YjmkvPFTOkxiP29k@kroah.com> (raw)
In-Reply-To: <20220322100218.2158138-3-pasic@linux.ibm.com>
On Tue, Mar 22, 2022 at 11:02:18AM +0100, Halil Pasic wrote:
> Unfortunately, we ended up merging an old version of the patch "fix info
> leak with DMA_FROM_DEVICE" instead of merging the latest one. Christoph
> (the swiotlb maintainer), he asked me to create an incremental fix
> (after I have pointed this out the mix up, and asked him for guidance).
> So here we go.
>
> The main differences between what we got and what was agreed are:
> * swiotlb_sync_single_for_device is also required to do an extra bounce
> * We decided not to introduce DMA_ATTR_OVERWRITE until we have exploiters
> * The implantation of DMA_ATTR_OVERWRITE is flawed: DMA_ATTR_OVERWRITE
> must take precedence over DMA_ATTR_SKIP_CPU_SYNC
>
> Thus this patch removes DMA_ATTR_OVERWRITE, and makes
> swiotlb_sync_single_for_device() bounce unconditionally (that is, also
> when dir == DMA_TO_DEVICE) in order do avoid synchronising back stale
> data from the swiotlb buffer.
>
> Let me note, that if the size used with dma_sync_* API is less than the
> size used with dma_[un]map_*, under certain circumstances we may still
> end up with swiotlb not being transparent. In that sense, this is no
> perfect fix either.
>
> To get this bullet proof, we would have to bounce the entire
> mapping/bounce buffer. For that we would have to figure out the starting
> address, and the size of the mapping in
> swiotlb_sync_single_for_device(). While this does seem possible, there
> seems to be no firm consensus on how things are supposed to work.
>
> Signed-off-by: Halil Pasic <pasic@linux.ibm.com>
> Fixes: ddbd89deb7d3 ("swiotlb: fix info leak with DMA_FROM_DEVICE")
> Cc: stable@vger.kernel.org
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> [pasic@linux.ibm.com: adapted for 5.10]
> ---
> Documentation/core-api/dma-attributes.rst | 8 --------
> include/linux/dma-mapping.h | 8 --------
> kernel/dma/swiotlb.c | 25 +++++++++++++++--------
> 3 files changed, 16 insertions(+), 25 deletions(-)
What is the git commit id of this commit in Linus's tree?
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-22 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 10:02 [PATCH for 5.10.y 0/2] backports of ddbd89deb7d3 and aa6f8dcbab47 Halil Pasic
2022-03-22 10:02 ` [PATCH for 5.10.x 1/2] swiotlb: fix info leak with DMA_FROM_DEVICE Halil Pasic
2022-03-22 10:10 ` Greg KH
2022-03-22 10:28 ` Halil Pasic
2022-03-22 10:36 ` Greg KH
2022-03-22 11:26 ` Halil Pasic
2022-03-22 10:02 ` [PATCH for 5.10.x 2/2] swiotlb: rework "fix info leak with DMA_FROM_DEVICE" Halil Pasic
2022-03-22 10:28 ` Greg KH [this message]
2022-03-22 10:29 ` [PATCH for 5.10.y 0/2] backports of ddbd89deb7d3 and aa6f8dcbab47 Greg KH
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=YjmkvPFTOkxiP29k@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bauerman@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=dgilbert@interlog.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=khandual@linux.vnet.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--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