From: Michal Hocko <mhocko@suse.com>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"david@redhat.com" <david@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"mgorman@techsingularity.net" <mgorman@techsingularity.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"quic_pkondeti@quicinc.com" <quic_pkondeti@quicinc.com>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"quic_charante@quicinc.com" <quic_charante@quicinc.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"quic_cgoldswo@quicinc.com" <quic_cgoldswo@quicinc.com>
Subject: Re: [RESEND PATCH V2] mm: page_alloc: unreserve highatomic page blocks before oom
Date: Tue, 23 Jan 2024 11:05:13 +0100 [thread overview]
Message-ID: <Za-PWcwmHFl3wmth@tiehlicka> (raw)
In-Reply-To: <01010dd280badd149291cf4d2a4a88847113cf6d.camel@infinera.com>
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
next prev parent reply other threads:[~2024-01-23 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 10:57 Charan Teja Kalla
2023-11-24 10:59 ` David Rientjes
2024-01-18 17:23 ` Joakim Tjernlund
2024-01-22 17:41 ` Greg KH
[not found] ` <PH0PR10MB461565CEE892267025BC697BF4752@PH0PR10MB4615.namprd10.prod.outlook.com>
2024-01-22 23:04 ` Greg KH
2024-01-22 23:14 ` Joakim Tjernlund
2024-01-23 10:05 ` Michal Hocko [this message]
2024-01-23 11:08 ` Joakim Tjernlund
2024-01-23 11:24 ` Michal Hocko
2024-01-27 0:31 ` gregkh
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=Za-PWcwmHFl3wmth@tiehlicka \
--to=mhocko@suse.com \
--cc=Joakim.Tjernlund@infinera.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=quic_cgoldswo@quicinc.com \
--cc=quic_charante@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=stable@vger.kernel.org \
--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