SETREUID(2) Linux Programmer's Manual SETREUID(2)

NAME

setreuid, seteuid - set real and / or effective user ID

SYNOPSIS

#include <unistd.h> int setreuid(uid_t ruid, uid_t euid); int seteuid(uid_t euid);

DESCRIPTION

setreuid sets real and effective user ID's of the current process. Un-privileged users may change the real user ID to the effective user ID and vice-versa. Prior to Linux 1.1.37, the saved ID paradigm, when used with setreuid or seteuid was broken. Starting at 1.1.37, it is also possible to set the effec- tive user ID from the saved user ID. Only the super-user may make other changes. Supplying a value of -1 for either the real or effective user ID forces the system to leave that ID unchanged. Currently (libc-4.x.x), seteuid(euid) is functionally equivalent to setreuid(-1, euid). If the real user ID is changed or the effective user ID is set to a value not equal to the previous real user ID, the saved user ID will be set to the new effective user ID.

RETURN VALUE

On success, zero is returned. On error, -1 is returned, and errno is set appropriately.

ERRORS

EPERM The current process is not the super-user and changes other than (i) swapping the effective user ID with the real user ID or (ii) setting one to the value of the other or (iii) setting the effec- tive user ID to the value of the saved user ID was specified.

HISTORY

The setreuid function call appeared in BSD 4.2.

CONFORMING TO

BSD 4.3

SEE ALSO

getuid, setuid,






Linux 1.1.38 2nd August 1994 1


Top Master Index Keywords Functions


This manual page was brought to you by mjl_man V-2.0 /tr>
diff options
context:
space:
mode:
authorHeiner Kallweit <hkallweit1@gmail.com>2016-08-17 21:11:01 +0200
committerMark Brown <broonie@kernel.org>2016-08-18 11:15:16 +0100
commit02a595d5d6e4ecc0564ec31afb76202035a7591c (patch)
treee4ec99f150702f31fc5d6afb60586492b32dbd44
parent5090cc6ae2f79ee779e5faf7c8a28edf42b7d738 (diff)
spi: fsl-espi: eliminate spi nor flash read loop
The fsl-espi driver contains a read loop that implicitely assumes that the device to read from is a m25p80 SPI NOR flash (bytes 2 - 4 of the first write transfer are interpreted as 3 byte flash address). Now that we have such a read loop in the spi-nor driver and are able to correctly indicate the message size limit of the controller, the read loop can be removed from the fsl-espi driver. Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat