From: David Howells <dhowells@redhat.com>
To: torvalds@osdl.org, akpm@osdl.org, kwc@citi.umich.edu
Cc: linux-kernel@vger.kernel.org, nfsv4@linux-nfs.org
Subject: [PATCH] Keys: Doc update for properly sharing process keyrings patch
Date: Fri, 25 Feb 2005 14:05:34 +0000 [thread overview]
Message-ID: <26049.1109340334@redhat.com> (raw)
In-Reply-To: <25723.1109339172@redhat.com>
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 <dhowells@redhat.com>
---
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
next prev parent reply other threads:[~2005-02-25 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 13:46 [PATCH] Properly share process and session keyrings with CLONE_THREAD David Howells
2005-02-25 14:05 ` David Howells [this message]
2005-02-25 19:57 ` Linus Torvalds
2005-02-26 13:07 ` David Howells
2005-02-26 17:58 ` Linus Torvalds
2005-03-01 16:04 ` [PATCH] Properly share process and session keyrings with CLONE_THREAD [try #2] David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26049.1109340334@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=kwc@citi.umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox