From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Sachin Sant" <sachinp@linux.ibm.com>
Subject: Re: [PATCH] lazy tlb: consolidate lazy tlb mm switching fix
Date: Wed, 15 Nov 2023 13:25:47 +1000 [thread overview]
Message-ID: <CWZ2CN22QYP0.2XINI4TL0M712@wheely> (raw)
In-Reply-To: <340b4d49-df81-05ad-3753-c1e60ec0df06@csgroup.eu>
On Fri Oct 13, 2023 at 11:12 PM AEST, Christophe Leroy wrote:
>
>
> Le 07/06/2023 à 02:56, Nicholas Piggin a écrit :
> > Fix an upstream powerpc bug that was discovered with a WARN_ON added in
> > "lazy tlb: consolidate lazy tlb mm switching":
> >
> > Switching mm and tinkering with current->active_mm should be done with
> > irqs disabled. There is a path where exit_lazy_flush_tlb can be called
> > with irqs enabled:
> >
> > exit_lazy_flush_tlb
> > flush_type_needed
> > __flush_all_mm
> > tlb_finish_mmu
> > exit_mmap
> >
> > Which results in the switching being incorrectly with irqs enabled.
> >
> > Link: https://lore.kernel.org/linuxppc-dev/87a5xcgopc.fsf@mail.lhotse/T/#m105488939d0cd9f980978ed2fdeeb89bf731e673
> > Fixes: a665eec0a22e1 ("powerpc/64s/radix: Fix mm_cpumask trimming race vs k>
> >
> > I will send that fix upstream, which will end up conflicting with these.
> > The resolution will be to take akpm's side of the merge (with this patch).
> > Or drop the patch when it conflicts and I'll resend it rebased on the fix.
>
> This seems to badly conflict at the moment, is it still applicable ?
Been away, will have to check where all this ended up.
Thanks,
Nick
prev parent reply other threads:[~2023-11-15 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 0:56 Nicholas Piggin
2023-10-13 13:12 ` Christophe Leroy
2023-11-15 3:25 ` Nicholas Piggin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CWZ2CN22QYP0.2XINI4TL0M712@wheely \
--to=npiggin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox