From: Vlastimil Babka <vbabka@suse.cz>
To: Sven van Ashbrook <svenva@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bgeffon@google.com, cujomalainey@chromium.org,
kramasub@chromium.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-sound@vger.kernel.org, perex@perex.cz,
stable@vger.kernel.org, tiwai@suse.com, tiwai@suse.de,
Michal Hocko <mhocko@kernel.org>,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations
Date: Mon, 26 Feb 2024 17:45:18 +0100 [thread overview]
Message-ID: <3b539d8d-e529-45b0-aa83-545248bc0670@suse.cz> (raw)
In-Reply-To: <CAG-rBijH3GaHN2zA2_cby-RsQCVHou-WjZnxudMebPrS9imgfg@mail.gmail.com>
On 2/26/24 17:09, Sven van Ashbrook wrote:
> Vlastimil,
>
> We noticed that this patch is now added to Andrew Morton's
> mm-hotfixes-unstable branch.
>
> How can we help to get this into mm-hotfixes-stable
> and from there, into mainline ?
A Tested-by: can't hurt, but of course you need to finish the testing first.
It's encouraging you didn't hit the bug yet anymore, thought!
> We are still stress-testing using low memory suspend. Anything else
> that is required, and we can help with?
I think that's already great enough, thanks!
> Sven
next prev parent reply other threads:[~2024-02-26 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240214170720.v1.1.Ic3de2566a7fd3de8501b2f18afa9f94eadb2df0a@changeid>
2024-02-19 11:36 ` Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case) Takashi Iwai
2024-02-19 11:40 ` Vlastimil Babka
2024-02-20 15:52 ` Sven van Ashbrook
2024-02-21 9:21 ` Takashi Iwai
2024-02-21 15:37 ` Sven van Ashbrook
2024-02-21 9:58 ` Vlastimil Babka
2024-02-21 15:40 ` Sven van Ashbrook
2024-02-21 11:43 ` [PATCH] mm, vmscan: prevent infinite loop for costly GFP_NOIO | __GFP_RETRY_MAYFAIL allocations Vlastimil Babka
2024-02-21 15:52 ` Sven van Ashbrook
2024-02-22 16:43 ` Karthikeyan Ramasubramanian
2024-02-26 16:09 ` Sven van Ashbrook
2024-02-26 16:45 ` Vlastimil Babka [this message]
2024-02-28 19:33 ` Karthikeyan Ramasubramanian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3b539d8d-e529-45b0-aa83-545248bc0670@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=cujomalainey@chromium.org \
--cc=kramasub@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-sound@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=svenva@chromium.org \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox