Not sure what you mean by this. The posted exploit reliably
crashes my unmodified 2.0.32 from user mode.
> > ! stack=(unix_socket **)kmalloc(max_stack * sizeof(unix_socket **),
> > ! GFP_KERNEL);
>
> This is not good. With a very large set of fd's you can now have the kmalloc
> hang forever deadlocking the fd recovery. Use vmalloc and your idea is
> correct.
>
> (see 2.1.x)
Does this mean that if you _haven't_ increased NR_FILE, the
patch works? Otherwise, does anyone have a ready-to-apply
patch that fixes this for 2.0?
-- Erik Corry erik@arbat.com