Re: [PATCH 11/13] mm/mlock: convert mlock code to use vma_flags_t
"Zi Yan" <[email protected]> Wed, 08 Jul 2026 22:01:22 -0400
| Newsgroups | gmane.linux.ports.tegra,gmane.linux.ports.mips,gmane.linux.kernel,gmane.linux.ports.ppc64.devel,gmane.comp.video.dri.devel,gmane.linux.ports.arm.kernel,gmane.linux.kernel.samsung-soc,gmane.comp.freedesktop.xorg.drivers.intel,gmane.linux.ports.arm.msm,gmane.comp.freedesktop.xorg.drivers.freedreno,gmane.comp.freedesktop.xorg.nouveau,gmane.linux.ports.arm.rockchip,gmane.comp.emulators.xen.devel,gmane.linux.kernel.aio.general,gmane.linux.file-systems,gmane.linux.kernel.mm,gmane.linux.sound |
|---|---|
| Message-ID | <[email protected]> |
On Mon Jun 29, 2026 at 3:25 PM EDT, Lorenzo Stoakes wrote: > Replace use of the legacy vm_flags_t flags with vma_flags_t values > throughout the mlock logic. > > Additionally update comments to reflect the changes to be consistent. > > No functional change intended. > > Signed-off-by: Lorenzo Stoakes <[email protected]> > --- > mm/mlock.c | 86 +++++++++++++++++++++++++++++------------------------- > 1 file changed, 46 insertions(+), 40 deletions(-) > LGTM. What confused me when I was reading the code is VMA_LOCKED_MASK and VMA_LOCKED_BIT, since both share the same prefix VMA_LOCKED. Before looking at the definition of VMA_LOCKED_MASK, I was wondering when to use _BIT or _MASK. But it is just a naming thing. Anyway, Reviewed-by: Zi Yan <[email protected]> --=20 Best Regards, Yan, Zi