From 7e0f021a9aec35fd8e6725e87e3313b101d26f5e Mon Sep 17 00:00:00 2001 From: Tobias Klauser Date: Sun, 27 Jan 2008 11:37:44 +0100 Subject: Initial import (2.0.2-6) --- reference/C/MAN/getuid.htm | 98 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 reference/C/MAN/getuid.htm (limited to 'reference/C/MAN/getuid.htm') diff --git a/reference/C/MAN/getuid.htm b/reference/C/MAN/getuid.htm new file mode 100644 index 0000000..f76486f --- /dev/null +++ b/reference/C/MAN/getuid.htm @@ -0,0 +1,98 @@ +getuid + +
+
+
+
+
+
GETUID(2)           Linux Programmer's Manual           GETUID(2)
+

+
+
NAME
+
       getuid, geteuid - get user identity
+
+
SYNOPSIS
+
       #include <unistd.h>
+
+       uid_t getuid(void);
+       uid_t geteuid(void);
+
+
DESCRIPTION
+
       getuid returns the real user ID of the current process.
+
+       geteuid  returns the effective user ID of the current pro-
+       cess.
+
+       The real ID corresponds to the ID of the calling  process.
+       The effective ID corresponds to the set ID bit on the file
+       being executed.
+
+
ERRORS
+
       These functions are always successful.
+
+
CONFORMS TO
+
       POSIX, BSD 4.3
+
+
+
+

SEE ALSO +

+setreuid, +setuid, +

+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Linux 0.99.11              23 July 1993                         1
+

+
+
+

+

+

+

+ + + + +
+Top + +Master Index + +Keywords + +Functions +
+
+

+

+ +This manual page was brought to you by mjl_man V-2.0 -- cgit v1.2.3-54-g00ecf ext.git/commit/?h=packet-loop-back&id=ba63f23d69a3a10e7e527a02702023da68ef8a6d'>commitdiff
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2016-09-08 14:20:38 -0700
committerTheodore Ts'o <tytso@mit.edu>2016-09-10 01:18:57 -0400
commitba63f23d69a3a10e7e527a02702023da68ef8a6d (patch)
treeef70ece0179f4d642e0b0b4d5f6aa6cfed7c9e74
parent002ced4be6429918800ce3e41d5cbc2d7c01822c (diff)
fscrypto: require write access to mount to set encryption policy
Since setting an encryption policy requires writing metadata to the filesystem, it should be guarded by mnt_want_write/mnt_drop_write. Otherwise, a user could cause a write to a frozen or readonly filesystem. This was handled correctly by f2fs but not by ext4. Make fscrypt_process_policy() handle it rather than relying on the filesystem to get it right. Signed-off-by: Eric Biggers <ebiggers@google.com> Cc: stable@vger.kernel.org # 4.1+; check fs/{ext4,f2fs} Signed-off-by: Theodore Ts'o <tytso@mit.edu> Acked-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat