Re: [PATCH] swiotlb: check dynamically allocated TLB address before decrypting

From: Petr Tesařík
Date: Mon Oct 30 2023 - 10:09:19 EST


Hi Christoph,

On Mon, 30 Oct 2023 14:31:12 +0100
Christoph Hellwig <hch@xxxxxx> wrote:

> I'm trying to review it properly this week. It was defintively too big
> to just rush it into 6.6 in the last few days.

Thank you for the answer. This is OK. Let me give a bit of background.

The bug was reported by Michael Kelley to me, while I temporarily lost
access to my @huaweicloud.com mailbox. Then I was not able to add him
in a Reported-by: header, because this was a private email, which could
not be referred by a Closes: header.

Anyway, Michael explained in that private email that the threat is more
or less theoretical, because environments where set_memory_decrypted()
actually does something are unlikely to have physical address
constraints for the bounce buffer.

But maybe we should add a CC: stable@xxxxxxxxxxxxxxx nevertheless.

Petr T