Hi,

I'm fuzzing 3.4.0-rc5 (mostly with
http://code.google.com/p/iknowthis/), and got to the point that new
fuzzing threads/processes don't want to run any more. I have script
that periodically sends SIGCONT to all processes.

while [ 1 ]; do su test -c 'kill -CONT -1'; su test2 -c 'kill -CONT
-1'; su nobody -c 'kill -CONT -1'; sleep 300; done

It doesn't work:

root@ise-test:~/kern-fuz# ./cont.sh
su: Cannot fork user shell
su: Cannot fork user shell
su: Cannot fork user shell

root@ise-test:~/kern-fuz# strace -e mmap,clone su test -c 'kill -CONT
-1' 2>&1 | grep "= \-1"
clone(child_stack=0,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7fadf334f9f0) = -1 ENOMEM (Cannot allocate memory)
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = -1 ENOMEM (Cannot allocate memory)

It happens with every user (even newly created one), so it doesn't
seem to be any per-id rlimit.

root@ise-test:~/kern-fuz# su - test3
su: Cannot fork user shell
root@ise-test:~/kern-fuz# su - test3
$  <-- success
root@ise-test:~/kern-fuz# su - test3
su: Cannot fork user shell
root@ise-test:~/kern-fuz# su - test3
su: Cannot fork user shell
root@ise-test:~/kern-fuz# su - test3
su: Cannot fork user shell

Not sure how to debug it yet. I can run kdb/kgdb on it, but before I
dive into mm structures, I though I attach some proc files from your
entertainment, maybe you can spot anything interesting there.

Also, whatever happened on this machine, i.e. any syscall during
fuzzing, was invoked from non-root user.

-- 
Robert Święcki