Thanks so much ! We will stress test this on our side. We do this by exhausting memory and triggering many suspend/resume cycles. This reliably reproduces the problem (before this patch). Of course, as we all know, absence of evidence (no more stalls in stress tests) does not equal evidence of absence (stalls are gone in all code paths).
- Follow-Ups:
- Re: [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations
- From: Karthikeyan Ramasubramanian
- Re: [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations
- References:
- Prev by Date: Re: Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
- Next by Date: Re: [PATCH] ASoC: qcom: Fix uninitialized pointer dmactl
- Previous by thread: [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations
- Next by thread: Re: [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations
- Index(es):