mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave McCracken <dmccr@us.ibm.com>
To: trond.myklebust@fys.uio.no
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 2.5.30+] Fourth attempt at a shared credentials patch
Date: Fri, 09 Aug 2002 14:24:09 -0500	[thread overview]
Message-ID: <55560000.1028921049@baldur.austin.ibm.com> (raw)
In-Reply-To: <15698.59577.788998.300262@charged.uio.no>


--On Thursday, August 08, 2002 11:55:05 PM +0200 Trond Myklebust
<trond.myklebust@fys.uio.no> wrote:

> What if one thread is doing an RPC call while the other is changing
> the 'groups' entry?

Gah.  Good point.  Ok, I've added locking to the cred structure to handle
this.  Here's my new patch with those changes made:

http://www.ibm.com/linux/ltc/patches/misc/cred-2.5.30-5.diff.gz

I've gone through all the code again, and don't see any other places where
locking is really necessary.  Feel free to point them out to me if you see
any.

Dave McCracken

======================================================================
Dave McCracken          IBM Linux Base Kernel Team      1-512-838-3059
dmccr@us.ibm.com                                        T/L   678-3059


  reply	other threads:[~2002-08-09 19:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 14:58 [PATCH 2.5.30+] Second " 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
2002-08-09 19:24               ` Dave McCracken [this message]
2002-08-09 19:51                 ` [PATCH 2.5.30+] Fourth " 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=55560000.1028921049@baldur.austin.ibm.com \
    --to=dmccr@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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
all inboxes | Powered by JetHome®