Re: [PATCH v3 1/5] mm: Make per-VMA locks available universally
Suren Baghdasaryan <[email protected]> Mon, 3 Aug 2026 12:43:43 -0700
| Newsgroups | org.kvack.linux-mm,org.kernel.vger.linux-kernel,org.kernel.vger.netdev |
|---|---|
| Message-ID | <CAJuCfpEaYgMx0HF8SDRPOfBJusdyAiJOM3S0TRjeFGwtmSHj8Q@mail.gmail.com> |
On Mon, Aug 3, 2026 at 12:34=E2=80=AFPM Jann Horn <[email protected]> wrote: > > On Sun, Aug 2, 2026 at 11:55=E2=80=AFPM Suren Baghdasaryan <surenb@google= .com> wrote: > > The per-VMA locks have been around for several years. They've had some > > bugs worked out of them and have seen quite wide use. However, they > > are still only available when architectures explicitly enable them. > > Remove the conditional compilation around the per-VMA locks, making > > them available on all architectures and configs. > > Reviewed-by: Jann Horn <[email protected]> > > I've grepped around in arch-specific code in the architectures that > weren't already opted in to look for stuff that takes the mmap lock in > write mode and manually mutates VMAs, and couldn't find anything, so I > think this is correct. Thanks Jann!