From: Benjamin LaHaise <bcrl@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [patch] (resend) credentials for 2.5.23
Date: Wed, 19 Jun 2002 21:29:09 -0400 [thread overview]
Message-ID: <20020619212909.A3468@redhat.com> (raw)
This message didn't seem to get through the first time, so here it is
again. The patch is available for review at:
http://www.kvack.org/~blah/v2.5.23-cred.diff
Several parts of the kernel need to obtain a reference to the
credentials of a process: aio, nfs, dirty mmap writebacks to
name a few. Additionally, POSIX threads need to be able to share
credentials between clones. The patch below moves the credentials
out of task_struct and into struct cred, which is reference
counted. It also adds support for CLONE_CRED which shares the
credentials between threads. Comments?
-ben
--
"You will be reincarnated as a toad; and you will be much happier."
next reply other threads:[~2002-06-20 1:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 1:29 Benjamin LaHaise [this message]
2002-06-20 2:30 ` [patch] (resend) credentials for 2.5.23 Robert Love
2002-06-20 16:28 ` Benjamin LaHaise
2002-06-20 17:11 ` Robert Love
2002-06-21 11:12 ` Trond Myklebust
2002-06-21 18:52 ` Benjamin LaHaise
2002-06-21 19:17 ` Trond Myklebust
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=20020619212909.A3468@redhat.com \
--to=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.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