Revision 80ef4464d5e27408685e609d389663aad46644b9 authored by Robert Richter on 20 March 2019, 18:57:23 UTC, committed by Joerg Roedel on 22 March 2019, 11:01:58 UTC
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@vger.kernel.org> # 4.20+
Fixes: bee60e94a1e2 ("iommu/iova: Optimise attempts to allocate iova from 32bit address range")
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Robert Richter <rrichter@marvell.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
1 parent 4e50ce0
| File | Mode | Size |
|---|---|---|
| .gitignore | -rw-r--r-- | 44 bytes |
| Kconfig | -rw-r--r-- | 3.4 KB |
| Makefile | -rw-r--r-- | 4.1 KB |
| blacklist.c | -rw-r--r-- | 4.0 KB |
| blacklist.h | -rw-r--r-- | 84 bytes |
| blacklist_hashes.c | -rw-r--r-- | 166 bytes |
| blacklist_nohashes.c | -rw-r--r-- | 122 bytes |
| system_certificates.S | -rw-r--r-- | 828 bytes |
| system_keyring.c | -rw-r--r-- | 8.0 KB |
Computing file changes ...
