In article <38FDE239.34B92DDB@sgi.com> you wrote:
> When the kernel goes to 32-bit pids (if it hasn't already,
> does it know to skip from 0xfffff000 to 0? More importantly -- the
> "relevant mailing lists" aren't read by system administrators who
> might try assigning UID's like -5000 or -4000 or their equivalent
> unsigned values. Maybe we should just treat pids and uid's, etc as
^^^^^
> consistent 31 bit values? Seems less error prone/confusing in the
> long run.
[snip]
> Not on a 64 bit machine -- but I guess return values will be
> 64 bit as well there. I guess I still don't like the inconsistency for
> pid's and uid's that are said to be 32 unsigned bits but really aren't.
PIDs are signed int and currently limited to 0x8000, so they don't
have a problem.
UIDs are unsigned int. The only calls that return uid_t (getuid and
geteuid) cannot fail, so there's no problem here either.
What is "etc" above? We can be careful when adding new system calls so
we don't run into this in the future.
Regards,
Borislav
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:15 EST