From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
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>,
"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: Mon, 22 Jan 2024 23:14:59 +0000 [thread overview]
Message-ID: <01010dd280badd149291cf4d2a4a88847113cf6d.camel@infinera.com> (raw)
In-Reply-To: <2024012210-outshoot-dragonish-fe8e@gregkh>
On Mon, 2024-01-22 at 15:04 -0800, Greg KH wrote:
> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
haha, serves me right :) (note to self, do not use webmail for Linux stuff ...)
>
> http://daringfireball.net/2007/07/on_top
>
> On Mon, Jan 22, 2024 at 10:49:32PM +0000, Joakim Tjernlund wrote:
> > Seems like I pasted the wrong commit(sorry), should be: ac3f3b0a55518056bc80ed32a41931c99e1f7d81
> > I only see that one in master.
>
> And what kernels have you tested this on? How far back should it go?
I am testing it now in latest 5.15.x but the jury is still out. No
OOM since a few days but the error does not happen often.
>
> 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.
Jocke
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2024-01-22 23:15 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 [this message]
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=01010dd280badd149291cf4d2a4a88847113cf6d.camel@infinera.com \
--to=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=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