mmap() bug in 2.1.106

Paul Gortmaker (paul@rasty.ph.unimelb.edu.au)
Fri, 19 Jun 1998 05:12:34 +1000 (EST)


For all intents and purposes, I think the two lines:

ptr = (void*)mmap(0, size, prot, mapping, fd, 0);

and

ptr = (void *)syscall(SYS_mmap, 0, size, prot, mapping, fd, 0);

should behave identically. However, in 2.1.106 (and most likely
other 2.1.x) the latter ends up permanently in D state and the load
climbs up to the next integer value. Need to reboot to kill 'em.

Info from "ps -l" shows the process stuck in down_failed (presumably
for the mmap semaphore). Arguments to the latter are irrelevant, and
aren't actually even necessary to see the problem.

Just came across this now while running some abuse tests. Doesn't
happen in 2.0.34

Paul.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu