> > 3rd Problem: one uid/gid process-wide
> > All the ID (uid/guid/euid/egid/...) must be process wide. The problem
> > is similar to the signal handler. I think one should again keep the
> > information exclusively in the master thread and have all others refer
> > to this information.
> No, it would be another "clone" option.
You dont want it in kernel space. Not unless you plan to lock uid/gid access
and make them atomic. Think about things like file operations where the uid
changes under you on another CPU as you walk a directory tree checking
Quota looks even more horrible.
Its also very rare and not a performance case to push into glibc
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Sep 07 2000 - 21:00:12 EST