Searched refs:setgid (Results 1 – 25 of 37) sorted by relevance
12
64 ret = setgid(TEST_SET_NEW_ID); in TestMap()106 ret = setgid(TEST_SET_OLD_ID); in childFunc()
100 ret = setgid(TEST_SET_NEW_ID); in childFunc()126 ret = setgid(TEST_SET_OLD_ID); in ItUserContainer002()
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()
297 if (setgid(NO_POLICY_USER) < 0) in main()314 if (setgid(RESTRICTED_PARENT) < 0) in main()
169 EXPECT_EQ(setgid(65534), 0) in TEST()
106 if (setgid(0) != 0) in create_and_enter_ns()
171 if (setgid(0) != 0) { in create_and_enter_userns()
82 a setgid file is written to. This is a security measure. The kernel has been85 to run mandatory lock candidates with setgid privileges.176 permissions (remove the setgid bit) before trying to read or write to it.
109 ret = setgid(3000); in Child()123 ret = setgid(-1); in Child()
174 COND_SYSCALL(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 -
65 46 32 setgid sys_setgid1666 46 64 setgid sys_setgid
192 if (setgid(0)) in setid_userns_root()
114 104 n64 setgid sys_setgid
114 104 n32 setgid sys_setgid
58 46 o32 setgid sys_setgid
49 37 common setgid sys_setgid
117 106 common setgid sys_setgid
152 138 common setgid sys_setgid
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
56 46 common setgid sys_setgid