[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2419C44A-2467-4FB2-A6D6-BA49856A9D85@vmware.com>
Date: Tue, 17 Oct 2023 22:29:22 +0000
From: Nadav Amit <namit@...are.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: Uros Bizjak <ubizjak@...il.com>,
the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andy Lutomirski <luto@...nel.org>,
Brian Gerst <brgerst@...il.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
"H . Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Nick Desaulniers <ndesaulniers@...gle.com>
Subject: Re: [PATCH v2 -tip] x86/percpu: Use C for arch_raw_cpu_ptr()
> On Oct 18, 2023, at 1:06 AM, Nadav Amit <namit@...are.com> wrote:
>
>
>
>> On Oct 18, 2023, at 12:53 AM, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>>
>>
>> but none of this should even matter, because by the time we actually
>> *schedule* that thread, we'll set active_mm to the right thing.
>>
>> Can anybody see what's up?
>
> Could it be related to exec_mmap() -> exec_mm_release() -> mm_release() -> deactivate_mm() ?
I am probably completely wrong. Sorry for the noise.
Powered by blists - more mailing lists