From: David Howells <dhowells@redhat.com>
To: torvalds@osdl.org, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: Splitting task-group stuff from task_struct
Date: Wed, 18 Aug 2004 21:18:44 +0100 [thread overview]
Message-ID: <28551.1092860324@redhat.com> (raw)
Hi Linus, Andrew,
Would you have any objection to task-group specific stuff being split from the
task_struct and placed into a refcounted structure of its own and shared upon
CLONE_THREAD.
The fields I'm thinking of include:
struct linux_binfmt *binfmt
unsigned long personality
pid_t tgid
struct task_struct *group_leader
u32 parent_exec_id;
u32 self_exec_id;
Should process credentials be shared?
I could then add the process/session keyring pointers from my patch to it too.
David
reply other threads:[~2004-08-18 20:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=28551.1092860324@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome