From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "quic_charante@quicinc.com" <quic_charante@quicinc.com>
Cc: "david@redhat.com" <david@redhat.com>,
"mhocko@suse.com" <mhocko@suse.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>,
"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: Thu, 18 Jan 2024 17:23:58 +0000 [thread overview]
Message-ID: <3fe3b3edd33cd784071dd9b459d20a79605ec918.camel@infinera.com> (raw)
In-Reply-To: <1700823445-27531-1-git-send-email-quic_charante@quicinc.com>
Could this patch be backported to stable? I have seen similar OOMs with
reserved_highatomic:4096KB
Upstream commit: 04c8716f7b0075def05dc05646e2408f318167d2
Jocke
next prev parent reply other threads:[~2024-01-18 17:24 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 [this message]
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
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=3fe3b3edd33cd784071dd9b459d20a79605ec918.camel@infinera.com \
--to=joakim.tjernlund@infinera.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--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