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

2021-10-04 Thread Stefan Agner
On 2021-09-30 18:09, Andre Przywara wrote: > On Tue, 28 Sep 2021 10:01:40 +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

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

2021-09-30 Thread Andre Przywara
On Tue, 28 Sep 2021 10:01:40 +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 after read

[PATCH] nvme: invalidate correct memory range after read

2021-09-28 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