>turns out, no global lock is necessary in do_brk(); both the
Fine.
>without the global lock. it's the general cases that appear in routines
>like mremap() that still need protection. i just didn't optimize the
Of course. I was talking only about the lock_kernel() in do_brk() (the
snapshot of code quoted by Linus).
For sys_mremap() the lock_kernel is needed before calling both
functions, because you can't assume as in sbrk that the mapping is
anonymous.
Andrea Arcangeli
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/