Re: [PATCH v2 01/13] mm/vma: remove __private sparse decoration from vma_flags_t
Pedro Falcato <[email protected]>
| Newsgroups | org.kernel.vger.linux-sgx,dev.linux.lists.ntfs3,dev.linux.lists.nvdimm,org.freedesktop.lists.dri-devel,org.freedesktop.lists.intel-gfx,org.kernel.vger.keyrings,org.kernel.vger.linux-cxl,org.kernel.vger.linux-ext4,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-security-module,org.kernel.vger.linux-xfs,org.kvack.linux-mm,org.ozlabs.lists.linux-erofs |
|---|---|
| Message-ID | <e3qrulshyfrqkpihfb7prx2xyp5sn37aobccihw6r7vwwj2zm2@fh56mijhhk3c> |
On Thu, Jan 22, 2026 at 04:06:10PM +0000, Lorenzo Stoakes wrote: > We need to pass around these values and access them in a way that sparse > does not allow, as __private implies noderef, i.e. disallowing dereference > of the value, which manifests as sparse warnings even when passed around > benignly. > > Signed-off-by: Lorenzo Stoakes <[email protected]> Reviewed-by: Pedro Falcato <[email protected]> -- Pedro