Re: [PATCH 1/2] dma-direct: set_memory_{en,de}crypted() take number of pages

From: Thiago Jung Bauermann
Date: Tue Jan 22 2019 - 17:39:05 EST



Lendacky, Thomas <Thomas.Lendacky@xxxxxxx> writes:

> On 1/22/19 3:17 PM, Thiago Jung Bauermann wrote:
>> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
>> index 355d16acee6d..bc78c37220ba 100644
>> --- a/kernel/dma/direct.c
>> +++ b/kernel/dma/direct.c
>> @@ -166,7 +166,7 @@ void *dma_direct_alloc_pages(struct device *dev, size_t size,
>>
>> ret = page_address(page);
>> if (force_dma_unencrypted()) {
>> - set_memory_decrypted((unsigned long)ret, 1 << get_order(size));
>> + set_memory_decrypted((unsigned long)ret, 1);
>
> The get_order() function will return the order for the specified size. To
> then get the number of pages you perform the shift as is being done. The
> change is definitely wrong since you are now hardcoding the page count to
> 1. The call to __dma_direct_alloc_pages() will allocate more than one page
> if the size is greater than a page.

<facepalm>

You are correct, of course. Sorry for the noise and thanks for explaining.

--
Thiago Jung Bauermann
IBM Linux Technology Center