From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: trond.myklebust@fys.uio.no, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.5.30+] Second attempt at a shared credentials patch
Date: Thu, 8 Aug 2002 23:55:05 +0200 [thread overview]
Message-ID: <15698.59577.788998.300262@charged.uio.no> (raw)
In-Reply-To: <81390000.1028837464@baldur.austin.ibm.com>
>>>>> " " == Dave McCracken <dmccr@us.ibm.com> writes:
> --On Thursday, August 08, 2002 09:56:23 PM +0200 Trond
> Myklebust <trond.myklebust@fys.uio.no> wrote:
>> ... which begs the question: are you saying that there are no
>> SMP issues with CLONE_CRED and setting/reading the 'struct
>> cred' members?
> Yes, I'm saying there are no SMP issues with the shared cred
> structure. I looked for them and failed to find any.
> Credentials are not set cross-task, and are always done via
> atomic ops. I also failed to find any broader race conditions
> that would require a lock.
What if one thread is doing an RPC call while the other is changing
the 'groups' entry?
Given that the first thread wants both to copy and/or compare the
groups entry what prevents scenarios of the form?
Thread 1 Thread 2
change cred->ngroups
copy cred->ngroups
copy cred->groups
change cred->groups
Cheers,
Trond
next prev parent reply other threads:[~2002-08-08 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 14:58 Dave McCracken
2002-08-08 15:32 ` Trond Myklebust
2002-08-08 16:20 ` Dave McCracken
2002-08-08 16:54 ` Trond Myklebust
2002-08-08 18:05 ` Dave McCracken
2002-08-08 19:56 ` Trond Myklebust
2002-08-08 20:11 ` Dave McCracken
2002-08-08 21:55 ` Trond Myklebust [this message]
2002-08-09 19:24 ` [PATCH 2.5.30+] Fourth " Dave McCracken
2002-08-09 19:51 ` Trond Myklebust
2002-08-09 20:51 ` Dave McCracken
2002-08-12 20:08 ` Trond Myklebust
2002-08-09 21:15 ` Linus Torvalds
2002-08-08 20:11 ` [PATCH 2.5.30+] Second " 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=15698.59577.788998.300262@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=dmccr@us.ibm.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
all inboxes | Powered by JetHome®