Re: [PATCH -mm 0/2] memcg: deuglify mm_update_next_owner()

From: Andrew Morton
Date: Wed Jun 26 2024 - 15:25:04 EST

Next message: Shuah Khan: "Re: [PATCH v3] selftests/resctrl: Fix non-contiguous CBM for AMD"
Previous message: Masahiro Yamada: "Re: [PATCH v2] kbuild: scripts/gdb: bring the "abspath" back"
In reply to: Michal Hocko: "Re: [PATCH 2/2] memcg: mm_update_next_owner: move for_each_thread() into try_to_set_owner()"
Next in thread: Oleg Nesterov: "Re: [PATCH -mm 0/2] memcg: deuglify mm_update_next_owner()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, 26 Jun 2024 17:28:35 +0200 Oleg Nesterov <oleg@xxxxxxxxxx> 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?

Next message: Shuah Khan: "Re: [PATCH v3] selftests/resctrl: Fix non-contiguous CBM for AMD"
Previous message: Masahiro Yamada: "Re: [PATCH v2] kbuild: scripts/gdb: bring the "abspath" back"
In reply to: Michal Hocko: "Re: [PATCH 2/2] memcg: mm_update_next_owner: move for_each_thread() into try_to_set_owner()"
Next in thread: Oleg Nesterov: "Re: [PATCH -mm 0/2] memcg: deuglify mm_update_next_owner()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]