On Tue, Jan 29, 2019 at 04:38:36PM +0100, Jann Horn wrote: > > >> +#define IORING_MAX_ENTRIES 4096 > > > > > > Where does this constant come from? Should it really be exposed to > > > userspace? > > > > Seems pretty handy for the application to know what the limit is? > > The running kernel version might be different from the kernel version > whose headers the userspace code was compiled with. So if this is a > limit that might change at some point in the future, and you think > userspace wants to know the limit, some other API might be better. If it changes it will increase, so I'm not worried it is all that harmful. What might be useful is a specific error code if it is too large so that applications can check it. Just which one?
