linux-kernel - Re: [RESEND PATCH V2] mm: page_alloc: unreserve highatomic page blocks before oom

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: <Za-PWcwmHFl3wmth@tiehlicka>
Date: Tue, 23 Jan 2024 11:05:13 +0100
From: Michal Hocko <mhocko@...e.com>
To: Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
Cc: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
	"david@...hat.com" <david@...hat.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"hannes@...xchg.org" <hannes@...xchg.org>,
	"mgorman@...hsingularity.net" <mgorman@...hsingularity.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"quic_pkondeti@...cinc.com" <quic_pkondeti@...cinc.com>,
	"vbabka@...e.cz" <vbabka@...e.cz>,
	"quic_charante@...cinc.com" <quic_charante@...cinc.com>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	"quic_cgoldswo@...cinc.com" <quic_cgoldswo@...cinc.com>
Subject: Re: [RESEND PATCH V2] mm: page_alloc: unreserve highatomic page
 blocks before oom

On Mon 22-01-24 23:14:59, Joakim Tjernlund wrote:
> On Mon, 2024-01-22 at 15:04 -0800, Greg KH wrote:
[...]
> > For mm patches like this, that are not explicitly tagged by the
> > maintainers to be included in the stable tree, we need their ack to be
> > able to apply them based on their requests.  So can you get that for
> > this change and provide tested patches, we will be glad to queue them
> > up.
> 
> I asked the author and he acknowledged it could be backported. Charan, please chim in.

The patch itself is safe to backport but it would be great to here what
kind of problem you are trying to deal with. The issue fixed by this
patch is more on a corner case side than something that many users
should see. Could you share oom report you are seeing?
-- 
Michal Hocko
SUSE Labs