mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mark Peloquin" <peloquin@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EVMS core (3/9) discover.c
Date: Thu, 10 Oct 2002 17:53:55 -0500	[thread overview]
Message-ID: <OFF9323A4C.87C7BFD1-ON85256C4E.007AF27F@pok.ibm.com> (raw)


On 10/10/2002 at 05:19 PM, Andi Kleen wrote:

> > We plan to register a "__this_module.can_unload()" that
> > should prevent plugin modules from unloading during
> > discovery.

> Ok in this case. But how about when you search that list later after
> discovery for some reason and drop the lock. Then you could race with
someone
> else removing the plugin inbetween, no ?

The only time the lock is released while actively
searching the list is during discovery and direct
ioctl communication. So yes, you are correct, the
can_unload() would have to take both operations
into account. All other list operations take
place completely inside the lock. All in-use
plugins are kept from unloading by module ref
counts. Outside of the scope of the discover and
direct ioctl operations, any unused plugins
should be safe to unload.

Is something being missed?

Mark



             reply	other threads:[~2002-10-10 22:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 22:53 Mark Peloquin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-10 22:05 Mark Peloquin
2002-10-10 22:19 ` Andi Kleen
     [not found] <02101014305502.17770@boiler.suse.lists.linux.kernel>
     [not found] ` <02101014352905.17770@boiler.suse.lists.linux.kernel>
2002-10-10 20:48   ` Andi Kleen
2002-10-10 21:15     ` Kevin Corry
2002-10-10 19:30 [PATCH] EVMS core (0/9) Kevin Corry
2002-10-10 19:35 ` [PATCH] EVMS core (3/9) discover.c Kevin Corry

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=OFF9323A4C.87C7BFD1-ON85256C4E.007AF27F@pok.ibm.com \
    --to=peloquin@us.ibm.com \
    --cc=ak@suse.de \
    --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®