Using remap_pfn_range() to increase total_vm beyond RLIMIT_AS

[Earl Chew]

remap_pfn_range() is defined in mm/memory.c and as far as I
can tell, does _not_ cause total_vm or reserved_vm to be updated.

Is this right?


RLIMIT_AS is only checked against total_vm in mm/mmap.c in the function
may_expand_vm().

I think this means that a device driver can map pages into
a process and thus effectively increase address space of
a process above and beyond the limit set by RLIMIT_AS.

Am I reading the code correctly?


Earl


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/