Re: [PATCH v2] nvme: invalidate correct memory range after read

2021-10-13 Thread Tom Rini
On Mon, Oct 04, 2021 at 11:24:51AM +0200, Stefan Agner wrote: > The current code invalidates the range after the read buffer since the > buffer pointer gets incremented in the read loop. Use a temporary > pointer to make sure we have a pristine pointer to invalidate the > correct memory range afte

[PATCH v2] nvme: invalidate correct memory range after read

2021-10-04 Thread Stefan Agner
The current code invalidates the range after the read buffer since the buffer pointer gets incremented in the read loop. Use a temporary pointer to make sure we have a pristine pointer to invalidate the correct memory range after read. Fixes: 704e040a51d2 ("nvme: Apply cache operations on the DMA