linux-kernel - Re: [PATCH] mm/memory-failure: allow memory allocation from emergency reserves

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20240625130110.ae4f6c3265559d1b1f979a3b@linux-foundation.org>
Date: Tue, 25 Jun 2024 13:01:10 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Rui Qi <qirui.001@...edance.com>
Cc: linmiaohe@...wei.com, nao.horiguchi@...il.com, linux-mm@...ck.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/memory-failure: allow memory allocation from
 emergency reserves

On Tue, 25 Jun 2024 10:23:42 +0800 Rui Qi <qirui.001@...edance.com> wrote:

> we hope that memory errors can be successfully handled quickly, using
> __GFP_MEMALLOC can help us improve the success rate of processing
> under memory pressure, because to_kill struct is freed very quickly,
> so using __GFP_MEMALLOC will not exacerbate memory pressure for a long time,
> and  more memory will be freed after killed task exiting, which will also
> reduce memory pressure.

Has this been observed to improve behavior in some situation?  In
other words, please fully describe the observed runtime effects of this
change.