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]
Date: Mon, 22 Jan 2024 23:14:59 +0000
From: Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
To: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC: "david@...hat.com" <david@...hat.com>, "mhocko@...e.com"
	<mhocko@...e.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, 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ