linux-kernel - Re: [PATCH -mm 0/2] memcg: deuglify mm_update_next

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: <20240626122456.a9eb021e4ccbfbb1b6b93d1c@linux-foundation.org>
Date: Wed, 26 Jun 2024 12:24:56 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Michal Hocko <mhocko@...e.com>, Christian Brauner <brauner@...nel.org>,
 "Eric W. Biederman" <ebiederm@...ssion.com>, Jens Axboe <axboe@...nel.dk>,
 Jinliang Zheng <alexjlzheng@...cent.com>, Mateusz Guzik
 <mjguzik@...il.com>, Matthew Wilcox <willy@...radead.org>, Tycho Andersen
 <tandersen@...flix.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm 0/2] memcg: deuglify mm_update_next_owner()

On Wed, 26 Jun 2024 17:28:35 +0200 Oleg Nesterov <oleg@...hat.com> wrote:

> On top of mm-optimize-the-redundant-loop-of-mm_update_owner_next.patch

What should we do with
mm-optimize-the-redundant-loop-of-mm_update_owner_next.patch?  It
prevents a hard lockup splat so I'm inclined to merge it into 6.10-rcX
and cc:stable.  Further improvements (this series) can be made in the
normal fashion?