On Sun, Oct 26, 2014 at 02:43:52PM +0200, Laurent Pinchart wrote:

On Friday 24 October 2014 18:26:58 Michal Nazarewicz wrote:

quoted

On Fri, Oct 24 2014, Laurent Pinchart wrote:

quoted

Commit 95b0e655f914 ("ARM: mm: don't limit default CMA region only to
low memory") extended CMA memory reservation to allow usage of high
memory. It relied on commit f7426b983a6a ("mm: cma: adjust address limit
to avoid hitting low/high memory boundary") to ensure that the reserved
block never crossed the low/high memory boundary. While the
implementation correctly lowered the limit, it failed to consider the
case where the base..limit range crossed the low/high memory boundary
with enough space on each side to reserve the requested size on either
low or high memory.

Rework the base and limit adjustment to fix the problem. The function
now starts by rejecting the reservation altogether for fixed
reservations that cross the boundary, tries to reserve from high memory
first and then falls back to low memory.

Signed-off-by: Laurent Pinchart
[off-list ref]

Acked-by: Michal Nazarewicz <redacted>

Thank you. Can we get this series merged in v3.18-rc ?

Hello,

You'd better to resend whole series to Andrew.

Thanks.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>