1SETFSUID(2) Linux Programmer's Manual SETFSUID(2)
2
3
4
6 setfsuid - set user identity used for file system checks
7
9 #include <unistd.h> /* glibc uses <sys/fsuid.h> */
10
11 int setfsuid(uid_t fsuid);
12
14 The system call setfsuid() sets the user ID that the Linux kernel uses
15 to check for all accesses to the file system. Normally, the value of
16 fsuid will shadow the value of the effective user ID. In fact, when‐
17 ever the effective user ID is changed, fsuid will also be changed to
18 the new value of the effective user ID.
19
20 Explicit calls to setfsuid() and setfsgid(2) are usually used only by
21 programs such as the Linux NFS server that need to change what user and
22 group ID is used for file access without a corresponding change in the
23 real and effective user and group IDs. A change in the normal user IDs
24 for a program such as the NFS server is a security hole that can expose
25 it to unwanted signals. (But see below.)
26
27 setfsuid() will succeed only if the caller is the superuser or if fsuid
28 matches either the real user ID, effective user ID, saved set-user-ID,
29 or the current value of fsuid.
30
32 On success, the previous value of fsuid is returned. On error, the
33 current value of fsuid is returned.
34
36 This system call is present in Linux since version 1.2.
37
39 setfsuid() is Linux-specific and should not be used in programs
40 intended to be portable.
41
43 When glibc determines that the argument is not a valid user ID, it will
44 return -1 and set errno to EINVAL without attempting the system call.
45
46 Note that at the time this system call was introduced, a process could
47 send a signal to a process with the same effective user ID. Today sig‐
48 nal permission handling is slightly different.
49
50 The original Linux setfsuid() system call supported only 16-bit user
51 IDs. Subsequently, Linux 2.4 added setfsuid32() supporting 32-bit IDs.
52 The glibc setfsuid() wrapper function transparently deals with the
53 variation across kernel versions.
54
56 No error messages of any kind are returned to the caller. At the very
57 least, EPERM should be returned when the call fails (because the caller
58 lacks the CAP_SETUID capability).
59
61 kill(2), setfsgid(2), capabilities(7), credentials(7)
62
64 This page is part of release 3.53 of the Linux man-pages project. A
65 description of the project, and information about reporting bugs, can
66 be found at http://www.kernel.org/doc/man-pages/.
67
68
69
70Linux 2010-11-22 SETFSUID(2)