Re: [PATCH v2] x86/sgx: use vm_flags_t for vm_prot_bits
TwT pupupu <[email protected]>
| Newsgroups | org.kernel.vger.linux-sgx,org.kernel.vger.linux-kernel,org.kvack.linux-mm |
|---|---|
| Message-ID | <CAGPELS7JdxTY5hthmTyU_yDxdG7xR2k0hoA1ZqV_Lj+8LEkO2w@mail.gmail.com> |
Sorry about that, I'll make sure to reply to the list. On Thu, Jan 23, 2026 at 4:57 AM Huang, Kai <[email protected]> wrote: > Hmm I was actually just pointing out, but not suggesting, since I am not > sure (honestly). Sorry for the misunderstanding. > With vm_flags_t I think "theoretically" it could stop being integer type > someday. But I guess the advantage is when someone does that that can > trigger build error here (so that we can be aware) which perhaps isn't a > bad thing? You're right, the build error would be a useful early warning if vm_flags_t ever becomes incompatible. I'm fine either way, let me know if you'd prefer keeping unsigned long and I'll send a v3.