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  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]
Date:   Fri, 17 Jul 2020 09:42:43 -0400 (EDT)
From:   Mathieu Desnoyers <>
To:     Nicholas Piggin <>
Cc:     Peter Zijlstra <>,
        Anton Blanchard <>,
        Arnd Bergmann <>,
        linux-arch <>,
        linux-kernel <>,
        linux-mm <>,
        linuxppc-dev <>,
        Andy Lutomirski <>,
        Andy Lutomirski <>, x86 <>
Subject: Re: [RFC PATCH 4/7] x86: use exit_lazy_tlb rather than

----- On Jul 16, 2020, at 7:26 PM, Nicholas Piggin wrote:
> membarrier does replace barrier instructions on remote CPUs, which do
> order accesses performed by the kernel on the user address space. So
> membarrier should too I guess.
> Normal process context accesses like read(2) will do so because they
> don't get filtered out from IPIs, but kernel threads using the mm may
> not.

But it should not be an issue, because membarrier's ordering is only with respect
to submit and completion of io_uring requests, which are performed through
system calls from the context of user-space threads, which are called from the
right mm.



Mathieu Desnoyers
EfficiOS Inc.

Powered by blists - more mailing lists