From: "Michal Koutný" <mkoutny@suse.com>
To: Dave Chinner <david@fromorbit.com>
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] memcg: calling reclaim_high(GFP_KERNEL) in GFP_NOFS context deadlocks
Date: Fri, 30 Sep 2022 14:18:56 +0200 [thread overview]
Message-ID: <YzbesGeUkX3qwqj8@blackbook> (raw)
In-Reply-To: <20220929222006.GI3600936@dread.disaster.area>
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
On Fri, Sep 30, 2022 at 08:20:06AM +1000, Dave Chinner <david@fromorbit.com> wrote:
> Fixes: b3ff92916af3 ("mm, memcg: reclaim more aggressively before high allocator throttling")
Perhaps you meant this instead?
Fixes: c9afe31ec443 ("memcg: synchronously enforce memory.high for large overcharges")
Thanks,
Michal
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next parent reply other threads:[~2022-09-30 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220929215440.1967887-1-david@fromorbit.com>
[not found] ` <20220929222006.GI3600936@dread.disaster.area>
2022-09-30 12:18 ` Michal Koutný [this message]
[not found] ` <20220930220834.GK3600936@dread.disaster.area>
2022-10-03 15:08 ` Michal Koutný
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=YzbesGeUkX3qwqj8@blackbook \
--to=mkoutny@suse.com \
--cc=cgroups@vger.kernel.org \
--cc=david@fromorbit.com \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
/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