From: Sven van Ashbrook <svenva@chromium.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
Karthikeyan Ramasubramanian <kramasub@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Brian Geffon <bgeffon@google.com>,
stable@vger.kernel.org,
Curtis Malainey <cujomalainey@chromium.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
Date: Wed, 21 Feb 2024 10:40:31 -0500 [thread overview]
Message-ID: <CAG-rBij0di69U38JzWK+rWHOn7AoX1OOBtVUZ4TqLCfysMFsEQ@mail.gmail.com> (raw)
In-Reply-To: <ea61304a-81a4-402d-9d71-b13b9ac89ed2@suse.cz>
On Wed, Feb 21, 2024 at 4:58 AM Vlastimil Babka <vbabka@suse.cz> wrote:
>
> Thanks a lot, seems this can indeed happen even in 6.8-rc5. We're
> mishandling the case where compaction is skipped due to lack of __GFP_IO,
> which is indeed cleared in suspend/resume. I'll create a fix.
I'm really grateful for the engagement here !!
> Please don't
> hesitate to report such issues the next time, even if not fully debugged :)
>
Will do :)
next prev parent reply other threads:[~2024-02-21 15:40 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 ` 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 [this message]
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
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=CAG-rBij0di69U38JzWK+rWHOn7AoX1OOBtVUZ4TqLCfysMFsEQ@mail.gmail.com \
--to=svenva@chromium.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=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=vbabka@suse.cz \
/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