From: Daniel Phillips <phillips@arcor.de>
To: Luca Barbieri <ldb@ldb.ods.org>, trond.myklebust@fys.uio.no
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux FSdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Initial support for struct vfs_cred [0/1]
Date: Sun, 1 Sep 2002 17:15:30 +0200 [thread overview]
Message-ID: <E17lWRm-0004Zg-00@starship> (raw)
In-Reply-To: <1030835635.1422.39.camel@ldb>
On Sunday 01 September 2002 01:13, Luca Barbieri wrote:
> On Sun, 2002-09-01 at 00:30, Trond Myklebust wrote:
> > >>>>> " " == Luca Barbieri <ldb@ldb.ods.org> writes:
> >
> > > Then the rest of the code doesn't need to know at all that
> > > credentials are shared and is simpler and faster. We have
> > > however a larger penalty on credential change but, as you say,
> > > that's extremely rare (well, perhaps not necessarily extremely,
> > > but still rare).
> >
> > What if I, in a fit of madness/perversion, decide to use CLONE_CRED
> > between 2 kernel threads (i.e. no 'kernel entry')?
> You don't or you manually patch the task_struct of the other threads.
> This isn't a serious concern.
It is a serious concern. Inventing new, subtle behavior differences
between user and kernel threads is, in a word, gross. It's certain
to bite people in the future.
--
Daniel
next prev parent reply other threads:[~2002-09-01 15:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1030820234.4408.119.camel@ldb>
2002-08-31 19:36 ` [PATCH] Initial support for struct vfs_cred [0/1] Linus Torvalds
2002-08-31 19:38 ` Luca Barbieri
2002-08-31 22:30 ` Trond Myklebust
2002-08-31 23:13 ` Luca Barbieri
2002-09-01 13:03 ` Trond Myklebust
2002-09-01 14:10 ` Trond Myklebust
2002-09-01 14:20 ` Luca Barbieri
[not found] ` <1030890022.2145.52.camel@ldb>
2002-09-01 16:40 ` Trond Myklebust
[not found] ` <15730.17171.162970.367575@charged.uio.no>
2002-09-01 18:54 ` Luca Barbieri
2002-09-01 19:40 ` Trond Myklebust
[not found] ` <15730.27952.29723.552617@charged.uio.no>
2002-09-01 21:34 ` Luca Barbieri
[not found] ` <1030916061.2145.344.camel@ldb>
2002-09-01 21:56 ` Trond Myklebust
[not found] ` <15730.36080.987645.452664@charged.uio.no>
2002-09-01 22:50 ` Luca Barbieri
2002-09-01 14:33 ` Luca Barbieri
2002-09-01 16:38 ` Trond Myklebust
2002-09-01 18:42 ` Luca Barbieri
2002-09-01 19:25 ` Trond Myklebust
2002-09-01 21:36 ` Luca Barbieri
2002-09-01 15:15 ` Daniel Phillips [this message]
2002-09-01 15:35 ` Luca Barbieri
[not found] <15728.61345.184030.293634@charged.uio.no>
2002-08-31 18:57 ` Luca Barbieri
2002-08-31 19:51 ` Luca Barbieri
2002-08-31 16:32 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=E17lWRm-0004Zg-00@starship \
--to=phillips@arcor.de \
--cc=ldb@ldb.ods.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=trond.myklebust@fys.uio.no \
/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