[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190322093146.GA18669@8bytes.org>
Date: Fri, 22 Mar 2019 10:31:46 +0100
From: Joerg Roedel <joro@...tes.org>
To: Robert Richter <rrichter@...vell.com>
Cc: Robin Murphy <robin.murphy@....com>,
Ganapatrao Kulkarni <gkulkarni@...vell.com>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] iommu/iova: Fix tracking of recently failed iova
address
On Wed, Mar 20, 2019 at 06:57:23PM +0000, Robert Richter wrote:
> From: Robert Richter <rrichter@...vell.com>
> Subject: [PATCH v2] iommu/iova: Fix tracking of recently failed iova address
> size
>
> If a 32 bit allocation request is too big to possibly succeed, it
> early exits with a failure and then should never update max32_alloc_
> size. This patch fixes current code, now the size is only updated if
> the slow path failed while walking the tree. Without the fix the
> allocation may enter the slow path again even if there was a failure
> before of a request with the same or a smaller size.
>
> Cc: <stable@...r.kernel.org> # 4.20+
> Fixes: bee60e94a1e2 ("iommu/iova: Optimise attempts to allocate iova from 32bit address range")
> Signed-off-by: Robert Richter <rrichter@...vell.com>
> Reviewed-by: Robin Murphy <robin.murphy@....com>
> Signed-off-by: Robert Richter <rrichter@...vell.com>
> ---
> drivers/iommu/iova.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Applied, thanks.
Powered by blists - more mailing lists