On Mon 19-10-20 08:32:34, pintu@xxxxxxxxxxxxxx wrote: [...] > b) This can be invoked from many places so we are adding the logging at > wrong layer? > If so, any other better places which can be explored? dup_mmap? > c) Adding logging at kernel layer is not the right approach to tackle this > problem ? > > d) Another thing we can do is, update the man page with more detailed > information about this commitment overflow ? This is a good thing in general > e) May be returning ENOMEM (Cannot allocate memory) from VM path is slightly > misleading for user space folks even though there are enough memory? > => Either we can introduce ENOVMEM (Cannot create virtual memory mapping) > => Or, update the documentation with approach to further debug this issue? No, it is close to impossible to add a new error code for interface that is used so heavily. -- Michal Hocko SUSE Labs
