[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250407113543.6a43461e397d58471e407323@linux-foundation.org>
Date: Mon, 7 Apr 2025 11:35:43 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Alexander Gordeev <agordeev@...ux.ibm.com>
Cc: Andrey Ryabinin <ryabinin.a.a@...il.com>, Hugh Dickins
<hughd@...gle.com>, Nicholas Piggin <npiggin@...il.com>, Guenter Roeck
<linux@...ck-us.net>, Juergen Gross <jgross@...e.com>, Jeremy Fitzhardinge
<jeremy@...p.org>, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
kasan-dev@...glegroups.com, sparclinux@...r.kernel.org,
xen-devel@...ts.xenproject.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org
Subject: Re: [PATCH v1 0/4] mm: Fix apply_to_pte_range() vs lazy MMU mode
On Mon, 7 Apr 2025 17:11:26 +0200 Alexander Gordeev <agordeev@...ux.ibm.com> wrote:
> This series is an attempt to fix the violation of lazy MMU mode context
> requirement as described for arch_enter_lazy_mmu_mode():
>
> This mode can only be entered and left under the protection of
> the page table locks for all page tables which may be modified.
>
> On s390 if I make arch_enter_lazy_mmu_mode() -> preempt_enable() and
> arch_leave_lazy_mmu_mode() -> preempt_disable() I am getting this:
>
> ...
>
Could you please reorganize this into two series? One series which
should be fast-tracked into 6.15-rcX and one series for 6.16-rc1?
And in the first series, please suggest whether its patches should be
backported into -stable and see if we can come up with suitable Fixes:
targets?
Thanks.
Powered by blists - more mailing lists