The attached patch updates the documentation on the kernel keys to reflect the
fact that process keyrings will no longer change ownership when the UID and
GID of a thread change; process's don't have UIDs and GIDs in Linux, only
threads do.
This patch is contingent on the keyring sharing patch submitted a few minutes
ago.
Signed-Off-By: David Howells <[EMAIL PROTECTED]>
---
warthog>diffstat -p1 keys-task-doc-2611rc4.diff
Documentation/keys.txt | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -uNr linux-2.6.11-rc4/Documentation/keys.txt
linux-2.6.11-rc4-keys-task/Documentation/keys.txt
--- linux-2.6.11-rc4/Documentation/keys.txt 2005-01-04 11:12:42.000000000
+0000
+++ linux-2.6.11-rc4-keys-task/Documentation/keys.txt 2005-02-25
13:48:17.387035408 +0000
@@ -151,8 +151,8 @@
by using PR_JOIN_SESSION_KEYRING. It is permitted to request an anonymous
new one, or to attempt to create or join one of a specific name.
- The ownership of the thread and process-specific keyrings changes when
- the real UID and GID of the thread changes.
+ The ownership of the thread keyring changes when the real UID and GID of
+ the thread changes.
(*) Each user ID resident in the system holds two special keyrings: a user
specific keyring and a default user session keyring. The default session
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
