NULL task->files problem?

Bill Hawes (whawes@star.net)
Sat, 04 Oct 1997 13:49:50 -0400

Is there any reason why a process needs to have a task->files structure
to fork another process? I want the nfs lockd and rpciod processes to
not hold their parent's files open, but the code in do_fork() isn't
checking for task->files being NULL. So if I do an exit_files in lockd,
this causes an oops if the rpciod process hasn't already been started.

I suppose I could defer doing the exit_files(), but it seems it would be
easier to have do_fork() check for NULL. Any suggestions on this?

Regards,
Bill