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: <afd9f99f-f49a-41c7-b987-9e59a9d296ad@suse.cz>
Date: Sun, 27 Oct 2024 20:40:14 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: Yu Zhao <yuzhao@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>,
 Link Lin <linkl@...gle.com>
Cc: David Rientjes <rientjes@...gle.com>, linux-mm@...ck.org,
 linux-kernel@...r.kernel.org, Johannes Weiner <hannes@...xchg.org>,
 Zi Yan <ziy@...dia.com>
Subject: Re: [PATCH mm-unstable v2] mm/page_alloc: keep track of free
 highatomic

On 10/26/24 06:40, Yu Zhao wrote:
> On Fri, Oct 25, 2024 at 10:24 PM Andrew Morton
> <akpm@...ux-foundation.org> wrote:
>>
>> Is a -stable backport needed?
>>
>> If so, is a Fixes: target identifiable?
> 
> The code has been there for many years, and we only recently noticed
> the problem from Link's repro. So it doesn't look like a stable
> material.

The stable backportability would be limited as there's a prerequisity on the
"mm: page_alloc: freelist migratetype hygiene" patchset from half a year ago
- patch applicability wise and importantly functionality wise. Otherwise the
counter could drift easily.

However we could perhaps mark it for a 6.12 stable backport as that's
presumably the upcoming LTS.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ