Andrew Morton wrote:
>Can you explain the bug a bit more completely? AFACIT, `bytes' here was
>always in the range 0 .. PAGE_CACHE_SIZE, so how can it have caused large
>amounts of the stack segment to have been faulted in?
'buf' is not page-aligned, so 'buf' + 'bytes' can touch the next page,
which may not be mapped. In fact, if 'buf' points to the *last* valid
mapped page (before the stack), and the stack ulimit is unlimited, the
VM_GROWSDOWN logic considers this access a request to grow the stack
down to this very page ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
Linux on zSeries Development
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
