From: Halil Pasic <pasic@linux.ibm.com>
To: stable@vger.kernel.org
Cc: Halil Pasic <pasic@linux.ibm.com>,
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: [PATCH for 5.10.y 0/2] backports of ddbd89deb7d3 and aa6f8dcbab47
Date: Tue, 22 Mar 2022 11:02:16 +0100 [thread overview]
Message-ID: <20220322100218.2158138-1-pasic@linux.ibm.com> (raw)
Dear Stable Team,
This is a backport of ddbd89deb7d3 ("swiotlb: fix info leak with
DMA_FROM_DEVICE") and aa6f8dcbab47 ("swiotlb: rework "fix info leak with
DMA_FROM_DEVICE"") to 5.10.y.
I had to handle some merge conflicts, and at this point we have
swiotlb_tbl_sync_single() as opposed to swiotlb_sync_single_for_device()
so I had to handle that as well.
Halil Pasic (2):
swiotlb: fix info leak with DMA_FROM_DEVICE
swiotlb: rework "fix info leak with DMA_FROM_DEVICE"
kernel/dma/swiotlb.c | 24 ++++++++++++++++--------
1 file changed, 16 insertions(+), 8 deletions(-)
base-commit: 9d7b0ced5647e0df1b200ee29119cb58ff958339
--
2.32.0
next reply other threads:[~2022-03-22 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 10:02 Halil Pasic [this message]
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
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=20220322100218.2158138-1-pasic@linux.ibm.com \
--to=pasic@linux.ibm.com \
--cc=bauerman@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=dgilbert@interlog.com \
--cc=hch@infradead.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
/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