[lkml]   [2012]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH c/r -mm] c/r: prctl: Simplify PR_SET_MM on mm::code/data assignment
On Mon, Apr 16, 2012 at 3:55 PM, Cyrill Gorcunov <> wrote:
> The mm::start_code, end_code, start_data, end_data members
> are set during startup of executable file and are not changed
> after.
> But the program itself might map new executable or/and data areas in
> time so the original values written into mm fields mentioned above
> might not have correspond VMA area at all, thus if one try to
> use this prctl codes without underlied VMA, the error will be
> returned.

Hrm, what is the utility of these fields then? If they're not "real",
should the kernel even bother tracking it at all? (Or, should it be
fixed to actually do something useful?)


Kees Cook
ChromeOS Security

 \ /
  Last update: 2012-04-17 18:29    [W:0.068 / U:5.556 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site