Re: [PATCH v3 0/2] sys/prctl: expose TASK_SIZE value to userspace

2019-05-03 Thread Yury Norov
On Fri, May 03, 2019 at 05:57:31PM -0400, Rafael Aquini wrote: > On Fri, May 03, 2019 at 01:49:12PM -0700, Yury Norov wrote: > > On Fri, May 03, 2019 at 02:10:19PM -0400, Joel Savitz wrote: > > > In the mainline kernel, there is no quick mechanism to get the virtual > > > memory size of the current

Re: [PATCH v3 0/2] sys/prctl: expose TASK_SIZE value to userspace

2019-05-03 Thread Rafael Aquini
On Fri, May 03, 2019 at 01:49:12PM -0700, Yury Norov wrote: > On Fri, May 03, 2019 at 02:10:19PM -0400, Joel Savitz wrote: > > In the mainline kernel, there is no quick mechanism to get the virtual > > memory size of the current process from userspace. > > > > Despite the current state of affairs,

Re: [PATCH v3 0/2] sys/prctl: expose TASK_SIZE value to userspace

2019-05-03 Thread Yury Norov
On Fri, May 03, 2019 at 02:10:19PM -0400, Joel Savitz wrote: > In the mainline kernel, there is no quick mechanism to get the virtual > memory size of the current process from userspace. > > Despite the current state of affairs, this information is available to the > user through several means, on

[PATCH v3 0/2] sys/prctl: expose TASK_SIZE value to userspace

2019-05-03 Thread Joel Savitz
In the mainline kernel, there is no quick mechanism to get the virtual memory size of the current process from userspace. Despite the current state of affairs, this information is available to the user through several means, one being a linear search of the entire address space. This is an ineffic