No subject

example, when running the test case from #8316, OOM killer does not kill 
browse, but just kills the gnash instance which is chewing up RAM.

>     - the warnings in the ramfs and tmpfs code about the deadlocks that
>       tmpfsen can generate under low- or no-memory conditions.

I have yet to see an actual deadlock. What I saw when trying to
reproduce #3816 is that the OOM killer just takes a very very long
time to kick in.

>     - whether our kernel "overcommits" when allocation requests are made?

By default vm.overcommit_memory is set to 0 which will refuse "Obvious
overcommits of address space". I will try setting this to 3 along with
vm.overcommit_ratio to 0 to force no overcommit at all and see how the 
system reacts.

~Deepak