On 11/3/2023 9:33 AM, Jeffrey Hugo wrote:
MAX_ORDER was redefined so that valid allocations to the page allocator are in the range of 0..MAX_ORDER, inclusive in the commit 23baf831a32c ("mm, treewide: redefine MAX_ORDER sanely").We are treating MAX_ORDER as an exclusive value, and thus could be requesting larger allocations. Update our use to match the redefinition of MAX_ORDER. Signed-off-by: Jeffrey Hugo <quic_jh...@quicinc.com> Reviewed-by: Pranjal Ramajor Asha Kanojiya <quic_pkano...@quicinc.com> Reviewed-by: Carl Vanderlip <quic_ca...@quicinc.com>
Applied to drm-misc-next -Jeff
