Searched refs:setgid (Results 1 – 25 of 32) sorted by relevance
12
6 its parent did not have. The most obvious examples are setuid/setgid27 been done without the execve call. For example, the setuid and setgid55 escalate its privileges by directly attacking setuid, setgid, and
95 int setgid; member253 opts->setgid = 0; in parse_mount_options()293 opts->setgid = 1; in parse_mount_options()411 if (opts->setgid) in devpts_show_options()580 inode->i_gid = opts->setgid ? opts->gid : current_fsgid(); in devpts_pty_new()
295 setgid(NO_POLICY_USER); in main()310 setgid(RESTRICTED_PARENT); in main()
75 a setgid file is written to. This is a security measure. The kernel has been78 to run mandatory lock candidates with setgid privileges.169 permissions (remove the setgid bit) before trying to read or write to it.
44 setgid[=gid] Same as above, but for gid.
102 ret = setgid(0); in change_to_userns()
171 if (setgid(0) != 0) { in create_and_enter_userns()
174 COND_SYSCALL(setgid);
65 46 32 setgid sys_setgid1666 46 64 setgid sys_setgid
49 46 32 setgid - compat_sys_s390_setgid16223 214 64 setgid sys_setgid -
49 46 32 setgid - sys_setgid16223 214 64 setgid sys_setgid -
114 104 n32 setgid sys_setgid
114 104 n64 setgid sys_setgid
58 46 o32 setgid sys_setgid
49 37 common setgid sys_setgid
152 138 common setgid sys_setgid
117 106 common setgid __x64_sys_setgid
56 46 common setgid sys_setgid16
69 ``setgid`` bit set, in which case it takes the ``gid`` from the70 parent directory, and also gets the ``setgid`` bit set if it is
59 46 common setgid sys_setgid
60 46 common setgid sys_setgid16
56 46 common setgid sys_setgid
140 132 common setgid sys_setgid
