> I understand what the CLONE_FS flag does -- my question was whether such
> a cloned task, when it makes a system call to sys_chdir, should get a
> private copy. The present sys_chdir code doesn't check whether the task
> is a clone or not, so one clone changing directory would change it for
> all clones.
>
> Is this the intended behavior?
yes, whats the problem with it? Also, sys_chdir() should _not_ check
wether this is a 'clone' or not. This kind of special-casing makes those
two-tier threading systems so ugly ...
-- mingo