Re: [PATCH] memfd_secret: use unsigned int rather than long as syscall flags type
Yury Norov <[email protected]>
| Newsgroups | org.01.lists.linux-nvdimm,dev.linux.lists.nvdimm,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-riscv,org.kernel.vger.linux-api,org.kernel.vger.linux-arch,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kvack.linux-mm |
|---|---|
| Message-ID | <20210331215218.GA3437@yury-ThinkPad> |
On Wed, Mar 31, 2021 at 05:23:45PM +0300, Mike Rapoport wrote: > From: Mike Rapoport <[email protected]> > > Yuri Norov says: > > If parameter size is the same for native and compat ABIs, we may > wire a syscall made by compat client to native handler. This is > true for unsigned int, but not true for unsigned long or pointer. > > That's why I suggest using unsigned int and so avoid creating compat > entry point. > > Use unsigned int as the type of the flags parameter in memfd_secret() > system call. > > Signed-off-by: Mike Rapoport <[email protected]> Acked-by: Yury Norov <[email protected]> _______________________________________________ Linux-nvdimm mailing list -- [email protected] To unsubscribe send an email to [email protected]