Re: [PATCH 11/13] mm/mlock: convert mlock code to use vma_flags_t
"Zi Yan" <[email protected]>
| Newsgroups | org.kernel.vger.linux-samsung-soc,dev.linux.lists.virtualization,org.freedesktop.lists.dri-devel,org.freedesktop.lists.intel-gfx,org.freedesktop.lists.intel-xe,org.freedesktop.lists.nouveau,org.infradead.lists.linux-rockchip,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-fbdev,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-mips,org.kernel.vger.linux-sound,org.kernel.vger.linux-tegra,org.kvack.linux-mm,org.ozlabs.lists.linuxppc-dev,org.xenproject.lists.xen-devel |
|---|---|
| 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]> -- Best Regards, Yan, Zi