public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "David S. Miller" <davem@redhat.com>
Cc: trond.myklebust@fys.uio.no, torvalds@transmeta.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove useless MOD_{INC,DEC}_USE_COUNT from sunrpc
Date: Mon, 5 May 2003 10:29:41 +0200	[thread overview]
Message-ID: <20030505102940.A16955@lst.de> (raw)
In-Reply-To: <20030504.131558.27788112.davem@redhat.com>; from davem@redhat.com on Sun, May 04, 2003 at 01:15:58PM -0700

On Sun, May 04, 2003 at 01:15:58PM -0700, David S. Miller wrote:
>    From: Christoph Hellwig <hch@lst.de>
>    Date: Sun, 4 May 2003 23:00:11 +0200
>    
>    Oh well, what about something like the following?
>  ...   
>    +	 */
>    +	if (!try_module_get(THIS_MODULE))
>    +		return -EBUSY;
> 
> Ahem... Why don't we just do this right? :-)
> 
> By this I mean provide some real registry thing in the
> main kernel image that we can use to do try_module_get()
> outside of the sunrpc module?

Please read the comment above that piece of code.  We always
enter this through an exported function so we know we currently
aren't unloadable.

> The other option is the make more progress in the area of
> two-stage module unload, and allowing cleanup() to return
> whether the module is unloadable or not.  This is being
> discussed on netdev so that we have some way to make ipv6
> modules work sanely (instead of putting try_module_get() in
> every other line, that simply isn't acceptable).

That's fine with me, but I won't sign up to do that work :)


      reply	other threads:[~2003-05-05  8:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04 17:14 [PATCH] remove useless MOD_{INC,DEC}_USE_COUNT from sunrpc Christoph Hellwig
2003-05-04 17:37 ` Trond Myklebust
2003-05-04 18:36   ` Christoph Hellwig
2003-05-04 18:46     ` Trond Myklebust
2003-05-04 18:53       ` Christoph Hellwig
2003-05-04 19:00         ` Trond Myklebust
2003-05-04 19:06           ` David S. Miller
2003-05-04 19:56             ` Trond Myklebust
2003-05-04 20:14               ` Trond Myklebust
2003-05-04 21:00             ` Christoph Hellwig
2003-05-04 20:15               ` David S. Miller
2003-05-05  8:29                 ` Christoph Hellwig [this message]

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=20030505102940.A16955@lst.de \
    --to=hch@lst.de \
    --cc=davem@redhat.com \
    --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