usertest for big write()s
push begin_trans/commit_trans down into syscalls

All tests pass

Variable declarations at top of function,
separate from initialization.

Use == 0 instead of ! for checking pointers.

Consistent spacing around {, *, casts.

Declare 0-parameter functions as (void) not ().

Integer valued functions return -1 on failure, 0 on success.

usertest that passes too many arguments, break exec

Remove the stack guard page.  Processes are now contiguous from 0 to proc->sz, which means our syscall argument validation is correct.  Add a pointer validation test and remove the stack test, which tested for the guard page.

increase PHYSTOP

put an invalid page below the stack
have fork() handle invalid pages

(maybe this never worked, but it works now)

group locks into structs they protect.
few naming nits.

the macro expansion of "char *cp;" turned into
char *(curproc[cpu()]);  which declares a dynamically
sized array of char* called curproc.

so then &cp == &(curproc[cpu()]) was actually a
stack variable as "expected".  it was one past the
end of the array, but the implicit alloca allocated
more than was necessary.

do not tell me that making cp a #define was a bad idea.
there are worse problems to fix.  more on that later.

test files with holes (not ok)

fix bug in test code of malloc

test malloc