The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] new module format
Date: Thu, 18 Jul 2002 14:13:35 +0200	[thread overview]
Message-ID: <E17VAA4-0004o6-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.44.0207181350020.8911-100000@serv>

On Thursday 18 July 2002 14:02, Roman Zippel wrote:
> Hi,
> 
> On Thu, 18 Jul 2002, Daniel Phillips wrote:
> 
> > To add a new user, the active bit has to be set, as shown in this skeleton,
> > which is pretty much the existing try_inc_mod_count scheme:
> >
> >        spin_lock(&some_spinlock);
> >        if (<mod_active_bit>)
> >                <inc_mod_user_count>
> >        spin_unlock(&some_spinlock);
> >
> >        if <users>, do the mount
> >
> > In other words, the module has some state, the transitions of which are
> > protected by a spinlock.
> 
> This means you still need another lock to protect the data structures and
> you still have module pointers everywhere.

A module pointer per filesystem does not count as 'everywhere'.

> I want to get rid of that
> "same_spinlock" (aka unload_lock), because it's not needed.
> I suggest we continue this discussion when I post the new patches in a few
> days, then it should become more clear.

Sure.

-- 
Daniel

  reply	other threads:[~2002-07-18 12:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16 13:04 [RFC] new module format Roman Zippel
2002-07-17 18:54 ` Daniel Phillips
2002-07-17 20:12   ` Roman Zippel
2002-07-17 20:34     ` Daniel Phillips
2002-07-17 22:45       ` Roman Zippel
2002-07-17 23:47         ` Daniel Phillips
2002-07-18 10:01           ` Roman Zippel
2002-07-18 11:09             ` Daniel Phillips
2002-07-18 12:02               ` Roman Zippel
2002-07-18 12:13                 ` Daniel Phillips [this message]
2002-07-19  8:42 ` Rusty Russell
2002-07-19  9:31   ` Roman Zippel
2002-07-20  4:13     ` Rusty Russell

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=E17VAA4-0004o6-00@starship \
    --to=phillips@arcor.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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